Auto-activate: changing from one directory with a virtualenv to another with a different one produces error messages

[daisylb]

It also takes longer than expected, although it does succeed in the end.

[~/project1] [ve1] $ cd ~/project2
pipe: Too many open files
fish: An error occurred while setting up pipe
pipe: Too many open files

[~/project2] [ve2] $

[justinmayer]

Probably not the best place to ask this question, but why did you decide to use .vfenv instead of the more common .venv? Is there something special or different that VirtualFish is doing in order to warrant using a different identifier? For folks who either (a) migrate from virtualenvwrapper or (b) routinely switch between fish and bash, wouldn't it make more sense to retain consistency with the .venv nomenclature instead of creating a new identifier?

[daisylb]

@justinmayer see #5. (Also, feel free to open new issues for questions like this, just apply the purple 'question' label)

[daisylb]

I'm going to close this, since I've not encountered this problem since bf813f3. If anyone else encounters this issue and is running the latest version, feel free to reopen.