Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy does shell output/settings differ when being executed from MacVim as opposed to the Terminal
    primarykey
    data
    text
    <p>When using Vim, you can shell out via</p> <pre><code>:!&lt;command_name&gt; </code></pre> <p>Here's my problem.</p> <p>I've got my current Ruby set to</p> <pre><code>ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.4.0] </code></pre> <p>This is the output from</p> <pre><code>ruby -v </code></pre> <p>in Terminal.app or simply the terminal.</p> <p>Once I load up MacVim and type</p> <pre><code>:!ruby -v </code></pre> <p>I get</p> <pre><code>ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-darwin11.2.0] </code></pre> <p>Where is Vim getting it's context from?</p> <p>It does not appear to be honoring my settings specified in <code>.zshrc</code>. None of those settings appear to loaded or taking affect. I even created a function to source my dotfile via the command line</p> <pre><code>:!source ~/.zshrc </code></pre> <p>and to no avail!</p> <p>I don't understand what the heck is going on here. I'm running into an issue because Vim is using Ruby 1.9.3p0, but RVM is set to a different Ruby. This is of course breaking any calls to Rails.</p> <pre><code>/usr/lib/ruby/1.9.1/rubygems.rb:314:in `bin_path': can't find gem rails (["&gt;= 0"]) with executable rails (Gem::GemNotFoundException) from /usr/bin/rails:19:in `&lt;main&gt;' shell returned 1 </code></pre> <p>Can someone tell me how to override this?</p> <p>Even my version of rails differs in Vim verses the terminal.</p> <pre><code># Terminal output which rails # prints - /Users/adubb/.rvm/gems/ruby-1.9.3-p194/bin/rails # Vim/MacVim output :!which rails # prints - /usr/bin/rails </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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