unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Alan Mackenzie <acm@muc.de>
Cc: Stefan Kangas <stefan@marxist.se>, 10945@debbugs.gnu.org
Subject: bug#10945: Can't search through help menu.
Date: Mon, 18 Nov 2019 23:18:00 +0200	[thread overview]
Message-ID: <87o8x8vq7r.fsf@mail.linkov.net> (raw)
In-Reply-To: <20191114182445.GA4297@ACM> (Alan Mackenzie's message of "Thu, 14 Nov 2019 18:24:45 +0000")

>> >> emacs -Q
>> >> C-h ?       ; brings up the help menu
>
>> >> I now want to search through this menu for "ChangeLog":
>
>> >> C-x         ; intending C-x o
>
>> >> The menu disappears.  This isn't friendly.
>
>> > We can now search that window using `C-h ? C-s', and it switches to
>> > the *Metahelp* window.  This functionality was added in this comit:
>
>> > 956c39d11d 2018-04-02 Make help-for-help window searchable (Bug#19655)
>
>> > `C-h C-x o' still doesn't work, though.
>
>> > Is that good enough here?
>
>> Maybe help-for-help should use the minibuffer for reading commands
>> instead of using explicit read-key-sequence?  This would allow
>> switching to the *Metahelp* window with 'C-x o'.
>
> This sounds like an excellent idea.

I tried, but the major problem is how to create a wrapper around
commands in 'help-map' to exit the minibuffer before running them.
For example, evaluating:

(read-from-minibuffer "C-h (Type ? for further options)- " nil help-map)

then typing one of the help character, doesn't exit the minibuffer.
Some additional layer of indirection could exit the minibuffer
before running the command, but currently I have no idea how to do this.

PS: Also isearch-help-for-help can't use the minibuffer to read help keys
while isearch-mode is enabled, but this is a minor obstacle.





  reply	other threads:[~2019-11-18 21:18 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
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 [this message]
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

  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=87o8x8vq7r.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=10945@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=stefan@marxist.se \
    /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).