From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Unexpected behavior of format-number with format-prompt Date: Thu, 07 Nov 2024 09:57:52 +0200 Message-ID: <86fro3qxvj.fsf@gnu.org> References: <875xp0b00l.fsf@breatheoutbreathe.in> <86h68jqyut.fsf@gnu.org> <3CD02C22-984C-42F7-AAE8-ECD413168503@breatheoutbreathe.in> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10535"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Joseph Turner Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Nov 07 08:58:59 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1t8xPu-0002XU-M5 for ged-emacs-devel@m.gmane-mx.org; Thu, 07 Nov 2024 08:58:58 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t8xPC-0008B7-J0; Thu, 07 Nov 2024 02:58:14 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t8xPA-0008AT-EF for emacs-devel@gnu.org; Thu, 07 Nov 2024 02:58:12 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t8xP7-0000nX-SI; Thu, 07 Nov 2024 02:58:11 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=tNWs3gZRV3GGcK+T8FZfOozUsAIcyvKLFEugD7S+NnI=; b=hcZJwOW8rCnQ wlqy/FyE66WljOzV41qzq+PxynSpjIOAbJE3lcxK4M5fBU0xDodEqDt0pPJOjqxrNsbq7kfa2AVp3 ZlWN3oiw9SEhwITlF+dH6+/ZgHEeQnbU7SWSf8tZqBU8dU5qsw2jDq5Txd5Dp3l3J7h9NBdoyFtWo r3TPqaOxK+SQgCKNCmF9cF44BwyMj5/+3DOS0s9UoMPqi/2cjab76P3FiPlyNrhcNsL9s+QbCk/PM euYEWc35eBFvPMzamZ3zQYN5cVTpMdt9SopZGndd1w3VeZ/UgM5qYO1Oki5DKV5cviZUrGV5Jksc4 giqTsIxvCzcFfmQ7DoZtMw==; In-Reply-To: <3CD02C22-984C-42F7-AAE8-ECD413168503@breatheoutbreathe.in> (message from Joseph Turner on Wed, 06 Nov 2024 23:44:00 -0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:325209 Archived-At: > Date: Wed, 06 Nov 2024 23:44:00 -0800 > From: Joseph Turner > 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?)