[texworks] Still an un resolved problem
jerome.laurens at u-bourgogne.fr
Mon Jul 13 19:28:30 CEST 2009
Le 13 juil. 09 à 11:14, Jonathan Kew a écrit :
>> In short, when MikTeX adds a .tex file extension, it forgets to
>> tell TeX that he did so.
>> Christian Schenk has fixed this in MiKTeX 2.8 Beta 4 (to be
>> released soon).
> Does it also provide the full path? So if \input foo actually caused
> TeX to read c:/some/path/to/texmf/tex/macros/foo.tex, does the
> name_field get updated only to foo.tex, or to the full path? SyncTeX
> needs the full path, as it cannot reliably know the search paths
> that TeX may have been using.
I don't know the complete rules used by MikTeX but it seems that
pdftex just provides a relative name, whereas the texify command
provides a full path.
The synctex parser should be smart enough to deal with both situations
as long as it is fed with the full path when a full path appears in
the synctex output file. At least this is what seems to happen with
Of course, hard coding a full path is not convenient when it comes to
copy or duplicate files.
For example, suppose you gather all your tex, pdf and synctex files in
folder foo1, then make a copy in foo2 and work from foo2.
If you synchronize from the pdf file inside foo2, you will be directed
to the tex source file inside foo1.
I bet this is not what one would expect.
More information about the texworks