when the content of

ref.typescript-interview-question

changes, it will both change in

software.language.typescript

and

learning.dev.typescript

, and the two notes can have their own context in their bodies without having to write them along with the interview questions.

`Todo+`is an extension that is part of the

awesome-dendron

list so I was hoping it was compatible with markdown files. Am I missing something? Has anyone set up Todo+ to look at something like

tasks.md

rather than

todo

or

todo.task

? If it has to be a non-markdown file, if I add frontmatter to it would it be picked up by dendron for linking/referencing etc?

alright, I've been trying to figure this out for awhile but now its officially bugging me. I sync my workspace between two laptops (work and personal). They're both setup basically the same (same version of MacOS, VSCode, and Dendron) however on one laptop I get margin/padding around emoji in the Note Preview, and in the other I do not. I can't figure out why they're rendering differently 🆘

do they both have the same extensions installed? are you using dendron note preview for both of them?

Yes (at least as far as I can tell). I have settings sync turned on, and I commit all my workspace settings between the two machines.

i recently installed "markdown preview enhanced", how can I disable the dendron markdown preview if I want to use just the other one? If I disable 'enablePreviewV2' will that do it?

Found the issue/difference. It has to do with display scaling. If the display is at "Default for Display" then the whitespace around the emoji renders "as expected." When its scaled, that's when I run into issues.

ah - nice

Was this problem solved ? I am having the same here.

Apparently not related to a file name but rather to the number of files beeing imported (>3500 in folders nested over 7 levels)

for one of the most populated folders it suceed when taking half of the files out

(also works whit the other half)

not sure how to debug this

Can you send a bug report with the diagnostic logs attached? (

Dendron:Dev: Diagnostic Report

command, please make sure to use it after seeing the error). We can look into why it's failing, and fix the problem. Bug report here: https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=bug_report.md&title=

does this helps ?

This shows that there's an error with the import pod, but doesn't tell me much more unfortunately. Could you send a bug report on Github, and attach the full log to the report? We'll assign someone to take a look at this. https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=bug_report.md&title=

this is the full log actually

Oh okay, I'd still recommend opening a bug report. We'll assign someone to investigate the issue, I can't offer more help than that unfortunately. It seems to be a bug.

meanwhile I could succeed to do the import by dividing the task in two batches (so apparently indeed a problem of number of files treated at the same time ...

OK will file this

Is there a way to quickly move an entire hierarchy to a different vault?

my (prefix).* (path to new vault)

reload index afterwards

okay, that's what I was wondering

are schema's per-vault or cross vault? My schema graph isn't looking like I expect and I'm trying to figure out why.

i.e., should each vault have a root?

cross vault

if you have multiple schemas with same starting pattern, the last schema loaded takes precedence

so then do I just pick a vault that is my "root" ?

sorry, not sure i understand. could you elaborate?