unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: isearch-resume-enabled
Date: Sat, 11 Sep 2004 21:21:51 +0200	[thread overview]
Message-ID: <m3u0u4r4q8.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1C5pO0-0007bv-QA@fencepost.gnu.org> (Richard Stallman's message of "Fri, 10 Sep 2004 13:40:36 -0400")

Richard Stallman <rms@gnu.org> writes:

> I see you added the variable, described this way in etc/NEWS:
>
>       +++
>     + ** New user option `isearch-resume-enabled'.
>     + This option can be disabled, to avoid the normal behavior of isearch
>     + which puts calls to `isearch-resume' in the command history.
>
> This doesn't clearly explain the user-level behavior
> either in the default case or in the other case.
> The doc string doesn't, either.
>
> Could you explain to me what they are?

With the default setting, when you do C-s SOMETHING RET, a command
     (isearch-resume "SOMETHING" nil nil t "SOMETHING" (quote t))
is added to the command history.

IMO, this is very annoying.

C-s C-s already resumes the last isearch, and
C-s M-p M-p resumes earlier isearches.

So there's no reason to clutter C-x ESC ESC with this.

Setting isearch-resume-enabled to nil avoid cluttering the command
history with those (superfluous) isearch-resume commands.

I would recommend using isearch-resume-enabled = nil the default.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

       reply	other threads:[~2004-09-11 19:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1C5pO0-0007bv-QA@fencepost.gnu.org>
2004-09-11 19:21 ` Kim F. Storm [this message]
2004-09-11 19:32   ` isearch-resume-enabled Miles Bader
2004-09-11 20:54     ` isearch-resume-enabled Kim F. Storm
2004-09-13  7:01   ` isearch-resume-enabled Richard Stallman
2004-09-13  8:19     ` isearch-resume-enabled Kim F. Storm

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=m3u0u4r4q8.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@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).