Documentistas! Anyone using Dendron to write emails? Back in my emacs days, this was a great way to keep track email correspondence. Would be real nice to be able to send emails with screenshots/medias straight from Dendron!

Different topic... Curious how you all are handling image/video assets. I have the Dendron Paste Image extension setup to put all pasted images into an "assets\images" folder at the top level of the vault. This can lead to all kinds of problems down the road (which assets go with which doc, etc). Hard problem to solve...

You could use a schema to have a monthly template that applies when you make a note corresponding with a month, e.g.

daily.journal.2022.02

. It's the same as applying templates using schemas for daily or weekly journal entries

Maybe you'd be interested in the project schema in the example vault and its corresponding template: https://github.com/dendronhq/templates/tree/main/templates If you're looking for information on how to structure your note hierarchies in a way that's project based, you might look at the PARA system: https://pkm.dendron.so/notes/20855ea8-0f1d-49bd-80ca-7b807ef77bbf.html

I'm interested in having more robust ways of doing this as well. The Dendron docs actually demonstrate an interesting way of handling this: https://discord.com/channels/717965437182410783/892453144632627200/923268200496525363 the TL;DR - all the images for the documentation are stored in a single node under different headings. Nodes where those images are required use header references to display them. Changes to the image node propagate through the notebase. Mostly though, I just don't use images all that much myself at this point.

I can confirm that this doesn't seem to be built-in functionality using vscodium on Linux. You could try something like this (I haven't tested it myself): https://marketplace.visualstudio.com/items?itemName=kisstkondoros.vscode-gutter-preview

What do you mean when you say "proper monthly functionality"? I use a schema that's different from Kevin's, where I have levels for years, months, weeks, and days. I've made it so there are different (but similar) templates for each level. If that's what you are hoping to have, I'm happy to share it!

The `Insert Template`Part looks like a workaround because it's not possible to create a monthly note right away

Interesting! Maybe I'll try this out.

I have it set up so that if I use the lookup bar ( command + l on mac ), I can create a monthly note right away. If I'm currently looking at

journal.2022

, I can just type

.02

into the lookup bar and it will make a new monthly note that I can use for February.

@User What do the chars on the end of the link represent? After the heading name,

,1:#*

Fulle example:

![[dendron://dendron.dendron-site/asset.preview#tree-view-dark,1:#*]]

What you're seeing there is syntax for referencing headers, I think. See this document for more information: https://wiki.dendron.so/notes/f1af56bb-db27-47ae-8406-61a98de6c78c/#wildcard-headers-as-a-range-boundary

Oh wow. Thats powerful... Basically, skip the first line under the reference header, and grab all content (the image) up to the next header.

Hi! I have problems with

Rename Note

in multi-valut usage. Wikilinks are not renamed out of current note vault. Is it a expected behavior?

I see a similar problem with

Refactor Hierarchy

.

nope. if you have a repro, please submit a bug report and we'll take a look!

Hi all ! I got a problem in a multivault workspace. When I trigger a new note creation with cmd + L and tick the Select vault option I get an error saying No available vaults for filename (see attached screenshot)

OK this apparently happens if their is a preexisting note with the exact same name (in any other vault). See following screenshots

This configuration (see above) leads to the above error message because todo.md is preexisting in another vault

This configuration (see above) will not lead to the error.

Not sure if it's expected.

Hi! Check for availability vault in files

dendron.code-workspace

and

dendron.yml

in your root WS

Is it possible to capture the Dendron working document in a variable? Similar to how

${currentFileDir}

grabs the current file directory for use with VS Code settings? Something like

${currentDendronFilename}

?

Hi @User what do you mean by "check for availibility vault" ? I do have multiple vaults and all are declared in the dendron.code-workspace and dendron.yml. What exactly do you mean I should check for ?

Are you moving a non-leaf note by any chance? https://github.com/dendronhq/dendron/issues/2003

Otherwise it sounds like a different bug

you might want to use

${fileBasenameNoExtension}

@User , hm... I can't seem to get that to work. Goal is to name media files more relevant to the document they were pasted into. Using Dendron Paste Image extension settings,

${fileBasenameNoExtension}

doesn't seem to prepend/suffix the actual image filename.

ah, sorry, i thought you were referring to generic vscode variables. here's a link to all relevant variables for paste image: https://marketplace.visualstudio.com/items?itemName=mushan.vscode-paste-image

That helps! If there was a way to

replace(${currentFileNameWithoutExt}, '.', '-')

for the

pasteImage.namePrefix

or

pasteImage.defaultName

settings, that would be great for naming of media assets. (eliminates '.' 's in asset filenames)