David Arnold

A couple of days ago, I also had a thought on relative-to-toml file paths in the context of wanting to load per-repo devshell modules (without resorting to `.nix`)

That's what the `extraModulesPath` is for: https://www.github.com/numtide/devshell/tree/master/modules%2Fdefault.nix

Oh, I just spotted it's unset via the `shellHook`, maybe we shouldn't: ``` shellHook='# Remove all the unnecessary noise that is set by the build env unset NIX_BUILD_TOP NIX_BUILD_CORES NIX_STORE...

I may add, that I'm giving the integration between `devshell` and `nixago` a shot and this is my first conclusion: https://github.com/nix-community/nixago/issues/29

It might. I can try to free some time in the next few month, please keep nudging in case I'm not reactive :smile:

Tangentially I'm also currently trying to find ways how to add proper multi-shell support. I'd be interested in exploring. My current thinking is just: don't at all: ```nix { devshell.startup.completion...

Here are my findings, so far while trying to get shell completion to work across different shells: - `nix develop --command "$SHELL"` is potentially slow since it reloads the entire...

So this PR is a direct conclusion of the above analysis: https://github.com/numtide/devshell/pull/205

After furthed research, I conclude that it would be best to use `nix print-dev-env --json ...` which returns something link the following JSON JSON ```json { "bashFunctions": { "runHook":" \n...

Looks like we can have this a _lot_ easier: ```console nix build "${nix_args[@]}" --profile "$profile_path/shell-profile" bash -c "source $profile_path/shell-profile/env.bash; SHLVL=$SHLVL; exec $SHELL -i" ``` - your current shell (required to...