-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
include
better at finding errors in line numbers than includet
#437
Comments
What Revise version are you on? With 2.5.3 (which includes #424) I get this:
I'm not sure we really need all those Revise frames in the stacktrace, but at least it does point out the correct line. |
Sorry, I should have been clearer. My error isn't on It happens when I make a typo in the midst of editing, calling I just updated to 2.5.3 and the behavior is the same. |
If I replace the broken line with one that parses properly, load the package, and then switch back to the broken version, here's what I get:
For me it's still showing line 87. |
I think this is fixed. Please provide more info if it is still a problem. |
Tim,
I think we chatted about this on slack a while ago. I found an MWE. Maybe it isn't as minimal as it could be but I ran into the error again.
Here is a script with an error in it.
My workflow is just
includet(q5.jl)
and then calling everything via a short module name. RunningRevise.errors()
on this script, after it has been working, produces the following output. As you can see it's not obvious what the error is.Running
include("q5.jl")
gives a much more informative error message. It tells me my error is on line 87.Hope this is helpful in improving Revise. love working with it.
The text was updated successfully, but these errors were encountered: