You can :q! any time you want, but you can never leave.
this post was submitted on 03 Sep 2023
729 points (93.0% liked)
linuxmemes
21234 readers
98 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
Insert Mode tho
It's really easy, just unplug your computer.
-
Esc× 2CTRL-[× 2CTRL-\CTRL-N× 2
-
:q:qa:wq:wq!:wqa:xZZ:q!ZQ:q!:cq
Nano is pretty good if you're in a terminal. Used to use vim for ssh related stuff but since nano added syntax highlights I didn't go back.
Nano's only appeal is that it's beginner-friendly, but you already know Vim, so why switch?
Because Nano just works. Vim is insane affront to good design and standards.
load more comments
(1 replies)
load more comments
(6 replies)
Micro exists. It's Nano with Lua plugins. Very robust and minimalist. No magic incantations. I actually use it to code simple stuff that I just don't want to wait a minute for VSCode to spin its wheels.
I know how to get out. But I still like nano a lot more.
WTF. Why? I could maybe see someone preferring emacs over vim, but not nano. Maybe there are nano features I don't know about, but it just seems like Windows Notepad to me.
I normally just use VS Code with a VIM extension. Unless I'm ssh-ing into something, then I use vim.
Well, you kind of got it but also didn't I guess. If I want to quickly edit a none critial config file or similar a terminal version of Notepad is perfectly fine and for more complex stuff I prefer a GUI anyway.
I edit in Micro. Which is Nano with Lua plugins. Come at me.
You exit vim by unplugging the pc.
Now do ed...
My main problem with vim is that they use hjkl instead of jkl; , it doesn't make sense to me why they'd do that.
And my second problem is that I use my own custom keyboard layout instead of qwerty, so I'd have to remap all the keys. Why spend hours learning and then rebinding all the keys when I can instead play some Dota? /s
My main problem with vim is that they use hjkl instead of jkl; , it doesn't make sense to me why they'd do that.
With qwerty you can be sure of layout of the letters and numbers across languages.
load more comments
(1 replies)
Been a vim user for decades but never used hjkl. Probably strongly correlated with the fact I'm non QWERTY as well (Dvorak). I just use the arrow keys combined with the jumps to start/end of lines/words or to characters.
You don't need to remap anything aside from hjkl as the keybindings are mostly mnemonic and not location based.
On Dvorak at least, ^C is so easy to press that it's great for switching modes, I never use Esc.
I find the more time you've spent in non-graphical shells, especially on low spec devices or laggy connections, the more you appreciate vim. Instead of pressing Del a bunch of times and having it overrun you can ct" to swap out that string. I even use vim keys in vscode, as my hands are so used to them.
My biggest complaint is logging into some legacy device that only has vi and not vim, when shortcuts like "dap" or "caw" don't work
load more comments
(2 replies)
That's how you learn Linux and Google: how to kill vim? kill -9 vim.
"vim" isn't a valid PID. I think you meant killall -9 vim
Pssh, come on, it's just :q or :q! - couldn't be simpler or more intuitive!
:q does the trick
I took the vim pill a few years ago and spent tons of time learning its shortcuts, trying out plugins, and forming strong opinions about my relationship with my text editor. It's a great tool, but I personally lost the plot somewhere down the line. I'm not sure that passion actually served me.
load more comments
(1 replies)
!killall vim
ctrl+z seems to work
Remember to actually kill the process though, since that will only background/suspend it in most cases.
(Be sure to save the file though first, Vim creates a "swap" / recovery file but its best to not rely on that, use fg to re-open, then press escape and type :wq)
Followed by kill -9 %1 to actually kill the process, otherwise your terminal might complain or freeze up when you try to close it
ggVGdwq!
I love using vim, but I'm not great at it. I'm just happy I completely understood this.
load more comments
(3 replies)
Init 6
Vim is crap. If a fucking text editor is hard to master, it's just a bad text editor.
That's a paddlin'
load more comments
(6 replies)
view more: next ›