unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Bartosz Duszel <dptdescribe@gmail.com>
Cc: 10945@debbugs.gnu.org
Subject: bug#10945: Can't search through help menu.
Date: Thu, 04 May 2017 22:48:27 -0400	[thread overview]
Message-ID: <87inlgm32c.fsf@users.sourceforge.net> (raw)
In-Reply-To: <BA751472-74BB-451F-B125-8444DDA308E0@gmail.com> (Bartosz Duszel's message of "Thu, 4 May 2017 20:10:45 +0200")

severity 10945 wishlist
quit

Bartosz Duszel <dptdescribe@gmail.com> writes:

>>> 1. You can click mouse-1 in buffer `*Metahelp*' (the buffer you want
>>> to search).
>>> 
>>> 2. I guess we could define a key in the local map (the value of
>>> `helped-map' from `make-help-screen') that would switch to that
>>> buffer.
>
> After some more thinking I am not sure if this is the best approach.
>
> 1. After clicking mouse-1 in buffer `*Metahelp*’ you can easily search in this buffer but
> all the mapped keys doesn’t work at this point. You need to look for what you need in the buffer
> and run C-h ? once again.
>
> 2. Author of the bug highlighted that the current behaviour is not friendly. I am also not sure
> if adding another key just for changing the window is a good solution.
>
> At this point I do not know how we should handle this case.

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.





  reply	other threads:[~2017-05-05  2:48 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 [this message]
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
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=87inlgm32c.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=10945@debbugs.gnu.org \
    --cc=dptdescribe@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).