On Jun 13, 2012, at 11:03 AM, Tim Gray wrote: > It's probably wiser to call MacVim from the command line instead of calling > the default OS X vim from the command line. This is because some of your > plugins and settings that you use for MacVim might depend on features built > into MacVim that aren't enabled in the version of vim bundled with OS X. The > OS X default vim doesn't have python, perl, or ruby support enabled, which > some plugins make use of. Also note, depending on your version of OS X, > Apple doesn't always include the most up to date copy of vim, while your > MacVim should be fairly recent. > > You can call MacVim from the command line several different ways. The > easiest is probably to just create an alias in your .bashrc: > > alias vim='/Applications/MacVim.app/Contents/MacOS/Vim' > > Alternately, you can use the 'mvim' script that comes with MacVim. It's a > shell script that looks for an calls MacVim in command line mode. Drop it > somewhere that's in your path and just type 'mvim' on the prompt.
Thanks for the heads up, Tim. And for the explanations of how to call vim from the command line. ------------------------------------------------------------------------------------------ Eric Weir Decatur, GA [email protected] "What is man without the beasts? If all the beasts were gone, men would die from a great loneliness of spirit." - Chief Seattle -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
