awesome, thanks 👍

Probably I miss some obvious vscode functionality but is there a way to autocomplete the hierarchy when searching or creating a new note? I have a schema defined e.g..for journal but still need to type out everything?

so whenever you type a

.

, dendron will suggest valid children that match. the problem is that vscode's input widget (what dendron uses for lookup) does not support autocomplete. have some ideas about allowing this using a web view but it's currently blocked on us finishg our server side migration https://dendron.so/notes/725d99be-fadd-4464-88c3-0a5fcc7292c7.html

is there an specific way to search all markdown documents in your vault for an specific tag you put in your frontmatter in some docs ?

I haven't seen this functionality in obsidian (they use regular

#text

as tags) nor foam, I think only Zettler does something like this

However maybe this doesn't fit with your hierarchy approach to vaults

@User this depends on how you do your tags. dendron supports multiple means of tagging 1. using

#{foo}

--> this is how obsidian and most editors do it 2. using

#[[{foo}]]

--> this is how roam does it 3. using

[[tag.{foo}]]

--> this was originally pioneered by @User and is how i would recommend doing tags in dendron 1. if you use method 1, you could find it by doing a search or right clicking and selecting "find all references" 2. if you use method 2, you can find all documents via backlinks of the

{foo}.md

3. method 3 is a special case of method 2 where instead of a page, your tags have their own hierarchy. this helps with autocomplete and you get the benefits of 2. plus you can even style it in the preview by using the following instructions: https://dendron.so/notes/692fa114-f798-467f-a0b9-3cccc327aa6f.html#stylized-tags-using-custom-css

I believe you can use #tag in Roam as an alias for #[[tag]] which is also equivalent to [[tag]]

@kevins8 are there plans to add commands to automate/standardize tagging

@User right now, we're looking to standardize on 3. we'll be adding functionality to make the syntax more natural (eg. #{foo} will be equivalent to [[tag.{foo}]])

on Win 10, just upgraded to 12.4 -- enhanced preview errors on video content, says: "Your browser does not recognize any of the formats available" regular preview displays the video however

are you playing the video from an iframe or a video tag? also, did this work before 12.4?

checking out the third option

given that this app is highly opinionated, makes sense to use the 3rd option

VSCode's snippets might help as well:

"tag_insert": {
    "prefix": "#",
    "scope": "markdown",
    "body": [
      "[[#${1:my-tag}|tag.${1}]]"
    ]
  }

Some variant might simplify some of the editing of these.

How is the cursor placed directly in the person reference after expanding the snippet as shown here? https://www.dendron.so/notes/cebe5393-5da0-484c-a24a-0939f0cef768.html Also, should is that snippet part of the default dendron workspace? mine is quite old and i might just be missing it.

> 1. using

#{foo}

--> this is how obsidian and most editors do it > 2. using

#[[{foo}]]

--> this is how roam does it > 3. using

[[tag.{foo}]]

--> t I ended using the third option with a different tag structure for books

tag.book.sci-fi

, snippets

tag.lang.cpp

etc....

@User I can't speak to that snippet in particular, but the VSCode snippets follow the TextMate conventions for snippets: - https://code.visualstudio.com/docs/editor/userdefinedsnippets -> https://macromates.com/textmate/manual/snippets -

$1

,

$2

,

$3

etc are tab stops -

${1:default}

is an example of a placeholder -- as you tab through the fields, this one will have

default

selected so you can replace it. This is what I did in the tag snippet I posted above

Suppose that I have a note named

people.Bob

with the

title: Bob

in the frontmatter. When writing in my daily note, I'd like to insert

[[Bob | people.Bob]]

using Intellisense completion. Right now, it looks like I can auto-complete

[[people.Bob]]

then manually insert the

Bob

alias after.

Bob

reads more naturally in text than

people.Bob

, so I'd rather see the note title in the Markdown preview. Sorry if I missed something obvious in the docs, but is there a way to auto-complete a wikilink with the frontmatter title as the alias?

Markdownlint is driving me crazy... I now have it linting only on save but it's still just too many squiggles when I'm trying to get my thoughts down. How have other people handled this? Would there be any dendron-specific consequences to turning it off? (I understand ofc that it could cause rendering issues when previewing or w.e.)

> are you playing the video from an iframe or a video tag? also, did this work before 12.4? @User

I'm just looking at the example "Dendron"-vault, reinitialized to bring it up to date, so I think you used tags. Yes this did work before 12.4 but I probably junped from some where in the 10.x series. So 3 places the error could be coming from, Dendron, the Enhanced Preview, or the vault

> How is the cursor placed directly in the person reference after expanding the snippet as shown here? https://www.dendron.so/notes/cebe5393-5da0-484c-a24a-0939f0cef768.html > Also, should is that snippet part of the default dendron workspace? mine is quite old and i might just be missing it. @User using the

$0

symbol will place the snippet after expansion. as far as default snippets, you're right. this will be included in the next update!

@User it's not you, it's us 😅 our intellisense currently doesn't complete links that have aliases. this is currently an october milestone item

@User how are you loading your videos? can you give an example snippet?

> Markdownlint is driving me crazy... I now have it linting only on save but it's still just too many squiggles when I'm trying to get my thoughts down. How have other people handled this? Would there be any dendron-specific consequences to turning it off? (I understand ofc that it could cause rendering issues when previewing or w.e.) @User i don't use markdownlint for that reason. i think you can tune down the strictness but in general, i found it to be more trouble than its worth

On the Roadmap I see (probably in the far future) a dedicated VSCodium fork of some sort for Dendron. Will Dendron eventually all be within one plugin ideally or will it always be the list of reccomended plugins?

@User we're moving to consolidate as a single plugin. we want it to be possible to use other plugins and make it possible to expose dendron hierarchies to plugin developers but dendron's core should all be within one extension

@kevins8 , sounds good. Thanks for your always snappy responses, tips & tricks and such.

I am glad that dendron is inside vscodium extensions