Not for the built-in Eq derive macro. But you can write your own derive macros that do allow you to take options, yeah.

Do you have some public code you could link to that you’re having this issue with? There isn’t a one-size-fits-all solution for Rc/RefCell, I think.

Whoa nice, I need to keep this in mind.

Interesting. I can’t find anything about the FLAC licensing issues. Do you have a link?

(Also, correction — Wikipedia says macOS in general can play FLAC. I guess it’s just the Music app that can’t import them.)

Yep. Lack of format support is usually to blame on the one who doesn’t support the format. You can absolutely blame Apple for this too though, their apps can’t open e.g. Matroska video or FLAC.

And perplexingly, they don’t support uploading HEIC, their own image format of choice, on the web iCloud Photos. So there’s that too.

(At this point my music library is stored as ALAC because it’s well supported in both Linux and Apple’s OSes. Really wish it wouldn’t have to be that way though. Someone needs to tell them about ffmpeg.)

For example they used to have their own video container .mov

It’s always very very funny every time someone mentions MOV, because while it’s very similar to MP4, it’s actually an open format while MP4 isn’t (!). You actually have to pay for the MP4 standard document while Apple just gives you the MOV documentation.

Also at least taking a screen capture on macOS still gives you a MOV container, actually.

Meeeeh, that sucks though compared to iCloud. I haven’t tried it but it seems like it will upload only and not download, and it will not store the entire Photos database (including faces, etc.).

Would be cool if this results in being able to store the Photos library in Nextcloud. Not holding my breath though.

Yes, it even uses BitTorrent to distribute videos.

The article starts with a table of contents with the change highlights as the first item.

Sounds like exactly the right way to talk about physical buttons to me.

The proton prefix should not be created on the external drive, but in the Steam folder in the home directory, I’m pretty sure. Even with a second Steam game install location. Why is it not there?

I’m guessing proton is trying to create this symlink when it installs .NET

No, it is created when Wine initializes the prefix. It has absolutely nothing to do with .NET.

Oh, so he has a new ID but I assume registered to vote before the name change and the registration is tied to the name? Ah yeah that sounds like a pain in the ass.

It’s not “c”, it’s “c:”

Why does his drivers license specifically have to match up with his ID to be able to vote? That seems really weird. (Also, could he pretend to just not have one?)

dosdevices/c: is missing I’m assuming is what you mean? That’s very weird, it is there in every wine prefix and should be a link to …/drive_c.

Proton is on a different drive than BG3, could that cause issues?

I don’t think so.

Try deleting the prefix (steamapps/compatdata/1086940). This should work completely fine out of the box. (Not sure if uninstalling the game deletes that already, just in case)

At the very least you can see it in dmesg.

Now that I think about it, dovecot drops permissions for security reasons (login runs as the “dovenull” user). It’s probably not a good idea to try to circumvent that actually.

What do you mean by “more powerful” wrt CMake?

CMake is a turing-complete language with some APIs that Meson either doesn’t have an equivalent yet because it’s comparatively new (for example, until 2023, there was no built in way to get a relative path from two paths, and if you wanted that you had to shell out to an external program), or they aren’t going to add because it doesn’t fit their design.

Meson is (intentionally) limited in terms of extensibility, instead it tries to come with everything built in that you need, even down to specific library support like Qt, from what it seems like to me. For example, you cannot define your own functions, it ships builtin modules but does not allow other packages to provide their own (for example like KDE’s Extra CMake Modules), to name a few that I’m familiar with and why I was put off using it so far.

I have yet to see how actually limiting that is, going to try to move the project I’ve been working on for years that relies on some of these CMake features to Meson soon and see how it fares. But considering that big projects like GNOME use it all over the place it’s probably workable in practice, I’ll just have to rethink the existing approach a bit.

Is that considered bait?

Wasn’t it? Go’s build system is very much not what I would call an example of good design (exhibit A: load-bearing comments and file names).

Nice!