Sebastian Pfitzner

There is https://juliahub.com/docs/jlpkg/aMH2o/1.1.3/autodocs/, but yeah, fair enough.

Both of these edge cases should be avoidable by checking each new local scope for assignments that shadow a global, right? We already should have the logic for that.

We'll also need to think about proper UIs for all of this, especially the global refactors. I'd love to reuse `find-and-replace`s pane, but that doesn't seem to be possible. So...

It is: https://atom.io/packages/search?q=latex-completions

Hm, I can't reproduce this -- latex completions work just fine in docstrings and strings for me.

No, both cases work fine for me. What are your `Selector` and `Disable For Selector` settings?

Thanks for the very detailed analysis. Would you consider opening a pull request which implements the improvements and tests you outlined?

1. Set your default browser to Firefox 2. There's the semi-official `ProfileCanvas.html_file(filename)` for that (you can also use this to open whatever browser you want afterwards: ``run(`firefox $filename`)``)

Uploading the result of `Serialization.serialize(Profile.fetch())` should be enough for me to look into this, if you can't figure out a way for me to run a reproducer.

Yeah, that seems reasonable. I'm not sure how type printing actually works, but the low-tech solution I had in mind is using a LimitIO (there's a package I think?) for...