porterjamesj/virtualenvwrapper.el

Deactivates current virtualenv even if interactive mode is cancelled

Closed this issue · 1 comments

Was about to submit a PR to fix this but the comments in the code suggest it is intentional. If I hit C-g after M-x venv-workon, why do I want to deactivate current?

oh, no reason, that sounds a like a bug to me. a PR fixing it would definitely be appreciated!