12/31/2023 0 Comments Cellar macvim![]() Right, really, so it's a bug in how Mac OS X is set up. Looks like it's caused by /etc/zshenv, which calls path_helperįor all zsh invocations, not just login shell invocations. So when zsh is used by Vim to run external commands we have the > Why the difference between the $PATHs? The second form is what > :!echo $PATH => ($PATH from /etc/paths)+($PATHs from /etc/paths.d/*)+($PATH from. > appear to be created in the following way: > with vim, gvim and gvim launched from the terminal, and the paths > (seems like I hadn't fixed anything after all), so I did some tests > Coincidentally, today I had some problems involving wrong paths on vim Is there any way to change this behaviour? The only way to make $HOME/bin to take precedence would be to add the full path to /etc/paths, which doesn't look right. Why the difference between the $PATHs? The second form is what path_helper returns. :!echo $PATH => ($PATH from /etc/paths)+($PATHs from /etc/paths.d/*)+($PATH from. Can you try changing your shell back to bash and see if you still have the same problems?Ĭoincidentally, today I had some problems involving wrong paths on vim (seems like I hadn't fixed anything after all), so I did some tests with vim, gvim and gvim launched from the terminal, and the paths appear to be created in the following way: > I changed my shell in the Accounts Preference Pane, which I'm assuming > set MMLoginShellCommand for MacVim and I'm still having the same exact ![]() > On Feb 17, 2011, at 1:54 PM, Wes Baker wrote: When in the terminal and I echo $PATH, I get this (edited to make it aīit more in MacVim (using mvim) and I type !echo $PATH, I get for a bit of added fun, when opening MacVim from the Applications As part ofĮxport PATH=/usr/local/Cellar/python/2.7.1/bin:/usr/local/bin: Maybe this is because this issue is from 2011, but I'm not finding it works for my JRuby usage.I'm using zsh and I'm using oh-my-zsh to set everything. Thanks a lot for the info, that is an amazing speed improvement for me! discussion #9 Heck, you could probably even get away with: if !empty($MY_RUBY_HOME) That also eliminates the dependence on the shell. I'd do if !empty(matchstr($MY_RUBY_HOME, 'jruby')) G:ruby_path is supposed to be comma separated (although spaces do work for backwards compatibility reasons). Let g:ruby_path=system('echo $MY_RUBY_HOME/lib/ruby/')ĭo you see anything wrong with this? discussion #7 This is my workaround: if !empty(matchstr(system('rvm current'), 'jruby')) If that still isn't enough, you can disable the load path querying entirely by setting g:ruby_path in your vimrc. My Mac currently reports that it takes about 125 ms, a significant improvement over what you're seeing. Just days ago, I significantly improved the speed of this by dropping the querying of Ruby Gems. The delay is attributable to ftplugin/ruby.vim querying the Ruby load path. discussion #4Īctually, I realized that the slowdown was happening because of another plugin: syntastic. Reply to this email directly or view it on GitHub:Īre you using jruby? I definitely see a slowdown when I'm using jruby with rvm. Your output correctly, taking the least amount of time to load of theĪh you are right I misread the output indeed, so it isįtplugin/ruby.vim that is taking a while to load. Is taking a long time? The indent/ruby.vim file is, if I understand Here is some relevant output where you can see how long it takes to load and when it jumps on loading the indent file:Ģ19.092 003.356 003.356: sourcing /Users/markmulder/.vim/syntax/ruby.vimĪm I missing something, or do you mean that the ftplugin/ruby.vim file I was just wondering if others are experiencing this as well. In my situation loading the ruby indent file is taking a very long time. I've been trying to see what could cause it with the -startuptime flag: mvim -startuptime vim.out file.rb When I open a ruby file it takes a (relatively) very long while before Vim is fully loaded.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |