From: martin rudalics <rudalics@gmx.at>
To: "Francesco Potortì" <pot@gnu.org>
Cc: 25054@debbugs.gnu.org
Subject: bug#25054: 25.1; bury-buffer makes bad choice of next buffer
Date: Wed, 30 Nov 2016 08:53:58 +0100 [thread overview]
Message-ID: <583E8596.80909@gmx.at> (raw)
In-Reply-To: <E1cBpGS-0002av-B1@tucano.isti.cnr.it>
> My main problem is with the *mail* buffer (I have mail-user-agent set to
> 'sendmail-user-agent). After I send mail, the *mail* buffer is buried,
> but after a while it pops up. I would expect that, being buried, it is
> the last choice as the other buffer. Apparently it is not.
It is. But the "other buffer" is not necessarily the one that will be
shown in a window when that window's previous buffer is about getting
buried or killed.
> I don't know why, and I have not time to investigate now, sorry. But if
> you care to suggest some ideas, I may find the time sooner or later :)
I suppose you mean something like
(progn
(switch-to-buffer "a")
(switch-to-buffer "b")
(when (y-or-n-p "Bury b ? ")
(bury-buffer))
(while (y-or-n-p "Previous ? ")
(previous-buffer)))
The loop in this scenario will eventually switch to "b" (because it has
been already shown in the selected window) rather than to "*Messages*"
(simply because it has never shown up in that window before). We could
invent an option to change that behavior, but so far you would be its
only user. And it's not even clear to me how to formulate that option.
martin
next prev parent reply other threads:[~2016-11-30 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 18:51 bug#25054: 25.1; bury-buffer makes bad choice of next buffer Francesco Potortì
2016-11-28 19:14 ` martin rudalics
2016-11-28 20:32 ` Francesco Potortì
2016-11-29 8:09 ` martin rudalics
2016-11-29 20:44 ` Francesco Potortì
2016-11-30 7:53 ` martin rudalics [this message]
2016-12-06 11:48 ` Francesco Potortì
2016-12-06 14:28 ` martin rudalics
2022-01-29 16:35 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=583E8596.80909@gmx.at \
--to=rudalics@gmx.at \
--cc=25054@debbugs.gnu.org \
--cc=pot@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.