2013/11/6 Tassilo Horn <[email protected]>: > Mads Jensen <[email protected]> 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. Bye, Mosè _______________________________________________ auctex-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/auctex-devel
