Was recently watching a musician, who’s much more proficient than me, creating a song in 7/4 time. And the whole time, he was like, oh man, this is so weird. Apparently, this was one of the first times that he worked in 7/4.
Meanwhile, you can be glad if my unskilled ass can sit still on one kind of meter for more than a few measures.

And like, he’s always got a baseline rhythm and repeating melody elements, then breaks it up with all kinds of effects and key changes.
In my songs, I practically never write straight repetitions. There’s pretty much always a different twist the second time around. Even my drum lines are generally intentionally arhythmic.

Yeah, just found that interesting, how even at a lower skill level, I can partially go for much more advanced concepts, and will do so just because I like them. There just is a big range of ways in which one can create familiar-yet-entirely-new music.

recreational coding

Well, good news, it actually is fun to dick around in the Nix configuration and see those changes manifest on your system.

The purpose is similar, i.e. configuring a system, but I’d say Ansible works best, if you need to make a few small changes from an existing distro, whereas NixOS rather takes the approach of controlling everything about the operating system.

And in many ways, controlling everything is actually simpler.

As the other person said, the bit about Arch is just the preamble.
But you can use Nix Home-Manager on Arch (or other distros), if you’re so inclined, which will give you that reproducibility for the stuff in your home-directory.

In some ways, this is like backing up and restoring your dotfiles, but it allows you to template those dotfiles and depending on the program, it offers simple ways to populate the dotfile templates. For example, KDE applications don’t generally offer very legible dotfiles and so configuring e.g. a panel via dotfiles is kind of a pain. To help with this, there’s Nix Plasma-Manager.

Copy Link to Highlight is my favorite addition.

To be fair, your “SUUUPER stable” is another person’s “not really going anywhere”…

Yeah, I also recommend this. Particularly with laptops, it’s good to have a full-fledged desktop environment, since you’re more likely to need WiFi, power management, easy display configuration etc…

Then you open it up and the single bean fills out the entire can. They had used a very big bowl for that photo.

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…

“Liebe die Liebe”. It’s a complete sentence, probably. 🙃

(Translation would be: “Love (the) love”)

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

deleted by creator

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.