I may have missed an obvious feature, but is there a shortcut to create a new note off of a text selection, or must I have the

[[note]]

format in the md and just ctrl+enter?

The lookup can do that: https://wiki.dendron.so/notes/0e57f8d1-e501-49db-974c-01eb64c20c22/#creating-notes-with-a-selection

Aha! Now I'll need to weigh out which default behaviour I'm likely to use 🙂 Thanks again 👍

Hello again, how can I enable the interactive checkboxes? I saw on the onboarding video that it's working but it doesn't for me, is this a known existing bug or is there some kind of a configuration for this? I can see that https://wiki.dendron.so/notes/593206ea-5658-4874-bafd-18a138870f91/ states that it should work out of the box

not working for me as well, it might be a bug 🐛

I've bound

Dendron: Insert Note Link

to a shortcut and it only works for a little while and then stops. Does this happen to anyone else? If not, what can I do to track it down / provide logs? When I looked through the logs of this last time it appeared as if the quick insert window got a cancel event when I pressed enter.

This has been happening to me too.

I've got two questions about references.

For a range boundary, is it possible to say "the end of the current heading" somehow? E.g. if I have: h2 A, h3 B, h3 C, h2 D, I'd like to take everything inside the first h2 (A, B, and C) without having to know what the next h2 (D) is named.

For a wildcard reference, is it possible to not include notes that don't have a matching reference? E.g. in my daily notes I will sometimes have a section like "Notes for Team A." But, not every daily note has that section. It currently will include a reference that says something about how the reference doesn't exist for each note without the corresponding section. Is it possible to just don't show those ones that don't match? Or maybe, is there a different way to query what I want?

There was some discussion for this feature recently, but we don't have support for it yet. For now you would have to pick the next H2 header as the end of the range yourself. Another option would be to add a block anchor before the next header and target that, so that you don't have to update the reference if you change the title.

Gotcha. Thanks!

Probably if I have to delimit it like that, I could change my workflow and extract the notes elsewhere to flip the problem on its head.

I'm hoping that the team decides to change the meaning of a heading reference to do what you describe... include all the content (including sub-headings) under the headings. The current meaning of "everything to the end of the file" might be accomplished with a range specification like

#h2:#*

-- see #896829973116121088

Yeah, I honestly didn't expect it to work that way.

I thought I did something wrong based on the reference it generated.

strange

any way I can change my root schema back to default?

because that doesn't look right

and i don't wanna screw things up by assuming I can change any of this

hmm, strange, that doesn't look like its from our side

you should be able to replace it with the following

version: 1
imports: []
schemas:
  - id: root
    children: []
    title: root
    parent: root

I have zero idea how it has worked if it's been like that for awhile

but could explain why I couldn't get namespaces down

or other stuff I'd been trying out

thanks Kevin

what is this in .gitignore? added by

echo .next >> .gitignore

that might be a quirk of

echo

and

>>

not being powershell specific

Hi! Please help me to compose regexp replace string for correct renaming notes in vault. Now i get not correct strings when entering arguments journal\.(\d{4})(\d{2})(\d{2}) $1.$2.$3 veles.daily.journal.20211013 veles.daily.journal.20211014 veles.daily.journal.20211015 veles.daily.journal.20211016 veles.daily.journal.20211017 veles.daily.journal.20211018 veles.daily.journal.20211019 veles.daily.journal.20211020 veles.daily.journal.20211021 veles.daily.journal.20211022 veles.daily.journal.20211023 veles.daily.journal.20211024 veles.daily.journal.20211025 veles.daily.journal.20211026 veles.daily.journal.20211027

I don't think Refactor Hierarchy supports captured variables. This might be easier to do outside of Dendron, you can just rename the files and Dendron should pick up the change. I can help with a bash command to do it of you'd like.