unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 56609@debbugs.gnu.org, Richard Hansen <rhansen@rhansen.org>
Subject: bug#56609: [PATCH] Derive `Info-mode' from `special-mode'
Date: Sun, 17 Jul 2022 12:14:14 +0200	[thread overview]
Message-ID: <87fsj0m4g9.fsf@gnus.org> (raw)
In-Reply-To: <87a698f5us.fsf@yahoo.com> (Po Lu's message of "Sun, 17 Jul 2022 17:25:47 +0800")

Po Lu <luangruo@yahoo.com> writes:

> That editing the info file still works after running "Info-edit" inside
> an Info buffer.

I don't think there could be any difference?  We shift from one major
mode to another, whether that one mode is derived or not.

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





  reply	other threads:[~2022-07-17 10:14 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87fsj0m4g9.fsf@gnus.org \
    --to=larsi@gnus.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).