unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@stupidchicken.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 12:32:16 -0700	[thread overview]
Message-ID: <EB321DD4E9F94663B785F669E840851F@us.oracle.com> (raw)
In-Reply-To: <87mxxbf8f5.fsf@stupidchicken.com>

> > 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:
> 
> (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")))

Yes, that's OK by me.
But either of these (equivalent) forms is clearer, IMO:

(if (or icomplete-mode
        (and completion-auto-help
             (or (not (eq completion-auto-help 'lazy))
                 (eq this-command last-command))))
    (minibuffer-completion-help)
  (minibuffer-message "Next char not unique"))

(if (or icomplete-mode
        (if (eq completion-auto-help 'lazy)
            (eq this-command last-command)
          completion-auto-help))
    (minibuffer-completion-help)
  (minibuffer-message "Next char not unique"))

---

And if we didn't care whether a non-t, non-`lazy', non-nil value calls
`minibuffer-completion-help', then this (not equivalent) would be OK too:

(if (or icomplete-mode
        (eq t completion-auto-help)
        (and (eq completion-auto-help 'lazy)
             (eq this-command last-command)))
    (minibuffer-completion-help)
  (minibuffer-message "Next char not unique"))







  reply	other threads:[~2010-04-10 19:32 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
2010-04-10 19:32       ` Drew Adams [this message]
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

  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=EB321DD4E9F94663B785F669E840851F@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=5849@debbugs.gnu.org \
    --cc=cyd@stupidchicken.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 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).