Jonas Chevalier

The main problem is that a user might open multiple shells on the same project. This is an idea that I keep running into. A number of users have proposed...

Nix works fine in WSL and WSL2 as far as I know. The only issue is that it doesn't start services so it must be a single-user install.

Looks good! It would be nice if there was a new `types.path` that could resolve those relative paths.

yes, it's compatible. of `use nix` when using `shell.nix`

This is an issue with Nix. `nix develop` is calling `mktemp` before entering the environment: https://github.com/NixOS/nix/blob/13e49be6602314fe5e5d7beb8a807d5d892e864e/src/nix/develop.cc#L198

I had to remove the pkgs.stdenv machinery in order to re-build a clean user experience. This means that all of the standard nix-shell hooks are missing. For now, the best...

I have two sides to this: Ideally, the devshell environment shouldn't be too fat. The issue is that each additional package makes it more expensive to load a fresh environment...

I forgot to say that there is also https://github.com/numtide/devshell/pull/6 which was an experiment to propagate all the build inputs of a derivation to packages. The solution is not complete as...

That was one of the motivations for the CLI. At some point, I want to add some heuristics to `devshell init` so it can detect the project structure and infer...

@bbigras I added the `language.c` module to handle C dependencies. With a bit of nix code is should be possible to inject those on both sides.