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: Fri, 06 Jun 2014 02:48:50 +0300 [thread overview]
Message-ID: <87k38u52o5.fsf@mail.jurta.org> (raw)
In-Reply-To: <5541.86351.568913.21381@gargle.gargle.HOWL> (Roland Winkler's message of "Tue, 27 May 2014 17:45:57 -0500")
>> A good placement of the *Completions* buffer can be achieved by using:
>>
>> (add-to-list 'display-buffer-alist '("\\*Completions\\*"
>> display-buffer-at-bottom (nil)))
>>
>> It works in Dired as well with different window configurations.
>
> This displays the *Completions* buffer at the bottom, whereas 24.3
> puts it above the *Marked Files* buffer. I have no strong
> preferences with this. I expect either way is fine.
The *Completions* buffer is displayed by `internal-temp-output-buffer-show',
so adding a new action `display-buffer-at-bottom' to it would affect many
other unrelated commands besides completion commands.
To modify the behavior of only *Completions* we need to add it to
display-buffer-alist that will be non-empty by default:
=== modified file 'lisp/simple.el'
--- lisp/simple.el 2014-06-02 00:18:22 +0000
+++ lisp/simple.el 2014-06-05 23:43:17 +0000
@@ -7300,6 +7300,9 @@ (defun switch-to-completions ()
;; FIXME: Perhaps this should be done in `minibuffer-completion-help'.
(when (bobp)
(next-completion 1)))))
+
+(add-to-list 'display-buffer-alist '("\\*Completions\\*" display-buffer-at-bottom (nil)))
+
\f
;;; Support keyboard commands to turn on various modifiers.
next prev parent reply other threads:[~2014-06-05 23:48 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 [this message]
2014-06-06 1:07 ` Stefan Monnier
2014-06-06 4:17 ` Roland Winkler
2014-06-06 23:05 ` Juri Linkov
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=87k38u52o5.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).