emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Chun <eyc8@yahoo.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: search in org-sparse-tree for multiple files
Date: Sun, 1 Jan 2023 18:44:09 +0000 (UTC)	[thread overview]
Message-ID: <1141450532.3462549.1672598649607@mail.yahoo.com> (raw)
In-Reply-To: <87sfgu75fv.fsf@localhost>

[-- Attachment #1: Type: text/plain, Size: 1642 bytes --]

 I think I found a solution but here are the steps in case others have the same problem:
* First, I open an org file in Emacs.* I then create a sparse tree using a regular expression.* I then type M-g M-n to move to the next occurrence of my search string but it doesn't work.  I get a message saying "user-error: Moved past last grep hit".
* I kill the pre-existing "*grep*" buffer in Emacs.
* I then try M-g M-n again and it works.

Writing out these steps got me thinking that there might be an option in compilation mode to switch buffers when finding next error.  I looked in the compilation mode section of the Emacs manual and found next-error-select-buffer that switches buffers when searching for errors.  I also just realized that you mentioned next-error-find-buffer-function configuration variable in an earlier post.  I'll try that as well.
You can consider my question answered.  Thanks for the help.
    On Sunday, January 1, 2023 at 06:24:39 AM MST, Ihor Radchenko <yantar92@posteo.net> wrote:  
 
 Eric Chun <eyc8@yahoo.com> writes:

> I'm assuming "current buffer" is the buffer which I can currently type input into.  The current buffer is not finding next occurrence of search string by pressing M-g M-n.  Is this expected?

Could you please elaborate?
What exactly you did and what do you expect to happen?
(see https://orgmode.org/manual/Feedback.html#Feedback)

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
  

[-- Attachment #2: Type: text/html, Size: 3590 bytes --]

      reply	other threads:[~2023-01-01 18:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1277881757.3298435.1672461584764.ref@mail.yahoo.com>
2022-12-31  4:39 ` search in org-sparse-tree for multiple files Eric Chun
2022-12-31 13:38   ` Ihor Radchenko
2022-12-31 15:29     ` Eric Chun
2023-01-01 13:25       ` Ihor Radchenko
2023-01-01 18:44         ` Eric Chun [this message]

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

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=1141450532.3462549.1672598649607@mail.yahoo.com \
    --to=eyc8@yahoo.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).