Navigating sparse tree results

Navigating sparse tree results

[suvayu ali]

Hi,

Is there any way to move to the next match after a sparse tree
command. Say I search for a regexp with the sparse tree command, how do
I to move to the next highlighted match? I was hoping something like
`next-error' or `C-s' for isearch[fn:1].

Footnotes:

[fn:1] I know all this does is search for the string again, maybe sparse
tree could provide a convenient binding immediately after the search to
jump to the next match?

-- 
Suvayu

Open source is the future. It sets us free.

Re: Navigating sparse tree results

[Sébastien Vauban]

Hi suvayu,

suvayu ali wrote:
> Is there any way to move to the next match after a sparse tree
> command. Say I search for a regexp with the sparse tree command, how do
> I to move to the next highlighted match? I was hoping something like
> `next-error' or `C-s' for isearch[fn:1].

I find the idea of =next-error= to be a great one. What I currently do, is
just =C-v= (some sort of Page Down) and look at the highlighted words. But, it
is still quite easy to miss one for long blocks of text under the headlines.

Best regards,
  Seb

-- 
Sébastien Vauban


_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: Navigating sparse tree results

[Carsten Dominik]

On Jan 5, 2011, at 1:38 AM, suvayu ali wrote:

> Hi,
>
> Is there any way to move to the next match after a sparse tree
> command. Say I search for a regexp with the sparse tree command, how  
> do
> I to move to the next highlighted match? I was hoping something like
> `next-error' or `C-s' for isearch[fn:1].


This is a great idea.  next-error and previous-error do now
work on sparse tree results.  In a standard Emacs, these
commands are bound to

M-g n
M-g M-n
M-g p
M-g M-p

- Carsten

Re: Navigating sparse tree results

[suvayu ali]

Hi Carsten and Seb,

On Thu, Jan 6, 2011 at 3:37 AM, Carsten Dominik
<carsten.dominik@gmail.com> wrote:
>
> On Jan 5, 2011, at 1:38 AM, suvayu ali wrote:
>
>> Hi,
>>
>> Is there any way to move to the next match after a sparse tree
>> command. Say I search for a regexp with the sparse tree command, how do
>> I to move to the next highlighted match? I was hoping something like
>> `next-error' or `C-s' for isearch[fn:1].
>
>
> This is a great idea.  next-error and previous-error do now
> work on sparse tree results.  In a standard Emacs, these
> commands are bound to
>
> M-g n
> M-g M-n
> M-g p
> M-g M-p
>

I was actually trying my hand on it after Seb's encouraging words but
you got to it faster. Thanks a lot! :)

-- 
Suvayu

Open source is the future. It sets us free.

Re: Navigating sparse tree results

[Carsten Dominik]

On Jan 6, 2011, at 5:14 PM, suvayu ali wrote:

> Hi Carsten and Seb,
>
> On Thu, Jan 6, 2011 at 3:37 AM, Carsten Dominik
> <carsten.dominik@gmail.com> wrote:
>>
>> On Jan 5, 2011, at 1:38 AM, suvayu ali wrote:
>>
>>> Hi,
>>>
>>> Is there any way to move to the next match after a sparse tree
>>> command. Say I search for a regexp with the sparse tree command,  
>>> how do
>>> I to move to the next highlighted match? I was hoping something like
>>> `next-error' or `C-s' for isearch[fn:1].
>>
>>
>> This is a great idea.  next-error and previous-error do now
>> work on sparse tree results.  In a standard Emacs, these
>> commands are bound to
>>
>> M-g n
>> M-g M-n
>> M-g p
>> M-g M-p
>>
>
> I was actually trying my hand on it after Seb's encouraging words

my apologies.  I hope you had not spent too much time.

- Carsten

> but you got to it faster. Thanks a lot! :)
>
> -- 
> Suvayu
>
> Open source is the future. It sets us free.

Re: Navigating sparse tree results

[suvayu ali]

On Thu, Jan 6, 2011 at 1:02 PM, Carsten Dominik
<carsten.dominik@gmail.com> wrote:
>>
>> I was actually trying my hand on it after Seb's encouraging words
>
> my apologies.  I hope you had not spent too much time.

No need for apologies, just an evening. :) I am still very novice at
lisp, hope to become better so that I can contribute. :)

-- 
Suvayu

Open source is the future. It sets us free.