Note that there are some explanatory texts on larger screens.

plurals
  1. POThe 'New File' function is not working in Textmate. Are shell variables to blame?
    text
    copied!<p>I can't create new files from within Textmate. I'm not sure why it's doing this or how to go about fixing it.</p> <p>I recently changed the "Shell Variables" because certain functions weren't working like the "Comment Line" ⌘/, and other stuff. It would say something like </p> <pre><code>env: ruby: no such file or directory </code></pre> <p>Ruby 1.8 is installed in <code>/opt/local/bin/ruby</code>. I recently installed Ruby 1.9 through RVM, but I was just following directions and don't know where it is installed, or if it is even being used.</p> <p><img src="https://i.stack.imgur.com/fy2ZQ.png" alt="Here is what my Shell Variables currently look like"></p> <p>I don't really know much about path dependencies and such. I searched for "<code>ruby</code>" in the Finder and there are 16 folders titled "ruby" or "Ruby", but they all stem from that original path <code>/opt/local/bin/ruby</code>. What should I do to get Textmate working again? Is it something to do with where I have Ruby installed?</p> <p>I followed the instructions on "<a href="http://michaelfarmer.info/blog-101" rel="nofollow noreferrer">TextMate 'env: ruby: No such file or directory'</a>" when trying to fix the "Comment Selection" function in TextMate.</p> <hr> <p>UPDATE:</p> <p>I just found on the "<a href="http://wiki.macromates.com/Troubleshooting/TextMateAndThePath" rel="nofollow noreferrer">TextMateAndThePath</a>" page on Textmate's help wiki that</p> <blockquote> <p>There can be many files named ruby on the system, but only one file can exist at the path /usr/bin/ruby</p> </blockquote> <p>When I run <code>type ruby</code> at the command line, it returns two <code>/opt/local/bin/ruby</code> paths. Is this what is breaking Textmate, and if so what can I do about it?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload