Re: One-off history for read-string

[Stefan Monnier]

> Is it fine to use a temporary, let-bound variable name as the HISTORY
> parameter, or is there a better way for a "history" I only need to read
> from, not to write to?

It's probably OK, but do declare this variable with (defvar <myvar>)
since it shouldn't be lexically bound

Note also that if the user uses nested minibuffers, she may have two
such commands active at the same time, so you may need to generate the
symbol dynamically rather than always use the same symbol.


        Stefan