Re: [External] : Re: Operating the HIST feature of completing-read

[carlmarcos]

Jul 13, 2022, 02:04 by bugs@gnu.support:

> * carlmarcos@tutanota.com <carlmarcos@tutanota.com> [2022-07-13 04:16]:
>
>>
>> Jul 12, 2022, 16:40 by drew.adams@oracle.com:
>>
>> >> Does the history remember the user input associated
>> >> with each specific completing-read call?
>> >>
>> >
>> > Only each specific history variable.
>> >
>> > If each `completing-read' (or `read-from-minibuffer'
>> > or whatever) call used a different history variable
>> > then the answer to your question would be yes.
>> >
>>
>> Have done as suggested 
>>
>> (defvar myhist nil
>>   "Stores previous minibuffer inputs so the user can reuse them.")
>>
>>   (let* ( (cseq '("bracemk" "expression" "extended" "mixed" "hlsexp" 
>> "disable"))
>>           (csel  (completing-read "Glowvis: " cseq nil t "mixed" myhist 
>> "extended"))
>> nn
>> When I go through the list in the minibuffer I am also getting the variable 
>> myhist
>> showing up but its value stays nil.
>>
>
> It should be 'myhist instead of myhist in completing-read
>
> Jean
>

Thanks Jean.  After doing that I am quite unsure how to figure out whether I am 
seeing the completing list or the history entries.