@User if you wanted to give the gitpod another try, it supports multi-vault now https://wiki.dendron.so/notes/3e519113-5820-4a84-bef8-85103a7b296b.html#gitpod

Indeed it works now with just small glitch: index.html refers to

out.csv

not

commits.csv

. Renaming the file fixed it. By they way: I think it should read `dendron-cli`in the docs rather than

dendron

?

your right. fixed! as for

dendron-cli

, we're shortening it to

dendron

now.

dendron-cli

is now an alias to

dendron

@User it is a functional partial fix, it seems! thank you. it looks like i still need to edit the config yaml at different workstations to ensure that it doesn't create a second

fsVault: vault

line, but editing it does something now!

@User heads up that you can now toggle hierarchy display on a per note basis: https://wiki.dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f48.html#hierarchydisplay

Somehow Dendron 0.36 seems broken regaridng multi-vault: whenever I try to open an existing note from the "second" of my vaults a new note with the same name is created in the "first" vault. Dendron log here:

taking a look

I closed all open editors and tried the same leading to this error: {"ctx":"h:run","err":{"status":"unknown","msg":"","payload":"{\"msg\":\"cannot open file:///c%3A/Users/Bassmann/Dendron/solid-octo-dollop/OCSP.md. Detail: Unable to read file 'c:\\\\Users\\\\Bassmann\\\\Dendron\\\\solid-octo-dollop\\\\OCSP.md' (Error: Unable to resolve non-existing file 'c:\\\\Users\\\\Bassmann\\\\Dendron\\\\solid-octo-dollop\\\\OCSP.md')\",\"stack\":\"Error: cannot open file:///c%3A/Users/Bassmann/Dendron/solid-octo-dollop/OCSP.md. Detail: Unable to read file 'c:\\\\Users\\\\Bassmann\\\\Dendron\\\\solid-octo-dollop\\\\OCSP.md' (Error: Unable to resolve non-existing file 'c:\\\\Users\\\\Bassmann\\\\Dendron\\\\solid-octo-dollop\\\\OCSP.md')\\n at file:///C:/Users/Bassmann/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2163:62975\"}"}}

just as a sanity test,

Reload Window

doesn't fix this?

No unfortunately not. Afterwards creates a new note again

ah, your navigating by wikilink?

No clicking on a file name in the tree view

got it. managed to repro and pushing out a fix

new version is out (36.1). thanks for catching this!

Awesome, thanks for the quick fix! How do I force VSCode to update to this version?

it usually just takes a few minutes btw me publishing and the extension being available.

reload window

usually will auto check for updates

Ok so I'll be a bot more patient (not my core strength ;))

thanks for catching this! you can tell I don't use the tree view all that much 😅

Hehe I use it a lot to go to stuff. BTW your proposed index page solution doesn't really address my issue for the tree view but apparently not too many people use it.

got it. i do want to revamp the tree view, the main blocker is that I'm planning on replacing the whole thing with a custom web component in the coming weeks so want to hold off doing work on the tree view until that's in place

Perfectly fine no worries

Confirm it's working now. Thanks again for the fast response!

thanks for the fast QA 🙂

Just discovered a markdown rendering bug. Having two

$

characters in a line is interpreted as katex. And some words are randomly getting italicized. Am using “Dendron markdown preview enhanced”

There are 107 repo's when searching for dendron. And there are two results for the dendron topic (which both happen to be related to this project fortunately). Adding the dendron tag to dendronhq repos will for now at least return our dendron results only

On github

this is because of inline rendering via katex. you can turn it off by setting

"markdown-preview-enhanced.mathRenderingOption": "None",

in your workspace settings

did not realize there were so many... you should be able to scope search to just

dendronhq

Thanks for the prompt reply kevin. I'll give it a go.

agreed though I'm not suggesting it for my sake but for those who like to navigate via or browse by topic. Also, don't topics trend and get featured in the github newsletter? Its low hanging fruit for some extra exposure