Graph deletion is always so hard!!

makes for some nightmarish homeworks hahaha

conceptualizing the renaming/refactoring thing as a file manager state machine, making a minimal UI to create a note then drag it into another to become a child, then out again, is how I'd go about smooshing these edge cases.

Does the refactor hierarchy function support capturing groups? I tried, but

$1

substitutions don't seem to work correctly; thinking of a usecase when you want to refactor your journal notes from

journal.2021.03.10

to something like

journal.2021-03-10

.

my notes graph seems to only be showing hierarchy but not the cross-note links, is this intentional/known?

not yet

yes, graph view only shows hierarchies. edges are on the road map!

Super, thank you. The decision to move to 11ty was definitely a good one in all sorts of ways!

What does the error

Unable to open 'project.something.2021.03.12.md': Unable to read file 'e:\dendron\vault\projects.something.2021.03.12.md' (Error: Unable to resolve non-existing file 'e:\dendron\vault\projects.something.2021.03.12.md').

mean? I'm linking to an existing file but I get this error.

can you show the raw link? also dm me the

> Diagnostics Report

when you get the error

I used the copy note link and it worked. Will it still be reflected in the Diagnostic Report? If yes, I'll send it you. What is a raw link?

Just curious, considering I'm looking at both Foam/Dendron...what was the reason to migrate from Foam?

Upvoted the issue, and added a comment requesting support for Github gists.

raw link is what you put into your markdown

see this answer about dendron vs roam: https://wiki.dendron.so/notes/683740e3-70ce-4a47-a1f4-1f140e80b558.html#how-is-dendron-different-from-roam

The raw link was [[project.something.2021.03.12]]. When I used the Copy Note Link feature from the command bar, it pasted [[12 | projects.something.2021.03.12]] and it worked. I then removed the

12 |

part, and it continued to work.

How do you quickly make a backlink with description ? Like, make a [[this is a desc | this.is.description ]] and still get the intellisens autocomplete ?

I make big blurbs of text for description of places, and seeing in the middle of my nicely formatted html output a big this.is.description (or, worse, something like shadowrun.gm.ooi.gangs.purple_assbreakers, instead of just "Purple Assbreakers") is annoying. It kind of take me out of my flow to need to have to go back and edit all those links

I'm having some trouble getting snippets to work. I just created a new workspace to try this out, and I can't find what setting or extension might be blocking snippets. Anyone else seen this?

If I use the command palette, the snippets are listed there. They just don't show up when using intellisense.

Alright, just read the docs - wasn't aware that I can type e.g.

to

and then TAB to activate that as a snippet. Neat. That works, although I'm more familiar with an intellisense menu appearing as I type that includes my snippets. Still not sure on that part.

if you use

useNoteTitleForLink

option, dendron will display a naked wiki link with the title of your note: https://wiki.dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f48.html#usenotetitleforlink would that help with what you're talking about?

More features and better publishing. And hierarchy facilitates that

That would help ! But it does not exactly match my use case

The use case would be that, given that I tend to write long stretches, without ever going back more than a few characters, I'd love to have a way to make backlinks "inline" so to speak.

Example: I have two notes

animals.vulpines.fox

and

animals.canine.dog

. I'm writing in the same vault but say in

stories.silly.2021

. The flow, currently, goes like this: 1/

the quick [[ ]]

<- I get some autocomplete if I begin to write "fox", I get suggested the

animals.vulpines.fox

note. 2/

the quick [[ brown fox | ]]

<- loose my autocomplete rights, now I must remember the exact note path 3.a/

the quick [[brown fox | animals.vulpines.fox]] jumps...

<- Here is the kind of stuff I want to have... but I usually end up with: 3.b/

the quick brown [[animals.vulpines.fox]] jumps over the lazy [[animals.canine.dog]]

... Which doesn't renders nicely on markdown, and I also have the problem that

brown

now is not part of the link. Of course, in this simple use-case, the setting you pointed me at would alleviate my throes... But I usually like add to the link a bit more flair than just the note title.

A "way" that I'd see that resolves would be to maybe have a setting so that the "default" auto-complete for a

[[

would be

|]]

rather than

]]

, and then have dendron start suggestions after the

|

.

But from what I know of VSCode, parenthesis completion is a built-in thing, rather than something that's easily overridable

Another way would be, to have the autocompletion stops when nothing matches (like it currently does), then restarts after a

|

within a

[[

That way you get autocomplete in most use cases.