5 ms·

So that's how it feels when people say they can't exit vim.

avereveard 5y ago
A quarter of support call when I was lab assistant for my uni was students pressing ctrl+s in vim out of habit and getting stuck in there.
vidarh 5y ago
That's what ^z and kill -9 is for... (yes, I know, unnecessarily brutal; consider it a passive aggressive reaction - it feels good)
- iso1631 5y ago
  ctrl-z does nothing (well it's mapped to undo in "easy" mode)
  - vidarh 5y ago
    Ah. Yikes. But randomly bashing a few keys with control held before ^z still worked for me... Random key-bashing is always a good bet if stuck in vim. (yes, I can usually get out of vim "properly" these days)
    - nostoc 5y ago
      Random key bashing in vim can have a lot of unforeseen consequences for whatever poor file you had opened.
      - vidarh 5y ago
        Given I never intentionally start vim, it's generally when I get thrown into editing some temporary file or other on some system where I haven't configured an editor. Not done any harm in the last 3 decades, so I think the odds are decent.
        fomine3 5y ago
        If you open any file and just type "DZZ" (in capital), you delete the first line of file and save and quit.
        vidarh 5y ago
        Even if I'd have done that, with the type of things I now and again end up accidentally thrown into vim for, that would hardly matter.
- fsflover 5y ago
  https://github.com/hakluke/how-to-exit-vim https://github.com/hakluke/how-to-exit-vim
- dylan604 5y ago
  Sounds like a good time to link to https://www.youtube.com/watch?v=0rG74rG_ubs https://www.youtube.com/watch?v=0rG74rG_ubs
- BoxOfRain 5y ago
  >yes, I know, unnecessarily brutal; consider it a passive aggressive reaction - it feels good Throwing SIGKILL at something that's misbehaving is very satisfying, especially if you have a habit of personifying your computer a bit too much.
- gnubison 5y ago
  Regular SIGINT will probably do the same thing (or SIGQUIT) if that doesn’t work. It’s absurdly easy to create software that misbehaves after a ‘kill -9’, because the only real use for it is 60 seconds after starting the shutdown process for the rare program that just won’t exit.
  - vidarh 5y ago
    Yes, but not as satisfying...
- andrewaylett 5y ago
  Hit the power switch. (In my youth, I definitely resorted to doing that more than once)
YeGoblynQueenne 5y ago
Try ed. That is how it feels when people can't exit vim :P
- iso1631 5y ago
  q or ctrl-z. Not rocket science, not like having to press Control-L (clear terminal) before quitting.
- mFixman 5y ago
  ?
  - toxik 5y ago
    ?
    - okl 5y ago
      eat flaming death
      - Shared404 5y ago
        ^C
  - eliasbagley 5y ago
    The mighty ed has spoken!
- amelius 5y ago
  I tried your suggestion ":P" It gave me: **warning** (netrw) using Pexplore or <s-up> improperly; see help for netrw-starstar
- Shared404 5y ago
  Also vanilla emacs. I just wanted to try out org >_< !
- Symmetry 5y ago

A quarter of support call when I was lab assistant for my uni was students pressing ctrl+s in vim out of habit and getting stuck in there.

vidarh 5y ago

That's what ^z and kill -9 is for... (yes, I know, unnecessarily brutal; consider it a passive aggressive reaction - it feels good)

iso1631 5y ago
ctrl-z does nothing (well it's mapped to undo in "easy" mode)
- vidarh 5y ago
  Ah. Yikes. But randomly bashing a few keys with control held before ^z still worked for me... Random key-bashing is always a good bet if stuck in vim. (yes, I can usually get out of vim "properly" these days)
  - nostoc 5y ago
    Random key bashing in vim can have a lot of unforeseen consequences for whatever poor file you had opened.
    - vidarh 5y ago
      Given I never intentionally start vim, it's generally when I get thrown into editing some temporary file or other on some system where I haven't configured an editor. Not done any harm in the last 3 decades, so I think the odds are decent.
      - fomine3 5y ago
        If you open any file and just type "DZZ" (in capital), you delete the first line of file and save and quit.
        vidarh 5y ago
        Even if I'd have done that, with the type of things I now and again end up accidentally thrown into vim for, that would hardly matter.
fsflover 5y ago
https://github.com/hakluke/how-to-exit-vim https://github.com/hakluke/how-to-exit-vim
dylan604 5y ago
Sounds like a good time to link to https://www.youtube.com/watch?v=0rG74rG_ubs https://www.youtube.com/watch?v=0rG74rG_ubs
BoxOfRain 5y ago
>yes, I know, unnecessarily brutal; consider it a passive aggressive reaction - it feels good Throwing SIGKILL at something that's misbehaving is very satisfying, especially if you have a habit of personifying your computer a bit too much.
gnubison 5y ago
Regular SIGINT will probably do the same thing (or SIGQUIT) if that doesn’t work. It’s absurdly easy to create software that misbehaves after a ‘kill -9’, because the only real use for it is 60 seconds after starting the shutdown process for the rare program that just won’t exit.
- vidarh 5y ago
  Yes, but not as satisfying...
andrewaylett 5y ago
Hit the power switch. (In my youth, I definitely resorted to doing that more than once)

YeGoblynQueenne 5y ago

Try ed. That is how it feels when people can't exit vim :P

iso1631 5y ago
q or ctrl-z. Not rocket science, not like having to press Control-L (clear terminal) before quitting.
mFixman 5y ago
?
- toxik 5y ago
  ?
  - okl 5y ago
    eat flaming death
    - Shared404 5y ago
      ^C
- eliasbagley 5y ago
  The mighty ed has spoken!
amelius 5y ago
I tried your suggestion ":P" It gave me: **warning** (netrw) using Pexplore or <s-up> improperly; see help for netrw-starstar
Shared404 5y ago
Also vanilla emacs. I just wanted to try out org >_< !
Symmetry 5y ago