149
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Jan 2026
149 points (99.3% liked)
technology
24208 readers
331 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 5 years ago
MODERATORS
I understand what you're saying, and I much prefer when people offering help provide terminal commands like this over when they provide vague directions (like "just add "fluffy_cat_mode_on" to the end of your config file for the program, that'll fix your issue", which I could eventually figure out, but telling me where the file is and supplying a command to do it automatically rather than finding the file in my file browser and opening it in a text editor is really handy) or attempt to provide directions that work with the specific graphical tools they're using, which might not be the same ones I've got.
Good lord do I ever hate trying to fix a Windows issue and being given graphical instructions that lead to menus and buttons that don't exist on the system I'm trying to fix. Just give me the bloody terminal command so I can see if it's a UI glitch/update or a deeper bug. I still won't know how to fix it if the terminal spits an error at me, but then I can look up the underlying error instead of sifting through pages of dead ends with pics of the nonexistent option I'm supposed to click just looking up "xxx button/menu missing". I do not like the CLI, on any operating system, but being told in Linux forums and software documentation to use specific terminal commands to fix things is significantly less frustrating than what appears to be SOP for Winblows troubleshooting. Which I suppose is the result of everyone using the same DE and core graphical tools.