From: Eli Zaretskii <eliz@gnu.org>
To: Joseph Turner <joseph@breatheoutbreathe.in>
Cc: emacs-devel@gnu.org
Subject: Re: Unexpected behavior of format-number with format-prompt
Date: Thu, 07 Nov 2024 09:57:52 +0200 [thread overview]
Message-ID: <86fro3qxvj.fsf@gnu.org> (raw)
In-Reply-To: <3CD02C22-984C-42F7-AAE8-ECD413168503@breatheoutbreathe.in> (message from Joseph Turner on Wed, 06 Nov 2024 23:44:00 -0800)
> Date: Wed, 06 Nov 2024 23:44:00 -0800
> From: Joseph Turner <joseph@breatheoutbreathe.in>
> CC: emacs-devel@gnu.org
>
> >First, this should have been sent to our issue tracker, via
> >report-emacs-bug or submit-emacs-patch.
>
> Got it. Shall I do this now?
Too late. Please remember this for the future.
> >More to the point: we cannot possibly change the behavior of
> >read-number in such a backward-incompatible way. Especially since
> >this behavior is old, and explicitly called out in the doc string. It
> >is perhaps unfortunate that read-number behaves differently in this
> >manner, but I'm afraid we will have to live with this.
>
> That makes sense. Can we apply the info manual change?
I think this change should be in the doc string of read-number, not in
the manual. One reason is that read-number is not documented in the
manual, while the description of this nit logically belongs to it, not
to format-prompt. (Btw, the same effect could be achieved if
minibuffer-default-prompt-format is bound to the empty string, right?)
next prev parent reply other threads:[~2024-11-07 7:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 20:06 Unexpected behavior of format-number with format-prompt Joseph Turner
2024-11-07 7:36 ` Eli Zaretskii
2024-11-07 7:44 ` Joseph Turner
2024-11-07 7:57 ` Eli Zaretskii [this message]
2024-11-09 19:18 ` Joseph Turner
2024-11-14 8:29 ` Eli Zaretskii
2024-11-07 13:50 ` Stephen Berman
2024-11-07 14:47 ` Eli Zaretskii
2024-11-07 15:57 ` Stephen Berman
2024-11-09 19:02 ` Joseph Turner
2024-11-09 21:51 ` Stephen Berman
2024-11-10 3:55 ` Joseph Turner
2024-11-10 10:37 ` Stephen Berman
2024-11-10 5:46 ` Eli Zaretskii
2024-11-10 10:40 ` Stephen Berman
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=86fro3qxvj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joseph@breatheoutbreathe.in \
/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).