I'm with Vince, though... Two vim packages would be a fine and dandy
way to approach it. I'd love to see it; I just don't think it should
be the only vim option.
Well... when writing my survey mail I was actually mulling over an
additional sentence like "Note that I'll maintain only one package."
but dropped it for the final mail. I should have known better.
The problem with vim is the number of configure options which do make
different sense for different people. What should I do?
- pure vim
- perl support
- python support
- tcl support
- ruby support
- perl and python but not tcl
- gvim with win32 interface (actually unsupported under Cygwin)
- gvim with X interface
- Which X interface, gtk, gnome, motif, athena?
- ...
See what I mean? You'd never hit the right combination. I've just
checked the vim release on my Linux box and found out that it's also
not built with any of the interpreter language support. Of course I'm
using my own handcrafted build of vim...