From: Drew Adams <drew.adams@oracle.com>
To: ndame <laszlomail@protonmail.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
"53507@debbugs.gnu.org" <53507@debbugs.gnu.org>,
"larsi@gnus.org" <larsi@gnus.org>,
"46092@debbugs.gnu.org" <46092@debbugs.gnu.org>
Subject: bug#53507: [External] : bug#53507: 27.1; syntax highlight in the eval-expression prompt
Date: Thu, 27 Jan 2022 03:19:56 +0000 [thread overview]
Message-ID: <CO6PR10MB5473E38AD455452F26176AA4F3219@CO6PR10MB5473.namprd10.prod.outlook.com> (raw)
In-Reply-To: <Ri_9w3z98napHyQgd4sQmFXDg5IPIVi5HhlEA23FadNG9y7RnQYT2z-blrnwnViZYCj7HebnuPnS6aD4jpASs0vHPdm68knYUAi013c1JV8=@protonmail.com>
> > 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 meant that, relative to the need for
reasonable support of the _output_
(examination, editing, undo), it's less
important, IMO.
But I wandered from the topic by bringing
up the output. Sorry for that.
> 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.
Yes, that's a reasonable use case as well.
Personally, even when I use `M-:' mainly for
a side effect, I'm often interested in the
resulting value as well.
The `M-:' dialog could be improved in both
ways. And a start for output enhancement
is to bind it to `pp-eval-expression' by
default, instead of `eval-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.
I understand.
> 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.
Yes, understood.
next prev parent reply other threads:[~2022-01-27 3:19 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 ` Drew Adams [this message]
2022-01-27 9:28 ` bug#53507: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CO6PR10MB5473E38AD455452F26176AA4F3219@CO6PR10MB5473.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=46092@debbugs.gnu.org \
--cc=53507@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=laszlomail@protonmail.com \
--cc=michael_heerdegen@web.de \
/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.