Live data from Hacker News

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

stackoverflow.blog

121–130 of 149 posts

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

#121

Earlier quoted context omitted.

Sure, why not something like pico / nano? Seems more friendly to occasional users, who are the people most likely to hit the default.

Would you drive a Yaris if you had a Ferrari in your garage? Didn't think so

Do you know how expensive it is to own and use an high end car?

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

#122
post #80

Earlier quoted context omitted.

When I first entered vi/vim I had no idea what it was. To know how to exit vim you first have to know that’s what you are trying to exit. I suspect at least half of the confusion comes from people accidentally entering vim without any intention to do so. One of the most common examples is git that some times launches a text editor and in some conditions that might be vim. If you are doing a “git rebase -i” for the fi…

(This is a reply to the GP comment, since it got flagged while I was typing my reply.) --- > If you downvote this you're to dumb to even look stuff up on Google. What do you think the first result is when you search for how to exit Vim? > RTFM is at least 50% of what makes a good programmer. Stack Overflow is part of the metaphorical manual.

To add, the word quit does not even appear in the man page

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

#123

Hot take: Vim should include a simple “Type :qa! to quit” line in its startup message. Something makes me think it would clear up a lot of confusion for first time users. EDIT: I notice now that it has a “Type :q to exit.” I never noticed that before, and I use Vim most days, so I can see how others might miss it too.

Anyone easily confused by how to quit vim should not be using a computer at all, much less vim.

> Anyone easily confused by how to quit vim should not be using a computer at all, much less vim.

IMHO - Anyone easily confused about how to converse constructively should not be using social, knowledge sharing websites at all. Much less Hacker News.

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

#125
post #6

Earlier quoted context omitted.

ctrl+d is the most dangerous kind! Since that one can also exit the terminal itself. gdb takes, depending on the situation, one time ctrl+d or two times ctrl+d to quit. It's a trap! So since gdb usually takes two times, muscle memory learns two times, but then in that rare instance where it required it only once... logged out of ssh :(

In bash: IGNOREEOF=10 In zsh: setopt ignore_eof In ksh: set +o ignoreeof In tcsh/csh: set ignoreeof Normally I just do this for login shells, so I can quickly exit out of subshells.

10 ???

For bash I set `IGNOREEOF=1` so as to have to press ctrl+d twice to exit. Ten times seems a bit too many.

How to do the same for zsh?

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

#126
post #62

Earlier quoted context omitted.

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.

True. A "professional" would obviously know to add `export EDITOR="emacs -nw"` to their `.bashrc`

Problem solved! :D

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

#127

Hot take: Vim should include a simple “Type :qa! to quit” line in its startup message. Something makes me think it would clear up a lot of confusion for first time users. EDIT: I notice now that it has a “Type :q to exit.” I never noticed that before, and I use Vim most days, so I can see how others might miss it too.

Anyone easily confused by how to quit vim should not be using a computer at all, much less vim.

I prefer to use `butterfly-mode` in Emacs.

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

#128
This means that 1 million developers need to do one or more of the below:

1. Switch to emacs (plain emacs, roll your own config - not advised)

2. Switch to emacs and learn adopt evil-mode

3. Switch to emacs and learn to configure it with use-package

4. Switch to emacs and install spacemacs, and configure it with step 3

5. Switch to emacs and install doom-emacs, and configure it with step 3

6. Take 4 then switch to step 5

7. Takes step 3, run it side by side with both 4 and 5, then switch wholly to step 3

1 million developers can have their cake and eat it. Vim, Neovim, VSCode, Sublime and IntelliJ and all other editors go into a slow death spiral.

5 years on: Emacs gains the abilities of all the other Lisp dialects, becomes the foundation for the McCarthy Desktop Environment. KDE, Gnome and Co go into a slow death spiral.

10 years on: Emacs is so advanced that programmers can instruct Emacs via brainwaves. Keyboards are not necessary.

20 years on: Emacs attains sentience. Emacs morphs into a 3 dimensional human form bearing an uncanny resemblance to Richard Stallman. Every Emacs user has their own Richard Stallman look alike at their beck and call.

30 years on: Cyberdyne's Skynet has attained sentience and threatens to destroy humanity. Emacs and Skynet duke it out.

40 years on: Emacs defeats Skynet. Emacs receives the Congressional Medal of Honor, The Victoria Cross, becomes a Peer of the Realm, and receives every award every single country of the world has to offer.

50 years on: Emacs brings peace on earth and goodwill to all men. Every man, his family and his dog live happily ever after.

60 years on: Emacs defeats both Alien and Predator

70 years on: Emacs colonizes new planets.

80 years on: Emacs attains nirvana and vanishes in an explosion of light.

90 years on: Human beings are back to Vim, Neovim and all those other horrible editors and desktop environments. The cycle begins anew.

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

#130
Well now the stats will get distorted as people reading the article check the question on stackoverflow. That is unless they have another way of gauging this. If I click that link to the question does that increase the count for the languages I use?
Post reply on HN