From: martin rudalics <rudalics@gmx.at>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: Liu Hui <liuhui1610@gmail.com>, 25115@debbugs.gnu.org
Subject: bug#25115: 26.0.50; ibuffer fails to show confirmation buffer when there are side windows
Date: Mon, 05 Dec 2016 17:24:22 +0100 [thread overview]
Message-ID: <584594B6.4010400@gmx.at> (raw)
In-Reply-To: <87shq25s7j.fsf@udel.edu>
> I don't use ibuffer often, but I have been changing instances of
> switch-to-buffer to pop-to-buffer-same-window since reading Bug#22244.
>
> Makes me wonder about switch-to-buffer's future
This is not primarily about ‘switch-to-buffer’. It's about displaying a
list of items (file or buffer names, completions, ispell's choices, ...)
in a buffer, temporarily showing that buffer in a window and then
proceeding in reaction to user input. ‘dired-mark-pop-up’ is a typical
function for this purpose.
ibuffer apparently uses the last window in ‘window-list’ to show the
buffer at the bottom of the frame, something ‘display-buffer-at-bottom’
should handle well. But I'd like to hear the opinion of a long time
user of ‘ibuffer’ before actually changing this.
Also, ‘ibuffer-confirm-operation-on’ does ‘fit-window-to-buffer’ and I'd
prefer fixing bug#25055 first before reintroducing it somewhere else ;-)
martin
next prev parent reply other threads:[~2016-12-05 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 3:28 bug#25115: 26.0.50; ibuffer fails to show confirmation buffer when there are side windows Liu Hui
2016-12-05 7:31 ` martin rudalics
[not found] ` <d0790209-000a-ea3a-d279-f04d5b0b65d8@gmail.com>
2016-12-05 10:16 ` martin rudalics
2016-12-05 15:08 ` Mark Oteiza
2016-12-05 16:24 ` martin rudalics [this message]
2016-12-06 10:20 ` Tino Calancha
2016-12-06 14:28 ` martin rudalics
2016-12-06 22:45 ` Tino Calancha
2016-12-07 8:15 ` martin rudalics
2016-12-12 5:22 ` Liu Hui
2016-12-12 9:59 ` martin rudalics
2016-12-12 10:09 ` Tino Calancha
2022-02-12 8:51 ` 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=584594B6.4010400@gmx.at \
--to=rudalics@gmx.at \
--cc=25115@debbugs.gnu.org \
--cc=liuhui1610@gmail.com \
--cc=mvoteiza@udel.edu \
/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.