From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: rms@gnu.org, drew.adams@oracle.com, larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: [External] : Re: master 513c5d827d: Use `format-prompt' in
Date: Mon, 05 Sep 2022 15:19:50 +0300 [thread overview]
Message-ID: <831qsqko7t.fsf@gnu.org> (raw)
In-Reply-To: <87pmgadojz.fsf@gmail.com> (message from Robert Pluim on Mon, 05 Sep 2022 13:54:24 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: rms@gnu.org, drew.adams@oracle.com, larsi@gnus.org, emacs-devel@gnu.org
> Date: Mon, 05 Sep 2022 13:54:24 +0200
>
> >>>>> On Mon, 05 Sep 2022 14:42:58 +0300, Eli Zaretskii <eliz@gnu.org> said:
>
> Eli> That part is fine, but the fact that using format-prompt splits the
> Eli> prompt text into two seemingly unrelated parts is a disadvantage, IMO.
> Eli> I wonder if we can do something about that, given that this function
> Eli> was released with Emacs 28.
>
> Are you suggesting something like
>
> (format-prompt "Prompt##all")
>
> which splits on "##"? That would be ugly.
I didn't suggest anything concrete. However, one possibility would be
to teach format-prompt to accept keyword arguments.
next prev parent reply other threads:[~2022-09-05 12:19 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
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 [this message]
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=831qsqko7t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.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).