<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><BLOCKQUOTE type="cite"></BLOCKQUOTE><DIV>I've read that, and I'm not going to follow its instructions. I rarely ever touch my .MacOSX/environment.plist file, and in this case I refuse to put PATH in there. One reason is because I occasionally change PATH (rarely, but it happens) and I don't like restarting in that case. But the main reason is because I don't want my GUI apps to have my new PATH. If a system-provided app accesses anything via PATH (I don't know why it would, but hey) I want it to get the system-provided tool it's trying to access. Anything I put in /usr/local/bin or /opt/local/bin is purely for me as a user to access, not for system-provided things to access. And that's true even of third-party apps - they were written to use the system tools, so I want to give them the system tools.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>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.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>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.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>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:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>/usr/bin/env ruby <<TM_EOF</DIV><DIV>insert ruby script here</DIV><DIV>TM_EOF</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>On Jan 23, 2007, at 8:42 AM, James Edward Gray II wrote:</DIV><BR><BLOCKQUOTE type="cite"><DIV>On Jan 23, 2007, at 5:37 AM, Kevin Ballard wrote:</DIV><DIV><BR></DIV><DIV>> Move Documentation code into separate file so PATH will be set up </DIV><DIV>> appropriately</DIV><DIV><BR></DIV><DIV>I don't really think this is the way to go. We have a lot of </DIV><DIV>commands like this and you could end up creating files for each and </DIV><DIV>every one. Users might even begin to expect this from us. It also </DIV><DIV>seems silly to have to hunt down an external file, when we just want </DIV><DIV>to see what some simple command does.</DIV><DIV><BR></DIV><DIV>I think it's better to just fix your PATH as described in the </DIV><DIV>"important" paragraph on this page:</DIV><DIV><BR></DIV><DIV><A href="http://macromates.com/textmate/manual/shell_commands#search_path">http://macromates.com/textmate/manual/shell_commands#search_path</A></DIV><DIV><BR></DIV><DIV>Allan has mentioned that he intends to add a PATH setting to TM's </DIV><DIV>preferences, for just this reason. That's probably another good </DIV><DIV>reason for us not to go down this road.</DIV><DIV><BR></DIV><DIV>James Edward Gray II</DIV></BLOCKQUOTE></DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR><DIV> <SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV>-- </DIV><DIV>Kevin Ballard</DIV><DIV><A href="http://kevin.sb.org">http://kevin.sb.org</A></DIV><DIV><A href="mailto:kevin@sb.org">kevin@sb.org</A></DIV><DIV><A href="http://www.tildesoft.com">http://www.tildesoft.com</A></DIV><BR class="Apple-interchange-newline"></SPAN> </DIV><BR></BODY></HTML>