update the above settings in your workspace (remove the prefix)

having some problems with the tagging - if i use [[#math|tag.math]] for instance i get an error when clicking on it, saying it can't find the file tag.math.md

but this should be a tag, so it should just show me other notes with the same tags no?

when you use wiki-link tags, the tags themselves are notes. so you'll need to create them first

if you use the

go to definition

shortcut (f12 key for most os), it will automatically create the note

if you click on it using preview, it will not

we'll be updating the ui so it will have the same behavior

sure thing. so, then you'll eventually end up with a log of tag.* files where there's nothing in it?

not saying that's a problem necessarily, just trying to wrap my head around it

or, then you would use these tag.* files to have some general information on a topic? or will all the notes with that tag be listed in the tag.* file?

yep. the nice thing with doings tags this way is you get to autocomplete tags and you also get to refactor them

(dendron lets you change any part of your hierarchy - tags are just another hiearchy)

and you can use backlinks to see every note that has a tag

by refactoring you mean, if i have a bunch of notes with tag.mathS and i wanna change them all to tag.math i can easily do that?

by changing the name of the tag.mathS file? or doing a big search and replace throughout my notes?

change automatically

that's one of dendron's core differentiators -> we let you have flexible hierarchies that you can change over time

we also update all links in the process

that's impressive

> that's one of dendron's core differentiators -> we let you have flexible hierarchies that you can change over time @kevins8 that's indeed the killer feature.

> @User a few days back you mentioned

option-click

not working anymore. did you figure out what happened? @User no, unfortunately not, but happily working in a new dendron vault. I still have a question that I asked a few days ago about not being able to click on a x-devonthink-item:// and have it open in devonthink. It seems to be an issue with third party url handlers in vscode.

@User hmm, okay. let me know if you figure it out. as far as i'm aware of, vscode doesn't natively handle deep links. dendron does have a

open link

command and we could add deep link support there https://dendron.so/notes/3472226a-ff3c-432d-bf5d-10926f39f6c2.html#other-links

> @User hmm, okay. let me know if you figure it out. as far as i'm aware of, vscode doesn't natively handle deep links. dendron does have a

open link

command and we could add deep link support there > > https://dendron.so/notes/3472226a-ff3c-432d-bf5d-10926f39f6c2.html#other-links @User thanks - I have put in a feature request!

Hi, is

dendron.code-workspace

rewritten during upgrades?

not sure, why?

Any idea on how to change the background color and link color of the site for dendron-jekyll based theme?

> Hi, is

dendron.code-workspace

rewritten during upgrades? @User Not sure, but it got changed when I tried to change theme in 'Preferences: color theme' in VSCode. It did not affect the website but it got changed

Mine changed too. It's no biggie, since I can restore it manually. But it would be nice to have a way to keep our changes to that file.

Yeah..any idea on hoe to change the link color and background color of jekyll-dendron based site?