[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [AUCTeX-devel] About commonly used and "expert" macros/environments

From: Mosè Giordano
Subject: Re: [AUCTeX-devel] About commonly used and "expert" macros/environments (was: auctex-devel Digest, Vol 103, Issue 2)
Date: Wed, 6 Nov 2013 23:50:58 +0100

2013/11/6 Tassilo Horn <address@hidden>:
> Mads Jensen <address@hidden> writes:
> Hi Mads and all,
>>> That should not be a criterion for being less helpful.  It might be
>>> an argument to divide stuff into two classes, like file completion
>>> does: you can still complete on ignored files if your prefix rules
>>> out any non-ignored file.
>> I like the idea about having some variable to discard some macros from
>> the completion.
> Yes, me too.

And me too.

> But I'm not sure which way to tackle that.  The cheapest
> solution was to have a new defcustom `TeX-include-advanced-macros/envs'
> which would either be t (include all commands) or a list of package
> names whose advanced commands to include.  Then we also had a function
> (defun TeX-include-advanced-macros/envs-p (style)
>   (cond
>    ((null TeX-include-advanced-macros/envs) nil)
>    ((listp TeX-include-advanced-macros/envs)
>     (member style TeX-include-advanced-macros/envs))
>    (t t)))
> Using that, style files could do:
>   ;; The commonly used macros and environments
>   (TeX-add-symbols ...)
>   (LaTeX-add-environments ...)
>   ;; The stuff only expert users of a package will use
>   (when (TeX-include-advanced-macros/envs "this-style")
>     (TeX-add-symbols ...)
>     (LaTeX-add-environments ...))
> Does that sound reasonable to anyone?  If noone objects, I'll implement
> it that way.

Your suggestion looks good to me, I didn't manage to come up with a
better solution.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]