From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: ndame <laszlomail@protonmail.com>,
"larsi@gnus.org" <larsi@gnus.org>,
"46092@debbugs.gnu.org" <46092@debbugs.gnu.org>,
"53507@debbugs.gnu.org" <53507@debbugs.gnu.org>
Subject: bug#53507: [External] : bug#53507: 27.1; syntax highlight in the eval-expression prompt
Date: Thu, 27 Jan 2022 00:06:15 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488B3C24B6E35F8921FC907F3219@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <878rv2m5hs.fsf@web.de>
> A part that currently is not that well covered in the
> minibuffer, in my opinion, is multi-line expression editing.
I suppose just multiline editing is the main thing
that needs love - i.e., independent of what the
input might be.
As for multiline Lisp expression editing (as opposed
to better support for multiline input in general), I
guess what you mean is support for indentation and
operations on sexps, e.g. motion. And you mentioned
font-locking. Is there something more than that?
___
But as for `eval-expression' enhancements, I repeat
that IMO the main need for improvement is wrt the
output. I think it's far more common to deal with a
complex output value than it is to input a complex
sexp for evaluation.
You'll no doubt point out that if we had better
input support users would use `M-:' to evaluate
more complex sexps. ;-)
Still, I think it'll remain the case that complex
sexps are eval'd more often in other ways (e.g.
`C-x C-e'), and that complex sexps will continue to
be more common on output than on input.
___
Yes, my comments here are no doubt a bit of a
distraction from the request - sorry. But we could
have better treatment of the output immediately.
And we could bind `M-:' to `pp-eval-expression' by
default, now.
next prev parent reply other threads:[~2022-01-27 0:06 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 ` Drew Adams [this message]
2022-01-27 3:08 ` 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=SJ0PR10MB5488B3C24B6E35F8921FC907F3219@SJ0PR10MB5488.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 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).