Oh alright, I do see the point now! I had the wrong idea about how it works. I get the need to have more guarantees on functioning packages

About that, I don’t really see the appeal of Slowroll, except as psychological reassurance for those who would feel the need to update every time a snapshot comes out. I mean, I personally slow-roll on Tumbleweed all the time by only updating once a month, sometimes more and sometimes less like for this update. I’d be interested to know why you use it!

That’s a great workaround, could you share the command?

How do the Tumbleweed Folks among us deal with this?

We generally don’t add many third party repos and we set repository priorities. If I understand this correctly, you are currently using official openSUSE packages and your upgrade is prompting you to upgrade them by changing vendor to this home:wolfi repo. If you want to keep the original packages, you just need to set priorities: in YaST 's “Software Repositories” page for instance, you can select a repo and see what its priority is (99 is the lowest priority, 1 is the highest). You could for instance put the official repos at 95 priority and the wolfi repo at 99. This way, packages will remain set on the official repos even if there are new versions on the other repo.

However, if you have packages that you want to get from the wolfi repo but are also in the official repos, with this method you will be asked to change those packages to the official repos, the inverse situation compared to your issue. You can tell the system to keep those packages from your chosen repo, I do it by choosing a version on the YaST Software page.

I had the same annoyance and ended up uninstalling it, I’ll look into remapping the up arrow too, I never liked the way ctrl-r works anyway. By the way, do you know how to delete a command from history in atuin? I found a bunch of discussions in development about this and some comments saying the function was added, but never mentioning the shortcut or command to delete

Beta? It isn’t experimental, it was an official feature that is no longer supported (even if it still works perfectly).

As I said somewhere else, to get more compact tabs you can go to about:config and search for a setting called browser.tabs.tabMinWidth, I usually change the number to 20 (the default minimum width is like 70) and tabs are allowed to become roughly as narrow as in chrome. And if by “more compact tab bar” you meant how tall tabs are, there’s the browser.compactmode.show setting, put it to “true” and then in the Firefox menu under More Tools → Customize Toolbars you can select “compact mode” in the “Density” menu on the bottom, which makes the tab bar and toolbars shorter

This video is criticising Lunduke, it isn’t made by him

I really don’t think it’s a matter of “haters”. It might be more logical and consistent if you have no other frames of reference, but most Plasma users come over from other OSs who all use double click (Windows, Mac, even Gnome). If a new user blindly tries KDE and keeps accidentally opening everything while trying to select it’s just an immediate and big annoyance. It’s not even clear that it isn’t a bug because there is no clear explanation of how to select and how to open.

Edit: we are of course all used to single clicking on touch screens, but there it is contrasted with the long press to see options and some “select mode” for file management. There is no system that works exactly like Plasma single-click, which makes it disorienting.

No, there are those big plus signs appearing on the top-right corner of the icon, if you click there it selects instead of opening. I guess it’s a matter of habit, I can’t get used to it

After 4 years on btrfs I haven’t had a single issue, I never think about it really. Granted, I have a very basic setup. Snapper snapshots have saved me a couple of times, that aspect of it is really useful.