Dear users of the textmate bundle for Latex,
I'm using the "Watch Document" command (is latex_watch.pl in version 2.8) in textmate to have my masters thesis always up-to-date when I change something in the tex file and hit save.
Since a few days this doesn't work as before, cause I'm running in a closed loop. When textmate starts watching my main document (the thesis is splitted in several files) it successfully compiles the document with pdflatex and displays me the result in my preferred viewer Skim. But after having done this it recompiles the whole file again and then reloads the file in Skim.
This is pretty annoying behaviour, cause I haven't changed anything in the main file, also it takes loads of cpu, speeds the macbooks fans up and is constantly refreshing Skim.
Wether there is a bug of "latex_watch.pl" or it observes a file which is updated through the initial and every following compilation and therefore runs in a closed loop.
I tried two versions of the latex.tmbundle so far. I think one was the original one which came with textmate and the other one was the one from the svn repository as of yesterday. Both show the same behaviour.
My question is now. How can I analyze the problem (closed loop). Is there a way to put the latex.tmbundle in debug mode so I can see some log messages? I tried this already by specifing the projects variable "TM_LATEX_WATCH_DEBUH = dialog" but without any success. I didn't found the debug output on my disk.
What are other ways? Whats are your advice?
Many Thanks,
Jan
2008/6/26 Jan Michael jan.michael@gmail.com:
Since a few days this doesn't work as before, cause I'm running in a closed loop. When textmate starts watching my main document (the thesis is splitted in several files) it successfully compiles the document with pdflatex and displays me the result in my preferred viewer Skim. But after having done this it recompiles the whole file again and then reloads the file in Skim.
It definitely should not do this!
If you can't diagnose the problem yourself (see below), perhaps you could send me a copy of your project so I can try and track it down. If you can cut it down to a minimal example, that would be even better.
Wether there is a bug of "latex_watch.pl" or it observes a file which is updated through the initial and every following compilation and therefore runs in a closed loop.
From your description, it is definitely a bug in latex_watch. You are
probably right about the cause of it, too. I would guess that the compilation process is changing a file, which is triggering a new compilation, and so on. My code is supposed to detect this situation and not go into a loop, but it sounds as though it isn't working correctly with your document.
My question is now. How can I analyze the problem (closed loop). Is there a way to put the latex.tmbundle in debug mode so I can see some log messages? I tried this already by specifing the projects variable "TM_LATEX_WATCH_DEBUH = dialog" but without any success. I didn't found the debug output on my disk.
If you set TM_LATEX_WATCH_DEBUG (I assume your version was a typo!) to anything at all, debugging messages will be printed to the system console. Early versions had an option to display debugging messages in a series of dialog boxes, which it looks as though you were trying to invoke, but that option no longer exists. You can see these messages using /Applications/Utilities/Console.app. They should tell you why the project is being recompiled, so you should be able to tell which file it thinks has changed.
Let me know what you find. Sorry about the problem.
Robin
It turns out that Jan's problem was caused by a bad interaction with the svn-multi package. My code didn't cope correctly with the situation where a file is read in during the processing of the preamble and written out during the processing of the document body.
The attached update seems to fix the problem. Perhaps someone with commit access could update the LaTeX bundle with this new code?
Thanks, Robin
-
Jan Michael -
Robin Houston