all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: npostavs@users.sourceforge.net, Bartosz Duszel <dptdescribe@gmail.com>
Cc: 10945@debbugs.gnu.org
Subject: bug#10945: Can't search through help menu.
Date: Thu, 4 May 2017 20:40:37 -0700 (PDT)	[thread overview]
Message-ID: <6d453079-1256-42bd-b00a-331e74b9e938@default> (raw)
In-Reply-To: <87inlgm32c.fsf@users.sourceforge.net>

> IMO any key that isn't bound should fallback to its standard binding,
> and the keys should only apply when the focus is in the minibuffer, like
> other prompts (e.g., find-file).
> 
> In terms of implementation, I think this would mean binding the map
> only in the minibuffer instead of using read-key-sequence.

I don't have time to check now, but I think that the minibuffer
is not involved here at all.  Instead, an event is read directly.
IOW, this is more akin to `y-or-n-p': there is a prompt, but is
not for reading input from the minibuffer.

And the keymap used is a local one created by
`help-for-help-internal', which is a function defined
using `make-help-screen'.





  reply	other threads:[~2017-05-05  3:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 10:07 bug#10945: Can't search through help menu Alan Mackenzie
2017-05-04 15:43 ` Bartosz Duszel
2017-05-04 15:52   ` Drew Adams
2017-05-04 15:54     ` Bartosz Duszel
2017-05-04 15:57       ` Drew Adams
2017-05-04 16:05       ` Drew Adams
2017-05-04 16:59         ` Bartosz Duszel
2017-05-04 18:10           ` Bartosz Duszel
2017-05-05  2:48             ` npostavs
2017-05-05  3:40               ` Drew Adams [this message]
2017-05-05 12:12                 ` npostavs
2019-11-01 22:24 ` Stefan Kangas
2019-11-13 20:56   ` Juri Linkov
2019-11-14 18:24     ` Alan Mackenzie
2019-11-18 21:18       ` Juri Linkov
2021-10-23  3:49         ` Stefan Kangas
2021-10-23 18:23           ` Juri Linkov

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=6d453079-1256-42bd-b00a-331e74b9e938@default \
    --to=drew.adams@oracle.com \
    --cc=10945@debbugs.gnu.org \
    --cc=dptdescribe@gmail.com \
    --cc=npostavs@users.sourceforge.net \
    /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.