Live data from Hacker News

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

stackoverflow.blog

91–100 of 149 posts

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

#93
post #10

Why is this such an issue? It is no harder exiting vim than it is exiting plain old vi, nvi or any other vi clone. In fact, the very same keystrokes that you use for exiting vi can be used in vim as well.

or ed! Wait, I don't think I'm helping your case.

ed(1) is the standard text editor: https://www.gnu.org/fun/jokes/ed-msg.html

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

#94

kill -9 `pidof vim` Also, whoever decided to have vim as the default editor in the windows port of git.. this is brain damaged . Just use notepad already!

Git wasn't designed with your average developer in mind.

Linus designed it for himself and for kernel development. This still shows. I don't think he ever intended it to be used outside of Linux development, maybe not even for long there.

I wouldn't be surprised if he expected people to run with the concept and develop their own tools. But inertia and hype prevailed and now we are stuck with a poorly designed UI.

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

#95

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…

This happens to me even in graphical text editors, my text ends up riddled with ':w's I have to go back through and remove later.

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

#99
post #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 changi…

Ins to write? I always press . (Nano user;-))

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

#100

I really love my vim bindings, I try to use them everywhere possible. So far that is: Web browser: Vimium plugin (Chrome) Music player: Cmus Terminal multiplexer: Tmux & Screen Terminal pager: GNU Less I'm still trying to figure out how best to use vim bindings in my z-shell (zsh) and ipython interactive sessions.

For zsh, just enable vi input mode? (bindkey -v in .zshrc) It starts in insert mode, hit esc to get to normal mode where your typical vi binds work. So instead of ^a to go to the beginning of the line it's 0
Post reply on HN