Am 11.03.2006 um 17:28 schrieb Christian Bogen:
Am 11.03.2006 um 17:16 schrieb Charilaos Skiadas:
I thought we had resolved all these issues by using: ~/bin/mate or in general the path to mate as the editor command, and %file -l %line as the editor arguments. Are you having problems with files with spaces under these conditions?
Well, I'm using ›open‹ as editor command and ›"txmt://open? url=file://%file&line=%line"‹ as argument in TeXniscope but I also had tried the mate command (which resides in /usr/local/bin on my system, but surely can't make a difference -- yes, it is included in $PATH in .profile …) and it made no difference for me. Nothing happened when I command-clicked in TeXniscope if the path and/or file name contains spaces.
I suspected that TeXniscope simply doesn't correctly escape the spaces …
Addendum: I've just tried it again to be sure (with the /usr/local/ bin/mate and %file -l %line in TeXniscope and it even seems to be broken both ways with a path/file name containing spaces. When I hit ctrl-select-command-o in TextMate focus shifts to TeXniscope but that's about it -- not green marker appears and it doesn't jump to the page. Command-clicking in TeXniscope on the other hand actually produces the error messages »Warning This document do not have syncronization info.« (Which is a lie! ;)
Once I remove the spaces from the directory and file name again, everything works as expected!
Chris