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: Tue, 11 Feb 2014 10:06:15 -0800 (PST)	[thread overview]
Message-ID: <902973cd-2e64-4fc4-9d2d-d49a690c10cb@default> (raw)
In-Reply-To: <jwva9dxr150.fsf-monnier+emacsbugs@gnu.org>

> > Could you give me a recipe that might show the problem?
> 
> M-x icomplete-mode RET
> C-x b left-char RET RET
> C-x b RET
> C-x b left-char
> 
> The first left-char does not output the key-binding (because the
> code is only triggered for matches), but the second does (in 24.3).

Got it.  Thx.  Yes, same thing with Icomplete+: key <left> is echoed.

Personally, this (rare, I would guess) minor nuisance is outweighed
by the positive help provided by showing keys for sole-match commands.

As a different user, you might feel differently about the relative
value.

The important thing is that if you restore this fine feature then
you simply give individual _users_ the choice: there was already a
user option for whether to show key bindings,
`icomplete-show-key-bindings'.  Restoring that option is of course
part of fixing the regression.





  reply	other threads:[~2014-02-11 18:06 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
2014-02-11 17:52         ` Stefan Monnier
2014-02-11 18:06           ` Drew Adams [this message]
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=902973cd-2e64-4fc4-9d2d-d49a690c10cb@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.