From: Andreas Schwab <schwab@linux-m68k.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Po Lu <luangruo@yahoo.com>, 52053@debbugs.gnu.org
Subject: bug#52053: 29.0.50; Nonsensical button "C-x C-f" in scratch buffer
Date: Wed, 24 Nov 2021 18:05:51 +0100 [thread overview]
Message-ID: <87sfvlh4b4.fsf@igel.home> (raw)
In-Reply-To: <87ee75y0by.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 24 Nov 2021 17:39:45 +0100")
On Nov 24 2021, Lars Ingebrigtsen wrote:
> Po Lu <luangruo@yahoo.com> writes:
>
>> I don't think it should, and similarly, it shouldn't apply to
>> lisp-interaction-mode, which is simply Emacs Lisp mode but slightly more
>> interactive.
>
> Sure, but that ;; comment there is put there explicitly as a message to
> the user.
Then it should probably get some special property.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-11-24 17:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87czmr5gr7.fsf.ref@yahoo.com>
2021-11-23 10:05 ` bug#52053: 29.0.50; Nonsensical button "C-x C-f" in scratch buffer Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 6:17 ` Phil Sainty
2021-11-24 7:53 ` Lars Ingebrigtsen
2021-11-24 9:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 10:58 ` Lars Ingebrigtsen
2021-11-24 11:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 11:27 ` Lars Ingebrigtsen
2021-11-24 11:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-24 16:39 ` Lars Ingebrigtsen
2021-11-24 17:05 ` Andreas Schwab [this message]
2021-11-25 0:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-25 13:34 ` Lars Ingebrigtsen
2021-11-26 0:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-26 12:36 ` Lars Ingebrigtsen
2021-11-26 12:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-25 10:23 ` Gregory Heytings
2021-11-25 10:59 ` Eli Zaretskii
2021-11-25 11:07 ` Gregory Heytings
2021-11-25 11:21 ` Eli Zaretskii
2021-11-25 12:47 ` Robert Pluim
2021-11-25 13:20 ` Eli Zaretskii
2021-11-25 13:36 ` Lars Ingebrigtsen
2021-11-25 13:41 ` Gregory Heytings
2021-11-25 14:16 ` Eli Zaretskii
2021-11-25 14:55 ` Gregory Heytings
2021-11-25 15:15 ` Eli Zaretskii
2021-11-25 22:45 ` Gregory Heytings
2021-11-26 6:26 ` Eli Zaretskii
2021-11-26 9:24 ` Robert Pluim
2021-11-26 11:13 ` Eli Zaretskii
2021-11-26 11:17 ` Robert Pluim
2021-11-27 16:06 ` Gregory Heytings
2021-11-27 16:08 ` Gregory Heytings
2021-11-29 13:56 ` Lars Ingebrigtsen
2021-11-29 14:05 ` Eli Zaretskii
2021-11-29 14:13 ` Lars Ingebrigtsen
2021-11-29 17:59 ` Stefan Kangas
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=87sfvlh4b4.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=52053@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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 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).