From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Juanma Barranquero' <lekktu@gmail.com>, 8911@debbugs.gnu.org
Subject: bug#8911: bs-cycle-next deletes window in some cases.
Date: Wed, 22 Jun 2011 16:07:53 -0400 [thread overview]
Message-ID: <jwvaad9bpm4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <9170F33E41584E0B8D96DD5EFC84599E@us.oracle.com> (Drew Adams's message of "Tue, 21 Jun 2011 19:53:01 -0700")
> As I also said earlier, to me (and per the doc string and the
> function's past behavior) `bury-buffer' is not about display. (That
> is, it is only secondarily about display, and only in the one
> particular case quoted above.)
There are two ways to call bury-buffer, which correspond to two fairly
different behaviors. One is with a non-nil argument, where it only
touches the order in the buffer-list. This one is uncontroversial and
doesn't matter much to me.
The other is when the argument is nil, in which case it is
*specifically* meant to make the buffer disappear (additionally to
changing the buffer-list order). This case is very much about display,
not just secondarily so.
> The reason is primarily the annoyance that iconifying can produce - on
> Windows it is kind of animated, essentially sweeping across the
> display down to the task bar. With frame deletion it just disappears
> instantly - poof.
Then we could add an option so that bury-buffer uses delete-frame
instead of iconify-frame. But doing nothing is not an option since the
caller specifically asked to undisplay the buffer.
Stefan
next prev parent reply other threads:[~2011-06-22 20:07 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 11:01 bug#8911: bs-cycle-next deletes window in some cases Juanma Barranquero
2011-06-21 13:37 ` martin rudalics
2011-06-21 14:00 ` Juanma Barranquero
2011-06-21 14:42 ` martin rudalics
2011-06-21 15:02 ` Juanma Barranquero
2011-06-21 16:12 ` martin rudalics
2011-06-21 16:21 ` Juanma Barranquero
2011-06-21 16:28 ` Stefan Monnier
2011-06-21 16:37 ` Juanma Barranquero
2011-06-22 2:14 ` Stefan Monnier
2011-06-22 2:31 ` Juanma Barranquero
2011-06-22 20:11 ` Stefan Monnier
2011-06-21 16:22 ` Stefan Monnier
2011-06-21 16:28 ` Juanma Barranquero
2011-06-21 17:15 ` Drew Adams
2011-06-22 2:11 ` Stefan Monnier
2011-06-22 2:53 ` Drew Adams
2011-06-22 3:13 ` Drew Adams
2011-06-22 20:07 ` Stefan Monnier [this message]
2011-06-22 22:01 ` Drew Adams
2011-06-23 21:55 ` Stefan Monnier
2011-06-25 21:24 ` Juanma Barranquero
2011-06-26 9:29 ` martin rudalics
2011-06-26 11:25 ` Juanma Barranquero
2011-06-27 1:30 ` Stefan Monnier
2011-06-27 1:53 ` Juanma Barranquero
2011-06-27 7:00 ` martin rudalics
2011-06-27 9:38 ` Juanma Barranquero
2011-06-27 12:46 ` martin rudalics
2011-06-27 14:01 ` Juanma Barranquero
2011-06-27 14:12 ` martin rudalics
2011-06-27 14:22 ` Juanma Barranquero
2011-06-27 20:11 ` Juanma Barranquero
2011-06-29 3:27 ` Stefan Monnier
2011-06-29 3:57 ` Juanma Barranquero
2011-06-30 17:02 ` Stefan Monnier
2011-06-30 18:50 ` Juanma Barranquero
2011-07-01 12:07 ` Juanma Barranquero
2011-06-29 7:11 ` martin rudalics
2011-06-30 17:06 ` Stefan Monnier
2011-06-29 11:36 ` Juanma Barranquero
2011-06-29 15:36 ` Drew Adams
2011-06-29 18:21 ` Drew Adams
2011-06-30 7:00 ` martin rudalics
2011-06-30 15:31 ` Drew Adams
2011-06-22 2:07 ` Stefan Monnier
2011-06-21 16:36 ` martin rudalics
2011-06-21 17:07 ` Drew Adams
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=jwvaad9bpm4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=8911@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=lekktu@gmail.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).