From: Juri Linkov <juri@jurta.org>
To: 17809@debbugs.gnu.org
Subject: bug#17809: 24.4.50; Completions display
Date: Mon, 06 Oct 2014 01:02:45 +0300 [thread overview]
Message-ID: <87iojyfa4a.fsf@mail.jurta.org> (raw)
In-Reply-To: <87d2e5js1o.fsf@mail.jurta.org> (Juri Linkov's message of "Thu, 19 Jun 2014 09:57:47 +0300")
> - display-buffer-below-selected for completion-at-point
> that could work like displaying *Marking Files* in Dired
> to display *Completions* near the point of completion
> in the current buffer.
I noticed that at-bottom is used instead of better below-selected
for some completion-at-point commands. For example,
completing a color in the Customization UI displays the
*Completions* at the bottom even when there is no active minibuffer.
Since completion-at-point commands set the value of `this-command'
I wonder wouldn't it be right to check its value?
=== modified file 'lisp/minibuffer.el'
--- lisp/minibuffer.el 2014-07-08 19:15:28 +0000
+++ lisp/minibuffer.el 2014-10-05 21:59:09 +0000
@@ -1811,7 +1811,7 @@ (defun minibuffer-completion-help (&opti
;; Use `display-buffer-below-selected' for inline completions,
;; but not in the minibuffer (e.g. in `eval-expression')
;; for which `display-buffer-at-bottom' is used.
- ,(if (and completion-in-region-mode-predicate
+ ,(if (and (eq this-command 'completion-at-point)
(not (minibuffer-selected-window)))
'display-buffer-below-selected
'display-buffer-at-bottom))
next prev parent reply other threads:[~2014-10-05 22:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 6:57 bug#17809: 24.4.50; Completions display Juri Linkov
2014-06-23 23:53 ` Juri Linkov
2014-10-05 22:02 ` Juri Linkov [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-22 13:30 bug#17831: 24.4.50; bad default value for `Man-width' Leo Liu
2014-06-23 12:53 ` Stefan Monnier
2014-06-23 23:17 ` Juri Linkov
2014-06-24 7:13 ` martin rudalics
2014-06-24 23:44 ` bug#17809: 24.4.50; Completions display Juri Linkov
2014-06-25 6:54 ` martin rudalics
2014-06-26 23:41 ` Juri Linkov
2014-06-27 2:07 ` Stefan Monnier
2014-06-27 6:43 ` martin rudalics
2014-06-27 23:54 ` Juri Linkov
2014-06-28 8:18 ` martin rudalics
2014-06-29 23:47 ` Juri Linkov
2014-07-01 23:30 ` Juri Linkov
2014-07-04 23:40 ` Juri Linkov
2014-07-06 4:32 ` Stefan Monnier
2014-07-06 23:32 ` Juri Linkov
2014-07-07 1:21 ` Stefan Monnier
2014-07-07 1:24 ` Stefan Monnier
2014-07-07 6:49 ` Juri Linkov
2014-07-08 3:43 ` Stefan Monnier
2014-07-08 8:03 ` Juri Linkov
2014-06-27 6:43 ` martin rudalics
2014-06-27 23:53 ` Juri Linkov
2014-06-28 8:17 ` martin rudalics
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=87iojyfa4a.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=17809@debbugs.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).