I feel like the images should be switched.
this post was submitted on 27 Dec 2023
148 points (75.0% liked)
linuxmemes
21178 readers
1424 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
If you wanna save changes: :wq
If not: :q!
Else: :SpanishInquisition
Hmm, I didn't expect that last one.
Why do so many people prefer :wq over :x?
Cause I don't like to think about my x
Because :wq to me means "Issue command write, followed by command quit." "Issue command x" to me means nothing in the context of vim, and ctrl + x on most systems is reserved for cutting, so it just "feels" wrong.
load more comments
(4 replies)
load more comments
(3 replies)
I prefer the extremely intuitive:
[C-R]=system("grep -P "PPid:\t(\d+)" /proc/$$/status | cut -f2 | xargs kill -9")
or
i:!grep -P "PPid:\t(\d+)" /proc/$$/status | cut -f2 | xargs kill -9[esc]Y:@"[cr]
It just rolls off the fingers, doesn't it?
Edit: damn it lemmy didn't like my meme because it assumes that characters between angle brackets are html tags :( you ruined it lemmy
EDIT 2: rewrote it, just assume that square brackets are buttons not characters
load more comments
(2 replies)
I always get annoyed when I'm on some system and nano pops up and I need to figure out how to kill that thing.
Same. As a vim user I now can't quit nano.
load more comments
(23 replies)
There's a button to exit vim on your pc. Just hold it 7 seconds and vim is closed. 😅
it's right next to the turbo button
you don't need the ! when you have the w, because your changes already get saved.
If anything it is dangerous as it will still exit even if changes cannot be saved.
Try editing a file in /etc as a regular user. It happens sometimes and you really want that warning that the write failed.
Anyway, :x is superior. It only writes if there are changes. So, your mtime doesn't change unnecessarily.
load more comments
(2 replies)
:ggdGwq (please don't do this)
VIM Golf.... Same outcome, fewer strokes:
%d|wq
E492: Not an editor command: ggdGwq
I use Vim daily, and i have absolutely no clue what that command would do, what would it do? Delete the document, save and quit?
exactly.
gg -> go to top of document
d -> delete (actually, it's cut, but it destroys the mnemonic)
G -> here is a modifier to "d" and tells it do "delete until end of document"
w -> write current state of buffer to disk
q -> exit program
Actually not, binds and commands aren't the same. ggdG only works as a series of inputs, while wq only works as a command (with the colon).
Exactly. The colon needs to be just before the w, not at the front of the sequence...
And while you're at it, throw an ESC in there at the beginning, will ya?
load more comments
(1 replies)
load more comments
(1 replies)
load more comments
(1 replies)
load more comments
(1 replies)
:x
I love how in the comments on even the most basic vim meme I learn something new
view more: next ›