From: martin rudalics <rudalics@gmx.at>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 6204@debbugs.gnu.org
Subject: bug#6204: vc-dir always splits the frame
Date: Thu, 20 May 2010 19:37:47 +0200 [thread overview]
Message-ID: <4BF5736B.1030605@gmx.at> (raw)
In-Reply-To: <jwvy6fezefm.fsf-monnier+emacs@gnu.org>
>>> Now after let-binding `pop-up-windows' to nil around the `pop-to-buffer'
>>> call, what if someone might want to restore the old behavior.
>
> Indeed. A good way would be to provide a way to override pop-up-windows
> (both nil and t) in special-display-regexps. We already have
> (same-window . t), so we only need to add the other half.
In Juri's `switch-to-buffer-other-window' case such options would be
useless anyway.
>> The intended use is that an application calling `display-buffer'
>> or `pop-to-buffer' could bind this as
>
>> (let ((pop-up-windows
>> (if (eq pop-up-windows t)
>> application-dependent-value
>> pop-up-windows)))
>
>> that is, the default value can be overridden by the application,
>> user customizations are respected.
>
> But maybe the user would like to follow the application's special
> handling, even tho she modified her pop-up-windows for other reasons.
> I think it's much better to use 2 separate variables, where the
> user-controlled var is never modified by Elisp code.
Applications that do care enough should either (1) use `split-window'
and `set-window-buffer' or (2) provide a separate customizable option
like `foo-pop-up-windows' and let the user decide whether this should
pop up a new window and where.
martin
next prev parent reply other threads:[~2010-05-20 17:37 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 5:06 bug#6204: vc-dir always splits the frame Glenn Morris
2010-05-17 7:27 ` Dan Nicolaescu
2010-05-19 3:01 ` Glenn Morris
2010-05-19 21:31 ` Juri Linkov
2010-05-20 9:45 ` martin rudalics
2010-05-20 17:14 ` Stefan Monnier
2010-05-20 17:37 ` martin rudalics [this message]
2010-05-21 20:15 ` Stefan Monnier
2010-05-22 8:50 ` martin rudalics
2010-05-22 23:51 ` Juri Linkov
2010-05-23 0:55 ` Stefan Monnier
2010-05-23 0:59 ` Juri Linkov
2010-05-23 12:15 ` martin rudalics
2010-05-23 13:32 ` Stefan Monnier
2010-05-23 19:04 ` martin rudalics
2010-05-24 14:07 ` Stefan Monnier
2010-05-25 15:36 ` martin rudalics
2010-05-25 17:00 ` Stefan Monnier
2010-05-25 17:32 ` martin rudalics
2010-05-25 18:01 ` Juri Linkov
2010-05-26 8:29 ` martin rudalics
2010-05-26 13:54 ` Stefan Monnier
2010-05-26 14:49 ` martin rudalics
2010-05-27 3:58 ` Stefan Monnier
2010-05-25 18:13 ` Stefan Monnier
2010-05-26 8:30 ` martin rudalics
2010-05-26 13:56 ` Stefan Monnier
2010-05-26 14:51 ` martin rudalics
2010-05-27 4:04 ` Stefan Monnier
2010-05-27 9:09 ` martin rudalics
2010-05-27 16:13 ` Stefan Monnier
2010-05-27 17:26 ` martin rudalics
2010-05-27 18:40 ` Stefan Monnier
2010-05-28 9:19 ` martin rudalics
2010-05-28 15:34 ` Stefan Monnier
2010-05-25 18:33 ` Drew Adams
2010-05-26 8:30 ` martin rudalics
2010-05-26 14:26 ` Drew Adams
2010-05-23 12:15 ` martin rudalics
2010-05-23 12:14 ` martin rudalics
2010-05-23 0:52 ` Stefan Monnier
2010-05-23 12:14 ` martin rudalics
2010-05-23 13:31 ` Stefan Monnier
2010-05-21 20:51 ` Juri Linkov
2010-05-22 8:49 ` martin rudalics
2010-05-22 23:54 ` Juri Linkov
2010-05-22 23:50 ` Juri Linkov
2010-05-23 12:13 ` martin rudalics
2010-05-20 18:33 ` Glenn Morris
2010-05-21 0:16 ` Juri Linkov
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=4BF5736B.1030605@gmx.at \
--to=rudalics@gmx.at \
--cc=6204@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).