3 ms·

How do you mean? I ran into a number of problems back when learning NixOS, but the error messages were usually sufficient to track them down.

• pxc 4y ago
  It's possible on NixOS to feel like you are struggling with a problem that you already know how to solve, dammit! This frustration hits harder earlier on in one's Nix journey, imo, when your first instinct may be to just edit that dang config file under /etc. As you progress, though, the 'layer of indirection' phenomenon almost reverses, as the Nixpkgs repository becomes a quick and reliable resource you can use to learn about how to configure and manage software that you didn't already know all that well.
  • ochoseis 4y ago
    Agree, once you realize how to traverse search.nixos.org and module definitions in nixpkgs it gets a lot easier.
  • ParetoOptimal 4y ago
    > just edit that dang config file under /etc. Using syncthing as an example do search here instead first: https://search.nixos.org/options?channel=22.11&from=0&size=50&sort=relevance&type=packages&query=services.syncthing https://search.nixos.org/options?channel=22.11&from=0&size=5... Or say you are using home-manager for something like neovim, use this options search: https://mipmip.github.io/home-manager-option-search/ https://mipmip.github.io/home-manager-option-search/ and search "programs.neovim".
    • pxc 4y ago
      Yep! The first habit one builds with NixOS is first searching the module systems to examine existing support. And these days, the module systems are so extensive that the result is almost always a pleasant surprise. :)