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: Sat, 30 Jan 2016 03:43:28 -0800 [thread overview]
Message-ID: <89D2C9D3-7CA3-49A8-9BFC-CE455C91A8A8@secretsauce.net> (raw)
In-Reply-To: <87r3h2boyj.fsf@mail.linkov.net>
On January 27, 2016 3:08:20 PM PST, Juri Linkov <juri@linkov.net> wrote:
>> Hi. It is possible to look for a symbol, and for this information to
>be
>> lost when repeating a search.
>> The simplest way to fix this would probably be to treat these as
>regex
>> searches wrapped in \_<...\_>. The downside is that to access the
>> history we'd have to do C-M-s C-M-s instead of C-s C-s, but maybe
>that
>> is ok. Thoughts?
>
>Thanks for the test cases. We started designing the customizable
>variables
>for this feature in bug#11378, and reached no final implementation.
>What do you think about the proposal in bug#11378?
>
>Since the original subject of bug#11378 was quite different,
>I propose to close bug#11378, and leave this bug#22479 open
>to implement this feature here.
Hi. #11378 doesn't talk about keeping the meta-data in the history generically. It mentions remembering the state for the last search, but you'd still have the issue in this bug for older searches. So unless I missed it (very possible since it was a very long thread), that bug doesn't touch on this. We can propose new things, however :)
I don't know how much complexity we want here. Each history item can be a richer structure than just the search string. Too much?
next prev parent reply other threads:[~2016-01-30 11:43 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 [this message]
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
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=89D2C9D3-7CA3-49A8-9BFC-CE455C91A8A8@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).