For example, if a third-party app wants to use ruby, I want it to use the system-provided ruby. If I want to use ruby I'll use my MacPorts- installed version, but I'm deliberately choosing to do that.
And yeah, I know that this is a slippery slope, but I finally edited this command like such simply because I kept trying to use ⌃H and having it fail, over and over. It was getting really annoying using ri from the command-line.
Incidentally, if your only worry is a bunch of extra files, there is a technique which can avoid the extra file. I just threw in the extra file because it's cleaner to do it this way, but if people want to avoid the shebang and still call, say, ruby, you can always do the following:
/usr/bin/env ruby <<TM_EOF insert ruby script here TM_EOF On Jan 23, 2007, at 8:42 AM, James Edward Gray II wrote:
On Jan 23, 2007, at 5:37 AM, Kevin Ballard wrote: > Move Documentation code into separate file so PATH will be set up > appropriately I don't really think this is the way to go. We have a lot of commands like this and you could end up creating files for each and every one. Users might even begin to expect this from us. It also seems silly to have to hunt down an external file, when we just want to see what some simple command does. I think it's better to just fix your PATH as described in the "important" paragraph on this page: http://macromates.com/textmate/manual/shell_commands#search_path Allan has mentioned that he intends to add a PATH setting to TM's preferences, for just this reason. That's probably another good reason for us not to go down this road. James Edward Gray II
-- Kevin Ballard http://kevin.sb.org [EMAIL PROTECTED] http://www.tildesoft.com
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ textmate-dev mailing list [email protected] http://lists.macromates.com/mailman/listinfo/textmate-dev
