From: ndame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "46092@debbugs.gnu.org" <46092@debbugs.gnu.org>
Cc: 53507@debbugs.gnu.org
Subject: bug#53507: 27.1; syntax highlight in the eval-expression prompt
Date: Mon, 24 Jan 2022 17:23:44 +0000 [thread overview]
Message-ID: <XgBlQfRbG-UbY_0-ocN4cJwLNDZ3km7O8xtxxE33dDPDt01QcIYIXO_pXmrCs1bvjYxNmdR6AWmJ2Gs9vuJASzQU3ETQUNO_3kvzE04k-iA=@protonmail.com> (raw)
There is some progress thanks to Stefan who gave a hint on the emacs help list.
There is a check in font-core.el which disables font lock for buffers starting
with a space and the minibuffer is like that:
;; Don't turn on Font Lock mode if we don't have a display (we're running a
;; batch job) or if the buffer is invisible (the name starts with a space).
(when (or noninteractive (eq (aref (buffer-name) 0) ?\s))
(setq font-lock-mode nil))
https://github.com/emacs-mirror/emacs/blob/master/lisp/font-core.el#L133
If one comments these lines, reevalutes the function and then goes to
eval-expression, pastes this code into it:
(progn (setq font-lock-mode t) (emacs-lisp-mode))
and evals this code right there in context (C-x C-e) then the lisp
code in the minibuffer gets font locking.
This is good, the only problem left to solve is that snippet affects
quitting from the minibuffer for some reason.
next reply other threads:[~2022-01-24 17:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 17:23 ndame via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-25 12:52 ` bug#46092: bug#53507: 27.1; syntax highlight in the eval-expression prompt 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 ` 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='XgBlQfRbG-UbY_0-ocN4cJwLNDZ3km7O8xtxxE33dDPDt01QcIYIXO_pXmrCs1bvjYxNmdR6AWmJ2Gs9vuJASzQU3ETQUNO_3kvzE04k-iA=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=46092@debbugs.gnu.org \
--cc=53507@debbugs.gnu.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).