Hi Tony!
(replying to vim_use and vim_dev. Should we keep the discussion on
vim_dev or rather on vim_use?)
Disclaimer:
I know, this is not a wishlist thread, but I could not resist ;)
On Mo, 12 Apr 2010, Tony Mechelynck wrote:
> It is true that they are in different stages of development. Here are
> my top five; not in preference order.
>
> #14 (Vince Negri's conceal/ownsyntax/cursorbind) already has a long
> track record. I first heard about it when I first learned about Steve
> Hall's Vim for Windows, that must have been in Vim 6.2 or 6.3 time, and
> it was not new even then. Has documentation. Maybe too controversial
> (not enough "mainline"-like) to be included by default? OTOH it has been
> victim of bit-rotting in the past (i.e. conflict with "mainline"
> patches) and of course bringing it in would eliminate that problem
> forever. A compile-time option maybe (or two, or three)? You're the boss.
I'd like that too.
>
> #13 (Access W32 clipboard from Cygwin "Unix" Vim) is interesting but
> still in beta. IIUC ifdeffed by whatever FEAT_* corresponds to
> has('win32unix'). Bring 'em in or let it bake some more?
I have no opinion on that.
>
> #10 (Variable tabstops) sounds interesting. I haven't tested it.
> Reportedly still in alpha. Probably wait some more (Vim 8.0 ?) but keep
> an eye on it.
I'd like that one.
>
> #9 (Relative line numbers) sounds interesting. I haven't tested it. Its
> authors say "it works". I don't feel competent to evaluate it by
> eyeballing the code.
I'd really like that one.
>
> #7 (Bill McCarthy's additional float functions). This one I've taken up
> in my "Huge" Vim. Not a single problem AFAICT. Code examination shows
> that it is done cleanly and simply, within #ifdef FEAT_FLOAT, and does
> not interfere with other stuff outside the "call function -> return
> value" codepath. IMHO this one is the most worthy of including into
> mainline Vim (and perhaps the least risky). Maybe a one-time check in a
> build with FEAT_EVAL on and FEAT_FLOAT off to make sure no #ifdef was
> forgotten. (I already compile a Tiny build without +eval in addition to
> my Huge build, from the same source, and no problems there either.)
> Documentation exists and is well-written, as a separate helpfile to
> avoid problems with rsync; probably merge that into eval.txt.
If you consider that, would you also consider including a random()
function call?
Additionally I'd like persistent undo (#4), unified colors (#12) and
correctly indent wrapped lines (#15) and maybe quickfix-title from the
extended git repository as well as fast-join and really nice would be
the margincolumn patch that was floating around vim_dev for some time.
regards,
Christian
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
To unsubscribe, reply using "remove me" as the subject.
