mib

Nixops now doesn't build without the insecure flag due to [CVE-2023-32681](https://nvd.nist.gov/vuln/detail/CVE-2023-32681), which requests v2.28.1 is affected by. As far as I understand, the CVE doesn't affect normal usage of Nixops...

would love to hear if there's anything new about this. struggling to get it to work properly when changing colorscheme while neovim is open. i've got this, but it doesn't...

> > vim.fn.system("printf '�[6 q' > " .. tty) > > You can print to the terminal via `chansend(v:stderr, "...")` Well hey, that certainly makes it a lot simpler! Thanks...

> Is there a chance that the work from #64 can be released with a tag? I don't see why not, but you'd have to get @cretz to handle that...

@lizthegrey: did using the branch work out for you? :)

I definitely second emulating the tap crate's behavior, favoring @ibraheemdev's approach. Having a `_matches` variant could be super convenient, especially with both mutable (`tap`) and immutable (`inspect`) variants.

does anyone know if there are any downsides to @TheArcaneBrony's approach? seems pretty good to me, all things considered :)

> > does anyone know if there are any downsides to @TheArcaneBrony's approach? seems pretty good to me, all things considered :) > > Looks like with this approach nix...

also, just fyi: instead of `eval`'ing twice (once with `nom`; once with `nixos-rebuild`), there's the alternative of building to a known directory (I use `/tmp/nixos-configuration`) then running `sudo $KNOWN_DIR/bin/switch-to-configuration switch`....

Any progress on this? would really like to build content-addressed derivations with nom! :)