From: Dima Kogan <dima@secretsauce.net>
To: Juri Linkov <juri@linkov.net>
Cc: 22479@debbugs.gnu.org
Subject: bug#22479: 25.0.50; isearch and query-replace histories do not remember if we were looking for symbols
Date: Mon, 01 Feb 2016 21:32:08 -0800 [thread overview]
Message-ID: <871t8v4qzr.fsf@secretsauce.net> (raw)
In-Reply-To: <87oac1o15f.fsf@mail.linkov.net>
Juri Linkov <juri@linkov.net> writes:
>>> 5. More ideas? ;)
>>
>> - We can retain the two histories: regex, non-regex
>>
>> - Any fancy (word, symbol, etc) searches can be stored into the regex
>> history, bookmarked with the appropriate regexen ("\_<", "\_>" for
>> instance)
>>
>> - When reading the history to present to the user, these can be parsed
>> out. So for instance when the user looks through the symbol-search
>> history by hitting
>>
>> M-s _
>> C-s
>>
>> emacs can look through the regex history, only selecting entries in
>> \_<...\_>. The C-M-s history can either include all of these, or show
>> only unbookmarked entries; both would be ok, I think.
>
> This approach is compromising but unreliable
Indeed it is a compromise. It feels to me to be much better than what we
have now, and the issues aren't too significant... I think...
> (doesn't distinguish between the case when the user uses the symbol
> search M-s _ or types \_<...\_> directly in the regexp search)
True, but I think this is OK. The symbol-search history would include
M-s _ searches AND those C-M-s searches where the intent was to look for
symbols; I think this is fine. The regex-search history would include
all symbol searches also; maybe that is less fine, but it isn't crazy.
The text search history would include none of these; this is GOOD, and
is not what we do now.
> (need to remember other search parameters like case-fold and
> lax-whitespace).
Hmmm. This clearly requires metadata so some of your other, more
intrusive proposals would be required to handle this. The above proposal
would work for word and symbol searches. I think fixing that would be
worth it. Do yall just want to leave it alone?
next prev parent reply other threads:[~2016-02-02 5:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 22:27 bug#22479: 25.0.50; isearch and query-replace histories do not remember if we were looking for symbols Dima Kogan
2016-01-27 23:08 ` Juri Linkov
2016-01-30 11:43 ` Dima Kogan
2016-01-31 0:04 ` Juri Linkov
2016-01-31 1:00 ` Drew Adams
2016-01-31 17:20 ` Dima Kogan
2016-01-31 22:05 ` Juri Linkov
2016-02-02 5:32 ` Dima Kogan [this message]
2016-02-03 0:39 ` Juri Linkov
2016-02-04 0:35 ` Juri Linkov
2016-02-04 1:38 ` Dima Kogan
2016-02-04 7:42 ` Dima Kogan
2016-02-05 0:50 ` Juri Linkov
2018-03-12 21:43 ` Juri Linkov
2018-04-14 21:22 ` Juri Linkov
2018-04-19 20:32 ` Juri Linkov
2018-04-20 7:29 ` Eli Zaretskii
2018-04-21 20:02 ` Juri Linkov
2018-04-22 2:37 ` Eli Zaretskii
2018-04-22 22:11 ` Juri Linkov
2018-04-23 2:34 ` Eli Zaretskii
2016-01-28 8:10 ` Stephen Berman
2016-01-28 10:17 ` Dima Kogan
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=871t8v4qzr.fsf@secretsauce.net \
--to=dima@secretsauce.net \
--cc=22479@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).