From: Eric Chun via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Compilation mode next error isn't searching all buffers
Date: Sun, 1 Jan 2023 19:30:33 +0000 (UTC) [thread overview]
Message-ID: <1175902378.3467541.1672601433900@mail.yahoo.com> (raw)
In-Reply-To: 1175902378.3467541.1672601433900.ref@mail.yahoo.com
I see the following at Compilation Mode (GNU Emacs Manual):"If the current buffer contains error messages or matches, these commands will iterate through them; otherwise, Emacs looks for a buffer containing error messages or matches amongst the windows of the selected frame (if the variable next-error-find-buffer-function is customized to the value next-error-buffer-on-selected-frame), then for a buffer used previously by next-error or previous-error, and finally all other buffers."
This seems to indicate that next-error function should switch to other buffers if there are no other errors in current buffer, but that doesn't seem to happen.
Here are the steps I followed:* 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.
Why doesn't next-error function jump to the next occurrence of search string found in current buffer? It seems to still be looking for occurrences in the grep buffer.
I'm using Emacs 28.2 on CentOS7.
parent reply other threads:[~2023-01-01 19:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1175902378.3467541.1672601433900.ref@mail.yahoo.com>]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1175902378.3467541.1672601433900@mail.yahoo.com \
--to=help-gnu-emacs@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.
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).