From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ndame <laszlomail@protonmail.com>,
"46092@debbugs.gnu.org" <46092@debbugs.gnu.org>,
53507@debbugs.gnu.org
Subject: bug#53507: bug#46092: bug#53507: 27.1; syntax highlight in the eval-expression prompt
Date: Wed, 26 Jan 2022 01:16:52 +0100 [thread overview]
Message-ID: <87fspbqrkb.fsf@web.de> (raw)
In-Reply-To: <87fspcx9hz.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 25 Jan 2022 13:52:56 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> So I don't think there's anything to be done on the Emacs side here, but
> perhaps I'm misunderstanding what this report is about?
Do we want to support syntax highlighting in eval-expression by default?
I would vote for it.
Michael.
next prev parent reply other threads:[~2022-01-26 0:16 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 ` bug#46092: " Michael Heerdegen
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 ` Michael Heerdegen [this message]
2022-01-26 14:41 ` bug#46092: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fspbqrkb.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 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.