I think that the Latex Watch is experimenting problems after the upgrades in
TM 2. To be sure, I need to know how do I correctly set the TM_LATEX_MASTER
in the .tm_properties file.
I was using TM_LATEX_MASTER = foo.tex
It is not working anymore. I tried:
TM_LATEX_MASTER = 'foo.tex'
TM_LATEX_MASTER = "foo.tex"
TM_LATEX_MASTER = /foo.tex
TM_LATEX_MASTER = '/foo.tex'
TM_LATEX_MASTER = "/foo.tex"
TM_LATEX_MASTER = ./foo.tex
What should I do?
View this message in context: http://textmate.1073791.n5.nabble.com/TM-LATEX-MASTER-and-Latex-Watch-tp267…
Sent from the textmate users mailing list archive at Nabble.com.
While I appreciate the desire to bring rmate into the rubygem fold, it
presents some difficulties.
Prior, I could install rmate into ~/bin on any machine I had ssh access to,
quickly and easily by copying the guts of the script. This let me minimize
my impact on remote machines that I needed to work on. (FWIW, I do most of
my work on client machines of, let's say, older vintage, with extremely
locked down environments. rmate is my secret sauce.)
Now, I find myself needing to install rubygems on the remote machine, just
to keep working, and without admin access.
In the interest of retaining my remaining hair, what's the quick and dirty
way of installing rmate on remote machines now, when one does not have
admin rights to do a simple install of rubygems?
% rmate mpp
/work/users/jsmith/bin/rmate:12:in `require': no such file to load -- rmate
[ install rubygems in ~/bin ]
% gem install rmate
/work/users/jsmith/bin/gem:8:in `require': no such file to load -- rubygems
% printenv GEM_HOME