unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>, <joakim@verona.se>
Cc: emacs-devel@gnu.org
Subject: RE: binding c-h in isearch
Date: Sat, 19 Apr 2008 14:20:12 -0700	[thread overview]
Message-ID: <001b01c8a263$27d917e0$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <jwvr6d5esbx.fsf-monnier+emacs@gnu.org>

> > It is difficult to remmeber all nice features of isearch.
> > Would it be possible to bind c-h to isearch-mode-help in isearch?
> 
> There's the following code in isearch.el:
> 
>     ;; Turned off because I find I expect to get the global 
>     ;; definition--rms.
>     ;; ;; Instead bind C-h to special help command for isearch-mode.
>     ;; (define-key map "\C-h" 'isearch-mode-help)
> 
> So it seems that Richard found it inconvenient.  Could someone try and
> work out some clever way to reconcile the two functionalities?
> 
> E.g. provide the generic help on C-h but the isearch-specific help on
> C-h C-h, or vice versa?

Since this can of worms has been opened and stirred...

FWIW, I disagree with the approach being considered (Juri's suggestion etc.). It
is complicated for nothing. The simplest approach is the best: C-h during
isearch should give the isearch bindings - bind C-h to `isearch-mode-help'.

That is the convention, and it is a good one. This is like C-h following any
other prefix key. Richard is just wrong about this. Why jump through hoops?

If you are isearching and you want the global help, then (guess what?) you
simply exit isearch: RET or whatever. Nothing hard about that.

Nothing new here. No need for fancy, inconsistent stuff. No need to complicate
the UI. Just C-s...C-h to see the isearch bindings and C-s...RET C-h to see the
global help.





  parent reply	other threads:[~2008-04-19 21:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16 12:10 binding c-h in isearch joakim
2008-04-16 13:30 ` Lennart Borgman (gmail)
2008-04-16 22:35   ` Lennart Borgman (gmail)
2008-04-16 15:28 ` Stefan Monnier
2008-04-16 17:44   ` Paul R
2008-04-17 19:25   ` joakim
2008-04-17 23:14   ` Juri Linkov
2008-04-18  0:42     ` Stefan Monnier
2008-04-19 20:07       ` Juri Linkov
2008-04-19 20:49         ` Lennart Borgman (gmail)
2008-04-19 22:52           ` Juri Linkov
2008-04-20  0:53             ` Lennart Borgman (gmail)
2008-04-20 23:51               ` Juri Linkov
2008-04-21  0:13                 ` Lennart Borgman (gmail)
2008-04-19 20:57         ` Stefan Monnier
2008-04-19 22:49           ` Juri Linkov
2008-04-18 10:59     ` Johan Bockgård
2008-04-19 21:20   ` Drew Adams [this message]
2008-04-19 21:49     ` Stefan Monnier
2008-04-19 22:39       ` Drew Adams
2008-04-19 22:59     ` Juri Linkov
2008-04-19 23:39       ` Drew Adams

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='001b01c8a263$27d917e0$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    --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 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).