GNU bug report logs - #53507
27.1; syntax highlight in the eval-expression prompt

Previous Next

Full log

View this message in rfc822 format

From: ndame <laszlomail <at> protonmail.com>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: Michael Heerdegen <michael_heerdegen <at> web.de>, "53507 <at> debbugs.gnu.org" <53507 <at> debbugs.gnu.org>, "larsi <at> gnus.org" <larsi <at> gnus.org>, "46092 <at> debbugs.gnu.org" <46092 <at> debbugs.gnu.org>
Subject: bug#53507: [External] : bug#53507: 27.1; syntax highlight in the eval-expression prompt
Date: Thu, 27 Jan 2022 03:08:28 +0000

>  Font-locking a sexp you're typing isn't very
>   important.

It may not be important for you, because you type
only simple expressions into eval-expression , but
others can use it differently.

I often paste multiline elisp snippets (e.g. 8-10
lines) into eval-expression which operate on the
current buffer (transforming content, etc). I'm
most of the time interestested in buffer changes,
not the result of the expression.

Such a snippet often needs small tewakings depending
on the current buffer content. In this case I
retrieve the snippet from the history of the eval
expression prompt and edit it right the in the
minibuffer.

When editing multiline snippets there, font locking
is important, because it makes it easier to read the
code (strings, etc.), just like in case of code  in
regular elisp buffers.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.