From: Tino Calancha <tino.calancha@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Mark Oteiza <mvoteiza@udel.edu>,
25115@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>,
Liu Hui <liuhui1610@gmail.com>
Subject: bug#25115: 26.0.50; ibuffer fails to show confirmation buffer when there are side windows
Date: Wed, 7 Dec 2016 07:45:14 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1612070742580.1921@calancha-pc> (raw)
In-Reply-To: <5846CB0F.5010907@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On Tue, 6 Dec 2016, martin rudalics wrote:
>> Your patch has perfect sense to me. Indeed i wrote an almost identical
>> fix but you were faster than me.
>
> Damn. Next time I'll wait a day or two :-(
>
> But we still don't know what this ‘window-list’ stuff is all about. I'd
> rather have asked ‘walk-window-tree-1’ on the main window to return the
> last window it sees, but consider the following emacs -Q scenario:
>
> C-x 2
> C-x o
> M-x ibuffer
> m
> m
> D
>
> The confirmation buffer appears above the ibuffer buffer. I doubt that
> such behavior is intentional but since I'm no ibuffer user ...
I think it shows the author preference for, if possible,
display *Ibuffer confirmation* in other window that
the one showing Ibuffer.
If the current frame just has a window showing
Ibuffer, then *Ibuffer confirmation* is shown in that
same window:
emacs -Q
M-x ibuffer RET
d d x
emacs -Q
C-x b test RET
M-x ibuffer RET
H
M-x other-frame RET
d d x
If we cannot show *Ibuffer confirmation* in the side window,
because it's not allow to split it, it's more useful to chose
another window, i.e., to follow your patch, instead of signal
an error.
Tino
next prev parent reply other threads:[~2016-12-06 22:45 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
2016-12-06 10:20 ` Tino Calancha
2016-12-06 14:28 ` martin rudalics
2016-12-06 22:45 ` Tino Calancha [this message]
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
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=alpine.DEB.2.20.1612070742580.1921@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=25115@debbugs.gnu.org \
--cc=liuhui1610@gmail.com \
--cc=mvoteiza@udel.edu \
--cc=rudalics@gmx.at \
/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).