Re: broken by the FPATH environment variable defined by bash / lmod

On 8/19/26 11:06 AM, Eric Cook wrote:
> It is still just a naming collision, collisions that occurred long after ksh/zsh's implementation of
> FPATH to work like PATH, but with shell functions. which includes importing from the environment when it exist.
> 

to use PS1 and python virtual environments as an example:

# people commonly `activate' these environments by sourcing a script that prepends to PS1 and exports it
[llua@sakubo ~/src/foo]$ . ./venv/bin/activate
(venv) [llua@sakubo ~/src/foo]$ zsh -f
# but if you start zsh and PS1 from the environment is used, you will see something unexpected than `hostname%'
(venv) [\u@\h \w]\$

but making zsh stop importing PS1 from the environment would still manage to `break' that script when sourced from zsh,
since it also changes PS1 and export it to signify that the python environment is activated.