Re: ioccur, incremental occur

[Thierry Volpiatto]

Hi Leo,

Leo <address@hidden> writes:

> On 2010-03-31 17:36 +0100, Thierry Volpiatto wrote:
>> Do you mean it is slow? (sluggish) sorry for my english.
>>
>>>       Processor Name: Intel Core 2 Duo
>>>       Processor Speed: 2 GHz
>>>       Number Of Processors: 1
>>>       Total Number Of Cores: 2
>>>       L2 Cache: 3 MB
>>>       Memory: 4 GB
>>>       Bus Speed: 1.07 GHz
>>
>> My laptop is by far not so good, Dell 1.8Ghz and 2Gb of Memory, and ioccur is
>> very reactive even on reasonable large buffer (files of 1.2 to 1.5 Mo).
>> I use it also on other machine (old Amd64) with no problem of performance.
>> I also tried it in virtual machine with windowsXP and it work fine also.
>> 
>>> I can literally see key sequences flash across the minibuffer when
>>> BACKSPC. This is tested in Emacs 23.1.94 and ioccur is compiled.
>> What is your OS?
>> Do you use Emacs in X or on terminal (xterm etc..)?
>>
>> What key sequences do you see in minibuffer?
>>
>>
>> I think it is may be not a problem of performance but a problem of key
>> compatibility with your system.
>> Actually, backspace is bound to ?\d.
>>
>> Can you do some test on ioccur.el itself and tell me what you see if for
>> example you enter:
>>
>> d e f u n backspace backspace v a r
>>
>> Also if from scratch buffer, you eval :
>> (read-key)
>> and press backspace, what do you see in minibuffer?
>> You should have 127.
>
> Sorry I should have tried running emacs on terminal before posting this.
> In fact when I run Emacs in terminal I don't see the problem mentioned
> in previous post.
>
> I am on OSX 10.6.3 and when running ioccur with Emacs with GUI, I can
> see keys flash in the minibuffer. For example, If i type d e f u n and
> then C-n, I can see C-n briefly show up in the minibuffer and then
> disappear. Does this happen to you? Let me know and if need be I will
> email YAMAMOTO Mitsuharu since it might be a problem specific to
> mac-port.
That can happen, but that is a problem with `read-key',not specific to
ioccur.
Here on Gentoo, sometime i can see the key flashing, but it is so fast
that it is not annoying (1ms about).But mostly no i see nothing.

> I am using GNU Emacs 23.1.94.1 (x86_64-apple-darwin10.2.0, Carbon
> Version 1.6.0 AppKit 1038.25). See this:
> http://permalink.gmane.org/gmane.emacs.devel/121879.
>
> * user interface
>
> 1. I think the cursor should be in the minibuffer not in the ioccur
> buffer. There's no use putting the cursor in the ioccur buffer unlike
> the isearch feature. C-y should work.

There is no use of minibuffer mechanism in ioccur, the prompt you see is
the prompt of `read-key', and when you enter characters, what you see is
always the prompt.
e.g
Here the prompt when you start ioccur:
Pattern: 
Then you enter d e f u n
Now the prompt is just (concat "Pattern: " "defun")

C-y work, it is implemented in ioccur.

> 2. M-n/M-p to bring up history searches.
M-n/M-p work only in X, not in terminals where you have to use tab and
S-tab.
Is it working with Mac on Osx?

> 3. the *iccour* buffer should be kept.
>
>    The reason to use occur or ioccur other than C-s is to have an
>    overview of entries that the user wants to look at for example during
>    bug fixing one might want to look at all places a function has been
>    used. So the *ioccur* buffer should be there for them to navigate to
>    entries easily without doing the search again.
Of course it is important to keep ioccur buffer.

You can keep the ioccur buffer, no problem, just hit RET when your
search is finish, and you will have an ioccur buffer with no more
incremental searching.

If you are fan of w3m (like me), you can use arrow keys:
left to goto-line in your buffer and destroy ioccur buffer,
right to goto-line persistent without quitting incremental search.

Do C-h f ioccur:

,----[ C-h f ioccur RET ]
| ioccur is an interactive compiled Lisp function in `ioccur.el'.
| 
| It is bound to C-c o.
| 
| (ioccur &optional INITIAL-INPUT)
| 
| Incremental search of lines in current buffer matching input.
| With a prefix arg search symbol at point (INITIAL-INPUT).
| 
| While you are incremental searching, commands provided are:
| 
| C-n or <down>  next line.
| C-p or <up>    precedent line.
| C-v and M-v    scroll up and down.
| C-z or <right> jump without quitting loop.
| C-j or <left>  jump and exit search buffer.
| RET            exit but don't quit search buffer.
| DEL            remove last character entered.
| C-k            Kill current input.
| C-w            Yank stuff at point.
| C-g            quit and restore buffer.
| C-down         Follow in other buffer.
| C-up           Follow in other buffer.
| M-p/n          Precedent and next `ioccur-history' element:
| 
| M-p ,-->A B C D E F G H I---,
|     |                       |
|     `---I H G F E D C B A<--'
| 
| M-n ,-->I H G F E D C B A---,
|     |                       |
|     `---A B C D E F G H I<--'
| 
| Special NOTE for terms:
| =======================
|   tab/S-tab are bound to history.
|   C-d/u are for following in other buffer.
|   Use C-t to Scroll up.
|  
| When you quit incremental search with RET, see `ioccur-mode'
| for commands provided in the search buffer.
| 
| ===*===*===*===*===*===*===*===*===*===*===
`----

And tell me if some keys are not working on OSX.
It would be great ioccur work well on OSX.

Thank you for helping for ioccur. ;-)

-- 
Thierry Volpiatto
Gpg key: http://pgp.mit.edu/