From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 39706@debbugs.gnu.org
Subject: bug#39706: 28.0.50; Search prefix nroff-mode
Date: Tue, 25 Feb 2020 07:42:07 +0200 [thread overview]
Message-ID: <83tv3fgr4g.fsf@gnu.org> (raw)
In-Reply-To: <8736azxzyz.fsf@mail.linkov.net> (message from Juri Linkov on Tue, 25 Feb 2020 02:39:00 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: 39706@debbugs.gnu.org
> Date: Tue, 25 Feb 2020 02:39:00 +0200
>
> > Thanks. I'm okay with the change, but I think it should be called out
> > in NEWS as an incompatible change, with an explanation why we did
> > that.
>
> Pushed to master with NEWS and removed the task from admin/release-process.
Thanks.
> Not sure what to do with other remaining tasks in admin/release-process:
>
> 1. Gnus binds 'M-s' to 'gnus-summary-search-article-forward'.
>
> 2. Minibuffer binds 'M-s' to 'next-matching-history-element'
> (not useful any more since C-s can now search in the history).
>
> 3. PCL-CVS binds 'M-s' to 'cvs-status', and log-edit-mode binds it to
> 'log-edit-comment-search-forward'. Perhaps search commands
> on the global key binding 'M-s' are useless in these modes.
>
> 4. Rmail binds '\es' to 'rmail-search'/'rmail-summary-search'.
IMO, only Gnus is popular enough to worry about. Lars, any
suggestions?
next prev parent reply other threads:[~2020-02-25 5:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 23:51 bug#39706: 28.0.50; Search prefix nroff-mode Juri Linkov
2020-02-21 7:48 ` Eli Zaretskii
2020-02-23 0:40 ` Juri Linkov
2020-02-23 15:18 ` Eli Zaretskii
2020-02-23 23:02 ` Juri Linkov
2020-02-24 16:25 ` Eli Zaretskii
2020-02-25 0:39 ` Juri Linkov
2020-02-25 5:42 ` Eli Zaretskii [this message]
2020-03-14 12:30 ` Lars Ingebrigtsen
2020-08-15 12:20 ` Lars Ingebrigtsen
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=83tv3fgr4g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39706@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
/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).