From: Lennart Borgman <lennart.borgman@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 6222@debbugs.gnu.org
Subject: bug#6222: Shouldn't f1 in isearch-mode be help?
Date: Thu, 20 May 2010 02:31:41 +0200 [thread overview]
Message-ID: <AANLkTiloX0dTJ_tF6tEWsCa0HWGq6KUac3_H7qMI8mhh@mail.gmail.com> (raw)
In-Reply-To: <87sk5n77bf.fsf@mail.jurta.org>
On Thu, May 20, 2010 at 2:20 AM, Juri Linkov <juri@jurta.org> wrote:
>> C-h gives isearch help in isearch, but f1 does not. Should not both do
>> the same for consistency?
>>
>> And should not `help-char' (or [help]) be used instead of C-h in the code?
>>
>> The doc string for isearch does not mention that you now have this
>> good help for isearch during isearch. Shouldn't it do that?
>>
>> BTW: My bad memory can't find a variable that is holding both C-h and
>> f1. Wasn't there such a variable?
>
> There is no such variable. E.g. in help.el help bindings are repeated
> three times:
>
> (define-key map (char-to-string help-char) 'help-for-help)
> (define-key map [help] 'help-for-help)
> (define-key map [f1] 'help-for-help)
>
> and
>
> (define-key global-map (char-to-string help-char) 'help-command)
> (define-key global-map [help] 'help-command)
> (define-key global-map [f1] 'help-command)
Thanks, I see. But shouldn't isearch do the same then?
What about having a function in help.el for defining a binding for all
three possibilities? Something like
(defun help-define-help-keys (map command)
(define-key map (char-to-string help-char) command)
(define-key map [help] command)
(define-key map [f1] command))
next prev parent reply other threads:[~2010-05-20 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 23:30 bug#6222: Shouldn't f1 in isearch-mode be help? Lennart Borgman
2010-05-20 0:20 ` Juri Linkov
2010-05-20 0:31 ` Lennart Borgman [this message]
2010-05-20 0:38 ` Juri Linkov
2010-05-20 0:47 ` Lennart Borgman
2010-05-20 22:04 ` Juri Linkov
2010-05-20 3:37 ` Stefan Monnier
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=AANLkTiloX0dTJ_tF6tEWsCa0HWGq6KUac3_H7qMI8mhh@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=6222@debbugs.gnu.org \
--cc=juri@jurta.org \
/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).