Profpatsch
Profpatsch
> * there is a command I can run to update then (deliberately) switch to the new environment That’s effectively “build in the background but don’t symlink the gcroot yet”,...
> The new lorri one is : cd, and type enter until the prompt says the shell is ready. You should immediately see direnv output if you have built this...
I found two different instructions on how to update fish and zsh asynchronously: https://github.com/acomagu/fish-async-prompt https://www.anishathalye.com/2015/02/07/an-asynchronous-shell-prompt/
Can you try using `lorri shell` instead? Does this work? It should run the shell hook and then execute your normal user shell. dmayle ***@***.***> writes: > It appears this...
> After stopping all existing manually started daemons and running `systemctl --user enable --now lorri.socket` it's now working. Does this mean we are missing a step in the tutorial?
> So I am wondering: Is there a supported and reliable way to get `lorri` into a state where it will never let nix build stuff locally: Either fetch everything...
We don’t support that yet, but it’s a good feature request. We deprecated `lorri shell` and are focusing on `direnv` (which does the environment setup), so I *guess* you’d have...
I’d tentatively close this for now and recommend that one just runs `nix-shell --pure` manually if that’s a required use-case.
> Personally I'd love to be able to use lorr's features with a pure shell sometimes. What’s your exact use-case there? Mostly to unset everything in the environment?
@curiousleo can we do that with the revived `lorri shell`?