mox

None of what you claim was done in the document being discussed.

It isn’t a fucking “convention” to push women down

No, but choosing either the male or female pronoun when writing about a hypothetical person has been the convention for a long time, and using the male one has been the usual default for far longer than any of us has been alive. It's not to push women down; it's a grammar compromise, and is not exclusive English.

You are misunderstanding the language as it was used, and you have jumped to a false conclusion that seems to make you so angry that you think it's okay to publicly vilify someone... for your own mistake.

I hope things get better for you.

Good day.

Certain forms of singular they are old, but the drive to make it the general convention when referring to a hypothetical person is new.

"Personal politics" is a vague phrase that generally just means someone's views and priorities. There is nothing pejorative about it, nor in the way he used it.

In other words, Andreas insists the OS developer be referred to as “he/him” instead of not assuming gender.

The build instructions in question follow English language conventions that have existed for hundreds of years (and are shared by more than few other languages). All he did was decline someone's proposed change that would have applied a very new convention regarding pronouns for a hypothetical person. This is not the same as insisting that anyone refer to anyone else in a particular way.

It's also not unreasonable. We can ask people to adopt new conventions, but we don't get to expect or demand it.

Change to a language takes time.

It’s textbook misogyny.

No, it is not.

I followed the links to see what he actually wrote. There's nothing transphobic or misogynistic about it.

If you are referring to some other incident, then please link it so we can see for ourselves.

The article refers to the pandemic as though it's over, which doesn't exactly help with the problem. Sigh.

Their summary of Dodo doesn't include a link, and a web search finds a seemingly unrelated webmail service. This looks like the right project:

https://github.com/akissinger/dodo

It reduces the drive’s lifespan.

Let's remember that swapping frequency and volume are system-dependent; practically zero on many systems. On a well-provisioned system that doesn't swap much, having swap space on an SSD can be easier on the environment and wallet than buying and powering a separate device for it.

Nevertheless, I agree that minimizing SSD writes is worthwhile, and reject the notion that an SSD's useful lifetime ends when I'm done with it. (See my other comment.)

I try to keep in mind that replacement shouldn't mean landfill. When my needs have outgrown an SSD, it gets repurposed, donated, or sold. Old ones still work great in computers used in education, special-purpose systems, test environments, refurbished laptops, appliance-like machines, etc.

In the long run, conserving SSD life while I own it translates into less waste and pollution in the world.

Rather than guessing at whether it's swapping, why not check your swap usage? Running free -h in a shell will give you a brief overview of memory usage. Various GUI system monitors will graph it.

You can also find out what process is hitting your storage so hard with a tool like iotop.

Do note that if you intend to use Debian for gaming, you'll probably want to enable Backports for access to newer kernel and firmware packages.

What fascists are ruining OSS?

Their metric for "older" is two years or more.

Glad you got it working!

BTW, in case you're not aware of it, you might find the shellcheck command useful when writing scripts.

I can't tell from that error message whether the inner quotes are being discarded when the command is run, or just hidden when the error message is displayed.

Too bad it doesn't tell you what part of the command is causing the syntax error. Have you checked for more info in the output of journalctl --boot _UID=1000? (Assuming your user id is 1000 and you use systemd.)

Re-reading the spec page that I linked above, I see reference to both a general escape rule and a quoting rule. That could be complicating things with the quotes and backslashes, and maybe even the dollar signs and semicolons, which apparently are reserved. In case it helps, I don't think those semicolons are needed at all.

Before diving deeper into escaping rules, though, I would consider whether it's time to move the whole command line into a script, and simply pass %f to the script in your Exec= line. That would avoid the need for nested escaping/quoting, and allow you to write debug information to a temporary file when the script runs.

You're using single quotes in your Exec lines, which is not legal .desktop file syntax.

I suggest replacing your single quotes with double quotes, and replacing your double quotes with backslash-escaped double quotes.

https://web.archive.org/web/20241130225327/https://specifications.freedesktop.org/desktop-entry-spec/latest/exec-variables.html

TIL 7 is a "massive amount".

Good point. I forgot about that possibility because I don't spend much time playing in Open mode.

The same thing tends to happen on stronghold carriers in Solo mode, I suspect because Frontier programmed the game to spawn a bunch of NPC ships eager to dock with those carriers when a mini-instance is created. You can be the only player within light years, and still have to wait several minutes for all those NPCs to leave before you can dock.

*facepalm*

Ah... Yes, it was most likely a fleet carrier, then. Those are owned by players, and not always open to the public.