You can now hover over local (when debugging) or global bindings and get a pop-up showing their value (#614, #173)
Improvements
QoL improvements for Juno’s block-finding algorithm: docstrings are ignored when using Shift-Enter (#611), but can be evaluated by selecting them; un-indented triple-quoted strings now evaluate properly (#623)
Juno shows a warning if the Atom and Julia packages are out-of-sync (#617)
Better default keybindings for debugger operations, which are also shown as tooltips (#619 – thanks for getting started on this, @milesfrain!)
Since we provide fairly accurate local completions, Atom’s default auto-completions are now hidden (#620)
go-to-symbol can now handle include statements (#618, #613)
uber-juno now automatically installs the hyperclick package (#76)
More consistent usage of “Terminal”, “REPL”; removed mentions of “Console” (#631)
Bugfixes
Fixed toolbar icons that have gone missing with a recent release of the tool-bar package (#626 – thanks @daviehh!)
Better error handling for projects on network drives etc (#627)
Prevented named tuple elements from erroneously showing up in the outline (#172)
Fixed a regression with handling errors in show methods (#177)
The outline now properly shows implicitly destructured values like s, c = sincos(3) (#183)
Fixed a bug where the outline would omit ; in method definitions with kwargs (#184)
The outline doesn’t treat bindings defined in macro calls as global (#188)
MethodList entries are now shown in the same order as in the REPL (#189, #190)
Fixed a bug that crashed Juno’s auto-completions when trying to complete in e.g. a baremodule (#193, #194)
Fixed a bug where styling of inline results/workspace items/… could leak into subsequently rendered results if they were styled with unclosed ANSI escape codes (#232)
After updating (with apm update) Revise errors for first using, but works after the second (Win10, Julia v1.3.0-rc3.0):
julia> using Revise
ERROR: InitError: KeyError: key "evalrepl" not found
Stacktrace:
[1] getindex(::Dict{String,Function}, ::String) at .\dict.jl:477
[2] setup_atom(::Module) at C:\Users\cstamas\.julia\packages\Revise\cbX7Q\src\Revise.jl:1117
[3] __init__() at C:\Users\cstamas\.julia\packages\Revise\cbX7Q\src\Revise.jl:1069
[4] _include_from_serialized(::String, ::Array{Any,1}) at .\loading.jl:692
[5] _require_search_from_serialized(::Base.PkgId, ::String) at .\loading.jl:776
[6] _require(::Base.PkgId) at .\loading.jl:1001
[7] require(::Base.PkgId) at .\loading.jl:922
[8] require(::Module, ::Symbol) at .\loading.jl:917
during initialization of module Revise
julia> using Revise
# from here Revise workflow works
In normal REPL using Revise works fine.
Juno debug info:
After updating to this version, I have the following bug.
This one that seems to be triggered by the choice of Error Notifications in the Julia Client settings.
Here’s how I managed to reproduce the error:
If I use the default settings of
Error Notifications: true
Show Errors in REPL (Inline Evaluation): true
and then run an entire julia file (ctrl+shift+enter), I get the following error message
I do not get that error if I select
Error Notifications: false
Show Errors in REPL (Inline Evaluation): true
I can’t run anything else in the REPL, regardless of if the error messages shows up or not.
I upgraded and did the step of “add Atom#master” as well. I am still trying out the new features, but I noticed that mouse hovering to show variable value is not working for me in debug, regardless if I am using “Compiled Mode” or not. Nothing happens if I hover my mouse over a variable that already has value.
Is there any special setting to turn on data tip etc.?
I’m on Windows 10 with Julia 1.3.0-rc3. Below are the Juno Debug Info:
Is there an easy way to revert to Juno 0.10 if people have problems? I know you can install the old version in Julia using Pkg, but what about on the Atom side?
But in debug mode, hover data tip still does NOT show up, for either global or local variable.
Can’t repro this. Are you in Juno’s debugger ? And are you sure your local variables are already assigned ?
And in general, restarting Atom might help.
Latest update broke something. This is what I get after trying with apm uninstall and then install again:
$ apm install ink
Installing ink to C:\Users\mc0022\.atom\packages failed
> ink@0.11.5 postinstall C:\Users\mc0022\AppData\Local\Temp\apm-install-dir-119910-7320-1ijyce4.e6xy\node_modules\ink
> node scripts/postinstall.js
npm WARN lifecycle npm is using C:\Users\mc0022\AppData\Local\atom\app-1.40.1\resources\app\apm\bin\node.exe but there is no node binary in the current PATH. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
'node' is not recognized as an internal or external command,
operable program or batch file.
npm WARN enoent ENOENT: no such file or directory, open 'C:\Users\mc0022\AppData\Local\Temp\apm-install-dir-119910-7320-1ijyce4.e6xy\package.json'
npm WARN apm-install-dir-119910-7320-1ijyce4.e6xy No description
npm WARN apm-install-dir-119910-7320-1ijyce4.e6xy No repository field.
npm WARN apm-install-dir-119910-7320-1ijyce4.e6xy No README data
npm WARN apm-install-dir-119910-7320-1ijyce4.e6xy No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ink@0.11.5 postinstall: `node scripts/postinstall.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ink@0.11.5 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\mc0022\.atom\.apm\_logs\2019-10-10T10_30_28_528Z-debug.log
