81–90 of 149 posts
This is probably the #1 problem with Unix-based systems in general for new users. There are so many ways to exit a command prompt depending on the application! Off the top of my head: Ctrl+D, q, :q, exit, quit(), Ctrl+C, Ctrl+X. Countless times have I been locked in an application and needed to cycle through those memorized commands to escape. Imagine doing that as a newbie.
Here’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 program…
Somewhat similar to how most of your comments here are down voted and/or dead/flagged, yet you keep posting new ones with the same tone.
vim -y
:q!
This is probably the #1 problem with Unix-based systems in general for new users. There are so many ways to exit a command prompt depending on the application! Off the top of my head: Ctrl+D, q, :q, exit, quit(), Ctrl+C, Ctrl+X. Countless times have I been locked in an application and needed to cycle through those memorized commands to escape. Imagine doing that as a newbie.
You forgot the most powerful of them all: Ctrl+Z followed by kill -9 pid
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…