Is there a reason TextMate copies mate into the user's $PATH instead of just making a symlink to the command inside the Application's resources?
What dangers do I run if I do decide to symlink it? (As part of a system configuration bootstrap script. I could copy it, but it would be a little more work.)
Thanks, Neil.
Is there a reason TextMate copies mate into the user's $PATH instead of just making a symlink to the command inside the Application's resources?
Yeah, I was about to ask the same :)
What dangers do I run if I do decide to symlink it? (As part of a system configuration bootstrap script. I could copy it, but it would be a little more work.)
Well I have it symlinked anyway (rather than copied using Preferences) and it works like a charm for long time already.
Cheers,
Alright, I'm going to do that. Seems saner. >.>
On Wed, Oct 31, 2012 at 2:28 AM, Adam Strzelecki ono@java.pl wrote:
Is there a reason TextMate copies mate into the user's $PATH instead of
just making a symlink to the command inside the Application's resources?
Yeah, I was about to ask the same :)
What dangers do I run if I do decide to symlink it? (As part of a system
configuration bootstrap script. I could copy it, but it would be a little more work.)
Well I have it symlinked anyway (rather than copied using Preferences) and it works like a charm for long time already.
Cheers,
Adam Strzelecki | nanoant.com | twitter.com/nanoant
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Oct 31, 2012, at 10:21 AM, Neil kngspook@gmail.com wrote:
Is there a reason TextMate copies mate into the user's $PATH instead of just making a symlink to the command inside the Application's resources?
The original reason was that mate was copied from the bundle support folder, which I didn’t feel was a good destination for a symlink.
But another reason is to have ‘mate’ still work if user rename or move TextMate.app.
Didn’t happen a lot with 1.x (which uses a symlink) but it did happen, and it seemed like a lot of users rename the alphas to “TextMate 2”.
TextMate 2 will keep the installed ‘mate’ executable up-to-date. So nothing is really gained by the symlink (other than maybe satisfying an aesthetic preference).
How does mate work if TM2 is moved/renamed? Is it finding the location of the app in a plist somewhere?
On Thu, Nov 1, 2012 at 7:40 PM, Allan Odgaard mailinglist@textmate.orgwrote:
On Oct 31, 2012, at 10:21 AM, Neil kngspook@gmail.com wrote:
Is there a reason TextMate copies mate into the user's $PATH instead of
just making a symlink to the command inside the Application's resources?
The original reason was that mate was copied from the bundle support folder, which I didn’t feel was a good destination for a symlink.
But another reason is to have ‘mate’ still work if user rename or move TextMate.app.
Didn’t happen a lot with 1.x (which uses a symlink) but it did happen, and it seemed like a lot of users rename the alphas to “TextMate 2”.
TextMate 2 will keep the installed ‘mate’ executable up-to-date. So nothing is really gained by the symlink (other than maybe satisfying an aesthetic preference).
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On Nov 2, 2012, at 10:12, Neil kngspook@gmail.com wrote:
How does mate work if TM2 is moved/renamed? Is it finding the location of the app in a plist somewhere?
It asks launch services to launch the application (based on the bundle identifier), you should be able to move and rename the app all you want.