I just updated the Latex bundle according to the instruction for bundle updating in the help file. Now the cmd-{ function does not work. Also it cannot find TeXniscope: /bin/bash: line 60: find_app: command not found Error locating external viewer: TeXniscope The shell variable TM_LATEX_VIEWER is correctly set.
All this worked fine until a moment ago. What has happened? I issued the commands: christopher-brewsters-computer:/Library/Application Support/TextMate/ Bundles kiffer$ svn --username anon --password anon co http:// macromates.com/svn/Bundles/trunk/Bundles/Latex.tmbundle
Christopher
***************************************************** Natural Language Processing Group, Department of Computer Science, University of Sheffield
Dear Christopher,
If you had already checked out the bundle from subversion, all you needed to do is: svn up *.tmbundle
Best, Mark
On 19 Sep 2006, at 17:26, Christopher Brewster wrote:
I just updated the Latex bundle according to the instruction for bundle updating in the help file. Now the cmd-{ function does not work. Also it cannot find TeXniscope: /bin/bash: line 60: find_app: command not found Error locating external viewer: TeXniscope The shell variable TM_LATEX_VIEWER is correctly set.
All this worked fine until a moment ago. What has happened? I issued the commands: christopher-brewsters-computer:/Library/Application Support/ TextMate/Bundles kiffer$ svn --username anon --password anon co http://macromates.com/svn/Bundles/trunk/Bundles/Latex.tmbundle
Christopher
Natural Language Processing Group, Department of Computer Science, University of Sheffield
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
HI Christopher, On Sep 19, 2006, at 12:26 PM, Christopher Brewster wrote:
I just updated the Latex bundle according to the instruction for bundle updating in the help file. Now the cmd-{ function does not work. Also it cannot find TeXniscope: /bin/bash: line 60: find_app: command not found Error locating external viewer: TeXniscope
The problem is likely that you have not updated the global support directory. You would need to check that out as well I think. It is under: http://macromates.com/svn/Bundles/trunk/Support/ And of course as Mark said, you should only be doing this if you haven't checked these things out before. Otherwise, you should be doing an “svn up”.
It might be possible that you now have two different LaTeX language grammars in your computer. Check the language popup and see. Also do a ctrl-shift-P to se the scope in a LaTeX document. The basic scope should now be text.tex.latex
If you have customized any of these commands, then you might have to remove/edit those customizations. If you open the Bundle editor and look at the "Environment Based on Current Word" command what does it show as "Scope Selector"? We've recently just renamed everything, so while before the scope for all LaTeX commands was text.latex, now it is text.tex.latex. (There were very good reasons for this change). So those command will possibly have to be changed if they have local modifications, depending on when those local modifications were made.
The shell variable TM_LATEX_VIEWER is correctly set.
All this worked fine until a moment ago. What has happened? I issued the commands: christopher-brewsters-computer:/Library/Application Support/ TextMate/Bundles kiffer$ svn --username anon --password anon co http://macromates.com/svn/Bundles/trunk/Bundles/Latex.tmbundle
Christopher
Natural Language Processing Group, Department of Computer Science, University of Sheffield
Haris
On 19 Sep 2006, at 18:10, Charilaos Skiadas wrote:
HI Christopher, On Sep 19, 2006, at 12:26 PM, Christopher Brewster wrote:
I just updated the Latex bundle according to the instruction for bundle updating in the help file. Now the cmd-{ function does not work. Also it cannot find TeXniscope: /bin/bash: line 60: find_app: command not found Error locating external viewer: TeXniscope
The problem is likely that you have not updated the global support directory. You would need to check that out as well I think. It is under: http://macromates.com/svn/Bundles/trunk/Support/ And of course as Mark said, you should only be doing this if you haven't checked these things out before. Otherwise, you should be doing an “svn up”.
Problem solved now. Thanks - it behaves as before.
It might be possible that you now have two different LaTeX language grammars in your computer. Check the language popup and see. Also do a ctrl-shift-P to se the scope in a LaTeX document. The basic scope should now be text.tex.latex
If you have customized any of these commands, then you might have to remove/edit those customizations. If you open the Bundle editor and look at the "Environment Based on Current Word" command what does it show as "Scope Selector"? We've recently just renamed everything, so while before the scope for all LaTeX commands was text.latex, now it is text.tex.latex. (There were very good reasons for this change). So those command will possibly have to be changed if they have local modifications, depending on when those local modifications were made.
All this is as it should be. However, what you said you had changed (in a previous mailing) does not show up, i.e.
I actually just went ahead and committed these two changes. For general reference for people not familiar with it, I've appended all the shortcuts used by the cmd-{ command at the moment. New shortcuts are added every now and then, and you suggestions would be welcomed.
Haris
it = '\textit{$1} '; bf = '\textbf{$1} '; tt = '\texttt{$1} ';
etc.
When I write: it <cmd-{> I get : \begin{itemize} \item \end{itemize}
and with 'em' I get: \begin{em} \end{em}
and with ctr-shift-w, I get \emph{} ^^^^^ with the 'emph' highlighted.
Any thoughts,
Christopher
On Sep 19, 2006, at 1:55 PM, Christopher Brewster wrote:
and with ctr-shift-w, I get \emph{} ^^^^^ with the 'emph' highlighted.
Yes, this is as it should be, so that you can overwrite the command. Pressing tab should take you inside the braces.
I'll respond to the other one in the other thread.
Any thoughts,
Christopher
Haris