From: Juri Linkov <juri@linkov.net>
To: Dima Kogan <dima@secretsauce.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: Fri, 05 Feb 2016 02:50:35 +0200 [thread overview]
Message-ID: <878u302bmw.fsf@mail.linkov.net> (raw)
In-Reply-To: <87k2mk3orm.fsf@secretsauce.net> (Dima Kogan's message of "Wed, 03 Feb 2016 23:42:21 -0800")
>> Yes, this is a harder problem. We have to remember meta-data for
>> every search history element. There are several possibilities:
>>
>> 4. Adding meta-data by text-properties to the strings in
>> ‘search-ring’ and ‘regexp-search-ring’ poses a problem of saving
>> the values in the desktop and restoring in another session.
>
> This feels like the best solution. I looked at desktop.el, and it
> doesn't save the properties, as you say. But it could be made to. Do you
> think some external packages would get broken by this change?
In addition to desktop.el, other external packages save histories as well
like savehist.el.
next prev parent reply other threads:[~2016-02-05 0:50 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
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 [this message]
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=878u302bmw.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=22479@debbugs.gnu.org \
--cc=dima@secretsauce.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).