You would think that those zealous power-mods on StackOverflow would have closed this as "not a programming question"
I think this question predates that era of stackoverflow. Early stackoverflow was a lot morw tolerant of these kind of questions.
Stack Overflow: Helping One Million Developers Exit Vim (2017)
51–60 of 149 posts
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#52Earlier quoted context omitted.
People with this attitude shouldn't be using a computer, for fear they might get into software development and alienate an entire swathe of potentially great engineers.
I sincerely hope that I do eliminate such people who can't figure out how to quit out of vim.
You’re just a bitter incel. It’s not the world’s fault that you’re a social outcast.
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#53This is something that the most hardcore vim users couldn't ever figure out. That's why they are still vim users.
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#54How is this even possible? I used EMACS for years and had no trouble understanding Vim. Who's hiring these developers who can't even exit Vim? Is this even a real story or the Onion?!? OK, it's real. I need to go outside and get some fresh air. This is simply too shocking.
And how should someone who has never been exposed to vim know how to use it without consulting any kind of reference (whether it is SO or any random unix sysadmin on the street you can hit over the head and drag home to your workstation)?
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#55Earlier quoted context omitted.
Given that notepad only supports unix newlines since a few months ago, I can see why that one wasn't the default
Sure, why not something like pico / nano? Seems more friendly to occasional users, who are the people most likely to hit the default.
micro would be a nice default. It has syntax highlighting, mouse support, and keybindings compatible with windows GUI programs (ctrl-s for save, ctrl-q for quit, etc).
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#56My 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.
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#57Here’s the proper fix. In your .bashrc, or wherever: export EDITOR= anything but vim >
Vim works fine. I use EMACS. TextMate, Atom and Sublime are OK. Any mainstream editor is fine is all but a few corner cases. Truth be told I would be fine without EMACS but maybe less happy. People unable to exit Vim is just a sign of a larger problem, that a generation of programmer relies more on Google and Stack Overflow than simply READING documentation and EXPERIMENTING by writing short little throw away programs. There is so much Vim material out there on the internet that it makes me afraid these defective programmers can't even use Google properly. I still look shit up on the internet all the time but 99% my answer is right in the documentation. Anyone who can really program is horrified by idiots who can't shut off Vim or use WordPad to write c programs and try to compile them.
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#58What's all this stuff about colon keys and enter? Just ZQ (without saving) or ZZ (to save) :)
Yeah that's a good memotip, to close Vim, just put it to sleep: ZZ
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#59:q
Re: Stack Overflow: Helping One Million Developers Exit Vim (2017)
#60Earlier quoted context omitted.
A professional would use the man page.
> 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.