A vi-centric family tree of editors (2000)

Re:A vi-centric family tree of editors (2000) by kazinator on Sunday November 27, 2016 @10:58PM (#13053310)

Vim is not instant. Moreover, it has annoying TTY handling behaviors; it flushes the TTY when starting.

So if I type

   $ vim file

and start entering editing commands, often I do it so fast that some of the characters get cut off, like the leading colon of an ex command or what have you.

There is no good reason for this. It will not happen with any reasonable command line utility.

I reported this to the Vim mailing list not long ago and was basically brushed off.

[ Parent | on HN ]

Re:A vi-centric family tree of editors (2000) by JdeBP on Monday November 28, 2016 @10:23AM (#13055940)

I read https://groups.google.com/d/msg/vim_use/XX6SoxHAzhI/vuyIx71G... and it doesn't look like a brush-off to me.

What's missing is the statement that this is how things work when one is relying upon terminals to respond to special control sequences with strings denoting their capabilities. In theory one could save up and re-process the input characters that arrive before the DECDSR response. In practice, people throw them away.

Did you try it on a non-xterm terminal type, as was suggested?

[ Parent | on HN ]

Re:A vi-centric family tree of editors (2000) by aktau on Monday November 28, 2016 @04:53AM (#13054435)

Have you reported it to the Neovim devs? It stands a better chance of being included there (IMHO) and from there it's possible that it trickles up (like the async features in Vim 8).

[ Parent | on HN ]

Re:A vi-centric family tree of editors (2000) by weaksauce on Monday November 28, 2016 @01:10AM (#13053724)

I love vim but recently started using Emacs with spacemacs and it takes a long time to load. Vim is basically instantaneous and Emacs is like molasses.

[ Parent | on HN ]