Mac users can already use Vim thanks to MacVim, another version of the programme adapted to Mac OS X operative systems. The best additions to MacVim are the tab system, transparencies, full screen editing and a very complete toolbar with lots of features: save and import sessions, run Vim scripts, multibyte editing and so on. MacVim Vim - the text editor - for macOS Download MacVim Release Notes (r171) GitHub: MacVim GitHub page; Releases: Binary releases and release notes; FAQ: Answers to some frequently asked questions; Troubleshooting: How to track down the source of common problems; Debugging: How to generate a debug log; MacVim is maintained by macvim-dev. This page was generated by GitHub. To run MacVim from the command line you need to call the mvim script which is in the app itself, somewhere like /Applications/MacVim.app/Contents/bin/mvim. The best way to do this is to use a bash alias in your.bashprofile file, alias mvim='/Applications/MacVim.app/Contents/bin/mvim. MacVim Vim - the text editor - for macOS Download MacVim Release Notes (r171) GitHub: MacVim GitHub page; Releases: Binary releases and release notes; FAQ: Answers to some frequently asked questions. MacVim supports multiple windows with tabbed editing and a host of other features such as bindings to standard OS X keyboard shortcuts (command-Z, command-V, command-A, command-G, etc.), transparent backgrounds, full-screen mode, multibyte editing with OS X input methods and automatic font substitution, ODB editor support.
On El Capitan worked version 7.4.1749 from 18.04.2016
if used rvm, need use any not system ruby interpretator
On El Capitan after install xcode, need run:
without this: ERROR: The Python zlib extension was not compiled. Missing the zlib?
pyenv interpretator must be builded with framework
lua from homebrew
build time ~2min
vi_cv_dll_name_python - you may set in the .vimrc befor first using python (load YouCompliteMe), after loading change interpretator not available. Build not supprort both python 2 and python 3 loaded simultaniosly:
Dynamic python interpretator not linked to the bin, for static linked interpretator need change link with otool:
test build
YouCompleteMe
If MacVim was not compilled on this machine, in the start .vimrc need insert:
Question or issue on macOS:
I have MacVim installed and I am trying to set it up as the editor for Git (version control), but I can’t run ‘mvim’ from the command line as it isn’t recognised. How do I setup mvim so I can run it from Terminal?
How to solve this problem?
Solution no. 1:
There should be a script named mvim in the root of the .bz2 file. Copy this somewhere into your $PATH ( /usr/local/bin would be good ) and you should be sorted.
Solution no. 2:
I don’t think I’d to add anything to the path, did
should then open macvim in the terminal, you can also go ahead and alias that
Solution no. 3:
If you go the brew route, the best way to install would be:
That will provide mvim, vim, vi, view, etc. in /usr/local/bin (all symlinked to the copy in the Cellar). This also removes the need to create any aliases and also changes your vi, vim, etc. to all use the same Vim distribution as your MacVim.
Solution no. 4:
In addition, if you want to use MacVim (or GVim) as $VISUAL or $EDITOR, you should be aware that by default MacVim will fork a new process from the parent, resulting in the MacVim return value not reaching the parent process. This may confuse other applications, but Git seems to check the status of a temporary commit message file, which bypasses this limitation. In general, it is a good practice to export VISUAL='mvim -f' to ensure MacVim will not fork a new process when called, which should give you what you want when using it with your shell environment.
Solution no. 5:
If you already have macVim installed: /Applications/MacVim.app/Contents/MacOS/Vim -g will give you macVim GUI.
just add an alias.
i use gvim because that is what i use on linux for gnome-vim.
alias gvim='/Applications/MacVim.app/Contents/MacOS/Vim -g'
Solution no. 6:
Assume MacVim is installed in the Application folder.
Instead of adding MacVim path to your environment, create a link by typing this in terminal:
sudo ln -s /Applications/MacVim.app/Contents/bin/mvim /usr/local/bin/mvim
Then, open a new terminal window/tab and type mvim.
Solution no. 7:
If you have homeBrew installed, this is all you have to do:
Then type mvim in your terminal to run MacVim.
Solution no. 8:
Here’s what I did:
After building Macvim I copied mvim to one of my $PATH destinations (In this case I chose /usr/local/bin)
Then when you invoke mvim it is now recognised but there is an annoying thing. It opens the visual MacVim window, not the one in terminal. To do that, you have to invoke
To make sure every time you call mvim you don’t have to remember to add the ‘-v’ you can create an alias:
alias mvim=’mvim -v’
However, this alias will only persist for this session of the Terminal. To have this alias executed every time you open a Terminal window, you have to include it in your .profile
The .profile should be in your home directory. If it’s not, create it.
include the alias command in there and save it.
That’s it.
Solution no. 9:
I’m adding Bard Park’s comment here for that was the real answer for me:
Since mvim is simply a shell script, you can download it directly from the MacVim source at GitHub here: http://raw.github.com/b4winckler/macvim/master/src/MacVim/mvim
Solution no. 10:
I’d seriously recommend installing MacVim via MacPorts (sudo port install MacVim).
When installed, MacPorts automatically updates your profile to include /opt/local/bin in your path, and so when mvim is installed as /opt/local/bin/mvim during the install of MacVim you’ll find it ready to use straight away.
When you install the MacVim port the MacVim.app bundle is installed in /Applications/MacPorts for you too.
A good thing about going the MacPorts route is that you’ll also be able to install git too (sudo port install git-core) and many many other ports. Highly recommended.
Gvim
Hope this helps!