That is a good tip. Unfortunately, I am too fish to understand it. 🙃

I just type ps and in 9 out of 10 cases, my shell suggests ps -ef | grep <process-name>. So, it’s actually less for me to type than “pgrep”…

Ah, that was a brainfart. I do use pkill primarily. I just use the other command, when I’m not sure what the process is called…

Yeah, I especially don’t understand it here, because it’s a graphical tool. You don’t have to keep backwards compatibility.

Even if you’re worried about people depending on the format that’s being piped, you could keep only the piped format stable. We have the technology.

Yeah, I would often just grab htop because I had no idea how to read the CPU usage out of top.
For example, for me it says:

%Cpu(s):  0,4 us,  0,4 sy,  0,0 ni, 98,8 id,  0,0 wa,  0,3 hi,  0,0 si,  0,0 st

Now that I look at it, I can guess that us and sy are supposed to be user and system time. And I guess id is supposed to be idle.
I have no guess what the other numbers might be, though. And well, I would often like to see the CPU usage per core.
Now I know that I can just press 1t and get effectively the same view as in htop.

I might learn top’s filtering workflow, too. But so far, I always killed processes with ps -ef | grep <process-name> and then kill <pid>, which isn’t particularly more cumbersome, so will see…

What terminal emulator are you using where ctrl-c copies instead of sending SIGINT when text is selected?

I know that the terminal emulator built into the JetBrains IDEs works that way…

I can’t really sell this as a solution, as it requires quite a lot more involvement than a simple configuration file should, but I use Nix Home Manager with Plasma Manager for this.

This is part of the tooling you’d use on NixOS, but you can use it on other distros, too, and it generally works fine (although I’m not sure, if the current version of Plasma Manager still supports Plasma 5, in case you’re still on a distro with that).

Basically, it allows you to define e.g. keyboard shortcuts like this:

    shortcuts = {
      ksmserver = {
        "Lock Session" = [
          "Screensaver"
          "Meta+Ctrl+Alt+L"
        ];
      };

      kwin = {
        "Expose" = "Meta+,";
        "Switch Window Down" = "Meta+J";
        "Switch Window Left" = "Meta+H";
        "Switch Window Right" = "Meta+L";
        "Switch Window Up" = "Meta+K";
      };
    };

It then fucks up the formatting, so that it looks like KDE expects, and throws it into ~/.config/kglobalshortcutsrc.
(KDE does actually have a text-based config, it’s just borderline unusable.)

Well, and you can do this with lots of other Plasma options, too. Here’s their official example: https://github.com/nix-community/plasma-manager/blob/trunk/examples/home.nix

I’d argue that it’s Android’s DE for Linux.

Works fine for me. ¯\_( ᵔ ~ ᵔ )_/¯

A colleague always complains that KDE looks like Windows. She does also get jealous, though, when she sees me using poweruser features.

Typically, touchpad gestures (particularly multi-touch gestures) will work better on Wayland, because it has libinput.

Yeah, it’s explicitly built to run in a browser: https://agama-project.github.io/

I guess, the idea is mainly that you can also perform the installation over the network. I can imagine this being quite cool for setting up a Raspberry Pi or similar.

Non-GitHub changelog: https://fishshell.com/docs/current/relnotes.html#fish-4-1-0-released-september-27-2025

The default on Fedora is btrfs, which sounds like what OP is using.

Are there other types of people? Writing software to be bug-for-bug compatible with something else is really difficult and, yes, not fun at all. You will not find many people looking to volunteer for that…

Well, there’s a separate technology stack for virtualization. So, it would be similar in effect, but the way you get there is different, and it’s possible that it performs better or worse for certain scenarios.

That’s kind of hilarious. At first we had VMs to run entirely separate operating systems. Then we had Containers to separate everything except the kernel. And now we might get separation for just the kernel.

Yeah, part of the reason I like open-source. The devs don’t need to sell you anything, so they can just tell you that what they made is a steaming pile of garbage.

somewhat logical, but entirely in practice verb-noun command structure.

That’s supposed to be “impractical”, not “in practice”, for others reading along.

For example, the “proper” command to list a directory is: Get-ChildItem
The “proper” command to fetch a webpage is: Invoke-WebRequest https://example.com/

In these particular cases, they do have aliases defined, so you can use ls, dir and curl instead, but …yeah, that’s still generally what the command names are like.

It’s partially more verbose than C#, which is one of the most verbose programming languages out there. I genuinely feel like this kind of defeats the point of having a scripting language in the first place, when it isn’t succinct.
Like, you’re hardly going to use it interactively, because it is so verbose, so you won’t know the commands very well. Which means, if you go to write a script with Powershell, you’ll need to look up how to do everything just as much as with a full-fledged programming language. And I do typically prefer the better tooling of a full-fledged programming language…

I just want to say that you’re probably worrying too much about it. Of course, there is lots of things one can do to improve security (which the others here are listing dutifully) and it is foolish to just assume that one’s computer is entirely secure, because as a user, you will always have the ability to bypass that.

But there’s a pretty firm consensus in the IT industry that Linux is more secure than Windows. And that the popular Linux distributions are more trustworthy organizations than Microsoft.

So, it’s good to inform yourself, but if you survived on Windows, you at least should not worry about the Linux side of things. It’s more than fine.