From: Michael Heerdegen <michael_heerdegen@web.de>
To: 46092@debbugs.gnu.org
Cc: laszlomail@protonmail.com, larsi@gnus.org, 53507@debbugs.gnu.org
Subject: bug#46092: bug#53507: 27.1; syntax highlight in the eval-expression prompt
Date: Wed, 26 Jan 2022 01:13:40 +0100 [thread overview]
Message-ID: <87k0enqrpn.fsf@web.de> (raw)
In-Reply-To: <CoSacQ_nKi-HqQExm9ToPbhAO6KVTp1lRSYskpPODhNV6tMUP1PoU2258xzQC7GU5QWzGAnDk4KRjBwC5QlUzJ2gX95KRioeHZfQI4K9PtY=@protonmail.com> (ndame via's message of "Tue, 25 Jan 2022 13:17:49 +0000")
ndame via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> In order to highlight elisp in eval-expression I changed the major
> mode of the minibuffer to emacs-lisp-mode. Is that the reason?
> If not so then what is? If so then why is changing the mode stops
> C-g from working there?
C-g is part of the mode that is normally active in the minibuffer,
`minibuffer-mode'.
Michael.
next prev parent reply other threads:[~2022-01-26 0:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 17:23 bug#53507: 27.1; syntax highlight in the eval-expression prompt ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-25 12:52 ` bug#46092: " Lars Ingebrigtsen
2022-01-25 13:17 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-25 13:23 ` bug#46092: " Lars Ingebrigtsen
2022-01-25 13:28 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-26 0:13 ` Michael Heerdegen [this message]
2022-01-26 6:14 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-26 19:53 ` bug#46092: [External] : " Drew Adams
2022-01-26 23:39 ` Michael Heerdegen
2022-01-27 0:06 ` bug#53507: " Drew Adams
2022-01-27 3:08 ` bug#46092: " ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-27 3:19 ` bug#53507: " Drew Adams
2022-01-27 9:28 ` ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-27 23:44 ` bug#46092: " Drew Adams
2022-01-26 0:16 ` bug#53507: bug#46092: " Michael Heerdegen
2022-01-26 14:41 ` Lars Ingebrigtsen
2022-01-26 16:39 ` bug#53507: " Michael Heerdegen
2022-01-27 15:34 ` Lars Ingebrigtsen
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=87k0enqrpn.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=46092@debbugs.gnu.org \
--cc=53507@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=laszlomail@protonmail.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).