From: MON KEY <monkey@sandpframing.com>
To: emacs-devel@gnu.org
Cc: martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>,
Andreas Schwab <schwab@linux-m68k.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: display-buffer-reuse-frames default to t
Date: Wed, 19 Jan 2011 13:48:26 -0500 [thread overview]
Message-ID: <AANLkTimZhMVvfBYKsWAX1Pf8GUyHMGkFZPSX8yP-g+Z1@mail.gmail.com> (raw)
>>> Any objection to defaulting display-buffer-reuse-framesto t?
>>
>> Does it restrict itself to visible frames?
>
> No. It can use iconified frames.
>
> Ideally, one would set this to 0, 'visible, or t and get the desired
> effect. That's what I do on my branch.
Is the suggestion to extend the range of acceptable values for
`display-buffer-reuse-frames'?
IMHO there is opportunity here for some much needed changes[1].
Indeed, it would make more sense to extend the range of values allowed
to any one of: { t nil 0 visible }
I would also suggest adding `selected-frame' as an option for
consistency with `display-buffer's provision for a "specific frame" as
argument to its FRAME parameter.
Such change would require changing the custom type declaration of
`display-buffer-reuse-frames' from:
:type 'boolean ;; Is the declaration even correct now?
Likewise, if such change(s) are made _please_ ensure that the
variable's docstring indicate explicitly the range of possible values
and their affect on frame/buffer display, i.e. don't just punt to
`display-buffer' with a "which see".
Maybe, better is to implement an additional/alternative variable:
`display-buffer-reuse-frames-if-graphic'
which inherits its defaults according to `display-buffer-reuse-frames'
and `pop-up-frames'?
As it is now, the current docstring of `display-buffer-reuse-frames'
is poorly specified wrt to the interaction of `display-buffer' around
`pop-up-frames' and `display-graphic-p'. Likely many users are
left with an essentially opaque customization option which often fails
to DTRT esp. where third-party authors using `display-buffer' in an
ill adapted position to appropriately accomodate user display
customizations, cf the recent report bug 7728:
(URL `http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7728')
and discussion of `save-window-excursion' beginning around msg 68:
(URL `http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7728#68')
[1] I use a two-head display with xrandr (and in the past with the
equivalent on w32 a three-head display) and rarely have less than two
frames open across these displays In both environments the behaviour
of `display-buffer-reuse-frames'/`display-buffer' has many weird/odd
corner cases wrt to the "strongly dedicated" and often commands do not
do what I would expect. The cummulative effect of these corner cases
is that I usually give up trying to figure out where/why/how certain
buffers/windows/frames will be displayed and just adapt to the funky.
--
/s_P\
next reply other threads:[~2011-01-19 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 18:48 MON KEY [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-19 16:04 display-buffer-reuse-frames default to t Stefan Monnier
2011-01-19 16:11 ` Eli Zaretskii
2011-01-19 21:00 ` Stefan Monnier
2011-01-19 16:25 ` Andreas Schwab
2011-01-19 16:44 ` martin rudalics
2011-01-19 20:59 ` Stefan Monnier
2011-01-19 19:15 ` Tassilo Horn
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=AANLkTimZhMVvfBYKsWAX1Pf8GUyHMGkFZPSX8yP-g+Z1@mail.gmail.com \
--to=monkey@sandpframing.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rudalics@gmx.at \
--cc=schwab@linux-m68k.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 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).