From: Juri Linkov <juri@jurta.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 11378@debbugs.gnu.org
Subject: bug#11378: 24.1.50; Suggestion: Let M-i in isearch cycle `search-invisible'
Date: Thu, 30 May 2013 11:12:05 +0300 [thread overview]
Message-ID: <87k3mgevq2.fsf@mail.jurta.org> (raw)
In-Reply-To: <6dcc689e-53a8-4982-953c-1b21c11cec78@default> (Drew Adams's message of "Wed, 29 May 2013 20:16:52 -0700 (PDT)")
> I understand that approach. I disagree, that's all.
It's no surprise that you disagree because both preferences make sense:
(1) Start each new search afresh with default values.
(2) Keep the current search state for subsequent searches.
There are more possible preferences:
(3) Someone even might prefer to keep the current search state
within the confines of the current buffer (easy to do with
`make-local-variable' on the transient search variables).
(4) Reuse the previous search values only for the repeated search
`C-s C-s'. This what the variable `isearch-last-case-fold-search'
is used for. But why `isearch-last-case-fold-search' only?
Other search variables could be supported too.
This suggests two new customizable options: one to define which search
variables to keep for the next search to be able to choose the behavior
between (1) and (2) for every search variable, and another option for (4)
to choose which search variables to keep for the repeated search `C-s C-s'
(its default value could reuse the last case-fold only as it currently does).
next prev parent reply other threads:[~2013-05-30 8:12 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 6:10 bug#11378: 24.1.50; Suggestion: Let M-i in isearch cycle `search-invisible' Michael Heerdegen
2012-04-29 14:46 ` Stefan Monnier
2012-04-29 15:32 ` Drew Adams
2012-04-29 21:04 ` Lennart Borgman
2012-04-30 0:28 ` Juri Linkov
2012-05-01 9:15 ` Juri Linkov
2012-05-01 12:59 ` Stefan Monnier
2012-05-01 15:15 ` Juri Linkov
2012-05-01 13:14 ` Drew Adams
2012-05-29 16:40 ` Juri Linkov
2012-05-29 18:22 ` Stefan Monnier
2012-05-30 0:40 ` Juri Linkov
2012-05-30 4:32 ` Stefan Monnier
2012-05-31 0:55 ` Juri Linkov
2012-05-31 21:25 ` Stefan Monnier
2018-04-24 19:50 ` Juri Linkov
2019-11-01 18:54 ` Stefan Kangas
2019-11-02 11:01 ` Michael Heerdegen
2012-06-11 23:44 ` Juri Linkov
2013-02-15 9:22 ` Juri Linkov
2013-05-27 22:45 ` Juri Linkov
2013-05-28 21:47 ` Juri Linkov
2013-05-28 22:45 ` Drew Adams
2013-05-29 22:45 ` Juri Linkov
2013-05-30 3:16 ` Drew Adams
2013-05-30 8:12 ` Juri Linkov [this message]
2013-05-30 13:34 ` Drew Adams
2013-05-30 23:47 ` Juri Linkov
2013-06-02 9:47 ` Juri Linkov
2019-11-01 18:50 ` Stefan Kangas
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=87k3mgevq2.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=11378@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).