From: Chong Yidong <cyd@stupidchicken.com>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 5849@debbugs.gnu.org, 'Leo' <sdl.web@gmail.com>
Subject: bug#5849: 23.1.95; completion-auto-help blocks icomplete-mode
Date: Sat, 10 Apr 2010 14:51:10 -0400 [thread overview]
Message-ID: <87mxxbf8f5.fsf@stupidchicken.com> (raw)
In-Reply-To: <2C116479CF744C2EAAAA4A28CC69F613@us.oracle.com> (Drew Adams's message of "Sat, 10 Apr 2010 10:55:58 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> If your suggestion were to just not show the message [Next char not
> unique] when icomplete-mode is on
Yes, obviously this is what I meant. Like this:
=== modified file 'lisp/minibuffer.el'
*** lisp/minibuffer.el 2010-03-24 18:02:56 +0000
--- lisp/minibuffer.el 2010-04-10 18:49:41 +0000
***************
*** 528,536 ****
;; Show the completion table, if requested.
(cond
((not exact)
! (if (case completion-auto-help
! (lazy (eq this-command last-command))
! (t completion-auto-help))
(minibuffer-completion-help)
(minibuffer-message "Next char not unique")))
;; If the last exact completion and this one were the same, it
--- 528,537 ----
;; Show the completion table, if requested.
(cond
((not exact)
! (if (cond (icomplete-mode t)
! ((eq completion-auto-help 'lazy)
! (eq this-command last-command))
! (t completion-auto-help))
(minibuffer-completion-help)
(minibuffer-message "Next char not unique")))
;; If the last exact completion and this one were the same, it
next prev parent reply other threads:[~2010-04-10 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 15:31 bug#5849: 23.1.95; completion-auto-help blocks icomplete-mode Leo
2010-04-10 17:24 ` Chong Yidong
2010-04-10 17:55 ` Drew Adams
2010-04-10 18:51 ` Chong Yidong [this message]
2010-04-10 19:32 ` Drew Adams
2010-04-11 11:53 ` Leo
2010-05-10 6:58 ` Leo
2011-04-10 21:30 ` Chong Yidong
2011-07-09 15:00 ` Johan Bockgård
2011-09-18 16:13 ` Chong Yidong
2010-07-23 22:18 ` Stefan Monnier
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=87mxxbf8f5.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=5849@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=sdl.web@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.