From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Juri Linkov' <juri@jurta.org>,
'Chong Yidong' <cyd@stupidchicken.com>,
'Geoff Gole' <geoffgole@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Annoying paren match messages in minibuffer
Date: Fri, 16 Jan 2009 15:52:18 -0500 [thread overview]
Message-ID: <jwvd4enrn8j.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <006801c9780e$1a0db130$0200a8c0@us.oracle.com> (Drew Adams's message of "Fri, 16 Jan 2009 11:10:30 -0800")
>> Say you have a M-x minibuffer open but you've switched to some other
>> buffer, say a shell buffer and you're using completion and the
>> completion code needs to say "Sole completion": your suggestion would
>> cause a " [Sole completion]" message to be added at the end of the M-x
>> minibuffer (i.e. an unrelated minibuffer), rather than replacing
>> it altogether.
> No, it would not, because I would not use the DWIM function
> (`msg-maybe-in-minibuffer') to display such a message. I would not,
> because the shell completion code in question is not using the
> minibuffer, and it is unlikely that it would ever be called from
> the minibuffer.
Huh? The shell completion is used in M-!
Also I have some work-in-progress patches to replace some of the shell
and lisp-symbol completion code (and sym-comp.el) to use
minibuffer-complete. There very much is a need for this completion code
to magically decide when to use message and when to use
minibuffer-message, and until now the best test I've found is
minibufferp, not active-minibuffer-window.
Stefan
next prev parent reply other threads:[~2009-01-16 20:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 12:18 Annoying paren match messages in minibuffer Geoff Gole
2009-01-12 15:20 ` Stefan Monnier
2009-01-13 2:26 ` Miles Bader
2009-01-13 14:00 ` Stefan Monnier
2009-01-13 15:55 ` Dan Nicolaescu
2009-01-13 18:27 ` Stefan Monnier
2009-01-13 18:33 ` Dan Nicolaescu
2009-01-14 22:15 ` Stefan Monnier
2009-01-14 22:30 ` Drew Adams
2009-01-13 13:58 ` Geoff Gole
2009-01-13 18:25 ` Stefan Monnier
2009-01-13 23:28 ` Juri Linkov
2009-01-14 13:46 ` Chong Yidong
2009-01-14 14:01 ` Stefan Monnier
2009-01-14 15:29 ` Drew Adams
2009-01-14 21:12 ` Juri Linkov
2009-01-14 21:52 ` Stefan Monnier
2009-01-14 22:22 ` Drew Adams
2009-01-14 23:10 ` Stefan Monnier
2009-01-15 0:52 ` Drew Adams
2009-01-15 2:41 ` Stefan Monnier
2009-01-16 19:10 ` Drew Adams
2009-01-16 20:52 ` Stefan Monnier [this message]
2009-01-16 23:42 ` Drew Adams
2009-01-17 2:15 ` Stefan Monnier
2009-01-14 22:13 ` Drew Adams
2009-01-14 21:12 ` Juri Linkov
2009-01-14 21:53 ` Stefan Monnier
2009-01-14 18:56 ` Geoff Gole
2009-01-14 21:14 ` Juri Linkov
2009-01-14 22:20 ` Geoff Gole
-- strict thread matches above, loose matches on Subject: below --
2009-01-14 23:16 Chetan Pandya
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=jwvd4enrn8j.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=geoffgole@gmail.com \
--cc=juri@jurta.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 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.