Hey folks. Has anyone else experienced their wikilinks breaking spontaneously in the past few days? When I click my wikilinks, it's trying to open them up in my web-browser (Chrome) and is trying to navigate to: [...].vscode-webview-test.com/vscode-resource/file///c:/Users/[my files] and it displays a "This XML file" error, ResourceNotFound, etc etc. I had set-up some wikilinks about 2 weeks ago and they were functioning correctly inside of VSC at that time. I hadn't used them since then, I'd been working on daily journals. Trying to think of what I might've done to break this... I installed Adobe Acrobat a few days ago and am wondering if that may be a factor, like if Acrobat messed with my file associations. However, If I try to open my markdown.md files from within File Explorer, they do launch in Visual Studio Code. So the file association doesn't seem broken there.

Okay I would need an example of how your wiki links look you can replace each segment of them with a star

*

so that you post

[[label|*.*.*.*]]

if you don't want to share your actual hierarchy. Secondly is your workspace open, Do you see the Dendron Tree View in the explorer pane? (if yes your workspace is open) And lastly do you have other Markdown extensions installed?

1) The links are just [[*]]. Something as simple as [[root]] fails. 2) Yes Dendron is initialized, I can see the Tree View in the VSC Explorer, I have the Preview pane open, and I have the Note Graph pane open. 3) For Markdown extensions, I have "Dendron Markdown Links," "Dendron Markdown Preview Enhanced" and "Markdown Preview Enhanced".

Guess it was the "Markdown Preview Enhanced". I hadn't realized this was a redundancy and potential conflict. I disabled it and things appear to be functional. 👍 Thanks for pointing me in that direction Fudo.

No worries happens to everyone at some point.

we're going to be calling this out in the onboarding tutorial since its a common point of confusion

Is there a shortcut method of creating a journal note contextually, say -- using the current node as a root?

Something like this seems to be feasible via the Lookup dialog: The toggle, "Create Journal Note".

did you take a look here https://wiki.dendron.so/notes/19a0ea9d-7292-4a68-bc6f-ffd462a54bc5.html#dendrondefaultjournaladdbehavior ?

I'll have to explore that.

Thank you.

childOfCurrent

looks appropriate.

oooo, and I can use schemas to make templates.

I'm about to add another dimension and it is exciting me.

good morning all - question: For the YAML front matter, how is the ID generated and how is it used? If I have documents originating outside of dendron, that wind up used in a vault, is there a value to adding the YAML frontmatter at some point after external creation of this document?

If there is a value to it, is there a method by which that frontmatter could be added after the fact?

Dendron Doctor fix frontmatter is the command you seek that fixes the front matter and the id is used for the publisched site links

Ok - perfect. Thanks!

@fudo hey fudo... any idea of how to perfrorm natural language processing on documents in a vault? I would settle for word frequency analysis for the moment

Did I read somewhere that you were planning on releasing something related to access levels?

When linking to another note using a wikilink, I often rely on the autocomplete that pops up after I start typing

[[

. However one thing that annoys me if how sometimes when I backspace when correcting a misspelled letter, the autocomplete completely disappears and won't reinitiate until I delete the whole link and re-type

[[

.This is probably more of a VSCode issue than Dendron, but I'm wondering if anyone has any tips on how to deal with this minor but frequent annoyance.

hit

ctrl+space

Thank you! This is so great!

I changed the parameter you highlighted, @User :

childOfCurrent

. However, when I use the +I keyboard shortcut, I still get a new note named,

daily.journal.Y.M.D

rather than

[current node].journal.Y.M.D

.

Sorry then I have no idea at the moment I would think that this setting does this.

Thanks for the sanity check.

I would have anticipated this functionality as well.

The tags documentation recommends doing a structure like [[tag.foo]] but then further down shows an example like [[books.tags]]. Does the [[books.tags]] allow some tagging capability that [[tag.books]] would not provide?

Well if you go with

[[book.tags.{a tag that is only applicable for books}]]

you specify tags that exist only in the book domain. If you go with

[[tag.{a tag}]]

you specify a tag that would be applicable to multiple domains. In a way booth give you the same result but provide you with ways to specify tags for certain domains or globally for all in my eyes.

Interesting... domains specific tags. Thanks... appreciate the insight!