Terje Larsen

Speaking of compatibility with `nix fmt`. Just plainly running `nix fmt` doesn't work as that will invoke. `nixfmt .` which is also not supported by `nixfmt`. ``` $ nix fmt...

Not the cleanest, but a current workaround is to create a wrapper and assign it to the formatter attribute, something like this: ``` pkgs.writeShellApplication { name = "nixfmt-wrapper"; runtimeInputs =...

Yeah, I guess `nix fmt` could be changed as well. Currently it does not support forwarding stdin by default, but you need to provide a `-` in order to get...

The reason why you see this behavior is due to how `variable-pitch-mode` works, when enabled it pairs the face `variable-pitch` with `default`. It is using the `buffer-face-mode` under the hood...

I see, because it is a YAML file right? I guess it could be possible to write a parser for the yarn.lock file in Nix, but might be some work....

We have discussed this briefly over at clj2nix: https://github.com/hlolli/clj2nix/issues/12#issuecomment-746744215 Now I see that this project doesn't use `fetchMavenArtifact` from nixpkgs. But perhaps we could come up with some solution that...

I'm guessing if this is adopted it could also potentially be a basis for fixing the issue #6124. My initial reaction is also concern about potential confusion of `nix dev`...

I am also able to reproduce this on our CI system. I have a build that fails with this every time. It always seems to be the same derivation failing...

For now there is a third party util that will achieve this for you, that comes with fish integration: https://github.com/junegunn/fzf

It does: https://github.com/junegunn/fzf/blob/master/install#L305-L310 It binds it to a ctrl-r binding by default which can be modified to your liking.