My current setup is Julia 1.5 run from the terminal and Visual Studio Code as editor (augmented with BBEdit to overcome VsCode's shortcomings in multi-file search and replace).
My startup file loads the packages OhMyREPL and the. Revise comes after packages from the standard libraries, so it does not track changes to those.
It appears that the default editor is determined by the system wide file association. No need to set the JULIA_EDITOR environment variable.
Updating to a new version¶
After starting the new version, basic packages need to be added so the startup code can be run (e.g.,
OhMyREPL). In my case these are:
]add OhMyREPL Revise
The bash profile needs to be updated to point to the new version. Alternatively, create a symlink for the new version with
rm /usr/local/bin/julia ln -s /Applications/Julia-1.5.app/Contents/Resources/julia/bin/julia /usr/local/bin/julia
The Jill bash script automates this process.
There is no need to copy installed packages to the new version's subdirectory. They are downloaded again as needed.
Customizing the REPL¶
On MacOS, meta-X means Esc-X.
There does not seem to be a way of binding Alt-x.
Customizing key bindings is somewhat tricky. One has to edit startup.jl to define a function that modifies the key map.
I have not been able to assign Ctrl-H and similar. Perhaps iterm intercepts them, but they always arrive as control sequences.
Invisible lines in stacktraces (1.6): This happens for various colorschemes. In
iTerm, set the minimum contrast slider to make those lines visible.
Set the Julia executable path to
/usr/local/bin/julia (the symlink created above).
A bash script that links an external terminal REPL to the Julia VSCode extension.
When problems with package operations occur, it often helps to reinstall the main registry:
pkg> registry rm General
Julia will automatically redownload the general registry when needed.
Clearing out the package cache may also help.