That’s nice, but what is the criterium for which is the environment selected by default when one types “o” ?
With push! the temporary environment goes to the end of the list and it is still the default one chosen (which is nice).
Aah, I guess now push! is indeed better for temp env! It wasn’t the case until recently, and most likely I chose insert!(2) originally because of default selection in the dialog. After try_prompt_pkg_add: on "other" preselect the first non-default env by aplavin · Pull Request #3473 · JuliaLang/Pkg.jl · GitHub, it preselects the first non-default env, and push! works just as well!
2 Likes
Is the possibility of always having a temporary environment in that list considered?
I don’t see any downside, and it would suggesting a good package management workflow for casual users much simpler.
1 Like
(y/n/o) [y]:
when this feature was added.
@StefanKarpinski and I were talking about having a y/n/o/t where t would create and activate a temp enviroment.
Push back was that it would be too complicated.
And I solved my original need by just creating TestEnv.jl
since I was mostly wanting to use that to test things interactively
6 Likes
Both this feature and TestEnv are great! I use this [o] autoinstall to temp dir way more than TestEnv though, mostlty not for package testing but for running some quick computation in the REPL or playing with an interesting package.
2 Likes
Why is the “2” important?
Not really, it is just that I want that the temporary environment is the one chosen by default when the options are shown, and that depends on the order of the entries of the path.