unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: LENNART BORGMAN <lennart.borgman.073@student.lu.se>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Patch that adds help to isearch
Date: Tue, 29 Nov 2005 11:23:11 +0100	[thread overview]
Message-ID: <36dd4d936dd9fb.36dd9fb36dd4d9@net.lu.se> (raw)

From: Juri Linkov <juri@jurta.org>

> What about enabling isearch-mode-help only when the search string 
> is empty?
> 
> I understand the need to exit the search with C-h when the search
> string is not empty like in the case of `C-s some-function-name C-
> h f RET'
> to call `describe-function' on the found function name.  But I 
> don't see
> the need to exit the search with C-h just after C-s as in `C-s C-h f'.
> 
> OTOH, I can imagine users (especially novices) after typing C-s 
> and seeing
> the prompt `I-search: ' wanting the help about what to do next.  
> It is
> natural for them to type C-h in this case to see the Help buffer from
> `isearch-mode-help'.

Thanks for the explanation about why C-h is needed for an experienced user. I think however that enabling the help only for the state when the search string is empty would be confusing. I would prefer a defcustom to enable/disable isearch-mode-help on C-h instead. Could that satisfy experienced users?

             reply	other threads:[~2005-11-29 10:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29 10:23 LENNART BORGMAN [this message]
2005-11-30  2:47 ` Patch that adds help to isearch Juri Linkov
2005-11-30  8:24   ` Lennart Borgman
2005-11-30 15:34     ` Juri Linkov
2005-11-30 22:27       ` Lennart Borgman
  -- strict thread matches above, loose matches on Subject: below --
2005-11-24 23:02 Lennart Borgman
2005-11-26  4:22 ` Richard M. Stallman
2005-11-27 22:53   ` Lennart Borgman
2005-11-28  7:21     ` Lennart Borgman
2005-11-29  9:04   ` Juri Linkov
2005-11-29 21:47     ` Richard M. Stallman
2005-11-29 22:12       ` Lennart Borgman
2005-11-30  2:48         ` 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=36dd4d936dd9fb.36dd9fb36dd4d9@net.lu.se \
    --to=lennart.borgman.073@student.lu.se \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.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).