Sebastian Pfitzner

That's easy enough, but then you can't initially `@edit` a function (because that takes you to the files in `use/share`).

Revise would need to fix `.file` for all methods on load then, no? That doesn't seem like a good idea.

I don't think there's a way for `includet` to stay a function _and_ get its caller's scope. You can of course already use `includet(@__MODULE__, "myfile.jl")`.

Can you get some more output (e.g. the LS stacktrace)?


We may need to start thinking about a eslintrc style config file for linting (although I guess having workspace-specific settings would also work for VS Code at least).

Yup. Also has the advantage of working with non-VS Code editors.

Isn't this just a replace operation, which is already support via `Ctrl-H`?

Yes, static analysis is for sure more limited in Julia. Do you have concrete examples where our current refactor utilities fail?

This change also affects refactoring. The issue with the current implementation is that we *don't* correctly follow Julia's scoping rules. You'd end up going from ``` function ff() x =...