Profpatsch

@regnat do you have a good and/or complete description of the semantics of `nix dev-env`? As you mentioned, the lorri `keep-env-hack` also prints all dependencies that changed. In order for...

That is a good insight. We could maybe query the daemon in the `lorri direnv` call (via a command that does not yet exist) and display a warning if the...

This would work by adding a `lorri internal project-status` or similar, which returns the required information (e.g. last build crashed), similar to how `lorri internal stream-events` shows some history at...

We could add an `--attr` attribute to mirror the one in nix-shell. On Thu, Aug 6, 2020 at 12:16 AM Marcos Benevides wrote: > This is an example shell.nix: >...

Doesn’t require reboot, just a reload of the user daemon: ``` systemctl --user daemon-reload ``` This is a regression in nixpkgs: https://github.com/NixOS/nixpkgs/commit/b20a0e49c8c0d5c84b917bfbbe3f2ead31886a67#r38459106

> As such, would it not be better to just have the very resource-light `lorri daemon` command always be running? Most other user services e.g. on NixOS already seem to...

We are swallowing varlink errors in the check, so I assume there is a varlink error message here that we silently ignore: https://github.com/target/lorri/blob/93d93013217cd9aa09d2bd316d6c3abf827a6601/src/ops/direnv/mod.rs#L24-L32 cc @curiousleo @nyarly We should really pay...

Please check out https://github.com/target/lorri/pull/441 and try reproducing the problem after running `lorri self-upgrade local /path/to/lorri/checkout` @codygman, @pepeiborra. It should print a better stacktrace then and we can debug what the...

Ah right, if you want to test the NixOS service you will have to put the new lorri version in your NixOS config. If you use nixpkgs unstable, there should...

> The tooling opportunities were exactly what made this approach appeal to me. As an integrator, I always appreciate options. What does exposing the interface give us that a plain...