![]() Today I started work on a new Ruby CLI allowing the user to play Connect Four and used MacVim as an experiment. Thoughts on Actually Using MacVim, As Compared to Vim in Terminal If you’re in the downloaded directory, you can run:Īfter restarting Terminal (probably), you should be able to run mvim filename.rb to open files in MacVim. To set up the ability to open files from the command line with the command mvim, simply move that mvim script to /usr/local/bin. In that release, besides the actual text editor application which (I think) you install like any other OS X application, there’s a shell script called mvim. There’s also a link on, but that active fork on GitHub is probably way better.) Also the icon is nicer and more modern: a better fit for OS X Yosemite. I’ve since switched to this fork, and am now running VIM 7.4.769. The blog post links to this snapshot of MacVim on GitHub, HOWEVER this seems to be a newer, more active fork of the project. For that, I found this simple but excellent blog post. Obviously, besides the actual MacVim editor, I also need to be able to launch it from the command line as easily as Terminal Vim or Sublime Text. bash_profile, another fall back for the work computer is to just use MacVim. If that doesn’t fix the system clipboard problem, or we just object to hard-coding the Vim version number into our. bash_profile, although that sucks because the version number is hard-coded… ![]() If the problem with the work machine is that the shipped version of Vim is 7.2 or 7.3, I could do what I did on my home machine to upgrade Vim– using homebrew to install Vim (not MacVim) and then add alias vim="/usr/local/Cellar/vim/7.4.488/bin/vim" to my. (I’ll note the version number next time I’m in the office.)įor the record, at home, where the * register works great, I’m running Vim 7.4.488 in the Terminal. There is a chance that the version of Vim that shipped with the computer does not support the feature in which the * register is connected to the system clipboard. On my work computer I’ve been having some trouble getting the 2015 MacBook Pro’s Terminal Vim to access the system clipboard. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |