Also ran nixfmt for consistent formatting of future changes.

This is more for general nix code, the style the package had before was formatting specific for expressions in nixpkgs https://github.com/nix-community/nixpkgs-fmt. I'd prefer if you reverted it.

Also ran nixfmt for consistent formatting of future changes.

This is more for general nix code, the style the package had before was formatting specific for expressions in nixpkgs https://github.com/nix-community/nixpkgs-fmt. I'd prefer if you reverted it.

Sorry about that, did not know there are two styles in play. I've completely reverted formatting changes and ran nixpkgs-fmt over the file to ensure it conforms to nixpkgs standards.

over the file to ensure it conforms to nixpkgs standards.

Uhnn, we don't have anything really official for this yet... So you can imagine some sort of impending code style battle 🤣 (hopefully not)
Myself and my collaborators feel strongly about that style being best aligned for nixpkgs, so I recommend it as much as possible.

It seems you using wnck makes this not work with wayland. Guess that's reworking to do in the future.

It seems you using wnck makes this not work with wayland. Guess that's reworking to do in the future.

Yeah, it's a pain, needed more robust window activation notifications to be able to implement the new trigger key checking for apps that aren't very accessibility savvy, hope to find a better solution in the future.

Thanks for the PR review @worldofpeace, much appreciated.