When I am in a note and I want to open a journal under that note, say -- "DSU": What is the command to open a note populated with the date, etc, etc?

I swore I could do what I describe.

Oh, it was a toggle on the Lookup dialog. Got it. Is there a keyboard shortcut for this?

They are not from dendron as far as i know

Take a look here: https://dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f47.html#lookup-journal-note

What extensions do you have installed

Now you are talking about commands. I've read the page and I wonder if the

args

for that commands are documented elsewhere. For example let' say I want to create a shorcut that launch the lookup for create an specific journal note:

json
      {
        "key": "enter",
        "command": "markdown.extension.onEnterKey",
        "when": "editorTextFocus",
        "args": [
            "noteType": "journal",
            "behavior": "childOfCurrent",
            "journalName": ""
        ]
      }

Something like this is possible?

take a look at the modifiers here https://dendron.so/notes/ad270a7d-2aed-4273-8319-eb6536e38b29.html

I think it might be related to having foam installed as well. Found this on their github: https://github.com/foambubble/foam/issues/94

yeah, this is a foam thing

I had it installed at the time of saving the file. I uninstalled, deleted the generated text, added another wiki-link and it didn't auto-generate so...

there's mention of prettier being related in the issue, but that hasn't come up yet so I think I'm good now 🙂

in case anyone is interested: https://github.com/foambubble/foam/issues/94#issuecomment-657241861

I'm having some difficulties with the

Dendron: Refactor Hierarchy

command failing on some of notes. So I've gone back and manually run

Dendron: Rename Note

to get back to the original state prior to the hierarchy refactor and I get this message when trying to rename some of the items: > {"ctx":"m:run","err":{"status":"unknown","msg":"","payload":"{\"status\":\"node_exists\",\"msg\":\"\",\"friendly\":\"proj.Dinner.2021.01.29 exists\",\"payload\":\"{}\"}"}} I'm not sure what it means because there is no other note with that name. Any way to fix the broken hierarchy? I'm afraid I may have gotten my Dendron into an unrecoverable state. Any tips anyone may have to fix this conflict?

Ctrl + Shift + J creates a journal entry. Depending on your config it will either create it as a subnote of your current note or as new entry in a separate hierarchy

Ah, so this behavior can be configured as well. . . Thank you

https://dendron.so/notes/5c213aa6-e4ba-49e8-85c5-1bdcb33ce202.html has the config options for the special notes. I can look up mine and share them if you get stuck

Thank you. I'll have some fun with this.

I use all of these special notes as a vital part of my workflow. It's tremendously useful

Regarding Dendron snippets, are the values for the prefix and body using regex?

I want to try to configure a "done" snippet to go with the "todo" snippet, so that I'm not always referring to the Preview to check the box.

this could be because you have a not called

proj.Dinner.2021.01.29.*

where

*

is another note deeper in the hierarchy. dendron creates stubs (https://dendron.so/notes/c6fd6bc4-7f75-4cbb-8f34-f7b99bfe2d50.html#stubs) in this case that refactor would today complain about

are you talking about vscode snippets? if so, they don't support regex but do support placeholders

I used snippets to create a tag

[[#my-tag|tag.my-tag]]

I get a file named

tag.my-tag

as well as

[[#my-tag|tag.my-tag]]

Is this behavior expected?

I feel like limiting myself to frontmatter but I thought it might be neat to use hierarchy for tags so I can namespace them as well as maybe add metadata.

Indeed this is the expected behaviour. Used like this tags are just another hierarchy of notes with all its capabilities. https://dendron.so/notes/8bc9b3f1-8508-4d3a-a2de-be9f12ef1821.html describes the recommended way to create and use tags.

Hi. is it possible to share a vault with a team (via a git repo) ? Is there documentation for such workflow ?

yes and no xD

If it is only one vault you can share the complete Workspace through a git repo / if you use multivault you may be able to use a remote vault to facilitate that.

I'm sorry -- I miswrote -- I get two files. The other is -my-tag-tag-my-tag.md as well as tag.my-tag.md What use does the the first serve?