From: Nix <nix@esperi.org.uk>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: Isearch: retrieve last successful search string from when you quit (`C-g')
Date: Tue, 02 Oct 2012 12:26:21 +0100 [thread overview]
Message-ID: <87obkl5d42.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <CAH8Pv0gzHGvrBvm_WYPRGZ+OB0QWLQp0mPDPk3=Mq502k8cLtQ@mail.gmail.com> (Dani Moncayo's message of "Mon, 1 Oct 2012 17:41:32 +0200")
On 1 Oct 2012, Dani Moncayo stated:
>> Since there is a difference in opinion, a user
>> configurable flag is what I would advocate for.
>
> Another approach: keep `C-g' as it is now (just cancel the current
> command) and choose another key for exiting i-search saving the
> current search string...
Quite. Perhaps I'm just an idiot, but I always thought the current
isearch behaviour of not immediately quitting when C-g was stuck on a
failed search was a *bug*. Only now, after Drew commented on it, do I
notice that it's removing the unfound component of the failed search:
i.e., it's a feature, but unless you spend your time looking at the echo
area while isearching (and who does that?) they'll never notice it.
I don't know the right way to fix this. The operation is clearly useful;
C-g is clearly a meaningful keybinding for it, and lots of keys work
differently form the norm in isearch, so why not keyboard-escape-quit
too; it is clearly documented... but I never realised it was there and
thought C-g instantly quit anything unless Emacs was busy at the C
layer. So perhaps there is no problem here and I should just chalk this
up to being a doofus and needing to spend some time learning what
features have been added to isearch in the last fifteen years. Maybe
everyone else expects C-g to work the way it does in isearch.
But perhaps something other than C-g is the right binding, and C-g
really *should* quit, dammit.
--
NULL && (void)
next prev parent reply other threads:[~2012-10-02 11:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 21:09 Isearch: retrieve last successful search string from when you quit (`C-g') Drew Adams
2012-10-01 6:41 ` Dani Moncayo
2012-10-01 14:57 ` Stefan Monnier
2012-10-01 15:05 ` Christopher Monsanto
2012-10-01 15:11 ` Dani Moncayo
2012-10-01 15:22 ` Drew Adams
2012-10-01 15:21 ` Drew Adams
2012-10-01 15:30 ` Christopher Monsanto
2012-10-01 15:40 ` Drew Adams
2012-10-01 15:41 ` Dani Moncayo
2012-10-01 16:00 ` Drew Adams
2012-10-01 17:49 ` Juri Linkov
2012-10-01 18:21 ` Drew Adams
2012-10-01 18:31 ` Dani Moncayo
2012-10-01 18:47 ` Drew Adams
2012-10-01 18:50 ` Christopher Monsanto
2012-10-01 18:54 ` Lennart Borgman
2012-10-01 20:00 ` Drew Adams
2012-10-01 19:12 ` Dani Moncayo
2012-10-02 11:26 ` Nix [this message]
2012-10-02 13:55 ` Drew Adams
2012-10-02 16:48 ` Eli Zaretskii
2012-10-04 11:37 ` Nix
2012-10-05 22:58 ` Andrew W. Nosenko
2012-10-01 15:18 ` Drew Adams
2012-10-02 3:22 ` Stephen J. Turnbull
2012-10-02 12:37 ` Richard Stallman
2012-10-02 14:05 ` Isearch: retrieve last successful search string from when youquit (`C-g') Drew Adams
2012-10-01 15:17 ` Isearch: retrieve last successful search string from when you quit (`C-g') Drew Adams
2012-10-02 11:29 ` Nix
2012-10-02 14:03 ` 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=87obkl5d42.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=dmoncayo@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--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).