I've tested the new MacTex beta with TextMate+Skim+synctex (with pdflatex, xelatex, and latex (with and without the latexmk.pl script)) and it all works well on my research articles and exam files. Synctex seems to do a slightly better job than pdfsync, in my setup.
Regards, David
Hi David,
I'm very glad to hear it, but it doesn't quite work over here so I want to make sure we are talking about the same thing. When you compile a file in TextMate, it should automatically take you to the corresponding page. Using the "Show in PDF (pdfsync)" command works fine (though we should probably rename it now, to omit the (pdfsync) part), as does syncing from pdf to code, but the automatic syncing on compile doesn't for me. Does that part work for you?
Brad, I am guessing this is because of the differences between sync_viewer and run_viewer? I am seeing a TODO there to make them work better with each other. I am guessing this is where the problems are? That the code using run_viewer checked for pdfsync explicitly, and hence was missing this new synctex stuff?
On Aug 14, 2008, at 3:50 PM, Snyder, David F wrote:
I've tested the new MacTex beta with TextMate+Skim+synctex (with pdflatex, xelatex, and latex (with and without the latexmk.pl script)) and it all works well on my research articles and exam files. Synctex seems to do a slightly better job than pdfsync, in my setup.
Regards, David
Haris Skiadas Department of Mathematics and Computer Science Hanover College
On Aug 14, 2008, at 3:50 PM, Snyder, David F wrote:
I've tested the new MacTex beta with TextMate+Skim+synctex (with pdflatex, xelatex, and latex (with and without the latexmk.pl script)) and it all works well on my research articles and exam files. Synctex seems to do a slightly better job than pdfsync, in my setup.
Syncing seems to work perfectly for me now too, since Brad's latest commit. Nice work Brad!
On a related note, we've been having an off-list discussion as to whether we should have a preference setting to allow the user to say "I know synctex is cool and all that, but I just don't want it used". Would that be something people would want? Currently if your tex engine supports synctex, it will be used no matter what. With pdfsync this was less of an issue, since you have to specify the \include {pdfsync} statement, hence the user had a chance to turn it on and off, should they wish to. In the case of pdfsync it was also more critical, since there were slight layout changes when it was used. My understanding is that this is not the case for synctex, which makes it less clear whether it would still be useful for users to disable it. Hence the reason for this email, to get people's views on the matter.
Regards, David
Haris Skiadas Department of Mathematics and Computer Science Hanover College
On Friday, August 15, 2008, at 09:49AM, "Charilaos Skiadas" cskiadas@gmail.com wrote:
On a related note, we've been having an off-list discussion as to whether we should have a preference setting to allow the user to say "I know synctex is cool and all that, but I just don't want it used". Would that be something people would want? Currently if your tex engine supports synctex, it will be used no matter what. With pdfsync this was less of an issue, since you have to specify the \include {pdfsync} statement, hence the user had a chance to turn it on and off, should they wish to. In the case of pdfsync it was also more critical, since there were slight layout changes when it was used. My understanding is that this is not the case for synctex, which makes it less clear whether it would still be useful for users to disable it. Hence the reason for this email, to get people's views on the matter.
You can explicitly enable synctex in a TeX source file with \synctex=1, so requiring that would be possible; I prefer enabling it via the command line, since that allows easy sharing of .tex files with collaborators using older TeX systems. Personally, I don't care to have it disabled, and the only reason I can see for disabling it is to avoid creating the synctex file (which isn't much of a reason, given all the other temporary files that LaTeX et al. create).
On 16/08/2008, at 2:43 AM, Adam R. Maxwell wrote:
Personally, I don't care to have it disabled, and the only reason I can see for disabling it is to avoid creating the synctex file (which isn't much of a reason, given all the other temporary files that LaTeX et al. create).
For what it's worth, I agree with Adam. No need to clutter the interface with an option that turns off something you're not using :)
Cheers, Will
-
Adam R. Maxwell -
Charilaos Skiadas -
Snyder, David F -
Will Robertson