got it. and the tree view isn't a good enough substitute? https://wiki.dendron.so/notes/f7ebd4aa-8ba7-4bc5-bd00-a1efc5315f07.html#dendron-tree-view

issue #210 is not about "tree view or folders" IMO it's about filing notes in dendron in folders while still remain the

.

naming syntax and the tree view for those who want a clean view of their notes when viewing/interacting with other tools

VSCode still loads the files list

So there’s a limit or an issue with the performance of having too many files in a folder on code-server?

(I hadn’t heard that and know a few people who do complex development workflows with trees that are very large on code-server)

I still get this error when using Dendron in Windows with WSL:

{
  "ctx": "h:run",
  "err": {
    "status": "unknown",
    "msg": "",
    "payload": "{\"msg\":\"no workspace file\",\"stack\":\"Error: no workspace file\\n\\tat Function.workspaceFile (/home/scott/.vscode-server/extensions/dendron.dendron-0.38.0/dist/extension.js:9:76947)\\n\\tat h.execute (/home/scott/.vscode-server/extensions/dendron.dendron-0.38.0/dist/extension.js:736:86934)\\n\\tat h.run (/home/scott/.vscode-server/extensions/dendron.dendron-0.38.0/dist/extension.js:9:103916)\\n\\tat async /home/scott/.vscode-server/extensions/dendron.dendron-0.38.0/dist/extension.js:9:79730\\n\\tat async S._executeContributedCommand (/home/scott/.vscode-server/bin/3c4e3df9e89829dce27b7b5c24508306b151f30d/out/vs/server/remoteExtensionHostProcess.js:86:106762)\"}"
  }
}

There's an issue already logged for it but it's difficult to use when trying to use different settings and being greeted with the same error each time

I also get this error when trying to open the

config

option

hmm, and you have a workspace open? https://wiki.dendron.so/notes/a6c03f9b-8959-4d67-8394-4d204ab69bfe.html#engine-not-initialized

yuppers

The configuration is super confusing and the documentation doesn't help if you say the configuration is in

.yml

then point to

.json

objects for the configuration options. I've spent the last 30 minutes trying to find an option that is in a json file but I'm being directed to use a

.yml

file to configure it.

yeah maybe the documentation for the config should be split into two pages one for Dendrons own config "the .yml file" and a page for the Settings that are part of the config from VSCode "the Json file"

It's a massive project and very powerful, thanks for cooking this up @User I've found the config option now but it wasn't because of the documentation (which is super detailed) what tripped me up is there's no reference for where these setting should go, look at the image the only file mentioned is the

dendron.yml

I read that and was confused to see a json object for the configuration

Also is there a way to identify that a user can't use certain command pallet options? I was running commands in one instance of vscode only for it not to work but did in the other one (workspace) 🤷 It's a bit disconcerting and disorienting when you think you need to be in one place when you actually need to be in another and there's no indication to say you're in the wrong place

Hey you may want to look at this PR -> https://github.com/dendronhq/dendron-site/pull/85 I tried my hand at improving the docs about the configs a bit.

it's not on complex trees of files, but rather too many files in a single directory. Also note that my code-server instance is hosted from my home cable internet (1000/40) so that may play a factor as well.

LGTM there still the confusing mention of the

dendron.yml

and mo mention (apart from at the top of the doc) of the file these setting can go in, it there's a specific mention of the

dendron.code-workspace.json

file there and that is where those settings go it would be clearer (imo) ========= ## folders - type: folders[] This is a list of folders that is tracked by your workspace. Should mirror vaults in

dendron.yml

. Each folder entry has the following structure

ts
type Folder = {
    // relative path to vault from workspace
    path: string
    // name for folder (default to folder anme)
    name?: string
}

========== Thanks 🙏

and that part got hopefully a better description.

Just created a Feature Request for this, https://github.com/dendronhq/dendron/issues/672 This should solve some of these Problems.

this was shipped with 0.40 🙂

In the documentation for tags, section [Pretty tags](https://wiki.dendron.so/notes/8bc9b3f1-8508-4d3a-a2de-be9f12ef1821.html#pretty-tags), it says

[[#foo|tag.foo]] --> will render as #foo

however that does not work for me, the hash symbol is not rendered. It's no big deal for me as I don't think I want to do that anyway, but I thought I should point it out.

thanks for the catch - this is due to how we currently parse links. will update the docs!

a work-around is to add the following to

~/.mume/style.less

...

a[href*="tag."]::before {content: "#";}

I'm really enjoying Dendron so far. There is only one thing which is a bit of a stumbling block for me, and that is the behaviour of links in the preview pane. I use a Zettelkasten system, closely following the methodology in Sönke Ahrens's book, and part of this is exploring your notes, following links and looking for connections. This is currently impossible in Dendron because clicking a link just opens the target in an editor (and worse it opens it in the same pane as the preview). I've seen it mentioned here that it is a known issue, but what sort of priority is it to fix this? Because it actually prevents me from working in the manner I'd like to.

what is the desired behavior? would opening the note in a split work for your use case?

I'm not sure what you mean by "opening the note in a split". My desired behaviour would be, where you have an editor pane on the left and a preview pane on the right, clicking a link in the preview pane opened the note in the editor in the left pane and updated the preview accordingly. So the preview pane behaves like a web browser, and the editor pane follows whatever it is diplaying, just as changing the editor pane changes what is being previewed. I'm not sure I expressed that very well.

ah i see. you mean clicking a link in the preview. yeah, that is the current behavior. if you open the link via the editor, that will refresh the preview. if you want to click through the preview, you can enable this following option: https://wiki.dendron.so/notes/401c5889-20ae-4b3a-8468-269def4b4865.html#prevent-newly-opened-files-from-replacing-the-preview-pane

I already have enabled that option. It doesn't seem to make any difference.

Oh, you mean that if I want to navigate I have to click in the editor, not the preview. That's not a very intuitive way of working, it means you have to change focus and identify the corresponding link in the editor.

I feel your pain and same issue here and changing

"markdown-preview-enhanced.automaticallyShowPreviewOfMarkdownBeingEdited"

doesn't solve it looking forward for a solution too

I'm currently experimenting with the custom editor api of vscode and I was thinking that it could be used to create an editor that combines preview and editor into one, like having reading mode and editing mode. This could be used to improve this UX by opening the linked note depending on in which mode the current editor is. @User