unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 4748@emacsbugs.donarmstrong.com
Subject: bug#4748: 23.1; least recently used window - is it?
Date: Mon, 19 Oct 2009 09:57:15 -0400	[thread overview]
Message-ID: <jwvzl7ntro0.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <1BFDEAEBA19040FBB0AC56AF03E66C6F@us.oracle.com> (Drew Adams's message of "Sun, 18 Oct 2009 23:28:43 -0700")

>> The window used by pop-to-buffer depends on so many different factors
>> that it's illusory to think you can control it from the outside.

> You didn't respond to the question, which was how to replace
> `switch-to-buffer', to both (a) keep the same-window and `quit-window'
> behavior that people are used to (and presumably want) and (b) respect
> `special-display-*' and `pop-up-frames'. Those vars would take
> precedence, but if their values don't require using another frame,
> then the behavior should be to do what `switch-to-buffer' does now
> (use the same window).

There is currently no way to do that (and changing get-lru-window won't
help in this respect).
That's part of the motivation for the idea of extending the
`other-window' argument to pop-to-buffer so it can specify things like
`same-window'.


        Stefan





      reply	other threads:[~2009-10-19 13:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18  8:41 bug#4748: 23.1; least recently used window - is it? Drew Adams
2009-10-18 10:24 ` martin rudalics
2009-10-18 16:30   ` Drew Adams
2009-10-18 17:36     ` martin rudalics
2009-10-18 18:48       ` Drew Adams
2009-10-19  7:36         ` martin rudalics
2009-10-19  1:58     ` Stefan Monnier
2009-10-19  6:28       ` Drew Adams
2009-10-19 13:57         ` Stefan Monnier [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=jwvzl7ntro0.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=4748@emacsbugs.donarmstrong.com \
    --cc=drew.adams@oracle.com \
    /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).