Sebastian Pfitzner

MultiDocumenter 0.8 should somewhat support vitepress generated docs, at least visually. You will get two top-bars and potential keybinding conflicts though.

You can always use `Main.@run` inside of your module. > I included this file into the module in order to have code jumping and completion support, but this interacts badly...

Might be due to 1.12 or something? Will take a look. In the meantime you should be able to use the normal Jupyter kernels (this one's provided by the extensions...

> I configured the path to the executable folder found under the .Julia and .juliaup directories. However, I'm unable to get this feature to work. Did you enter the full...

That's fairly expected. You can disable the progress logging integration in the settings.

What Julia version are you on and how many threads are you running Julia with? I'll try reproing the issue, just in case there's something unexpected happening here.

Current main works fine for me: ``` julia> with_logger(TerminalLogger()) do @time sample(M(), S(), MCMCThreads(), 50, 10; progress=true) end; Sampling (8 threads) 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| Time: 0:00:00 0.476202 seconds (38.04 k allocations: 3.524...

I suspect the difference is mostly down to 1.12 starting with an additional interactive thread by default. I don't quite understand why you're seeing a 26x performance on 1.11 though...

Caused by https://github.com/julia-vscode/julia-vscode/pull/3852. An easy way to add some distinction between code blocks in docstrings and actual code is to add something like ``` "editor.tokenColorCustomizations": { "textMateRules": [ { "scope":...

This isn't something we have control over in this extension. Styling gets decided by the theme, not the grammar -- the config snippet above _could_ also replicate your theme's styling...