Daniel Hahler
Daniel Hahler
I like the idea (an indicator that an envshell is active) in general, but this approach requires PS1 to be exported. Since I am using another method than PS1 anyway...
@slafs Any update on this?
Thanks! #45 is merged - please rebase on master.
I would say by now that only `ENVSHELL_PATH` is required, because `ENVSHELL_NAME` can easily get derived from it in your shell (`${ENVSHELL_PATH##*/}`).
> I wouldn't say "easily". I can see that it's not obvious, but should be known / easy to find if you're into shell scripting. What about `$(basename "$ENVSHELL_PATH")`? We...
@lwm `ENVSHELL_NAME` is still in the PR. @slafs Do you want to remove it? Does everybody agree that a single env var is enough? I'm really undecided on this myself.
There appears to be no traceback. Using a 100mb full of NUL I get this error: ``` envdir envdir/ ls Unable to run command ls: [Errno 7] Argument list too...
I am merging issue #26 with this one. Maybe `envdir.open` could gain support for a new kwarg `overwrite`, which would control this behaviour. While it's certainly clear that `FOO` should...
I've looked into this again and have a working prototype, but in the end is probably better to just use: ``` envdir envdir/ env DB=somedb python app.py ```