Live data from Hacker News

Stack Overflow: Helping One Million Developers Exit Vim (2017)

stackoverflow.blog

61–70 of 149 posts

Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)

#61

Whenever I end up on another computer without my environment setup and end up in nano because it is the default, it always takes me a while. There is the cheat sheet at the bottom but as soon as the text appears I'll start manipulating it using vim keybindings and delete things and whatever else randomly. I always assume my fingers were not on the homerow correctly or something first. It is very disorienting. So I im…

My first command in any new install is the equivalent of:

dpkg --purge nano

31 years of exiting vi FTW.

Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)

#62

Earlier quoted context omitted.

> A professional would use the man page. A professional would verify that the man page contains the information that they snarkily told others to look for there before they told them to read the man pages. In this case it doesn’t. The closest you get to that sort of information from the vim man page is: > Type ":help" in Vim to get started. Type ":help subject" to get help on a specific subject. For example: ":help Z…

So the information IS there but, in any case, a professional would not continue to stumble and fumble and give up on the editor as so many amateurs do.

A professional would be able to reconfigure the system afterwards to make sure it'll never drop them into this annoying to use editor again.

Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)

#64
If you can't turn off Vim and you're a paid professional programmer, then QUIT. If you downvote this you deserve every bit of suffering coming to you working with these people who can't turn off Vim. If you downvote this you probably can't turn off Vim yourself. If you downvote this you're to dumb to even look stuff up on Google. Vim even give everyone a :help with links to a tutorial which explains :q :wq :q! etc. RTFM is at least 50% of what makes a good programmer. Nobody is above reading documentation, no matter how smart you are.

Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)

#65

Here’s the proper fix. In your .bashrc, or wherever: export EDITOR= anything but vim >

Or just learn the very basics of the program:

Ins to write

Esc to enter command mode Shift+V while in cmd mode to select lines, d to cut or y to copy selected lines. p to paste. u in cmd mode to undo, ctrl+r to redo.

:q! to quit and discard changes when in cmd mode. :qw to quit and write changes :w to write changes and no exit.

It aint that hard really, once you get the hang of it :) - And then I would suggest changing default editor if you still wish.

Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)

#69

My first year of grad school I was a TA for a first year computer science course that was often taken by students from a variety of majors. The first editing sessions I spent the whole lab time running around help students with frozen vi editors. The main problem is you don't start in "edit mode" and students expect to be able to just start typing (which is a reasonable expectation). Who knows what "command" they jus…

That sounds like someone's idea of a practical joke. Assigning vi as a default editor for first year CS students has to be an efficiently cruel way to clear out an overpacked classroom for the semester.

For the cost of tuition, that should be banned.

Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)

#70
post #64

If you can't turn off Vim and you're a paid professional programmer, then QUIT. If you downvote this you deserve every bit of suffering coming to you working with these people who can't turn off Vim. If you downvote this you probably can't turn off Vim yourself. If you downvote this you're to dumb to even look stuff up on Google. Vim even give everyone a :help with links to a tutorial which explains :q :wq :q! etc. R…

Troll
Post reply on HN