From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 59121@debbugs.gnu.org
Cc: bjorn.bidar@thaodan.de
Subject: bug#59121: 29.0.50; Gnus: Nnir is deprecated but not mention in the manual
Date: Tue, 08 Nov 2022 13:18:51 -0800 [thread overview]
Message-ID: <87y1sljgas.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <874jv9wuve.fsf@thaodan.de> ("Björn Bidar via \"Bug reports for GNU Emacs, the Swiss army knife of text editors\""'s message of "Tue, 08 Nov 2022 13:25:41 +0200")
Björn Bidar via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> Hey,
>
> While trying out how to search for emails in Gnus, I noticed that
> nnir.el is deprecated but the manual (gnu.org/software/emacs/manual)
> doesn't mention any of that.
> I think the manual should mention that. I think such changes should be
> documented right a way in general.
Do you mean that you recently upgraded Emacs, and got a deprecation
warning for a nnir-* variable, but there's no information in the Gnus
manual about migrating away from nnir?
That does seem like an oversight...
next prev parent reply other threads:[~2022-11-08 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 11:25 bug#59121: 29.0.50; Gnus: Nnir is deprecated but not mention in the manual Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-08 21:18 ` Eric Abrahamsen [this message]
2022-11-08 21:35 ` Eric Abrahamsen
2022-11-09 5:42 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-09 22:01 ` Eric Abrahamsen
2022-11-11 19:10 ` Eric Abrahamsen
2022-11-11 20:58 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-09 5:29 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-09 10:42 ` Robert Pluim
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=87y1sljgas.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=59121@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
/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).