I’m using https://pkgdocs.julialang.org/v1/environments/ to make a new project directory, clean of all my added packages. I do: cd("MyNewProj") pkg> activate``` Thinking I'd have a clean environment, but pkg> st shows All my old packages. What's not working?

] activate without any argument goes to the default environment. You want ] activate . which says “activate in this directory”

Thanks. So much for the docs :grinning:

Why do you sound like docs doesn’t mention this: https://docs.julialang.org/en/v1/stdlib/Pkg/ When you are done experimenting with tutorial , you can return to the default environment by running activate with no arguments:

Also here . It’s also available at the REPL (@v1.6) pkg> ? activate activate activate [--shared|--temp] [path] Activate the environment at the given path, or the home project environment if no path is specified. The active environment is the environment that is modified by executing pack…

Well, I ctrl-f searched that page for “activate” and didn’t see the following dot. I guess it’s just assumed you’ll know to do that. But thanks for the default environment tip.

[image] The first example in that page has a dot, no?.

Why isn't pkg> activate creating a new environment?

New to Julia

rafael.guerra August 24, 2021, 9:47pm 8

If you are using Windows, you may like Jeeves, a nice utility to create new Julia projects, VSCode ready.

Topic		Replies	Views
What does `pkg> activate` do? New to Julia	7	1299	January 14, 2025
Julia is missing the deactivate command New to Julia	32	8363	December 3, 2021
Pkg environment is sticky (Julia v0.7-beta) Internals & Design	11	1576	July 10, 2018
How does one activate the environment of an added package? General Usage package	3	546	October 5, 2019
Can't find Project (environment) New to Julia	6	168	September 11, 2024

Why isn't pkg> activate creating a new environment?

Related topics