Direnv: I think direnv should be changed and only emit that error whenever PS1 is part of the diff.
I think direnv should be changed and only emit that error whenever PS1 is part of the diff.
Another workaround is to change the zsh profile configuration to only set, not export the PS1.
_Originally posted by @zimbatm in https://github.com/direnv/direnv/issues/408#issuecomment-610387778_
Usability
zimbatm
👍1
>All comments
Even if PS1 is part of the diff, I feel it's too noisy to emit this warning, as the source may very well be a third party script. For instance, activating Python virtualenvs (source <venv>/bin/activate) triggers this warning.
Given that it's easy to locate the ticket and the wiki entry on this topic, I would suggest reverting https://github.com/direnv/direnv/pull/483 entirely.
nickray
on 17 Jul 2020
👍3
Was this page helpful?
0 / 5 - 0 ratings
Related issues
ssbarnea
路
5Comments
fschuindt
路
3Comments
allomov
路
3Comments
coulonxyz
路
5Comments
osterman
路
3Comments
Most helpful comment
Even if PS1 is part of the diff, I feel it's too noisy to emit this warning, as the source may very well be a third party script. For instance, activating Python virtualenvs (
source <venv>/bin/activate) triggers this warning.Given that it's easy to locate the ticket and the wiki entry on this topic, I would suggest reverting https://github.com/direnv/direnv/pull/483 entirely.