Skip to content

ordering of using Revise in startup.jl #663

@ctkelley

Description

@ctkelley

I have been using revise the old way with

atreplinit() do repl
    try
        @eval using Revise
        @async Revise.wait_steal_repl_backend()
    catch
    end
end

and everything worked well. I have never had any luck with simply

using Revise

Now it seems that the old way is being phased out and I had to figure out
what to do. My startup.jl file has many using statements at the start.
using Revise works perfectly if it is the first line in the startup.jl
file and did not work when it was the last of the using statements.

Did I miss something in the Revise documentation?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions