Jump-to-definition for variables

[fonsp]

Easy to add in, because Pluto already has the list of which variables are defined where, but disproportionally difficult is:

• Shadowed variables, i.e. the second x in f(x) = x does not refer to the global x.
• Local variables (defined in the same cell).

Pluto understands both cases, but that information is not linked to a line number - it's accumulated at the cell level.

The same shortcut as VS Code: Ctrl+Click.

[fonsp]

Needs the same mechanism as #13. (It's only a "Good first issue" after that's done.)

[fonsp]

@pfitzseb do you have any tips for making the string index available inside the AST? Does that question make sense?

Can we re-use something from the VS Code project?

[pfitzseb]

The question makes sense, but it's also why CSTParser exists: To get a syntax tree with column/line info available (and one that is round-trippable).

StaticLint.jl has everything you'd need here, I think, but I'm not 100% sure how easy it is to interface with. Juno also supports this just based on CSTParser (see the code here).

[fonsp]

Thanks for the Juno link - this looks similar to what I have written so far (ExpressionExplorer.jl), with metadata on top of just tracking Symbols. I will look into it more!