all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 13092@debbugs.gnu.org
Subject: bug#13092: 24.3.50; regression: `icomplete-mode' does not echo key bindings
Date: Mon, 10 Feb 2014 22:35:04 -0800 (PST)	[thread overview]
Message-ID: <8b403428-3297-445d-b96c-659c757e7cf2@default> (raw)
In-Reply-To: <jwvwqh2xqtn.fsf-monnier+emacsbugs@gnu.org>

> > Icomplete mode used to echo the keys bound to commands matching
> > your input as you type the command name.  This useful feature was
> > removed - a regression.  Please restore the feature.  Thx.
> 
> Yes, it was useful but it was completely broken, echoing this info
> regardless if the minibuffer input was actually meant to represent
> a command name or not.
> 
> So, to have it back, someone will have to write it in the right way,
> such that the echo is only performed for M-x completion and not (for
> example) for buffer name completion.

I see.  FWIW, I show the key in icomplete+.el still, and I have
never see it try to show a key for buffer-name completion (or any
other kind of completion besides command completion).

Could you give me a recipe that might show the problem?  Was there
perhaps an Emacs bug filed about that?  I'd be curious, so I can see
what happens with icomplete+.el in this regard.





  reply	other threads:[~2014-02-11  6:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-05 22:08 bug#13092: 24.3.50; regression: `icomplete-mode' does not echo key bindings Drew Adams
2014-02-10  7:33 ` Lars Ingebrigtsen
2014-02-10 18:50   ` Drew Adams
2014-02-11  3:40     ` Stefan Monnier
2014-02-11  6:35       ` Drew Adams [this message]
2014-02-11 17:52         ` Stefan Monnier
2014-02-11 18:06           ` Drew Adams
2020-12-04 11:04           ` Lars Ingebrigtsen

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=8b403428-3297-445d-b96c-659c757e7cf2@default \
    --to=drew.adams@oracle.com \
    --cc=13092@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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.