From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 22479@debbugs.gnu.org, dima@secretsauce.net
Subject: bug#22479: 25.0.50; isearch and query-replace histories do not remember if we were looking for symbols
Date: Mon, 23 Apr 2018 05:34:20 +0300 [thread overview]
Message-ID: <83r2n6wt03.fsf@gnu.org> (raw)
In-Reply-To: <87bmeaaphd.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 23 Apr 2018 01:11:18 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: 22479@debbugs.gnu.org, dima@secretsauce.net
> Date: Mon, 23 Apr 2018 01:11:18 +0300
>
> > The manual can say what NEWS says, for starters.
> >
> > It also seemed to me that the Isearch prompt has changed a little; if
> > that is true, maybe that should be documented.
>
> Now the prompt has changed a little. Should this be mentioned in NEWS,
> or this fact is self-evident?
I think every user-visible change should be called out in NEWS,
especially if the prompt itself may need some explanation (e.g., due
to abbreviated words, acronyms, etc.).
next prev parent reply other threads:[~2018-04-23 2:34 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r2n6wt03.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22479@debbugs.gnu.org \
--cc=dima@secretsauce.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.