Tassilo Horn <[email protected]> writes:
> Julien Cubizolles <[email protected]> writes:
>
> Hi Julien,
>
>>> Of course, now your metalabels aren't matched anymore, too. But you
>>> can easily add a new entry that is a copy of the default entry for
>>> keyval labels with "meta" prepended to "label".
>>
>> I'm actually having trouble adding the following entry:
>>
>> \[[^]]*\<\(meta\)?label[[:space:]]*=[[:space:]]*{?\(?1:[^],}]+\)}?
>>
>> I tested it with regexp-builder, it correctly matches the
>> metalabel={...} entries in my file.
>>
>> But whether I add it through customize or with a (setq ...) command,
>> it doesn't seem to get picked up when I refresh the TOC buffer, either
>> through r or R.
>
> Oh, yes. You have to call (reftex-compile-variables) afterwards to make
> the change effective. So in Lisp, this works for me.
>
> (add-to-list 'reftex-label-regexps
>
> "\\[[^]]*\\<metalabel[[:space:]]*=[[:space:]]*{?\\(?1:[^],}]+\\)}?")
> (reftex-compile-variables)
That's ok for me too, I just need to use eval-after-load 'reftex in my
.emacs file
> I've just committed a fix in emacs bzr. With that, if you change the
> variable with customize, then `reftex-compile-variables' will be called
> automatically.
That's useful too.
>> \begin{tikzpicture}
>> \node [label={\RayonArc:$\theta$}] at (\AngleMilieu:\RayonArc) {};
>> \node [shape = vector out,label=left:$\vvEz $] {};
>> \end{tikzpicture}
>
> Ah, that's unfortunate. reftex actually doesn't know anything about
> environments, so it's not even possible to skip some of them right
> now...
That's what I thought, and rewriting the regexp to explicitely exclude
some environments doesn't seem quite right.
_______________________________________________
auctex mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/auctex