I tried this earlier and I’m trying this now. Both times do not work. This time,
Julia> using Juno
Julia> Juno.@enter split("hello, world", isspace)
It takes a long time to run, like forever, with a relative quick computer… it is unacceptable.
Yeah, the macro invocation itself works, but the REPL input is broken as you observed above:
Thank you for your quick reply. I finally roughly figure out why do I get the feedback message “no previous command executed”. Somehow I typed “n” and then press enter, but debugger does not get it. Debugger understands it as “nothing”, which literally means nothing is typed… sigh. In this case, it will execute the previous command. But there is no previous command.
Juno.@enter split("hello, world", isspace) takes less than 10s on my machine until it drops you into the debugger. The second invocation is basically instant.
1 Like
Are you sure that’s not just the usual “Julia has to compile methods the first time you call them” latency? It should not be too bad on the second try.
Also, why are you calling using Juno from the REPL? Either you should start a plain REPL (e.g., from the linux prompt) or you should start atom and be using Juno already. Then:
- if you’re in a plain REPL, use Debugger.jl and the
s,n, etc. commands to advance to the next line. If you want to see the value of a variable, hit ` so that you enter the “julia” mode (and hit backspace to return to “debug” stepping mode) - if you’re in Juno, use the GUI tools to step. You’re effectively already in the variable-evaluation mode, anything you type on the command line gets interpreted within the scope of the program. In other words, in Juno you don’t use the
s,n, etc. commands
2 Likes
I’m using Atom + Linux Ubuntu, so I’m in Juno interface already. But either I miss something, or something misses me. Sigh. it does not work with my Juno.
Your screenshot above suggests you’re using an ancient version of Juno. (Yours is still affected by https://github.com/JunoLab/Juno.jl/issues/264, which was closed an eternity ago by Julia standards 
.)
2 Likes
The screenshot was taken from a weblink, it’s not from my computer. I just checked the Juno package by using Pkg and Pkg.installed(), the version is v"0.7.2". I guess it is not an ancient version. On the other hand, I remembered I checked the Juno editor package installed, it is actually uber-juno 0.3.0, the official installer of Juno, the Julia IDE. It is the uber-juno who does not work in my computer. Any comments about it?
Can you paste Juno’s debug info into a gist? You can get it either from the Julia Client: Debug Info command or the Juno > Debug Information menu entry.