unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 17554@debbugs.gnu.org
Subject: bug#17554: 24.3.91; [Regression] re-usage of dired *Marked Files* buffer window
Date: Sat, 07 Jun 2014 02:05:30 +0300	[thread overview]
Message-ID: <87r431prk5.fsf@mail.jurta.org> (raw)
In-Reply-To: <16581.64879.470025.21393@gargle.gargle.HOWL> (Roland Winkler's message of "Thu, 5 Jun 2014 23:17:09 -0500")

>> > +(add-to-list 'display-buffer-alist '("\\*Completions\\*" display-buffer-at-bottom (nil)))
>>
>> `display-buffer-alist' has to stay nil by default.
>
> I do not know much about how emacs manages its windows.  Yet I am a
> bit surprised that the above approach establishes a rather special
> treatment of *Completions* buffers.  I'd say the problem is that *a*
> buffer with typically more than two or three lines gets
> automatically displayed in a window that is only three lines high.
> We have a particular example where this happens to the *Completions*
> buffer.  But if this happened with any other buffer this would be
> equally annoying.  So it seems to me that this should be solved in a
> more generic way.
>
> Am I missing something?

This is how `display-buffer-use-some-window' works:
it calls `get-lru-window' to get the least recently used window
which is `*Marked Files*' in this case.





  reply	other threads:[~2014-06-06 23:05 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22 19:59 bug#17554: 24.3.91; [Regression] re-usage of dired *Marked Files* buffer window Roland Winkler
2014-05-23  1:07 ` Stefan Monnier
2014-05-23  2:17   ` Roland Winkler
2014-05-23  6:06     ` Eli Zaretskii
2014-05-23  7:24     ` martin rudalics
2014-05-23 21:32       ` Juri Linkov
2014-05-27 21:54         ` Juri Linkov
2014-05-27 22:45           ` Roland Winkler
2014-06-05 23:48             ` Juri Linkov
2014-06-06  1:07               ` Stefan Monnier
2014-06-06  4:17                 ` Roland Winkler
2014-06-06 23:05                   ` Juri Linkov [this message]
2014-06-09 16:15                     ` Roland Winkler
2014-06-10  0:12                       ` Juri Linkov
2014-06-10  6:07                         ` martin rudalics
2014-06-10 22:57                           ` Juri Linkov
2014-06-11  7:15                             ` martin rudalics
2014-06-12  6:33                               ` Juri Linkov
2014-06-16  6:51                                 ` Juri Linkov
2014-06-16 19:49                                   ` Roland Winkler
2014-06-16 21:47                                     ` Stefan Monnier
2014-06-17  6:44                                       ` Juri Linkov
2014-06-18  7:57                                         ` Juri Linkov
2014-06-06 23:04                 ` Juri Linkov
2014-06-18  8:07                   ` Juri Linkov
2014-05-23  5:48 ` Eli Zaretskii
2014-05-23  7:25   ` martin rudalics
2014-05-23  7:31     ` Eli Zaretskii

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=87r431prk5.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=17554@debbugs.gnu.org \
    --cc=winkler@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 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).