From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, 54993@debbugs.gnu.org
Subject: bug#54993: 28.1; Editing etc/NEWS on master with Emacs 28 signals an error
Date: Mon, 18 Apr 2022 13:12:31 +0200 [thread overview]
Message-ID: <87tuaqir1c.fsf@gnus.org> (raw)
In-Reply-To: <837d7mwtzj.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 18 Apr 2022 13:45:04 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> We could add NEWS to auto-mode-alist instead, and that would solve the
> issue cleanly for everyone. That was one of the original
> alternatives, but somehow it was forgotten now.
My worry with that was that adding etc/NEWS to auto-mode-alist would be
false positives (for other files with that name). But I guess we could
check that it's actually an Emacs NEWS file before enabling the mode.
But that would mean removing the mode: setting from NEWS itself, because
mode: takes precedence over auto-mode-alist, I think? (But I may well
be misremembering.) So then we're back to people editing the file in
Emacs 28 in fundamental-mode.
> Btw, another issue with emacs-news-mode is that it invokes
> outline-minor-mode, which means all the headings-related commands are
> now bound to different keys than they were before. Wouldn't it be
> better if emacs-news-mode were a minor mode invoked by Outline
> instead?
emacs-news-mode is quite major-modeish, though, so I think that would be
awkward.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-18 11:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 17:44 bug#54993: 28.1; Editing etc/NEWS on master with Emacs 28 signals an error Eli Zaretskii
2022-04-17 18:38 ` Lars Ingebrigtsen
2022-04-17 18:49 ` Eli Zaretskii
2022-04-17 18:54 ` Lars Ingebrigtsen
2022-04-17 19:15 ` Eli Zaretskii
2022-04-17 19:37 ` Lars Ingebrigtsen
2022-04-17 20:12 ` Eli Zaretskii
2022-04-18 8:40 ` Michael Albinus
2022-04-18 8:45 ` Lars Ingebrigtsen
2022-04-18 8:48 ` Michael Albinus
2022-04-18 8:56 ` Michael Albinus
2022-04-18 9:35 ` Lars Ingebrigtsen
2022-04-18 9:27 ` Eli Zaretskii
2022-04-18 9:34 ` Lars Ingebrigtsen
2022-04-18 9:36 ` Eli Zaretskii
2022-04-18 10:08 ` Michael Albinus
2022-04-18 10:45 ` Eli Zaretskii
2022-04-18 11:12 ` Lars Ingebrigtsen [this message]
2022-04-18 14:15 ` Eli Zaretskii
2022-04-19 12:04 ` Lars Ingebrigtsen
2022-04-17 20:17 ` Jim Porter
2022-04-17 20:27 ` Lars Ingebrigtsen
2022-04-17 21:32 ` Lars Ingebrigtsen
2022-04-18 8:41 ` Lars Ingebrigtsen
2022-04-18 8:44 ` Lars Ingebrigtsen
2022-04-18 19:05 ` Juri Linkov
2022-04-19 12:10 ` Lars Ingebrigtsen
2022-04-19 13:18 ` Michael Albinus
2022-04-19 13:21 ` Lars Ingebrigtsen
2022-04-19 19:15 ` Juri Linkov
2022-04-20 6:22 ` Kévin Le Gouguec
2022-04-20 10:49 ` Lars Ingebrigtsen
2022-04-18 16:48 ` Jim Porter
2022-04-19 12:08 ` Lars Ingebrigtsen
2022-04-19 13:56 ` Lars Ingebrigtsen
2022-04-19 14:24 ` Lars Ingebrigtsen
2022-04-19 16:06 ` Eli Zaretskii
2022-04-20 6:14 ` Kévin Le Gouguec
2022-04-20 6:46 ` Eli Zaretskii
2022-04-20 10:45 ` Lars Ingebrigtsen
2022-04-20 12:28 ` Eli Zaretskii
2022-04-21 11:32 ` Lars Ingebrigtsen
2022-04-19 16:09 ` 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=87tuaqir1c.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=54993@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael.albinus@gmx.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).