Hmm, for whatever reason, I’m on 2.31.4, so that might be the difference.

That version was tagged two weeks ago, because they apparently still release patch versions for rather old minor versions of nix. So, apparently I am getting updates, but I’m on some older release channel or something. No idea why.

I have to head to work now, so will have to debug in the evening or the weekend. Thanks for the clue, though.

Yeah, my mum is like that. She’ll readily tell you that you can put dandelion into salad, but also considers it a weed.

She’s also always very concerned what the neighbors think of our lawn (not that she ever asked), and one time she told me we had to mow the lawn, because dandelions are growing on there. When I told her that dandelions are flowers and that I think flowers look better than bland green, you could really see that she never even thought about it this way.

Im Schwäbischen übrigens auch großartig. Sowohl “an-” als auch “ab-” wird zu “a-” verkürzt, nur mit leicht anderer Aussprache (ə vs. ɐ).

Bei an-/abschließen kann man sich in der Regel noch aus dem Kontext ableiten, was gemeint ist, aber z.B. bei an-/abschalten geht das nicht. 🫠

Ist auch echt immer so ein bisschen ein Problem. Egal, ob es insgesamt schon heiß genug ist, kannst es ja nicht wirklich nochmal reinmachen, wenn dann vielleicht noch mehr von deinem Essen zerknallt und u.U. in der Mikrowelle verteilt wird.

I don’t think, we are doing different things. I create a new file, put {} inside, then add it into the imports = [...];. It gives me that error.
Then I git add ., run again and don’t get the error anymore.

Is the error you pasted now from some manual assertion you did?

Yeah, linked lists are rarely a good idea. Modern memory optimization, where contiguous regions of memory are loaded into CPU caches, means that array-backed lists have better performance in virtually all situations.

In a way, I’d want to argue that you should actually only ever roll your own linked lists, because you should only use linked lists when you’re not working in-memory, i.e. when array-backed lists are not an option to begin with.

My assumption would’ve been they do PDFs, because they have the same menu printed out in their restaurant. They’re gonna need an A4/letter size format either way, so PDF is the simplest way of putting that same format onto their webpage.

PSA: Android Firefox can show PDFs without throwing it into your Downloads folder.

Hmm, that sounds exactly like my setup. Weird.

I did have the file created, with {} inside (empty Nix expression). If I git add it, it works as well:

And yeah, I understand that it’s supposed to be a stacktrace, but other error messages look similarly horrendous and I can often only try to guess what’s wrong by reading the stacktrace top-to-bottom, so I’ve somewhat gotten used to doing that.

But good to know that these terrible error messages might be a problem with my system. Thanks!

Hmm, that’s interesting. For me, it looks like this:

I actually thought, it said somewhere in there, that the file isn’t staged, but apparently not even that (anymore?).

You don’t happen to be using Lix or something, do you? I’ve heard that it’s supposed to have better error messages, but I was never sure how much better it might be…

Edit: Perhaps I should add that those code locations it shows, are not from my code. Only the modules/terminal/new_file.nix in the second-last line is relevant.

I mean, I do find the American burger chain food aesthetic rather unappetizing. The food looks like it’s made out of plastic and rubber.

With the offset bun, it’s not massively better, because it’s still the same food, but at least you get the impression that it didn’t fall out of a 3D printer.

I thought, you posted about the warning, because that’s actually easier to see than the error. Because yeah, it does say what you posted, but it’s in the middle of like 30 lines of other stuff. When I forget to stage a new file, it almost always takes me 5+ seconds to spot what the problem is. 🥲

Unfortunately, that shows up even when you’ve just modified an existing file, which is not a problem for it.

And which also happens to be the state my repo is in basically all the time, because I’ll change some setting, then see if it works like I want it to before making a commit…

Yeah, I was gonna say, that might be the root cause.

In the vast majority of cases, you want Box<dyn Error + Send + Sync>, but folks tend to leave out the Send + Sync, because it looks like additional complexity to them, and because it doesn’t cause problems when they’re not doing async/await.
It’s better to define a type alias, if you don’t want that long type name everywhere.

Huh, I’ve been using a directory named exactly like that for basically the same reason. Still not sure, how I feel about applications randomly deciding to throw a folder into there. I guess, it is much better than MuseScore deciding, fuck it, here’s a folder under Documents/, though.

And while I’d prefer applications not to just randomly create folders in general, I can also understand that it’s a somewhat big ask from average users, where they’d like your random folder to be stored.

until some random AI agent

Wait, do they now have spam bots going around on random PRs to post advertisements?

Innenministerium macht illegale Dinge, ist irgendwie auch so ein Dauerbrenner, vor allem bei CDU-Regierungen…

Servo company? It’s an open-source project underneath the Linux Foundation. The Servo Shell source code seems to be here: https://github.com/servo/servo/tree/main/ports/servoshell
It probably wouldn’t be too difficult to compile it yourself, if you really want it.

However, you have to mind that it’s damn near impossible to build a browser from scratch that supports the majority of web standards at this point. Servo does not do so. Most webpages will not be usable on it.
That’s the reason why they don’t care to provide a general-purpose browser interface. Because Servo is only useful at this point when only a specific webpage or specific set of webpages needs to be displayed.
So, generally when it’s embedded into hardware or into a software application, where the user does not have a URL bar to type arbitrary addresses into, and where the webpage to display can be specifically crafted for Servo.

cfg_select! looks good. cfg_if! always added so much boilerplate that it rarely reduced complexity, even though it offered a valid solution for when you had a complex condition in one branch and then not() that in the other. It was also annoying that you had to add a dependency for those rare cases.

We did also move away from cfg_if!, though, because IDE tooling would mostly just quit working within the cfg_if! macro call. Will have to see, if that’s better with this compiler built-in, or if the IDE tooling gets updated to support that well.

Jo, finde ich gerade auch wichtig, wenn mal was ausfällt oder man die Abfahrt verpasst. Dann schaut man schnell im Internet die nächstbeste Verbindung nach und kann da genauso einsteigen.