GNU bug report logs - #12443
24.2.50; Default values in the minibuffer prompt (fix

Previous Next

Package: emacs;

Reported by: Dani Moncayo <dmoncayo <at> gmail.com>

Date: Fri, 14 Sep 2012 14:08:01 UTC

Severity: minor

Found in version 24.2.50

Fixed in version 28.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: Juri Linkov <juri <at> jurta.org>, 12443 <at> debbugs.gnu.org, Stefan Kangas <stefankangas <at> gmail.com>, Dani Moncayo <dmoncayo <at> gmail.com>
Subject: bug#12443: 24.2.50; Default values in the minibuffer prompt (fix inconsisntecy)
Date: Sun, 30 Aug 2020 15:16:12 +0200
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

>>> It seems 'format-prompt' should not use 'minibuffer-default-prompt-format'
>>> when 'default' is nil.
>> nil is a perfectly valid default value in many prompts.
>
> No, `nil` should mean there's no default.
> `"nil"` is a perfectly valid default value, OTOH.

I imagined there was a read-symbol function in use somewhere that used
symbols for completion/defaults, but apparently not -- it's all
completing-read with an intern at the end?

I'll adjust read-prompt to interpret a nil default as "no default".

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no




This bug report was last modified 4 years and 123 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.