I have started looking into hyperrefs induced by term references, ... and they are quite off.
The main culprit seems to be the one in the title: here is an example.
If we have a file FOO.tex:
then this reports the module@ID: FOO in the log file.
But \module@id is used in the references and the change causes havoc.
I do not remember what I had done to prevent this in the past, I suspect that I put the code in the \input called in the \importmodule into a {} group, since we only need it for the global side-effects. But when I look at \@importmodule, there seems to be a group, ... so I do not quite understand.
Ah, I think I know what I must do.
in metakeys, I had used gdefs for the keys, but the global is too aggressive.
But before I commit something as drastic as this, I will have to test more.
I have started looking into hyperrefs induced by term references, ... and they are quite off. The main culprit seems to be the one in the title: here is an example. If we have a file
FOO.tex
:and a file
test.tex
then this reports the
module@ID: FOO
in the log file. But\module@id
is used in the references and the change causes havoc.I do not remember what I had done to prevent this in the past, I suspect that I put the code in the
\input
called in the\importmodule
into a{}
group, since we only need it for the global side-effects. But when I look at\@importmodule
, there seems to be a group, ... so I do not quite understand.