Hi,
I'm currently working on an article, together with some other authors, so we thought it wise to split it up into separate files, and then one main file, where all the others are \input-ed. Works great, and the TM_LATEX_MASTER variable makes life a little bit easier.
However, it turns out that support for this variable is a bit sketchy: - Using a full path in that variable breaks everything. Escaping a full path in quotes breaks it even more. The "Typeset and View" command normally constructs the filename and path itself, and assumes a clean input, but this breaks when the value of TM_LATEX_MASTER is used directly.
- If you just give a filename (and the file is in the project root), then "Typeset and View" can at least build the file. Viewing it breaks, because file://localhost/${TM_LATEX_MASTER%.tex}.pdf can not be found. (the variable is properly expanded in the URL, the file just can't be found)
I tried to look into it, but I couldn't really figure out how to get it to work properly. I hope someone else here has some time and is willing to look at it.
Regards, Jeroen.
I am using a full path like /Users/me/file/path/to/master.tex and all works fine.
Dan
Daniel Käsmayr wrote:
I am using a full path like /Users/me/file/path/to/master.tex and all works fine.
You're right...It even works with a space. My bad..
However, enclosing a full path in quotes does not work, because it just eats off the filename and quote at the end, not the beginning quote.
Jeroen.
On May 17, 2006, at 7:05 AM, Daniel Käsmayr wrote:
I am using a full path like /Users/me/file/path/to/master.tex and all works fine.
I am having no problems with it either. I too use the full path to the file, however this full path does not have any spaces in it, don't know how that would affect things.
In fact I have defined TM_LATEX_MASTER as a global variable, since I am only working on one project right now, and it executes fine even if the project is not even open, but another random tex file is open instead. I use TeXniscope as my previewer.
Dan
Haris
I am having no problems with it either. I too use the full path to the file, however this full path does not have any spaces in it, don't know how that would affect things.
The only thing I'd just bring to 'the fore' is that during my brief flirtation, I think we figured out that spaces in the path to the file broke the pdfsync ability, if nothing else.
-steve
On May 17, 2006, at 10:04 AM, Steve Lianoglou wrote:
The only thing I'd just bring to 'the fore' is that during my brief flirtation, I think we figured out that spaces in the path to the file broke the pdfsync ability, if nothing else.
To be precise: Texniscope currently does not pdfsync if the filenames have spaces. I've contacted the developer of Texniscope and brought this to his attention, and he fixed this and the next version of Texniscope will be working fine with spaces. Not sure when that next version will be though.
-steve
Haris
To be precise: Texniscope currently does not pdfsync if the filenames have spaces. I've contacted the developer of Texniscope and brought this to his attention, and he fixed this and the next version of Texniscope will be working fine with spaces. Not sure when that next version will be though.
Sweet! Did the developer happen to mention, by chance, if it would be universal binary as well :-)
-steve
Haris
-steve
To be precise: Texniscope currently does not pdfsync if the filenames have spaces. I've contacted the developer of Texniscope and brought this to his attention, and he fixed this and the next version of Texniscope will be working fine with spaces. Not sure when that next version will be though.
There will be a next version of TeXniscope? Cool, I already thought development was gone there… the version I could find was ages old. I am lucky it runs in Carbon/Rosetta… ;)
Does it work if Spaces are escaped or encoded?
Dan
On May 17, 2006, at 11:44 AM, Daniel Käsmayr wrote:
There will be a next version of TeXniscope? Cool, I already thought development was gone there… the version I could find was ages old. I am lucky it runs in Carbon/Rosetta… ;)
Well, don't hold me to it, he said that it will be fixed in the next version, didn't say when this version is going to be.
Does it work if Spaces are escaped or encoded?
Eh, were exactly are you going to escape them? :) The problem is not passing the filename to Texniscope, the problem is what texniscope does with it.
Dan
Haris
Charilaos Skiadas wrote:
To be precise: Texniscope currently does not pdfsync if the filenames have spaces. I've contacted the developer of Texniscope and brought this to his attention, and he fixed this and the next version of Texniscope will be working fine with spaces. Not sure when that next version will be though.
Cool! Which reminds me, I have to get back to the developer of latexmk.pl too, for saying that his fix for working with spaces works fine (or has anyone encountered problems?).
We are one heck of LaTeX-for-filenames-with-spaces evangelists! ;)
Jeroen.
-
Charilaos Skiadas -
Daniel Käsmayr -
Jeroen van der Ham -
Steve Lianoglou