aboutsummaryrefslogtreecommitdiff
path: root/flake.nix
AgeCommit message (Collapse)Author
2024-08-26flake: Remove maintainer commentIvan Molodetskikh
Effectively other contributors maintain it now.
2024-08-25fix `cargo run` on nixossodiboo
this boils down to adding some extra dependencies to the shell environment. they're also inherited from craneArgs because the ones from the package are actually transformed into the WRONG outputs of the packages. also refactors to use craneLib.devShell because it's somewhat cleaner.
2024-08-14Fix `nix build`Fea
2024-07-08flake: update nix flakeSuyashtnt
Signed-off-by: Suyashtnt <suyashtnt@gmail.com>
2024-04-30Add `libXcursor` and `libXi` to nix flakeMichael Forster
In my tests this was necessary to develop Niri using non-NixOS Nix. Otherwise Niri panics with this error message: called `Result::unwrap()` on an `Err` value: EventLoopCreation(NotSupported(NotSupportedError)).
2024-03-01Correctly handle parsing of Binds and DefaultColumnWidth (#234)sodiboo
* add dev dependencies to flake * parse only one default-column-width * require exactly one action per bind, and unique keys for binds * use proper filename for config errors if possible * fix duplicate keybinds after invalid action, lose some sanity
2024-02-12exclude visual tests from nix, closes #181Kiara Grouwstra
2024-01-18Add a config parse error notificationIvan Molodetskikh
We can't rely on a notification daemon being available, especially during initial niri setup. So, render our own.
2024-01-17Add an IPC socket and a niri msg outputs subcommandIvan Molodetskikh
2024-01-10Add Nix Flake (#77)Bill Sun
* Add Nix Flake Co-authored-by: Bryce Berger <bryce.z.berger@gmail.com> * Describe nix flake in readme * Add `niri-config` to build source list * Add maintainer info Add comment at top to indicate the Nix Flake file is community maintained. * Clarify Nix/NixOS README instructions * Shorten Nix/NixOS build instructions Co-authored-by: Ivan Molodetskikh <yalterz@gmail.com> * Move NixOS installation instruction to "Tip" section --------- Co-authored-by: Bryce Berger <bryce.z.berger@gmail.com> Co-authored-by: Ivan Molodetskikh <yalterz@gmail.com>