From: "Drew Adams" <drew.adams@oracle.com>
To: "'Christopher Monsanto'" <chris@monsan.to>
Cc: emacs-devel@gnu.org, 'Stefan Monnier' <monnier@iro.umontreal.ca>,
'Dani Moncayo' <dmoncayo@gmail.com>
Subject: RE: Isearch: retrieve last successful search string from when you quit (`C-g')
Date: Mon, 1 Oct 2012 08:40:52 -0700 [thread overview]
Message-ID: <5F547EDB722D47C9919E87174C28D0F0@us.oracle.com> (raw)
In-Reply-To: <CAC5n7THYeZQ=PBaZ1myzaGGxoa0r_8o+ZhxfKERQw_Umdb2sxQ@mail.gmail.com>
> When I hit C-g, it means "I don't want to operate at the search
> position, I was just looking for something and now I'm ready to go
> back to where I was."
Precisely. "I was just looking for something" and I didn't really want to move
there - just now at least.
And you perhaps have no idea at that time whether you might want to repeat that
looking later, or even perhaps move to one of the search hits.
The question (between the two proposals) is whether to record all such abandoned
searches or just the last one.
More precisely (because we could, if we wanted, create additional search rings
for this), it is whether to record such abandoned searches in the regular search
rings or separately. Should they be mixed in with the accepted/used searches?
> > I doubt if you would really love it, in practice. But it
> > is simple for you to try it, to see. ...
>
> That's your speculation :) I'm just putting my two cents in for what
> works best for my (perhaps eccentric, but that's none of your
> business!) workflow. Since there is a difference in opinion, a user
> configurable flag is what I would advocate for.
Why don't you try it? Try both.
next prev parent reply other threads:[~2012-10-01 15:40 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 [this message]
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
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=5F547EDB722D47C9919E87174C28D0F0@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=chris@monsan.to \
--cc=dmoncayo@gmail.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).