"Invalid virtualenv specified" in mkvirtualenv
Closed this issue · 5 comments
cc @usharf
I can't reproduce :/
This sounds like what might happen if you didn't have the virtualenv executable on your PATH though. What happens if you just run:
(shell-command "virtualenv test")on it's own?
Also what happens if you git clone latest master and run the test suite? (which you can do with cask install --dev && cask exec ert-runner, if you have cask installed)
Also, what happens if you try it in an emacs with no other packages or configuration loaded (cask exec emacs -Q followed by (load-file "virtualenvwrapper.el") should get you one).
I've tested it in a new machine I happen to prepare, with pyenv and the virtualenvwrapper plugin installed, and it seems to work just fine.
I've tried mkvirtualenv and cpvirtualenv and both seem to do what's expected.
I have $WORKON_HOME set to $HOME/.virtualenvs in bash (on OS X, imported into Emacs using exec-path-from-shell).
Are you happy with closing this as a misconfiguration issue on your part then?
I think the thing to do on my end is probably to add a more helpful error message when no virtualenv executable is found, so I might leave it open just as a reminder to myself.
implemented a more useful message on mkvirtualenv, so I'm going to close this.