@timholy I realised in the examples above it's better for the revision to throw if there are issues, so I added a kwarg.

Maybe the default for that kwarg should be !isinteractive()...

I didn't get why you would not want to revise after tracking?

Sorry I don't follow.

Sorry, nevermind, I was confused about what the kwarg actually did.

I'd be open to removing the kwarg and just making it revise(throw=!isinteractive())

Can you expand on what's triggering the throwing? Bad code? Something else? In the OP I'm assuming the error stems from the command (Base.Threads.foo()) but that the keyword is targeted at something else?

Yeah, bad code.

Previously

• Edit code badly i.e. syntax errors.
• Run Revise.track(Base); include("test.jl")
• revise will soft fail, logging the parsing error and then continue to run test.jl with the un-revised Base, which you then have to interrupt

It's better for revise to throw.

JuliaRegistries/General#139976