I use quake style terminals, and often start writing a file and completely forget about it and turn off the computer, and only remember what i left behind when i find the random recovery files around, so :w a lot is quite useful for me.
Is there any reason to use :w other than it being the default? I have mine mapped to CTRL-S and it makes sure to keep me in insert mode if I was in insert mode. Feels way faster and easier to spam than the 4 key presses it takes to execute “:w”.
It'd be great if there were side kind of feedback, like the cursor quickly flashing a "C" or something... anything to let you know the operation occurred; better yet, was successful.
I actually disagree from a systems engineer perspective: The program doesn’t actually know shit if those bits hit any permanent medium, just that the OS told them “I’ll take care of it” it could be sitting in a write back cache when you save, see the “write complete” and rip the power and that’s all gone now. Basically, I don’t like promising durability when it’s not really there.
Don't worry, most modern brains have a builtin jit compiler, so when a habit starts to form, the check will be optimised out. (It saves excess neurons from being generated.)
Ctrl + C literally doesn't work at times, it drives me crazy. It might be due to some shitty applications and websites overriding it or adding complexity (Like copying not only the text but additional information).
I'm often 100% sure I copied the text, change the window and an old clipboard entry gets pasted.
God I hate this so much. It's especially frustrating on mobile where it takes like thirty seconds to try to get the right part of the text copied and use the fucking magnified blue dots... Ugh.
I just can't stand Kate showing me a little orange bar meaning I have not saved the changes yet. The bar must be green! I am a slave to the green bar. The white dot in vscode (I use an open source build) is a bit more tolerable, but whenever I notice it I HAVE to save the file.
But then, if you’re forced to develop on microsoft 🤬, it’s late, you’re tired, you’re hand slides just a little to the right (win + d), aaaaand everything is gone, and you’re sitting there looking at you’re background wondering what the hell just happened 🙃.
You can bind it to a key in gnome/kde (not sure how they handle custom keybinds. Otherwise add a call to xbindkeys to your .bashrc or equivalent). It kills any window you want, responsive or not.
As for the terminal, I don’t think you can send SIGKILL, but ctrl + \ will result in a core dump if you’re using bash.
Actually vim has swap files which it saves to when you make any edit, whether you save the change or not, meaning you shouldn't lose any work even if you kill -9 vim on unsaved work.
Tell me you use Windows without telling me you use Windows.
Meanwhile I just reboot my Mac without bothering to save anything and everything just restores as it was, even new documents that were never saved. It works so well I don’t even think about it anymore.