I just upgraded TextMate today, but it didn't have the usual includes (the service and the bin/ applications). Now running "tm" says, "tm: you need to update this helper tool (server at version 2)." How can I get the latest version of these extras?
James Edward Gray II
On Oct 6, 2005, at 8:11 AM, James Edward Gray II wrote:
I just upgraded TextMate today, but it didn't have the usual includes (the service and the bin/ applications). Now running "tm" says, "tm: you need to update this helper tool (server at version 2)." How can I get the latest version of these extras?
I ran into that this morning, too. I found a copy of the mate command (which replaces 'tm' due to closeness to 'rm') in the Contents/ Resources directory of TextMate's package. Copying this to /usr/local/ bin made my machine happy again.
On Oct 6, 2005, at 10:19 AM, Gavin Kistner wrote:
On Oct 6, 2005, at 8:11 AM, James Edward Gray II wrote:
I just upgraded TextMate today, but it didn't have the usual includes (the service and the bin/ applications). Now running "tm" says, "tm: you need to update this helper tool (server at version 2)." How can I get the latest version of these extras?
I ran into that this morning, too. I found a copy of the mate command (which replaces 'tm' due to closeness to 'rm') in the Contents/Resources directory of TextMate's package. Copying this to /usr/local/bin made my machine happy again.
To future-proof this, what you actually want is:
ln -s /path/to/TextMate.app/Contents/Resources/mate /usr/local/bin/ mate
Per this release note:
[NEW] The 'mate' shell command is now contained in the TextMate.app bundle (under Contents/Resources). So I encourage you to delete what you previously installed in ~/bin (or maybe /usr/bin) and instead use a symbolic link, e.g.: ln -s /Applications/TextMate.app/ Contents/Resources/mate ~/bin/mate. That way, if the command is updated in the future, you will get this update as part of the TM auto-updating mechanism (I'll likely give TM the capability to create this link in the future).
Chris
On 06/10/2005, at 16.11, James Edward Gray II wrote:
I just upgraded TextMate today, but it didn't have the usual includes (the service and the bin/ applications). Now running "tm" says, "tm: you need to update this helper tool (server at version 2)." How can I get the latest version of these extras?
It's now named 'mate' and, from the release notes:
The 'mate' shell command is now contained in the TextMate.app bundle (under Contents/Resources). So I encourage you to delete what you previously installed in ~/bin (or maybe /usr/bin) and instead use a symbolic link, e.g.: ln -s /Applications/TextMate.app/Contents/Resources/mate ~/bin/ mate. That way, if the command is updated in the future, you will get this update as part of the TM auto-updating mechanism (I'll likely give TM the capability to create this link in the future).
On Oct 6, 2005, at 9:21 AM, Allan Odgaard wrote:
It's now named 'mate'
Why?
-- __ ____ / / / __/ Brian Lalor "If you still have gas, you're not lost." / _ /__ \ blalor@bravo5.org -- Jacques Strappe /_.__/____/ http://bravo5.org/
Some of us had already had to rename the script or create a symlink to it. My fingers know "rm" far too well to risk trying to learn "tm". Thanks to cvs I haven't lost any files, but I came close! I like the new name and that is it now embedded in the .app file. Are the TM guys thinking of an installer that creates the symlink for you?
-Eric
On Oct 6, 2005, at 12:53 PM, Brian Lalor wrote:
On Oct 6, 2005, at 9:21 AM, Allan Odgaard wrote:
It's now named 'mate'
Why?
-- __ ____ / / / __/ Brian Lalor "If you still have gas, you're not lost." / _ /__ \ blalor@bravo5.org -- Jacques Strappe /_.__/____/ http://bravo5.org/
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 06/10/2005, at 20.01, Eric Knapp wrote:
[...] Are the TM guys thinking of an installer that creates the symlink for you?
Yes, just need to figure out what's best.
E.g. probably only makes sense to ask if the application is installed (rather than running from a disk image), and maybe not ask the first time a user runs the application (since he wouldn't know if he'd want it yet). And also provide a way for the user to maybe create it later and or inspect what was what done… and personally I favor ~/bin but that doesn't exist by default, and thus would also need to be added to the PATH… a lot to think about :)
On Oct 6, 2005, at 3:01 PM, Allan Odgaard wrote:
[...] Are the TM guys thinking of an installer that creates the symlink for you?
Yes, just need to figure out what's best.
E.g. probably only makes sense to ask if the application is installed (rather than running from a disk image), and maybe not ask the first time a user runs the application (since he wouldn't know if he'd want it yet). And also provide a way for the user to maybe create it later and or inspect what was what done… and personally I favor ~/bin but that doesn't exist by default, and thus would also need to be added to the PATH… a lot to think about :)
You'd probably just want an entry in preferences. Maybe a toggle for enable/disable, and another pref for installation location? And maybe a third toggle for installing mate_wait as well. Of course, I'd also want it renamed to tm (and tm_wait). And this is starting to sound a bit complicated...
On Thu, Oct 6, at 2:01 PM, Allan Odgaard wrote:
On 06/10/2005, at 20.01, Eric Knapp wrote:
[...] Are the TM guys thinking of an installer that creates the symlink for you?
Yes, just need to figure out what's best.
E.g. probably only makes sense to ask if the application is installed (rather than running from a disk image), and maybe not ask the first time a user runs the application (since he wouldn't know if he'd want it yet). And also provide a way for the user to maybe create it later and or inspect what was what done… and personally I favor ~/bin but that doesn't exist by default, and thus would also need to be added to the PATH… a lot to think about :)
Please do not hardcode it to ~/bin. If you want to introduce a unixy kind of hierarchy in the users directory, it should rather be ~/ something/bin, because when you think about it you also want ~/ something/man, ~/something/lib, ~/something/include, ~/something/etc and so on, and I would rather not have all those directories cluttering up my home directory. 'something' happens to be 'Unix' on my system, and I bet other folks system found any number of different names for that.
Also /usr/bin, /usr/local/bin, /opt/bin and others might all be candidates, but I know of a number of companies that have conflicting policies about how those directories should be used.
In short an installer may suggest a location, but the user should be able to edit it. And it should probably be noted in the preferences system, so when the next TM installer comes along it can find it.
Gerd
On 06/10/2005, at 23.51, Gerd Knops wrote:
[...] Are the TM guys thinking of an installer that creates the symlink for you?
Yes, just need to figure out what's best. [...]
Please do not hardcode it to ~/bin. If you want to introduce a unixy kind of hierarchy in the users directory, it should rather be ~/something/bin, because when you think about it you also want ~/ something/man, ~/something/lib, ~/something/include, ~/something/ etc and so on, and I would rather not have all those directories cluttering up my home directory.
I could show a popup with the (potential) destinations harvested by doing something like this (of course adding Other… as last option):
bash --login -c '{ tr <<<$PATH : \n|grep "^$HOME.*/bin$" [[ -e /usr/local/bin ]] && echo /usr/local/bin [[ -e /opt/bin ]] && echo /opt/bin echo /usr/bin; }'
Probably double-checking the result (inserting separator) to avoid users MOTD and similar (since I'll be running a login shell).
As for setting the name of the link (kevin), I think expert users will just have to rename it themselves (and/or skip this “wizard”) -- the main point of the automation is really just to make the user aware, that there's a bundled shell command.
[...] when the next TM installer comes along it can find it.
Hopefully with the symbolic link, there won't be a next time :)
Too close to rm.
On Oct 6, 2005, at 11:53 AM, Brian Lalor wrote:
On Oct 6, 2005, at 9:21 AM, Allan Odgaard wrote:
It's now named 'mate'
Why?
-- __ ____ / / / __/ Brian Lalor "If you still have gas, you're not lost." / _ /__ \ blalor@bravo5.org -- Jacques Strappe /_.__/____/ http://bravo5.org/
______________________________________________________________________ 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 6 oct. 05, at 19:53, Brian Lalor wrote:
On Oct 6, 2005, at 9:21 AM, Allan Odgaard wrote:
It's now named 'mate'
Why?
Some people sometimes typed rm instead of tm. To be honest, it's not my case, but anyway, "fixing" it is easy:
ln -s /path/to/TextMate.app/Contents/Resources/mate /usr/local/bin/tm
or
ln -s /path/to/TextMate.app/Contents/Resources/mate ~/bin/tm
-
Allan Odgaard -
Brian Lalor -
Chris Thomas -
Eric Knapp -
Fred B. -
Gabe da Silveira -
Gavin Kistner -
Gerd Knops -
James Edward Gray II -
Kevin Ballard