all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liu Hui <liuhui1610@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Mark Oteiza <mvoteiza@udel.edu>,
	25115@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#25115: 26.0.50; ibuffer fails to show confirmation buffer when there are side windows
Date: Mon, 12 Dec 2016 13:22:25 +0800	[thread overview]
Message-ID: <13c2beac-ab53-b893-ada4-ff76c4fb860f@gmail.com> (raw)
In-Reply-To: <5846CB0F.5010907@gmx.at>


> 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 have seldom noticed this because I usually do C-x 1 
(delete-other-windows) before operating buffers using ibuffer, but 
displaying the confirmation buffer above, or in other unrelated windows, 
is strange indeed.

IMO, displaying the confirmation buffer just above the minibuffer 
waiting for user input, or by splitting ibuffer itself (like Dired*), is 
better.


--------
* I just found Dired seems not to preserve the window height with the 
similar steps, and have submitted a bug report.





  parent reply	other threads:[~2016-12-12  5:22 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
2016-12-07  8:15                 ` martin rudalics
2016-12-12  5:22               ` Liu Hui [this message]
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=13c2beac-ab53-b893-ada4-ff76c4fb860f@gmail.com \
    --to=liuhui1610@gmail.com \
    --cc=25115@debbugs.gnu.org \
    --cc=mvoteiza@udel.edu \
    --cc=rudalics@gmx.at \
    --cc=tino.calancha@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 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.