From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 9432@debbugs.gnu.org
Subject: bug#9432: 24.0.50; doc string of `next-error-highlight'
Date: Wed, 7 Sep 2011 07:05:23 -0700 [thread overview]
Message-ID: <2BF83CABDAD949B19F7A752CDB1B43F3@us.oracle.com> (raw)
In-Reply-To: <87aaahsa0i.fsf@mail.jurta.org>
> Permanent highlighting for `next-error-highlight' is a new feature,
> so it should be postponed to 24.2.
Sure, great. But please do not call it "permanent" in the doc.
There would be several times/actions that removed such highlighting; that's all:
next command, next locus change, explicit user command (e.g. `C-0 C-x `').
> > The already displayed source buffer should obviously be
> > used, instead of multiplying things unnecessarily. Or the
> > behavior should be optional, under user control, and the
> > default should be to show hits in a window already
> > displaying the source buffer.
>
> This should be customizable with `display-buffer-alist'.
sm> It's optional, controlled by display-buffer-reuse-frames.
sm> The default is nil, largely for historical reasons.
Users should not have to customize anything to get unbugged behavior using emacs
-Q. If the source file is already showing, why pop it up again in a new window,
by _default_?
next prev parent reply other threads:[~2011-09-07 14:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 1:16 bug#9432: 24.0.50; doc string of `next-error-highlight' Drew Adams
2011-09-05 8:45 ` Juri Linkov
2011-09-05 13:55 ` Drew Adams
2011-09-06 9:42 ` Juri Linkov
2011-09-06 13:47 ` Drew Adams
2011-09-07 11:48 ` Juri Linkov
2011-09-07 14:05 ` Drew Adams [this message]
2011-09-07 23:52 ` Juri Linkov
2011-09-08 1:42 ` Stefan Monnier
2011-09-08 13:17 ` Drew Adams
2011-09-08 20:09 ` Juri Linkov
2011-09-09 2:17 ` Stefan Monnier
2016-04-28 11:20 ` Lars Ingebrigtsen
2011-09-08 13:15 ` Drew Adams
2011-09-07 13:34 ` Stefan Monnier
2019-06-13 11:26 ` Stefan Kangas
2019-06-13 12:44 ` Eli Zaretskii
2019-06-13 13:07 ` Stefan Kangas
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=2BF83CABDAD949B19F7A752CDB1B43F3@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9432@debbugs.gnu.org \
--cc=juri@jurta.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.
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.