Hello,
I have tried to figure out why pdfsync was not working with my (large and multiple file) thesis tex project. I figured out, that pdfsync has to be included from the main tex file and NOT from a stylefile (i.e a custum made thesis.sty that includes pdfsync...). This is not a big deal, but maybe it could be fixed so that texMate.py would find pdfsync there too...
Thanks Chris
On Mar 28, 2008, at 10:02 AM, Christopher Frauenberger wrote:
Hello,
I have tried to figure out why pdfsync was not working with my (large and multiple file) thesis tex project. I figured out, that pdfsync has to be included from the main tex file and NOT from a stylefile (i.e a custum made thesis.sty that includes pdfsync...). This is not a big deal, but maybe it could be fixed so that texMate.py would find pdfsync there too...
Hm, I suppose that would require our parser search into all packages included in the main file, and any packages they load, and so on. Not sure how I feel about that. Presumably we would need to also scan inside the cls file in that case?
Perhaps we could put a switch in the preference to force TM to assume that pdfsync is in place? Not very efficient though.
Thanks Chris
Haris Skiadas Department of Mathematics and Computer Science Hanover College
On 28/03/2008, Charilaos Skiadas cskiadas@gmail.com wrote:
Hm, I suppose that would require our parser search into all packages included in the main file, and any packages they load, and so on. Not sure how I feel about that. Presumably we would need to also scan inside the cls file in that case?
Why can't we just check for existence of the foo.pdfsync file, after compilation?
Robin
On Mar 28, 2008, at 7:28 PM, Robin Houston wrote:
On 28/03/2008, Charilaos Skiadas cskiadas@gmail.com wrote:
Hm, I suppose that would require our parser search into all packages included in the main file, and any packages they load, and so on. Not sure how I feel about that. Presumably we would need to also scan inside the cls file in that case?
Why can't we just check for existence of the foo.pdfsync file, after compilation?
Because it might have been left there from a previous time, when the pdfsync package was included, but then removed (I often do that). In that case, the sync file will be "out of sync", if you pardon the expression.
We could check for the modification dates though, make sure that the pdfsync file is current.
Robin
Haris Skiadas Department of Mathematics and Computer Science Hanover College
-
Charilaos Skiadas -
Christopher Frauenberger -
Robin Houston