Sridhar Ratnakumar
Sridhar Ratnakumar
We have a larger problem: https://github.com/direnv/direnv/issues/443 Even `nix develop` doesn't provide shell completion for `nativeBuildInputs` (eg: `exa`).
The alternative we now recommend supports shell completion through `just`. See https://github.com/juspay/just-flake
> Rewrite the wrapper Or we would just (no pun intended) write a `just` backend for mission-control: https://github.com/casey/just
> > Rewrite the wrapper > > Or we would just (no pun intended) write a `just` backend for mission-control: https://github.com/casey/just Or just use `just`: db46f39d46aacc289e1b054d830c3fe8ffdb3451
You can provide those Nix dependencies in the Nix shell. A `just` DSL is Nix is a viable idea, but it should have to be possible to replicate all of...
Ah yea, I've noticed this too, but forgot to open an issue. Basically if a mission-control script is named the same as something in your dev shell it'll lead to...
In you case, I assume the cycle is between `/run/current-system/sw/bin/install` and `install`
I'm not really sure about "M.Map Text OrgClock" (since each key can have _different_ type). I personally am compelled to use GADTs and DSum to represent the various properties in...
Also, since the rest of the newtypes in the library are defined without a field name, these types could just be: ```haskell newtype Priority = Priority Text newtype TodoState =...
Examples in the README would be appreciated.