Good heavens!! I knew I had done this before, but forgot.. lol yes that works, thanks!

No Problem just be aware that when you have

domain.parent.child1.note1

and

domain.parent.child2.note1

then you would reference the notes from from booth children

Thanks! Yeah, my use case is that the 'child' nodes here are scratch nodes under that parent node, and I wanted to be able to reference to "grand children" notes for specific dates.

This surfaced on HN again the other week. One of my favorite short talks about programming https://www.destroyallsoftware.com/talks/wat

Just enabled bots 🤖 in our project. I see that the stale bot has already tagged up some community issues (never fear, will go through them today and triage) 🙂 but if you see anything amiss, please let me know. More rationale here: https://wiki.dendron.so/notes/4e14f66f-4df2-4414-8e99-f37159de0f61.html

Like commented on the PR for it I would choose a different Label for Stale Issues -> https://github.com/dendronhq/dendron/pull/651#issuecomment-823975560

Yeah, you're right - I'm good with that change. If anyone's got some more feedback, please comment here, will merge later today: https://github.com/dendronhq/dendron/pull/654

Will take a look in a bit!

woah when did github change their embed

Yeah ... that's way fancier than I remember...

think we can do that for published dendron notes? 😄

Does auto-completion work on block references to headers inside pages as well or am I doing something wrong? (I.e.:

[[design.mechanics# .. ]

=> autocomplete gives me everything inside

design.mechanics

not yet. can you submit a feature request?

@User For your question in #757779937833779361 if the Engine indexing is Markdown Dependent you would need to look into the Note Parser since they get Parsed for Links and such informations.

Ok so the indexing code uses remark to gather information useful for indexing. I wil try to to take a look, the big barries is to see if the server could accept org files!

The logic for indexing notes is described here: https://wiki.dendron.so/notes/ebf58a4a-18f8-498d-95eb-04d856c0a000.html To make Dendron work with org files, you would need to update the

store

component as well as the

noteparser

component. you can see how that's currently implemented here: https://github.com/dendronhq/dendron/blob/dev-kevin/packages/engine-server/src/drivers/file/storev2.ts#L428:L428

@User a little late but finally got around to leaving comments on your graph rfc: https://github.com/dendronhq/dendron/discussions/615#discussioncomment-670626 let me know what you (and for that matter, anyone else here) thinks. we should be ready to move forward with this in may/june

I will respond to it today after dinner probably, we could probably even combine multiple parts in the backend to create a system that is performant and benefits us in multiple ways.

Nice! I will take a look, let see if it's possible to decouple indexing from parsing. However I don't know too much about js so I will take it slow :slight_smile:

Geez I already wrote more than I thought i would I take a bit more time for it.

no rush, take as much time as you need 🙂

Hey All, Just wrote an RFC for Dendron block references which will be implemented this summer. This will let you link and embed to arbitrary blocks of text inside Dendron. https://wiki.dendron.so/notes/95f7193b-9940-42ba-841f-3e2a4d937ba3.html Interface wise, we will be adopting the obsidian syntax for referencing blocks. Please leave feedback in the discussion thread here: https://github.com/dendronhq/dendron/discussions/685 @User would love to have your input if you get a chance to look this over. would be great for us to be interoperable on this front

Hello #748936364283920495 - in the spirit of streamlining our RFC process and providing more transparency on where we're at for each RFC, please take a look at this: https://wiki.dendron.so/notes/f143ca38-dcc6-4cd3-b84b-997aec1160ef.html . Feedback welcome - this was intended to simply write out what we've already been doing so if you see any gaps/adjustments needed let me know.

Top for structuring that and organising it

yeah, it looks great!

Just a question Corresponding to it, should I update the Graph Rework RFC accordingly? Or should I leave that to the assigned Shepard?

since you’re the original author, feel free to update. in the future, @User will also make adjustments as he’ll be working on the implementation

@User question, in regards to the RFC Process. currently they are incrementally numbered, should this be continued or should we find a better approach to that?

Let’s continue incrementing for now, if it doesn’t scale and we get collisions we can just base it on the tracking issue number

Don't know if this is the right place to report this kind of things. Getting annoying error notifications all the time lately:

{"ctx":"parseTree","err":{"status":"unknown","msg":"","payload":"{\"msg\":\"no childNote found: 8411ebfc-b0b4-4dac-ae92-307bc01bada3, current note: root\",\"fullDump\":[{\"fname\":\"root\",\"id\":\"root\",\"children\":[\"d8eaa6bb-ab36-43cf-a562-7f91648ba3e5\",\"98bf2617-d1c3-4682-9624-b1851628816d\",\"fe80b61d-e701-4fed-971e-f5d203e11cdc\",\"2d53c83b-25cf-4cda-acc7-3004e4d156ea\",\"1c40aa2c-4ac4-4b3d-bf21-fb4cffb3631b\",\"de78d48c-9013-4185-9f5d-ca83bfe65301\",\"25e54a0f-0e65-41b8-9a40-f0d83ff3cb87\",\"88163112-aece-438d-a0f4-c095a8656d75\",\"3267a5f1-0ee1-4c48-aded-82f4260cf540\",\"c4047292-42df-44c6-838e-7082d6bf7a1e\",\"8411ebfc-b0b4-4dac-ae92-307bc01bada3\",\"8371a49d-7d53-4958-ae20-1a8cfa16fdd8\",\"d9ead4af-6918-4fc5-badb-28fb6026f5df\",\"bb68c8d7-d8cf-4539-899a-57158add754a\",\"81df3aa9-fe89-4dca-ac36-82ad129135cb\",\"03d0024e-1d0c-41d2-865d-8296a5074fd8\",\"a48afec3-e3e9-44c2-a298-83b8cf76b50a\",\"36d3531c-54a3-4649-abd7-dc14c93b8108\",\"d67c482c-f6b0-4dfb-8850-8f1798771333\"],\...