all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: suvayu ali <fatkasuvayu+linux@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Navigating sparse tree results
Date: Thu, 6 Jan 2011 22:02:59 +0100	[thread overview]
Message-ID: <C2CE19FE-EF03-4E81-81C5-B2E0583A744B@gmail.com> (raw)
In-Reply-To: <AANLkTin37qq=+LXEc1bKFwXSqdPkOmhfFRqhsri0r4-Q@mail.gmail.com>


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.

  reply	other threads:[~2011-01-06 21:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05  0:38 Navigating sparse tree results suvayu ali
2011-01-05  8:35 ` Sébastien Vauban
2011-01-06 11:37 ` Carsten Dominik
2011-01-06 16:14   ` suvayu ali
2011-01-06 21:02     ` Carsten Dominik [this message]
2011-01-06 21:06       ` suvayu ali

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C2CE19FE-EF03-4E81-81C5-B2E0583A744B@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fatkasuvayu+linux@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.