Live data from Hacker News

Helping a Million Developers Exit Vim

stackoverflow.blog

251–260 of 489 posts

Re: Helping a Million Developers Exit Vim

#251
post #39
post #3

Obviously my personal bias, but it's emacs I can never remember how to exit from.

(kill-emacs) C-x C-e Pretty straightforward.

> (kill-emacs) C-x C-e

> Pretty straightforward

If this is a joke, it's totally whooshing over my head right now

Re: Helping a Million Developers Exit Vim

#252
post #168

Earlier quoted context omitted.

On many editors ctrl-c is the copy key. Not a good key to exit on...

It's the other way around - mapping copy to ctrl-c was a bit stupid...

Very true, but that argument was lost over 20 years ago.

Re: Helping a Million Developers Exit Vim

#253
post #95

Earlier quoted context omitted.

So it actually doesn't, it's basically just a hack around the fact that the repl is basically: while True: print(str(eval(input()))) Case in point: >>> x = str(quit) >>> x 'Use quit() or Ctrl-Z plus Return to exit' I suppose you could implement quit.__str__ as sys.exit(0), if you really wanted to avoid this problem.

> So it actually doesn't It does, it just does not care. > it's basically just a hack around the fact that the repl is basically: I know what a REPL is. Here's an idea: it's not difficult to add an exit special case to the REPL. > Case in point: Case in point: the developers added a "help text" to tell users to go fuck themselves, knowing exactly what users wanted to do and refusing to do it. quit's repr didn't appea…

It's insidiously more malevolent than that, considering how much productivity is wasted.

Re: Helping a Million Developers Exit Vim

#255
post #184

I'm somewhat amazed but mostly amused that the Vim developers care so little about user experience that they continue to ignore that people have trouble with exiting their tool and refuse to adapt to a more expected convention for exiting it.

It’s tremendously important to realize that Vim comes from a VERY long line of text processing utilities that stretches back over a half a century. Vim is the result of constant iteration on a set of design ideas and conventions that predates it. `Q` for `Quit` is one of the oldest Vim commands, tracing its roots all the way back to the `QED` editor of the 1960s[1]. Changing it now would be foolish. [1] http://waybac…

While I love vim, your argument holds no water. By your argument, it's foolish to change anything at any time, because everything traces its roots back to "something."

Re: Helping a Million Developers Exit Vim

#256

Earlier quoted context omitted.

Because it's an editor, and if it just quit on me every time I mistyped Ctrl-C just because you can't be bothered to type the right command, I would be quite angry.

My GUI editors quit on me every time I mistype Ctrl+Q. I don't really see the difference.

Right... I think the point is that this behavior is not preferable.

Re: Helping a Million Developers Exit Vim

#257

I'm somewhat amazed but mostly amused that the Vim developers care so little about user experience that they continue to ignore that people have trouble with exiting their tool and refuse to adapt to a more expected convention for exiting it.

"You can check out any time you like but you can never leave."

Re: Helping a Million Developers Exit Vim

#258

I'm somewhat amazed but mostly amused that the Vim developers care so little about user experience that they continue to ignore that people have trouble with exiting their tool and refuse to adapt to a more expected convention for exiting it.

the experience of trying to get up-to-speed with the original vim codebase in order to contribute to it is apparently quite awful. So bad that a bunch of folks started neovim. Anyone with the frustration tolerance to go through that gauntlet is unlikely to be very new-user-UX focused.

Re: Helping a Million Developers Exit Vim

#259
post #171

I spent almost 10 years doing IT for a company whose backend was based entirely on as/400. If you've ever used a system like that, I'm sure you know where this is going... The console's that the front-desk or clerical users used every day had a steep learning curve. It was something that you would definitely not be able to walk up to and just intuit. However , once you figured it out, there is never going to be a fas…

[deleted]
Post reply on HN