From: Drew Adams <drew.adams@oracle.com>
To: Richard Hansen <rhansen@rhansen.org>,
"56609@debbugs.gnu.org" <56609@debbugs.gnu.org>
Subject: bug#56609: [PATCH] Derive `Info-mode' from `special-mode'
Date: Sun, 17 Jul 2022 14:23:51 +0000 [thread overview]
Message-ID: <SJ0PR10MB54888D6B86BCC2E28D76AEDAF38D9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <dd1eb01a-0cd4-04f0-8381-524f61902128@rhansen.org>
> Derive `Info-mode' from `special-mode'
>
> * lisp/info.el (Info-mode): Derive `Info-mode' from `special-mode'.
>
> This makes it easier to exclude it from globalized minor modes that
> don't apply to special modes (such as `global-whitespace-mode' and
> global-display-fill-column-indicator-mode').
Is that the only reason? If so, why is that
a real problem? And if it is, why is this a
good solution?
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?
Emacs has already pondered this question, as
evidenced by the code comment. It's still a
question, and worth raising.
But to raise it, there should be some (more)
information about what problems there might
be now. Otherwise, `special-mode', here, is
a solution in search of a problem.
Info mode has been around nearly forever;
`define-derived-mode' has been around at
least since Emacs 20; and `special-mode' has
been here since Emacs 23.
next prev parent reply other threads:[~2022-07-17 14:23 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 [this message]
2022-07-17 22:21 ` Richard Hansen
2022-07-18 0:10 ` Stefan Kangas
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=SJ0PR10MB54888D6B86BCC2E28D76AEDAF38D9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=56609@debbugs.gnu.org \
--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.