all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 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 09:48:51 -0700	[thread overview]
Message-ID: <f89d57da-f623-6f3c-a051-52bac6de5473@gmail.com> (raw)
In-Reply-To: <874k2qn5pl.fsf@gnus.org>

On 4/18/2022 1:41 AM, Lars Ingebrigtsen wrote:
> I've now fixed this regression, but I see there's (at least) one other:
> In Emacs 27, if the mode: had a mode that's not defined, it just says
> that it's ignored instead of trying to call it, which seems sensible, so
> I'll fix that regression, too.
> 
> But I can't get this to work in Emacs 27.2 -- Jim, are you sure that
> this worked at some point?

I just tried it in 27.2, and it works fine for me. If the "preferred" 
mode is defined, it uses that. Otherwise, it says "Ignoring unknown 
mode..." and uses the "basic" mode.

> mode: emacs-news; mode: outline-mode

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

It's a bit surprising at first, since as humans, we'd probably expect 
the "preferred" mode to be first, but the way this works is to activate 
outline-mode, and then (try to) activate emacs-news-mode. That's a 
little bit inefficient, but since this would mostly be used in cases 
where the "preferred" mode is derived from the "basic" mode, it's 
probably not too bad.





  parent reply	other threads:[~2022-04-18 16:48 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f89d57da-f623-6f3c-a051-52bac6de5473@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=54993@debbugs.gnu.org \
    --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 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.