emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Eric Chun <eyc8@yahoo.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: search in org-sparse-tree for multiple files
Date: Sat, 31 Dec 2022 13:38:28 +0000	[thread overview]
Message-ID: <87edsfae23.fsf@localhost> (raw)
In-Reply-To: <1277881757.3298435.1672461584764@mail.yahoo.com>

Eric Chun <eyc8@yahoo.com> writes:

> I can't seem to use the M-g M-n keys to jump to occurrences in sparse tree search for second org file within same Emacs window.
> If I search first file by pressing C-c / r <regex> RET and then search second file by pressing C-c / r <regex> RET, I'm not able to jump to occurrences in that second file by pressing M-g M-n.  I get a message saying "No more matches" even though there are matches.  If I close the first file buffer, then I am able to use M-g M-n to jump to occurrences in the second file.
> Does anybody know what I may be missing?
> I'm using org mode version 9.6 in Emacs 28.2 on CentOS7.

`org-occur-next-match' does not support multiple buffers.
Looking at the docstring of `next-error-function', I am also not sure if
we need to support this there. The docstring talks only about the
current buffer.

What might be relevant is `next-error-find-buffer-function' - a user
customization you may want to set.

Generally, it is unclear for me how to implement multiple buffers
support for org-spare-tree. Ideas and patches welcome.

-- 
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>


  reply	other threads:[~2022-12-31 13:39 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 [this message]
2022-12-31 15:29     ` Eric Chun
2023-01-01 13:25       ` Ihor Radchenko
2023-01-01 18:44         ` Eric Chun

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=87edsfae23.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=eyc8@yahoo.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 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).