all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jporterbugs@gmail.com, 54993@debbugs.gnu.org
Subject: bug#54993: 28.1; Editing etc/NEWS on master with Emacs 28 signals an error
Date: Wed, 20 Apr 2022 12:45:15 +0200	[thread overview]
Message-ID: <87lew09gp0.fsf@gnus.org> (raw)
In-Reply-To: <83bkwxukfg.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 19 Apr 2022 19:06:43 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Now the only issue that remains, AFAICT, is the different key bindings
> for outline-related commands in NEWES, caused by the fact that
> emacs-news-mode activates outline-minor-mode.  Could we perhaps solve
> this by having emacs-news-mode be derived from outline-mode, not from
> text-mode?  If not, why not?

I thought it would be more consistent to have both emacs-news-view-mode
and emacs-news-mode use outline-minor-mode, but I don't really have a
strong opinion here.  (We're moving all the "help"-ish buffers to use
outline-minor-mode, after all.)

But emacs-news-mode is for editing, so perhaps it makes sense to use
outline-mode here.  It does steal an awful lot of the `C-c C-*' keys,
though, so I'm not very enthusiastic about outline-mode in general and
think we should avoid it.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2022-04-20 10:45 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
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 [this message]
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=87lew09gp0.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=54993@debbugs.gnu.org \
    --cc=eliz@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 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.