![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.kde.social/pictrs/image/19e6d51f-5131-409e-8990-827d3d29e4d3.png)
Not KDE but might be similar: For the MATE desktop it is mate-screensaver-command --inhibit
. I would expect something similar for KDE.
Not KDE but might be similar: For the MATE desktop it is mate-screensaver-command --inhibit
. I would expect something similar for KDE.
So we can write Macro viruses in two languages now?
I would go nowhere near a drenched feline since the most common version of them is likely in a very bad mood due to being drenched.
clickops
I think I will steal this.
Ah, the horcrux technique.
A reference to the software engineer who worked 20+ years at Microsoft and then became a goose farmer. The LinkedIn post became viral.
Really true. I hope “new UI” stays optional until I retire or become a potato farmer. I haven’t worked long enough at Microsoft to deserve geese.
The thing you are thinking about is called TOTP or timed one time password.
When you are allowed into the vicinity of this kind of equipment, you should be able to identify matching shapes without circles in the first place…
uninstalls essential package
Why is my system broken? :O
Masks don’t only protect from airborne viruses…
Oh, that makes warnings errors and does not mean “ignore errors”. I’m not too familiar with compiler flags. You could do some mental gymnastics to argue that the unused variable causes the compiler to exit and thus the code is not functioning and thus the unused variable is not a warning but an error :^)
I for my part prefer it that way. Makes sure the code stays clean and nobody can just silence the warnings and be done with it. Because why would you accept useless variables that clutter the code in production builds? Imagine coming back after some time and try to understand the code again. At least you have the guarantee the variable is used somehow and not just “hmm, what does this do? … ah, it’s unused”
Unused variable is an error which fails to compile.
And half of them are “curated list of X”
I want to add that Gmail is a bit of a dick when it comes to SMTP.
The stalebot is most times useless. The only scenario where I can see use of it is a maintainer waiting for the reporter to add information. But closing issues because no maintainer checked on them? That’s garbage and discourages bug reports.
Proton Mail sounds quite promising to me
I am in this post and I don’t like it.