From: Stefan Kangas <stefankangas@gmail.com>
To: Richard Hansen <rhansen@rhansen.org>,
Drew Adams <drew.adams@oracle.com>,
"56609@debbugs.gnu.org" <56609@debbugs.gnu.org>,
Po Lu <luangruo@yahoo.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#56609: [PATCH] Derive `Info-mode' from `special-mode'
Date: Sun, 17 Jul 2022 17:10:12 -0700 [thread overview]
Message-ID: <CADwFkmnrP6DYUnfjDmV=NkTB1rx2QCuTVadsb4+c1YpR0r4OWg@mail.gmail.com> (raw)
In-Reply-To: <5f242723-f776-2ff7-2491-5ed4e7c32172@rhansen.org>
Richard Hansen <rhansen@rhansen.org> writes:
> That's my motivating reason. I guess "improved code readability via
> consistency" could be considered a secondary reason.
Your patch LGTM.
>> If you see some real problem of a particular
>> globalized minor mode interfering with Info
>> mode, why not report that as a specific
>> problem to be considered for solving?
???
Is there even one reason why Info-mode shouldn't inherit special-mode?
next prev parent reply other threads:[~2022-07-18 0:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 5:16 bug#56609: [PATCH] Derive `Info-mode' from `special-mode' Richard Hansen
2022-07-17 5:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 5:52 ` Richard Hansen
2022-07-17 6:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 9:10 ` Lars Ingebrigtsen
2022-07-17 9:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 10:14 ` Lars Ingebrigtsen
2022-07-17 11:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 15:39 ` Lars Ingebrigtsen
2022-07-17 14:30 ` Drew Adams
2022-07-17 14:23 ` Drew Adams
2022-07-17 22:21 ` Richard Hansen
2022-07-18 0:10 ` Stefan Kangas [this message]
2022-07-18 0:26 ` Drew Adams
2022-07-18 0:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-18 2:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='CADwFkmnrP6DYUnfjDmV=NkTB1rx2QCuTVadsb4+c1YpR0r4OWg@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=56609@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=rhansen@rhansen.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.