> Arash Esbati writes:
> Ikumi Keita writes:
>> All right, then my propsal is the attached one.
> Thanks, LGTM.
Thank you, pushed to the git repo.
Bye,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
Hi Keita,
Ikumi Keita writes:
> All right, then my propsal is the attached one.
Thanks, LGTM.
Best, Arash
Hi Arash,
> Arash Esbati writes:
> I'd probably change the last sentence to:
> The second element can also be a variable returning a list of strings.
All right, then my propsal is the attached one.
Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
>From
Hi Keita,
Ikumi Keita writes:
> Looking at multi-prompt.el again, `multi-prompt-expand-completion-table'
> is implemented so as to allow the second element to be a variable.
Ah, yes, that rings a bell :-)
> So how about this alternative?
>
> TABLE is an alist where each entry is a list. The
Hi Arash,
> Ikumi Keita writes:
>> TABLE is an alist. The first element of each list is a string
>> representing a key and the optional second element is a list with
>> strings to be used as values for the key.
>> Does is make sense? Any comments welcome.
> Reasonable. :-)
Looking at
> Arash Esbati writes:
> Good catch :-) I think this should read:
> TABLE is an alist. The first element of each list is a string
> representing a key and the optional second element is a list with
> strings to be used as values for the key.
> Does is make sense? Any comments
Hi Keita,
Ikumi Keita writes:
> Here is a quote from the doc string explaining KEY-VAL-ALIST argument
> of `TeX-read-key-val'. `multi-prompt-key-value' has the same phrase as
> well:
> ,
> | The car of each element should be a string representing a key and
> | the optional cdr should be a
Hi, all
Here is a quote from the doc string explaining KEY-VAL-ALIST argument
of `TeX-read-key-val'. `multi-prompt-key-value' has the same phrase as
well:
,
| The car of each element should be a string representing a key and
| the optional cdr should be a list with strings to be used as
|