> Arash Esbati writes:
>> Alternatively, one could view the contents of "|...|" as a "required
>> argument" and extend the string display spec folding to work with
>> "|...|" in addition to "{...}", but I don't see the immediate payoff
>> from doing so.
> What do others think?
It seems a rea
Hi Paul,
Paul Nelson writes:
> I just realized that my earlier patch
> 8db1e90b6d25beb72b5ebbc706b6def64794dcf8 broke key-binding support for
> auto-reveal (i.e., using left/right rather than C-f/b to open previews
> and folds). The attached patch remedies this. Details below.
Thanks. I have
Hi Arash,
> Thanks. I have one question: Is it possible to set the LEXICAL argument
> of `eval' to t?
If I understand correctly, your suggestion is to use something like
the following?
(defcustom preview-auto-reveal
'(eval . ((apply #'preview-arrived-via
(mapcar (la
Paul Nelson writes:
>> Thanks. I have one question: Is it possible to set the LEXICAL argument
>> of `eval' to t?
>
> If I understand correctly, your suggestion is to use something like
> the following?
Yes, plus the one addition below.
> (defcustom preview-auto-reveal
> '(eval . ((apply
