From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 9432@debbugs.gnu.org
Subject: bug#9432: 24.0.50; doc string of `next-error-highlight'
Date: Thu, 28 Apr 2016 13:20:16 +0200 [thread overview]
Message-ID: <87fuu6nfnz.fsf@gnus.org> (raw)
In-Reply-To: <jwvmxeev4r8.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 08 Sep 2011 22:17:43 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Yes, this use-case is rare, but there are other use-cases where
>> something more than `display-buffer-reuse-frames' is necessary
>> like described in http://lists.gnu.org/archive/html/emacs-devel/2011-08/msg00267.html
>
> I don't see how that goes against changing the default of
> display-buffer-reuse-frames.
The doc string of this variable is included below.
Has whatever this bug report is talking about been fixed now?
----
display-buffer-reuse-frames is a variable defined in ‘window.el’.
Its value is nil
This variable is obsolete since 24.3;
use a `reusable-frames' alist entry in `display-buffer-alist'.
Documentation:
Non-nil means ‘display-buffer’ should reuse frames.
If the buffer in question is already displayed in a frame, raise
that frame.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-28 11:20 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
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 [this message]
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
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=87fuu6nfnz.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=9432@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.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).