231–240 of 489 posts
Earlier quoted context omitted.
And worse vim is often the default EDITOR or software's fallback in case no EDITOR is set, so you get dropped into a vim edition buffer seemingly randomly.
I'm pretty sure that I've never seen any OS/Linux distribution set default EDITOR to vim. If EDITOR is set to vim, then someone must intentionally did that.
EDITOR=/Applications/TextEdit.app/Contents/MacOS/TextEdit
cd /usr/bin
rm vim vimtutor
ln -s /Applications/TextEdit.app/Contents/MacOS/TextEdit vimEarlier quoted context omitted.
Imagine you don't know that. Now try to exit vim.
Add in the bonus confusion that you may not have even been trying to run vim, and in fact may not know what it is (hey, everyone's a beginner some time), but have landed there due to a default $EDITOR value. [EDIT] also, a typical mid-level computer user's tendency to slap "ESC" when panicked. Ha!
git rebase -i
For example
Earlier quoted context omitted.
That looks more like emacs behavior though, vim rarely (never?) prompts the user for anything. You enter a command, you get a reaction (either an action like quits vim, or a message indicating something happened) -- which I personally prefer much more than getting annoying prompts.
You get a prompt if you try to exit and you haven't written the buffer to file
> E37: No write since last change (add ! to override)
Earlier quoted context omitted.
Why doesn't it just quit? That's as stupid as Python's >>> quit Use quit() or Ctrl-D (i.e. EOF) to exit The software knows perfectly well what I'm trying to do FFS.
Because it's an editor, and if it just quit on me every time I mistyped Ctrl-C just because you can't be bothered to type the right command, I would be quite angry.
E492: Not an editor command: Wq> Github search for ":wq" returns more than 7,000,000 results https://github.com/search?q=%22%3Awq%22&ref=cmdform&type=Cod...
https://twitter.com/kennethn/status/470771879397949441?lang=...
Earlier quoted context omitted.
If you took the modal interface away from vim, you wouldn't have vim anymore. If you don't want a modal interface, don't use vim. You may as well expect Porsche to move the 911's engine to the front.
> If you took the modal interface away from vim, you wouldn't have vim anymore. If you don't want a modal interface, don't use vim. The vast majority of people don't use vim, so this "solution" has already been widely adopted. (Which in turn causes people who like vim to periodically wonder why more people don't use it.) The problem comes because there are scenarios where you don't have a choice as to which editor to…
Do we need to spoon-feed you people the solution for all of your problems?
Use SSHFS to mount your remote file system, and edit your remote files with your fancy, LOCAL, non-vim editor.
Earlier quoted context omitted.
Many of us get dropped into vim by accident.
That's your distro's problem, not vim's. There is no reason to fuck up vim just because distros are poorly configured.
> that no actual user of the software has? It's not an iphone, it isn't meant for use by the general public.
You're obviously wrong.
Millions of users of the software have that problem. It is used by the general public. It's irrelevant whether they intended to be users of the software or not. No one decides on a distro based on the default text editor, and some people are still learning how to use nix and won't know to change it right away.
Plus, from vim.org:
> It's not just for programmers, though. Vim is perfect for all kinds of text editing, from composing email to editing configuration files.*
Sounds like vim is for use by the general public to me. It just isn't very good at usability.