Hello,
Yesterday I decided to give TeXniscope a try after watching the screencasts from Haris (btw, great screencasts!)
I have a problem making TextMate using TeXniscope though. I have set the TM_LATEX_VIEWER variable to TeXniscope, and in TeXniscope I have set the editor command path to /usr/local/bin/mate and the editor arguments to %file -l %line.
When I typeset the document, TeXniscope doesn't open at all and the log window shows this message:
****************************************** Compiling LaTeX...
This is pdfeTeXk, Version 3.141592-1.20a-2.2 (Web2C 7.5.3) Typesetting: ./test.tex
Document Class: article 2004/02/16 v1.4f Standard LaTeX document class Typesetting: ./test.aux) (/usr/local/teTeX/share/texmf.tetex/tex/context/base/supp-pdf.tex
Output written on test.pdf (1 page, 20593 bytes).
test.log
Success 2006-03-08 08:59:20.072 open[11309] LSOpenFromURLSpec() returned -10827 for application TeXniscope path /Users/geir/Desktop/test.pdf. 2006-03-08 08:59:20.074 open[11309] Couldn't open file: /Users/geir/Desktop/test.pdf ******************************************
The document I'm trying here is a fresh document from the article template.
Any idea of a solution for this?
(TeXniscope version 0.3.4, and TextMate version 1.5(906))
-- Mvh/Regards Geir-Tore Lindsve lindsve@bluezone.no http://privat.bluezone.no/lindsve
On Mar 8, 2006, at 2:16 AM, Geir-Tore Lindsve wrote:
Hello,
Hi Geir-Tore,
Yesterday I decided to give TeXniscope a try after watching the screencasts from Haris (btw, great screencasts!)
thanks! They were very fun to make.
Success 2006-03-08 08:59:20.072 open[11309] LSOpenFromURLSpec() returned -10827 for application TeXniscope path /Users/geir/Desktop/test.pdf. 2006-03-08 08:59:20.074 open[11309] Couldn't open file: /Users/geir/Desktop/test.pdf
(TeXniscope version 0.3.4, and TextMate version 1.5(906))
Your setup seems alright. A couple of things to try: 1) Have you actually run TeXniscope directly first? If so, do it now and then try again. 2) Have you spelt the variable with correct capitalization? (i.e. TeXniscope) 3) Where does TeXniscope.app reside? If it is not in ~/Applications/ or /Applications/ then move it there and try again. In any case, tell us what the path is. 4) Can you open the pdf by ctrl-clicking on it and choosing to open it with the application Texniscope.app? 5) Open the application Console.app and see if there are any relevant messages there.
-- Mvh/Regards Geir-Tore Lindsve lindsve@bluezone.no http://privat.bluezone.no/lindsve
Good luck, Haris
Den 8. mar. 2006 kl. 09.34 skrev Charilaos Skiadas:
Your setup seems alright. A couple of things to try:
- Have you actually run TeXniscope directly first? If so, do it
now and then try again.
Running (TeXniscope is, not I ;-) )
- Have you spelt the variable with correct capitalization? (i.e.
TeXniscope)
Copied directly from the preference pane:
Variable: TM_LATEX_VIEWER Value: TeXniscope
- Where does TeXniscope.app reside? If it is not in ~/
Applications/ or /Applications/ then move it there and try again. In any case, tell us what the path is.
/Applications/TeXniscope.app
- Can you open the pdf by ctrl-clicking on it and choosing to open
it with the application Texniscope.app?
Yes, that works fine
- Open the application Console.app and see if there are any
relevant messages there.
No messages in Console.app during these operations, and not in console.log either.
I even downloaded the two apps and ran fresh copies of them too, without better results. -- Mvh/Regards Geir-Tore Lindsve lindsve@bluezone.no http://privat.bluezone.no/lindsve
On 8/3/2006, at 9:16, Geir-Tore Lindsve wrote:
Success 2006-03-08 08:59:20.072 open[11309] LSOpenFromURLSpec() returned -10827 for application TeXniscope path /Users/geir/Desktop/test.pdf. 2006-03-08 08:59:20.074 open[11309] Couldn't open file: /Users/geir/Desktop/test.pdf
Try open a terminal and then run:
open -a TeXniscope /Users/geir/Desktop/test.pdf
That should effectively be what TM ends doing, and what seems to produce the error above.
Den 8. mar. 2006 kl. 12.52 skrev Allan Odgaard:
On 8/3/2006, at 9:16, Geir-Tore Lindsve wrote:
Success 2006-03-08 08:59:20.072 open[11309] LSOpenFromURLSpec() returned -10827 for application TeXniscope path /Users/geir/Desktop/test.pdf. 2006-03-08 08:59:20.074 open[11309] Couldn't open file: /Users/geir/Desktop/test.pdf
Try open a terminal and then run:
open -a TeXniscope /Users/geir/Desktop/test.pdf
That should effectively be what TM ends doing, and what seems to produce the error above.
Came a bit closer to the issue here now.
Running the above command in Terminal produced the same result, so I tried to run:
open -a TeXniscope
which also produced the error (with path=(null), most likely because I didn't add more parameters).
Running this:
open -a /Applications/TeXniscope.app
works fine though. Running the same command as above (without / Applications/) works on other applications.
Any idea what is wrong here? -- Mvh/Regards Geir-Tore Lindsve lindsve@bluezone.no http://privat.bluezone.no/lindsve
On 8/3/2006, at 13:26, Geir-Tore Lindsve wrote:
Running this: open -a /Applications/TeXniscope.app works fine though. Running the same command as above (without / Applications/) works on other applications.
In that case, you could set the variable to the full path.
Any idea what is wrong here?
Your launch services database likely has two entries for TeXniscope, the first one being bogus.
You can reset the database by running:
/System/Library/Frameworks/ApplicationServices.framework/ Frameworks/LaunchServices.framework/Support/lsregister -kill -r / System/Library/CoreServices /Applications /Developer/Applications
The last path is only if you have the dev-tools installed. After having reset it, you will get a warning the first time you open an application indirectly by opening the document (if it hasn’t been started before). This is no bigie, just so you now…
Maybe you have an old version moved to the trash. Emptying the trash would help.
Stan.
2006-03-08 08:59:20.072 open[11309] LSOpenFromURLSpec() returned -10827 for application TeXniscope path /Users/geir/Desktop/test.pdf. 2006-03-08 08:59:20.074 open[11309] Couldn't open file: /Users/geir/Desktop/test.pdf
Finally find a solution. It seems that my Launch Services cache was corrupt, and it works after reseting it by using this tip:
http://www.macosxhints.com/article.php?story=20031215144430486
It doesn't seem to by fully optimal though. It varies a lot whether pdfsync information are included (tried \usepackage{pdfsync} on several documents with no results, but using it on the article template works. Some documents doesn't open at all when using command- b, but works from other manual ways. Weird, but these are other issues which I'm going to investigate further.
Thanks for all your tips. -- Mvh/Regards Geir-Tore Lindsve lindsve@bluezone.no http://privat.bluezone.no/lindsve
Am 08.03.2006 um 20:22 schrieb Geir-Tore Lindsve:
It doesn't seem to by fully optimal though. It varies a lot whether pdfsync information are included (tried \usepackage{pdfsync} on several documents with no results, but using it on the article template works. Some documents doesn't open at all when using command-b, but works from other manual ways. Weird, but these are other issues which I'm going to investigate further.
I had some issues with TeXniscope and pdfsync, too. TeXniscope seems to have problems if the pdf file name and/or the path to the pdf contains spaces. At least the pdfsync-ability from TeXniscope to TextMate seems to be broken if the path contains spaces. (It still works the other way round in that case, though.)
HTH!
Christian
On Mar 11, 2006, at 10:01 AM, Christian Bogen wrote:
I had some issues with TeXniscope and pdfsync, too. TeXniscope seems to have problems if the pdf file name and/or the path to the pdf contains spaces. At least the pdfsync-ability from TeXniscope to TextMate seems to be broken if the path contains spaces. (It still works the other way round in that case, though.)
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?
HTH!
Christian
Haris
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 …
Christian
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
On Mar 11, 2006, at 10:41 AM, Christian Bogen wrote:
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! ;)
huh, you are right it is still broken. Not much we can do though I think, other than avoid spaces in the path name of the file. It seems to be in TeXniscope's hands. I emailed the developer, and if we are lucky he might have a workaround to suggest.
Chris
Haris
huh, you are right it is still broken. Not much we can do though I think, other than avoid spaces in the path name of the file. It seems to be in TeXniscope's hands. I emailed the developer, and if we are lucky he might have a workaround to suggest.
Howdy.
First off, Charis: Thanks for those LaTeX screen casts ... gave me the gumption to finally stop being lazy and give LaTeX a try over the weekend ... was able to use it to actually submit a project -- even though I burned like an hour trying to figure out why it wouldn't compile a few times .. sometimes the error messages aren't so handy ;-)
Second .. maybe more on topic .. is there any way we could use TeXShop as the LaTeX previewer ... since I'm pretty sure it deals w/ pdfsync, might be something to look into.
I did a quick search in the archive and found someone talking about just using the Tiger pdfsearch instead of pdfsync -- not sure exactly if that superscedes pdfsync in that I like the ctrl-cmd-shift-o shortcut to jump to the current place from your textmate doc to the TeXniscope pdf .. maybe it does, I have no idea.
Otherwise, the no-space-document-path + TeXniscope is working for me in the meanwhile, though I like the fact that TeXShop is universal.
cheers, -steve
On Mar 12, 2006, at 5:43 PM, Steve Lianoglou wrote:
figure out why it wouldn't compile a few times .. sometimes the error messages aren't so handy ;-)
I know what you mean :) Well, the error messages are a bit better on the command line actually. Textmate seems to chop off some of the key lines.
Second .. maybe more on topic .. is there any way we could use TeXShop as the LaTeX previewer ... since I'm pretty sure it deals w/ pdfsync, might be something to look into.
You can easily use TeXShop as the previewer, it's as easy as setting the TM_LATEX_VIEWER variable to it. On the other hand, though TeXShop does an admirable job with syncing among its own windows, it doesn't seem to have the infrastructure to support an outside editor in that manner. It has no interface that I can see for specifying to it what command to execute and how to pass the parameters of file and line etc. Maybe someone with more knowledge of TeXShop can help us here.
I did a quick search in the archive and found someone talking about just using the Tiger pdfsearch instead of pdfsync -- not sure exactly if that superscedes pdfsync in that I like the ctrl-cmd- shift-o shortcut to jump to the current place from your textmate doc to the TeXniscope pdf .. maybe it does, I have no idea.
I personally don't see much reason in using Tiger pdfsearch when we have a platform independent solution, and I don't see what more it would get us, or how we would go about using it. The problem here how to tell TeXShop what editor to call back.
Otherwise, the no-space-document-path + TeXniscope is working for me in the meanwhile, though I like the fact that TeXShop is universal.
cheers, -steve
Haris
On Mar 12, 2006, at 6:43 PM, Charilaos Skiadas wrote:
On Mar 12, 2006, at 5:43 PM, Steve Lianoglou wrote:
figure out why it wouldn't compile a few times .. sometimes the error messages aren't so handy ;-)
I know what you mean :) Well, the error messages are a bit better on the command line actually. Textmate seems to chop off some of the key lines.
If you would send me examples of those errors that TextMate chops off, I will be glad to fix the bugs in my script that produces the html output from latex.
Brad
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Mar 12, 2006, at 6:53 PM, Brad Miller wrote:
If you would send me examples of those errors that TextMate chops off, I will be glad to fix the bugs in my script that produces the html output from latex.
I don't have any in mind at the moment, but I will send you when I encounter them. One example is for instance, that if I misspell a LaTeX command, it will silently ignore it and compile, with no messages, while if I was compiling from the command line it would have waited for my input, with something like:
! Undefined control sequence. l.6 ...deserunt mollit anim id est laborum. \singf {2}
That {2} is supposed to be vertically positioned right below and to the right of \singf, the actual sentence in the document being:
deserunt mollit anim id est laborum. \singf{2}
In this case no error is reported (at least in my system). In other situations where it is reported, one doesn't usually get to see all three lines. I'll send you a more specific example when I have one.
Brad
Haris
Den 11. mar. 2006 kl. 17.41 skrev Christian Bogen:
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
That is the same experience here. I have spaces in almost all of my document folders so the paths will end up with spaces in them. I guess that is why it worked when I tried it with the test document which where located in ~\Desktop. -- Mvh/Regards Geir-Tore Lindsve lindsve@bluezone.no http://privat.bluezone.no/lindsve
-
Allan Odgaard -
Brad Miller -
Charilaos Skiadas -
Christian Bogen -
Geir-Tore Lindsve -
Soryu -
Steve Lianoglou