From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: next-error question
Date: Sat, 16 Nov 2019 18:35:52 +0200 [thread overview]
Message-ID: <835zjj7p93.fsf@gnu.org> (raw)
In-Reply-To: <CAJnXXoiayq59sehJEe0LfQqMf0Qj_Kmiqmj5PmXdh90M2p2J-A@mail.gmail.com> (message from John Yates on Sat, 16 Nov 2019 11:02:52 -0500)
> From: John Yates <john@yates-sheets.org>
> Date: Sat, 16 Nov 2019 11:02:52 -0500
>
> I have a large monitor so even with one window showing the *compilation*
> buffer I often have multiple relevant files visible.
> When next-error visits a file it always does so in the "other-window" even
> when that file is already visible elsewhere on the frame.
> Is it possible to suppress this "other-window" behavior?
What version of Emacs is that? Looking at compilation-goto-locus on
the current master branch and in Emacs 26.3, it sounds like the
behavior you want should already be the default. Maybe submit a bug
report with more details?
prev parent reply other threads:[~2019-11-16 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 16:02 next-error question John Yates
2019-11-16 16:35 ` Eli Zaretskii [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.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=835zjj7p93.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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).