macvim

We as developers and open source advocates have to get over this "thou shall not ever remove code" no matter how old and useless it may be. What the NeoVim team is doing sounds a whole lot like what the libressl team did when they forked OpenSSL, which also had tons of code for obsolete operating systems. At the point of this presentation[1], they removed 90,000 lines of code; it's probably more now. Unlike system software like OpenSSL, Vim is something I (and many developers) spend many hours each day using. In 2014, there's no good reason why it shouldn't be as responsive and flexible as possible. Sometimes when my projects get large and have lots of files open and Vim starts to slowdown just a little, you can almost feel the decades of technical debt taking its toll. As someone mentioned previously, the function that waits for user inp

Are you familiar with Vim's code? Just look at all the OS-specific files in the source tree[1]. Not only that, there are ifdefs-galore in the shared code. RealWaitForChar is over 400 lines and contains 41 ifdefs.[2] Many are for long-dead features or platforms. That function just waits for user input, but it has to be ridiculously complicated to account for platforms without basic functions like select(). The infamous eval.c starts off with ifdefs for Amiga, VMS, and Mac OS Classic.[3] Neovim has ripped out tons of this stuff, and it's drastically reduced line count. 1. https://github.com/b4winckler/macvim/tree/master/src 2. https://github.com/b4winckler/macvim/blob/master/src/os_unix... 3. https://github.com/b4winckler/macvim/blob/master/src/eval.c

Have you looked at the Vim source? There are a few things in platform-specific headers, but most ifdefs are scattered in actual code. There are even ifdefs in the middle of control flow statements. For example, in RealWaitForChar(): https://github.com/b4winckler/macvim/blob/master/src/os_unix... That function is over 400 lines and has over 50 ifdefs. What does it do? It waits for any key to be pressed. Unfortunately, Vim is single-threaded and synchronously character-driven, so it has to try and process some autocmds and other events in the same loop. Oh and the wait loop uses gettimeofday(), which is not monotonic. To get another taste of Vim's source, take a look at https://github.com/b4winckler/macvim/blob/master/src/eval.c (Warning, may crash your browser.) That file is 25,000 lines and checks hundreds of different ifdefs.

The author of NeoVim (Thiago de Arruda) tried to add support for multi-threaded plugins to Vim and has been stymied[1]. I'm not sure how to get a patch merged into Vim. Bram Moolenar is the only person with commit access, and he's not a fan of most changes beyond bug fixes. My co-founder and I tried to add setTimeout & setInterval to vimscript[2]. Even six weeks of full-time effort and bending over backwards wasn't enough. Eventually we were just ignored. I've contributed to a lot of open source projects, and the Vim community has been the most difficult to work with. I've been writing C for almost two decades, and the Vim codebase is the worst C I've ever seen[3]. The project is definitely showing its age, and I'd love for something new to replace it. 1. https://groups.google.com/d/msg/vim_dev/65jjGqS1_VQ/fFiFrrIB... 2. https://groups.go

The source is available if you build it yourself: https://github.com/b4winckler/macvim/releases. The binaries should be coming soon.

It should appear here soon: https://github.com/b4winckler/macvim

The vim that ships with 10.8 (and IIRC 10.7, maybe 10.6) has ruby and python linked out of the box, and straight-up ./configure --enable-rubyinterp && make works just fine on my machine. Or if yours isn't for whatever reason, you could cheat and grab MacVim[0] then symlink `/Applications/MacVim.app/Contents/MacOS/Vim` to `/usr/local/bin/vim` (editing paths as necessary) [0] https://github.com/b4winckler/macvim

Not sure if this really is interesting, seems very niche. However, I got curious and dug up the commit: https://github.com/b4winckler/macvim/commit/ce5b7a2d6d8b69d2....

* Adium is great. * Growl works very well but the whole notification business (emails + builds + IM + song details…) can be counter productive. Use it lightly. * iTerm2 is the most modern terminal emulator you'll find on Mac OS X. I use it only because I wanted 256 colors and I'm not on Lion. I've never used its more advanced features. * I don't know Notepad++ but I would say Sublime Text 2 (http://www.sublimetext.com/blog/articles/sublime-text-2-beta) and TextMate (http://macromates.com/) may do. You could also try a full blown IDE like Aptana (http://aptana.com/) or RubyMine (http://www.jetbrains.com/ruby/). If you already know Vim, MacVim (https://github.com/b4winckler/macvim) is the way to go for both the GUI and the CLI. * Apple's own Mail.app works well. I've never felt the need to use another app. Microsoft's Outlook is pretty good

Curious, why vim /and/ TextMate? And on the former, console or MacVim[1]? [1] https://github.com/b4winckler/macvim

Same here. I found this: https://github.com/b4winckler/macvim/wiki/ChangeLog Might just have to upgrade to snapshot 59. I guess I'll find out when lion finishes downloading. But really, people actually use the open/save panels in MacVim?

http://github.com/b4winckler/macvim/downloads More specifically, http://github.com/downloads/b4winckler/macvim/MacVim-7_3-53.... It's solid.