GNU bug report logs - #38317
Buffer-local variables don't work as history for read-from-minibuffer

Previous Next

Full log

Message #44 received at 38317 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Federico Tedin <federicotedin <at> gmail.com>
Cc: larsi <at> gnus.org, 38317 <at> debbugs.gnu.org
Subject: Re: bug#38317: Buffer-local variables don't work as history for
 read-from-minibuffer
Date: Wed, 27 Nov 2019 21:25:00 +0200

> From: Federico Tedin <federicotedin <at> gmail.com>
> Date: Wed, 27 Nov 2019 19:50:00 +0100
> Cc: 38317 <at> debbugs.gnu.org
> 
> Thanks. In what part of the manual would you document this? I was
> thinking of either in:
> 
> 1) The "Minibuffer History" section (but it doesn't mention the actual
> HIST variable anywhere in there, though, and never mentions any specific
> minibuffer-reading function)

That section does mention the history variables, and even includes a
list of them.  So I'm not sure why you say it doesn't.

> Should I update the docstring for `read-from-minibuffer' as well? I
> would like to add two things: that the value can be buffer-local, and
> that the newly read item will be added to the history list.

That it adds to the history is worth mentioning, but the fact that it
can be buffer-local we don't normally say explicitly, because it's
expected to "just work".

Previous Next

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