alias v=vim. There, just saved you two keystrokes.

That could break some peoples’ dotfile management, e.g. symlinks or git repos. I’d say deprecation notice and reading from both, at least for a while, is better.

The DEs listed for a distro will be ones you can get out of the box, i.e. you install the distro and it already has the DE. However, you can then install pretty much any DE/WM on pretty much any distro. Most of the time, you’ll also get a login screen where you can choose between different DEs, so you can try multiple on the same distro to see how you like them.

Most of the ‘random desktops’ will be window managers, there are just a few main DEs, which each have a window manager bundled in. If you take one of the separate window managers (which can be tiling, stacking, or a mix) you’ll just have a bit more work to do to make it like you want, but they can have more customisation than full DEs. You can make most window managers look like pretty much any DE, but not necessarily the other way around. If you look at [email protected], most of those are window managers. Saying they’re confusing to understand and you don’t want to have to customise them to make them look nice and add any separate programs you need for a full system is fair, but saying they’re ugly is kinda nonsensical, since you can make them look however you like.

As for why some distros’ Plasmas look different, that’s just because it is itself quite customisable (from what I hear, the most customisable of the mainstream DEs). So if you install XeroLinux, you could customise it to look like stock Plasma, and vice versa.

Long story short, don’t choose a distro based on their default DE or vice versa, don’t disregard window managers out of hand (but do if you just want a full out-of-the-box environment), and look at different distros’ customisations, as well as [email protected] and similar, to see what DEs can look like you want, but again you don’t have to decide distro based on that.

You can a bit, but that will be limited and will differ by browser. Look at something like this to do it: https://medium.com/@ross.angus/styleable-select-box-replacement-in-pure-css-and-semantic-html-1f38a400b285

You can’t style options, as they’re browser-dependent and there isn’t an agreed standard. You’d have to use a replacement, which provides the functionality with other components.

Then, to keep it open, you should be able to toggle classes and states in the inspector. I’m Firefox, it’s above the style inspector, labelled as .cls and :hov, I believe (I’m on mobile at the moment).

Seems like it. The article also mentioned that there are only 73 pairs available, so it sounds like Mozilla has to explicitly define what Chrome extensions corresponds to what Firefox extension.

Instead of importing the Chrome extension directly, Firefox is installing the Firefox version of the extension from Mozilla’s own extension store.

Seems like it’s just for making the switch from Chrome smoother, rather than being useful for long-time Firefox users.

I haven’t used tomb and I don’t think I really have a usecase for this, but I respect the on-brand command aliases.

Yep, that was it. Thanks for the reminder.

It works great for me on Arch with Hyprland, even though that really isn’t designed with touch in mind. I think there are some programs that provide touch gestures generically (egg something comes to mind?), but I’ve never needed them. I’m sure if you go with Gnome or something it would work great, so long as the touchscreen is recognised properly (I’ve never had issues, but that doesn’t say much about if you would). I’d just get a live USB with whatever you would install, and see if it physically works. If it does, I’m sure there’s a DE/WM that fits the workflow you want.

You could do that at the firmware level, with QMK or ZMK macros (or, presumably, whatever other firmware). It might be a long one, but launching an application or the like could just be typing the combination that runs it. I haven’t used KDE, but something like super, then type the name, then enter, should work.

Having said that, a quick look at keyd proposed by the other replier does seem like it has more than enough capability, and if you have one setup you want to use it for and not move the keyboard between computers, it very well might be the better choice for you.

While this generally gets a little chuckle from me, it really needs to die. It’s as old and untrue now as ‘ubuntu is just for noobs’, etc. I have never broken Arch with an update. I have broken it with changes I’ve made actively, but never just an upgrade. If you want to say the install process is unintuitive, or that the lack of defaults for practically anything you actually use is debilitating for new users, or overreliance on AUR is unsafe, or any number of other valid points, fine. But it doesn’t just break everything constantly.

You run Arch.

I’m on hybrid Intel/Nvidia, and it works fine. The discrete card isn’t particularly powerful, so I don’t use it much, but it works pretty much as I would expect. If you’re wary, just try on a live USB. It won’t harm your computer as long as you check it’s working before installing, and if it works on there it should work once installed. Might be best to start with a distro that at least has a toggle for proprietary drivers in the installer though, so you don’t have to do any faffing about yourself.