is this correct

i feel like i should only be seeing header 1 here right?

@kevins8 i cannot screenshot and copy paste an image in dendron. My dendron repo is set in WSL.

Hello. I am very happy to see the

Go To Note

command should now open external links! However, perhaps I misunderstand the release note. I have

Ctrl-Enter

linked to the

Go To Note

command but still cannot open web links. I get the following error message from Dendron:

selection is not a valid link

. I can reproduce this with any link such as:

https://google.com

or

[Google](https://www.google.com)

What am I doing wrong? Or perhaps I simply misunderstood the release notes. Thanks again for a lovely product that I use every day!

Should be

Go To

on external links instead of

Go To Note

Wonderful! That was it! Again, Dendron is one of the programs that I use every day. Thank you very much for all of the work that everyone has done to continue to improve it.

folks, I find the doc about templates confusing, I can't tell dendron schemas and templates apart(silly me), but all that I want is very simple: for each journal I create(by clicking today button), there should be 2 headers: TIL and DEV, and that's it, no need for frontmatter variables substitution. So what should I do?😳

This should help get you on your way: walks through schema setup and templating for a daily journal and helps explain the differences :) https://wiki.dendron.so/notes/5U4eAiqshI67VxIL40KWH/

Hey ! I have a question, I asked a similar one a month ago, but I'm still stuck on it. With my team, we have multiple projects, so we switch between them using "Open recent" on VSCode. The issue is, I'd like to use Dendron, with a remote vault, and writing a "Community" docs, so we have a sub-note for each projects, and shared across all project but if I do that, I have to have a Workspace for each project, set up Dendron each time, and sync it each time ... which is cumbersome. Am I missing a way to do it ? Without re-setting the workspace each time I create a new project and have it to sync it each time ?

So your set up is: have one vault that holds note(s) for all projects, and you have them added to each of your projects multiple times as native workspaces?

Basically, yes

It seems I can workaround that by just having a dendron.yml pointing to a directory OUTSIDE the current folder (../notes) for example

I still need to duplicate dendron.yml, but that's not that much of an issue

Hmm.. In that case my personal preference would be having a separate code-workspace for the vault, and adding your projects to that workspace. but there might be some hiccups here and there since now all the projects (as well as your vault) would share the same vscode workspace setting.

Yeah, which is impossible, honestly, we're at 11 projects, and growing, so ...

Took a quick look at how multi-root workspace works (https://code.visualstudio.com/docs/editor/multi-root-workspaces), you could create a separate dendron workspace, add all your projects to it with

Add folder to workspace...

in the explorer, and have each of the "roots" have their own settings scoped to the respective projects (they go in the

.vscode

under the project: https://code.visualstudio.com/docs/editor/multi-root-workspaces#_settings). A bit of work moving the individual workspace settings to a folder setting, but this way you can preserve most of the project scoped settings that matters. and of course have one and only one place where the document is stored / synced

the limitation here I believe is that settings can't be scoped per-folder if it directly affects the UI element of VSCode

The trick with the dendron.yml seems to be more ... "efficient/easy", I feel like Dendron follow the dendron.yml, and then go to that folder and add the workspace itself

So to enable the "community" Dendron, I just need to have that file present with a few settings (the vaults path, ...) but otherwise, it just work out of the box

Not entirely sure how you are setting that up, so I can't tell for sure if that won't have problems. If you can create and share a minimal example of that setup I can take a look and see if that will have any issues.

Basically, here is my structure : / --- /docs --- dendron.code-workspace --- .gitignore --- (a folder for each of the vaults I've setup, one for work, one for personnal stuff, the personnal is added to the .gitignore) --- /projectA --- dendron.yml --- (other project files) --- /projectB --- dendron.yml --- (other project files)

The dendron.yml I'm using is this :

When I open projectA, Dendron is starting up, and I can properly lookup the notes in ../docs/{any_vault}

Tried this out. It does work, but this isn't a scenario that we've accounted for in general so there might be some things that don't work 😅 this is an interesting setup. Do keep us posted on how this setup works for you moving forward.

It seems to be working, I'm testing with a coworker

I'm just having trouble automating a few things, is there a way to easily trigger "Dendron: Workspace: Add and commit" then "Dendron: Workspace: Sync" on save of a *.md ? Because GitDoc or auto-git don't allow me to specify the git directory and use the primary (which is the projectX one, so it ... commit nothing), while the command executed by Dendron seems to be understanding which repo to commit

@hikchoi : Sorry for the ping, I'm fixing stuff by installing other extension, but how can I go about proposing a feature for Dendron ?

Adding the option to auto add, commit and sync on save of a .md would be SO timesaving

That would indeed be a nice feature. You can create a feature request / enhancement request here: https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

I don't think VSCode natively lets you hook into the on-save event to run arbitrary commands, but a quick look at existing extensions it looks like this would do: https://marketplace.visualstudio.com/items?itemName=emeraldwalk.RunOnSave We haven't explored customizing on-save behaviors a lot yet but do leave us a feature request.