On Mon, Sep 21, 2009 at 5:16 AM, Tony Fitzgerald <[email protected]> wrote:
> > On Mon, 21 Sep 2009, Yongwei Wu wrote: > > > Did you miss that GUI VIM exists on Mac OS X, is easy to use, is > > maintained regularly, and has a lot of users? I myself am a happy user > > of MacVim. > > I've refrained from comment so far because I've only been a Mac user > for a few months, having migrated from Solaris. The original > questioner asked about idiosyncracies of gvim on Macs and, to date, I > don't think anyone has pointed out the one thing that irks me somewhat. > > I have gvim with native Mac support installed because that version is > what you need if you want to use gvim as the editor for the Firefox > plugin "It's All Text!" or to use gvim as the browser for downloaded > text files. > > If you make extensive use of spaces, however, and want to be working on > different projects in different spaces and use the native Mac version > of gvim launched from the tray then I have not found a way to have > multiple copies of gvim open in different spaces editing the files for > different projects. (There may be a way, I haven't found it.) > > To work the way I want with gvim, I had to install a separate instance > which works under the X11 support and can be launched in the normal way > from the shell prompt. > > The main idiosyncracy appears to be needing two separate installations > of gvim for the two separate windowing contexts. The main annoyance > was the amount of time it took to figure this out. > > I have been a frequent user of the gui version of Vim for the Mac (called MacVim) for a long time. The developers have done a great job in making MacVim act like a native Mac application while still keeping all the great tools of Vim. I have never had a problem of multiple MacVim windows across multiple Spaces. It just works (as they say). As far as launching the gui from the command line, this works well also. Included with the MacVim distribution is a shell script called mvim. Place this script somewhere in your PATH (mine is in ~/bin) and then you can just launch MacVim with the command mvim. It passes all the normal Vim command line options so everything works as expected. Of course the best way to get help with MacVim is on the vim-mac email list. The developers are always around answering questions as well as other seasoned MacVim users. Try out MacVim; it's great. Jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
