Open vtjnash opened 3 years ago
It will already have precompiled everything by then? Or do you mean when you have turned off auto precompilation.
I mean instead of. Otherwise simple workflows like above can end up recompiling several times, and I've got hundreds of packages installed, so it leads to several minute delays between steps (that I end up skipping with ^C).
I do think there's an elegance to this, lumping everything together does seem beneficial
But on the other hand it seems like it could be a little jarring from a UX perspective that exiting Pkg REPL would become complicated and slow whereas currently its simple and fast. Feelings of being trapped in Pkg REPL?
Of course this can be almost achieved with turning auto-precomp off, and just writing pkg> precompile
before exiting. (Maybe there should be a short form too?? pkg> pc
?)
Or perhaps if the user knows they want to do a series of things in Pkg REPL we could support concatenation of pkg commands?
pkg> up
add Foo
dev Bar
build Bar
... # do all the stuff
Precompiling...
But that could get tedious when errors occur.
One proposal over in https://github.com/JuliaLang/Pkg.jl/pull/2248
Is this still possible? I see the referenced PR got rejected. It is very annoying to have to wait a minute between consecutive package operations.
I often think about this too. I don't really see #2248 as being rejected, just postponed. Perhaps I shouldn't have closed it. Stefan's suggestion in there to make it customizable seems like a good way to go.
I'm not sure I prefer that the mode is sticky, but since it is, it'd be really nice to be able to queue a sequence of operations, and have them all applied when I switch back to the main REPL. (ignore the version number in the prompt, I'm on master, but I like the name v1.1)
For example: