From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: rpluim@gmail.com, emacs-devel@gnu.org
Subject: Re: master 513c5d827d: Use `format-prompt' in
Date: Sat, 03 Sep 2022 12:38:24 +0300 [thread overview]
Message-ID: <83fsh8ol0v.fsf@gnu.org> (raw)
In-Reply-To: <87r10sizhc.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 03 Sep 2022 11:22:39 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Robert Pluim <rpluim@gmail.com>, emacs-devel@gnu.org
> Date: Sat, 03 Sep 2022 11:22:39 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Thanks, but is this supposed to be an improvement? Before the change,
> > I knew what the text meant and what was the "all" part about; after
> > the change, I don't. It's a net loss, since the code is now less
> > readable, and in fact without either running the code or looking at
> > what format-prompt does, one cannot understand what the prompt will
> > say in Real Life.
>
> `format-prompt' isn't about making the code more readable, but allowing
> the users to customise how prompts look. So I don't understand the
> objection -- it's a good change.
I explained why I think it's less than good.
There are two contradictory aspirations here that clash. You seem to
be disregarding one of them.
next prev parent reply other threads:[~2022-09-03 9:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 9:15 master 513c5d827d: Use `format-prompt' in Eli Zaretskii
2022-09-03 9:22 ` Lars Ingebrigtsen
2022-09-03 9:38 ` Eli Zaretskii [this message]
2022-09-03 9:45 ` Lars Ingebrigtsen
2022-09-03 9:56 ` Eli Zaretskii
2022-09-03 15:50 ` [External] : " Drew Adams
2022-09-05 4:04 ` Richard Stallman
2022-09-05 8:26 ` Robert Pluim
2022-09-05 11:42 ` Eli Zaretskii
2022-09-05 11:54 ` Robert Pluim
2022-09-05 12:19 ` Eli Zaretskii
2022-09-05 12:29 ` Robert Pluim
2022-09-05 12:33 ` Eli Zaretskii
2022-09-05 16:02 ` Gregory Heytings
2022-09-05 16:10 ` Robert Pluim
2022-09-06 4:16 ` Richard Stallman
2022-09-06 12:37 ` Eli Zaretskii
2022-09-07 2:23 ` Richard Stallman
2022-09-07 10:03 ` Robert Pluim
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=83fsh8ol0v.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=rpluim@gmail.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).