<rekado>thought about GUIX_EXTENSIONS_PATH: I think I’ll have to use something other than guix/scripts/ as the directory.
<rekado>say you have “guix” itself installed in a profile; all the Guix scripts themselves would end up being considered extensions, which is obviously incorrect.
<rekado>you aren’t supposed to install “guix” into your profile, but it’s probably better to be safe
<zimoun>rekado: I have not look into the details of your recent patch, but what I would like to have is “guix foo” where ’foo’ is a Guile module living somewhere, say GUIX_EXTENSIONS_PATH. That way, it would fully replace “guix repl -- path/to/module/foo.scm”; which is somehow another way to extend. :-)
<rekado>it only needs a slight modification to use guix/extensions instead of guix/scripts; but the idea is the same
<rekado>a few months ago I tried to implement the inferior route, but using the invoking Guix instead of creating a new inferior from channel specs; it did not go well, because the API doesn’t allow me to just invoke any Guix (such as ~/.config/guix/current/bin/guix) as the inferior.
<rekado>I suppose it would work with “guix repl”, though
<rekado>I’d make the GWL spawn a “guix repl” process and evaluate all the environment/profile computations in there.
<civodul>doesn't using an inferior prevent you from doing interesting things?