Comments on: Improving mvim for MacVim

By: andy

andy — Fri, 23 Mar 2012 02:33:29 +0000

Is there any reason you wouldn’t want to just do an: alias mvim=”open -a MacVim” in your .profile?
Just tried it out and it works great for me!

By: Nicolas

Nicolas — Sat, 22 Oct 2011 11:45:51 +0000

Hey,

not sure this would be the right place to ask but it seems like you have a better understanding of this script than I do..

Whenever invoking MacVim thru the terminal via the mvim command, I get a errors detected while processing menu.vim. MacVim starts but i have to press enter a couple of times to clear the errors and be able to use the terminal again.. Would you have any idea how to stop these ?

Thanks,

Nicolas

By: Kim Holburn

Kim Holburn — Sat, 24 Sep 2011 02:43:25 +0000

Here's my version of that first loop that is more complete. I don't know if all the strange bash characters will work. You can always use open -a MacVim .

if [ -z "$VIM_APP_DIR" ]; then
  myDir="`dirname "$0"`"
  declare -a apps=("/Applications" "$HOME/Applications" "$myDir/../Applications")
  utils="Utilities"
  declare -a vims=("MacVim" "vim")
  declare -a all=( "${apps[@]}" "${apps[@]/%//$utils}" )
  declare -a more
  for i in "${vims[@]}"; do
    more=( "${more[@]}" "${all[@]/%//$i}" )
  done
  for i in "${all[@]}" "${more[@]}"; do
    if [ -x "$i/MacVim.app" ]; then
      VIM_APP_DIR="$i"
      break
    fi
  done
fi

By: alex

alex — Fri, 06 May 2011 12:48:42 +0000

Thank you for this script.

I’m not sure if this is bad practice, but I wanted to silence the output for the mvim script, so I appended 2> /dev/null to all the exec statements.

For example:

exec “$binary” -g $opts ${1:+”$@”} 2> /dev/null

Not sure if it works in all circumstances (though I don’t see why not) .. but it’s enough for my uses.