Neovim's Next Feature Poll

Post by edanm » Fri, May 02, 2014, 1:29 PM UTC

hk__2 wrote: post #101

edanm wrote: post #54

Earlier quoted context omitted.

Simple (very common example): .some-css-rule { padding-left:50px; padding-right:50px; } Say I want to edit those two numbers. With multi-cursors, it's as simple as select one number, hitting a button that causes the other number to be selected, then writing the new value. Now, after I wrote it, I realize I forgot to put a space after the colon, and want to change the formatting. No problem - I just make the change to…

I see the point, but when you have to duplicate the code like here for the `50px`, you should use something like SASS/LESS to put the value in one place and then use a variable everywhere.

Post by timc3 » Sun, May 04, 2014, 6:59 PM UTC

MetaCosm wrote: post #33

dasil003 wrote: post #31

Earlier quoted context omitted.

I don't want a product that moves fast and breaks things, but I also don't want to carry the baggage of legacy support for strict vi-mode and whatever else ungodly edge cases vim continues to support. What I'd rather see is vim with deprecations and upgrades on a reasonably timed roadmap. It's obviously a lot more work to maintain a 7.x branch, 8.x branch etc, but this is much more sustainable and meets everyone's ne…

Those ungodly edge cases are what makes vim usable everywhere, and the default of the defaults on so many systems. That trusty vi command that works a certain way has been dependable since the late 1970s. But, that misses the point of Neovim a bit -- Neovim is about letting the community in (with all the good, and bad that comes with that). I suspect most people won't shift over to Neovim until either (1) They want t…