I consistently get that error. Then I tried it by changing the export scope from 'Vault' to 'Workspace' and got the error: "error while running command: Export Scope Not Yet Implemented"

This should automatically happen 🙂 The little icon should now be, when within Dendron workspaces working with Markdown files, just be for

Dendron: Show Preview

. Note that you can still use the VSCode markdown preview with

Markdown: Open Preview

or

Markdown: Open Preview to The Side

from the command palette, if wanted

are you using export pod v2? that's currently experimental which is why we don't have docs posted for it yet 😅 for now, would use regular export pod

Okay, it worked with the regular export pod 🙂

Hi all - which channel would be most appropriate for a more philosophical question around Dendron's hierarchical approach?

here is good 🙂 feel free to start a thread as well if you expect more back and forth

Hierarchical categorization - Why is this not a limitation for Dendron?

Sorry if this is a duplicate. Just noticed the new notes I'd made are all stored in

dendron.templates

not intended. Any way to move them out? Additionally, is it worth moving them to a separate folder or

root

alternative if there will be a lot of notes in this section?

you can just move them into using the

mv

command or dragging and dropping

generally, you can use hierarchies to organize information and vaults to do access control -> see https://wiki.dendron.so/notes/24b176f1-685d-44e1-a1b0-1704b1a92ca0.html

Thank you I was nervous I might break something

I submitted an issue yesterday regarding some [issues](https://github.com/dendronhq/dendron/issues/1871) with the published site, but am not confident that it'll be resolved soon. So I started poking around to fix the one thing that was bothering me the most: truncated headings in the ToC in the right sidebar. I am not a developer, but after many, many hours of poking around, I discovered that turning off 3 instances of css properties named

white-space: nowrap

results in no truncation. See the gif below. Could someone tell me how to make this fix permanent? I'm thinking, somewhere on my computer, there must be a file whose content I can edit, so that when the notes are published, that css property will be off by default.

I have a multi-vault setup, and I think that the tree view began including vault names with version 0.72. Is there a way to control this? For the vaults I have with overlapping node names, I think that feature is a great addition. For the vaults with no overlap, I'd prefer to be able to turn that off.

hey, appreciate the issue and i'll be working on some publishing improvements this weekend. in the meantime, we don't currently have a persistent way of updating the css. you can always update

pages/_app.tsx

of your nextjs template with custom css but this will be erased for the next time nextjs updates

ah, are you using the webview version of the treeview? if so, we don't have a toggle but its a oneline change. if you submit an issue, we can get to it for the next release!

> you can always update pages/_app.tsx of your nextjs template with custom css but this will be erased for the next time nextjs updates Heh, I have no idea what any of that means [Those sound like developer words; I'm a mere n00b User] Will wait to see what you do over the weekend. If you at all can, please do look at the ToC truncation.. the other issues can await if needed. I am eager to publish a Digital Garden and doing it with Dendron seems to make sense since I already use Dendron to take notes. But with the truncation issue, I'm forced to play with exporting to markdown pods and using something like Mkdocs and that workflow has its own issues. Many thanks in advance.

I guess I am! At some point I added these lines to my YAML, but I don't remember when, why, or what the difference is between the last two lines.

dev:
    enableWebUI: true
    previewV2Enabled: false
    enablePreviewV2: true

the last two lines are no longer needed (they were to enable the new preview). the first one uses the web view tree view (if you switch it off, it goes back to the vscode ui tree view)

Great. Thanks for the info, Kevin! I'll submit an issue later today or over the weekend.

@User which flavour of markdown does Dendron use/support ? My question is specific to syntax highlighting for inline code blocks - Similar to https://stackoverflow.com/questions/23226224/inline-code-syntax-highlighting-in-github-markdown, but the answers there are specific to github flavoured markdown. TL:DR: If I want to choose syntax highlight a piece of code, I will usually use triple backticks followed by language name. But the code block starting with triple backtick needs to be on a separate line. (which makes sense for multiline code anyway) But there is no such option for single backtick - which is used for inline code block. So is there a way to specify language for inline code block ?

We mostly use Github-flavored markdown with some of our own extensions, but we don't have support for highlighting single-tick inline code blocks. Please do feel free to submit a PR for this.

I don't think this is used by lot of people. So may not be worth feature request. 🤷‍♂️ I think your time may be worth spent elsewhere.

I'm always surprised which features people use and which they don't. I'd still encourage sending in a feature request if you have a few minutes because who knows, maybe a lot of people wanted it but also thought noone would want it. 🙂

Quick question: Does the Description field in Note headers get used for anything?

yes, it shows up when you do a lookup:

Ah ok, thanks! But so I'm understanding it right, the description itself doesn't get searched?

@User can I ask about the candidate backlinks feature? I was wondering why it isn't enabled by default. Are there big performance degradations or something? Or is it just to avoid cluttering the UI for people who aren't using it?

yes. it's possible to enable this behavior but it's currently turned off. We use our own indexing method and VSCode does it themselves so there is some conflict there.

It was introduced with limited capabilities as an experimental feature. To be honest, I haven't worked on it beyond that point so it's still a dev feature 😅 I haven't seen any issues brought up with it so far, but just to be safe some perf tests should be done if we decide to enable it by default.

It's a feature I'm excited about, so thanks for implementing 🙏 . I guess I'll start using it, and maybe some useful data will come from testing in daily usage