Kristoffer Carlsson

> I quite like what you did with the tests, overall. The issue as you say is worse line info. Even putting the `@test` outside like you suggest we don't...

Could maybe use https://github.com/JuliaLang/julia/pull/46138

Does this repro if you have `push!(empty!(LOAD_PATH), "@")` before adding the packages?

Maybe it is an stdlib but the `is_stdlib` fails..?

Same with https://github.com/JuliaLang/Pkg.jl/blob/ca9f4426568d85d2ed276b4ab3083dc8f2184478/src/REPLMode/argument_parsers.jl#L38 https://github.com/JuliaLang/Pkg.jl/blob/ca9f4426568d85d2ed276b4ab3083dc8f2184478/src/REPLMode/argument_parsers.jl#L81-L85

Similar matchers as in https://github.com/JuliaLang/Pkg.jl/blob/a657e5941c610fd3ce0405f6b419e4a88dc054ca/src/REPLMode/argument_parsers.jl#L13-L15 could be added. There is a bit of an ambiguity between a numeric branch name and a PR number with this syntax, but maybe that...

So you want to see the equivalent of what `gc --verbose` outputs? ``` (Pkg) pkg> gc --verbose Active manifest files: 6 found `~/JuliaPkgs/PackageCompiler.jl/Manifest.toml` `~/.julia/environments/v1.6/Manifest.toml` `~/.julia/environments/v1.8/Manifest.toml` `~/JuliaPkgs/Pkg.jl/Manifest.toml` `~/.julia/environments/v1.7/Manifest.toml` `~/JuliaPkgs/MKL.jl/Manifest.toml` ... ```...

Yes, I think the shared environments are indeed pretty uncommon and that people almost always associate an environment with a piece of code that they then have next to the...

> What I would like to see is a list of shared environments in the depot stack. You mean see the `pkg> status` output for all environments in the stack?

Also fails on https://github.com/JuliaLang/Pkg.jl/pull/3178 which I just updated.