Sebastian Pfitzner

I'll need to look into this more, but I assume the JS side of the extension currently doesn't do any `realpath` calls and just works with the URI that VS...

Try deleting `/Users/pitipatwongsittikan/Library/Application Support/Code/User/globalStorage/julialang.language-julia/symbolstorev5`.

We have a `julia.completionmode` setting, which is kinda similar but only affects unexported bindings [Peek 2024-01-09 15-46.webm](https://github.com/julia-vscode/julia-vscode/assets/6735977/3a4beeb9-0ee5-49a4-a36d-465560be1975)

Why are you checking that explicitly instead of emitting log messages unconditionally at the "right" level and letting the logger determine whether the messages are discarded or not?

Ref https://github.com/julia-vscode/julia-vscode/pull/3380

Not sure what's going on here, but you should be getting those hints if said packages are in your current environment:  There seems to be a specific issue with...

Yes, this is a JET issue. Our API supports column info, but JET currently can't emit that (due to `Expr` not having them).

``` @async while true display(VSCodeServer.InlineDisplay(), report_file(path; analyze_from_definitions=true)) sleep(5) end ``` in the REPL should do the trick.

Hm, ProgressLogging nominally supports nested progress bars (but not sure how well VS Code handles that case -- probably not well at all). Might make sense to implement the aggregation...

While we could probably work around that, this really feels like an issue with CondaPkg. It shouldn't rely on string comparisons to determine file identity.