is vscode and os info

Downgrade to 0.112 fixes it for now

we're investigating. thanks for the logs!

@Bassmann @aleksey - could you do us a huge favor? Can you see if the issue repro's with this build? https://github.com/dendronhq/dendron/suites/8440343427/artifacts/374082673

Do either of you happen to have link candidates enabled? i.e.

yml
dev:
    enableLinkCandidates: true

I'm quite sure I have link candidates enabled. I can check the setting and build tomorrow morning.

Yes, I have it enabled. I'll try to check the build sometimes tomorrow.

Speaking of candidate backlinks, I've now opened a GitHub Discussion after trying the feature out. Wasn't sure the best route to provide the feedback: - https://github.com/dendronhq/dendron/discussions/3583

The link leads to a 404 for me 😕 @jyeung

That version shows the same behaviour for me

Logs with debug turned on as @kevins8 had asked @aleksey for

Thanks a lot for the help @Bassmann and @aleksey - a fix for this should come out in the next release,

0.114.0

Does Dendron now silently runs

Doctor: fixfrontmatter

for notes added to the vault manually without any frontmatter? That's very cool!

yep 🙂

thanks, fixed!

im seeing overflow on the sidebar

updated this. if you push another change, this should be fixed

Hi guys, I just found that when I switched to a non-dendron note(meaning its frontmatter is not dendronish), the preview didn't change, until I manually clicked the "Dendron: Toggle Preview" button" twice to have the node rendered, once for closing the preview and the other for re-open it. It would be great if the Dendron preview responses to all note switches. Thanks

hey guys just wanted to say thanks for implementing wildcard matching of headers, ie.

![[daily.journal.2022.39.*#done]]

works as expected. It would be nice if dendron didn't generate an error in case heading doesn't exist (nothing got done that day :)).

also a question: is there a away to match the last level note name, , ie. ![[.*todo]] ?

not currently

it might be a useful feature, ie. right now I generally have one

todo

note per project (directory). The top-level

todo

note could then simply enumerate all child notes named

todo

recursively to get an overview of outstanding work

ie. note hierarchy

todo:
   ![[.*todo]]] // displays TODOs inline from proj1.todo and proj2.todo

proj1.todo
proj2.todo
etc.

What happens if you try

![[**.todo]]

(with two stars, before the period)?

it doesn't find anything, but

![[**.todo**]]

works!

thanks @foureyedsoul

Sure! I just started using that pattern last week—I'm glad it works for what you need, too!

Just FYI, @gurbege , here's the full pattern I've been using. It might be useful for you, if you'll also want to make notes that automatically list what you've finished. I use

![[domain.**.tp.**]]

, with notes at that last level being Dendron task notes. Once I finish all the tasks in a task note, I'll rename it, replacing the

tp

with `ta`—instead of "tasks (project)" it's "tasks (archived)" or "tasks (accomplished)" in my mind. This naming convention would let you also use

![[domain.**.ta.**]]

to easily list things you've done on another note or in another section of a note.

re: renaming

tp

with

ta

, I think most projects would always contain a non-empty

ta

ie. there is always something you won't get around to..

since I don't really care about what has been done except for weekly status, I like to send completed tasks to a

#done

section of the daily note