From: Drew Adams <drew.adams@oracle.com>
To: Po Lu <luangruo@yahoo.com>, Richard Hansen <rhansen@rhansen.org>
Cc: "56609@debbugs.gnu.org" <56609@debbugs.gnu.org>
Subject: bug#56609: [PATCH] Derive `Info-mode' from `special-mode'
Date: Sun, 17 Jul 2022 14:30:54 +0000 [thread overview]
Message-ID: <SJ0PR10MB54887C6D3AC0E807A854B37EF38D9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87h73gguij.fsf@yahoo.com>
> Did you test this with Info-edit-mode?
>
> (It's in obsolete/, but I still use it daily.)
+1.
(I don't use it daily. But IMO it should not be
deprecated. There's nothing wrong with letting
users edit Info nodes directly.
And if you want to prevent them from doing so
accidentally then either ask for confirmation
(once only) or (put 'Info-edit 'disabled "...").
next prev parent reply other threads:[~2022-07-17 14:30 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 [this message]
2022-07-17 14:23 ` Drew Adams
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=SJ0PR10MB54887C6D3AC0E807A854B37EF38D9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=56609@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--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.