Hi! In 63.0 autocomplete in field in Rename Note don`t works. I usually create Scratch Note and then run Rename Note -> Cut current string in field -> enter name project and autocomplete with tabs to end -> add . to end proj name -> Paste name.

Quick question: is it possible to apply a trait to a note created according to some schema via the lookup bar? For example, I would like to use the

journalNote

with a custom schema, and would like not to have to run the

Dendron: Create Note with Custom Traits

command all the time.

as far as I know that is planned but I don't know where the implementation stands

Oh, I see. I'd be curious to know as well. Thanks for the info.

You can take a look here https://docs.dendron.so/notes/E8ZUvTzJ7cVOyZtqHiIKX/#schema-and-type-relationship for the info that it at least is included in the rfc for the note types

Currently not all commands have the autocomplete capability 😅 we plan to make all commands that are derived from lookup (rename note command being one of them) have this capability so stay tuned 🙂 And of course, create a feature request if you wish: https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=feature_request.md&title=

I'm going through the getting started guide At this part

Children
In this case, vegetarian is considered a child note of recipes. When looking at the recipes note, the preview view will list vegetarian (and any other recipes.* notes) at the bottom as Children. Children can also be seen and navigated via the tree view.

I've created the

recipes.vegetarian

note and it's showing in the Tree View, but when I go back to the

recipes

note, there is no section with "Children" in the preview and the vegetarian note is not referenced anywhere. I'm assuming that, if I went back to the recipes note, it would have added a section called "Children" with the vegetarian note. Am I off base?

nvm, they showed up after I closed the preview and opened it again.

Was it supposed to autorefresh?

It should have, I think that's a bug. Would you mind sending us a bug report and we can take a look at it? https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=bug_report.md&title=

@User Created: https://github.com/dendronhq/dendron/issues/2489

Hi @User , what are the plans with task due dates going forward? For instance, will there be a way to assign due dates to normal tasks as well? (At the moment I can create task notes which have due dates as properties). And will it be possible to e.g. have an overview of the tasks due on a certain day? At the moment I oscillate between linking to the daily note of a specific day in the file where the task lives (daily.journal.....), and actually linking to the task (or copying the task over) to daily.journal...... (so I would create that daily journal in advance to host links to tasks due on that day)

You can add due to dates to any note. By "normal tasks" if you mean writing

- [ ] thing to do

in a note, you can write a due date for it yourself but we don't have any special features planned for it yet. We do have plans for a query system which would make the overviews you describe possible, but building the query system has been a bit delayed as we are focusing on stability and ease of use for core Dendron features at the moment.

Thanks for clarifying that!

Hello @User, I recently added the GitHub seed.dendron.onboarding repo to my Dendron Workspace, for testing purposes, but I can't seem to get the "Lookup" function to find the sample notes in that vault. I tried reloading the index and restarting VSCode, but that doesn't seem to have any effect. Is there a change in the Dendron configuration files that I need to update for this to work? I apologize if this has already been asked.

Did you add the vault with the "Add Vault" or "Add Seed" command?

neither, I cloned the repo using the VSCode command and when it prompted me to add to the workspace I clicked "Yes" and it showed in my workspace

That won't work, I'd recommend deleting that and using the command instead. The command will add the vault to

dendron.yml

okay, I will try that now, thanks!

when I try either "Add Vault" or "Add Seed" the onboarding repo does not appear as an option, the link to the GitHub repo is https://github.com/dendronhq/seed.dendron.onboarding

Can I write a note that doesn't have the

/notes

in the URL? ie.

https://notes.opensrc.dev/my-cool-note

instead of

https://notes.opensrc.dev/notes/my-cool-note

I don't see much value to having the extra

/notes

part of the URI path.

@User, I figured it out, use the "Add Vault" --> Local, and then point to the path of the "vault" folder in the seed.dendron.onboarding local repo, and now the "Lookup" function works. I was originally entering the path to the root folder instead of the vault folder inside the repo. Thanks for pointing the way!

I was trying to suggest selecting remote and pasting the git url, but glad you got it working!

In a recent video published on the YouTube channel, I noticed Kevin uses links that contain

$dd

to generate notes. What is the purpose of

$dd

? Can it, for instance, be used to automatically inject the day number in the file name of a note?

Can you add a . to a filename? Trying to create a note for a product with Semver.

product."v1.3"

Dendron uses dots to delineate hierarchy levels.

product.v1.3

will work fine.

Yes, but I don't want a file 3 as a child to v1, I'd like a file v1.3 as a child to product. I'll rephrase as, is there a way to escape a period so it's a period in the title. I ended up doing product.v1-3 and the renaming the title.

if you just create

product.v1.3

through lookup (https://wiki.dendron.so/notes/0e57f8d1-e501-49db-974c-01eb64c20c22/), there will only be one file (

product.v1.3.md

). Internally Dendron will recognize

product

and

product.v1

as a hierarchy, but they will be virtual and not saved in the file system (As long as you don't create them yourself later. You can if you have to later down the line). If you intend to publish, the default behavior will be writing the stub notes to file, but that can also be disabled through config.

though, if your use case demands that a single note is a direct children of

product

, then what you've done would be what I would do as well.

not right now, its just an identifier i put for myself to easily c/p with current day 😅