[go: up one dir, main page]

  • 0 Posts
  • 111 Comments
Joined 1 year ago
cake
Cake day: February 19th, 2025

help-circle








  • lmr0x61@lemmy.mlto196@lemmy.blahaj.zoneBubble Rule :3
    link
    fedilink
    English
    arrow-up
    6
    ·
    9 days ago

    If you’re on the US like me, it’ll take you and I out with it. Worth it in the long-run, of course, but as always, we hardly ever gain anything when wealthy win, but boy are we made to suffer when they lose.

    As someone else said, more succinctly: privatize the profits, socialize the losses.








  • lmr0x61@lemmy.mltoProgramming@programming.devWhy I love NixOS
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    17 days ago

    Yeah, that paragraph is where I stopped reading lol

    Blog post aside, NixOS is fantastic. Once you get the Nix DSL down, it makes everything so smooth once you know how to configure your system. The learning curve for me came not from the packages, but learning how to set up system/program configurations using configuration.nix, instead of the standard config files. But once you get that down, you can rebuild essentially the exact same system from a single file. I use it for my worker nodes on my server cluster, and it makes setup of new nodes a dream. Definitely recommend.





  • Hmm, this sounds like it could be solved by tweaking the systemd unit file for libinput-gestures. It’s better not to have the service wait a set amount of time (what if that amount of time isn’t enough?), but to depend on the this it is supposed to start after. My guess is you’ll need to do do the following:

    1. Find the name of the service that starts your compositor.

    2. In libinput-gestures.service, add a line under the [Unit] heading that starts with Wants= and then has the name of the compositor service.

    I can’t guarantee that’ll address your issue, but it might help.