this post was submitted on 09 Jan 2025
499 points (94.8% liked)
linuxmemes
22865 readers
1693 users here now
Hint: :q!
Sister communities:
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
3. Post Linux-related content
sudo
in Windows.4. No recent reposts
5. 🇬🇧 Language/язык/Sprache
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It always surprises me how complicated some of the editor tooling sounds in threads like this. Obviously once you learn how to use these things they are powerful, but how do people have the patience to deal with all of that in the beginning? This is coming from a guy who writes scripts constantly to avoid doing tedious, error-prone things.
Also I keep seeing people say vscode is slow. One of the reasons I switched to it is that it's insanely fast compared to other editors I used (even those with far-inferior featuresets) 🤷♂️
Whenever I was frustrated with a stupid undecipherable error message, I would just tweak my
vim
config a bit.Within a few minutes, my rage at the error would be completely replaced with rage toward
vimscript
.Then I would revert my
vim
config change, and return to the undecipherable error message with a fresh perspective. mainly relief that at least it's notvimscript
.Joking aside, I really did learn
vim
mostly during coffee breaks or while waiting on some long running build process.