From: Lars Ingebrigtsen <larsi@gnus.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 54993@debbugs.gnu.org
Subject: bug#54993: 28.1; Editing etc/NEWS on master with Emacs 28 signals an error
Date: Tue, 19 Apr 2022 15:56:31 +0200 [thread overview]
Message-ID: <874k2pb2i8.fsf@gnus.org> (raw)
In-Reply-To: <87sfq9b7hw.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 19 Apr 2022 14:08:43 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
>> It's probably failing for you because you need to do this in the
>> opposite order (and remove the "-mode"):
>>
>> mode: outline; mode: emacs-news
Aha! This works:
-*- mode: outline; mode: emacs-news -*-
But it doesn't work in the Local variables: section, which can only have
one mode/variable per line.
But! Emacs only interprets the first mode: line it finds, so having
mode: outline
mode: emacs-news
and then extending Emacs on the trunk heed the final (defined) mode
would be both backwards and forwards compatible (as well as making this
an alternative to -*-, making things more regular), so I'll take a peek
at doing that.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-19 13:56 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
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 [this message]
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=874k2pb2i8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=54993@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
/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).