Step by step. These are my first 10min here...

Well, the temptation was too strong so I did it. Do not blame me if this is a wrong branch or some such. 😋

lol I love it, the badge is yours!

@User for bystanders and curious folk, the last PR for phase I of seed bank should be merged today and will be shipped out next week. for educational purposes, i'm experimenting with doing public PRs for features. @User pr for last of seed bank changes: https://github.com/dendronhq/dendron/pull/831/files doc for seed bank: https://wiki.dendron.so/notes/4039fc46-06b2-4f83-b817-fc490bafbcb3.html#phase-i

That looks pretty cool!

As noted... Was curios to see the plans. There are lots of rich TODO extensions in vscode...

oh yeah, this is the TODO rfc that i've been working on but haven't published yet 😅

this is the rfc: https://github.com/dendronhq/dendron-site/blob/dev/vault/dendron.rfc.13.todo-notes.md#L1:L1

Oh! I really want to see how this comes to life. I've been pretty busy this weeks with customers and I was struggling with task management

Ah, thanks. I understand that journals and todo's are most common generic activities but this is also where there are lots of tools already and where permanence and subsequent discovery are less important, the aspects that seem to be the comparative distinctions of dendron. In vscode Todo+, Todo Tree and Todo MD are all pretty good already and appear to be doing what you describe? I am likely missing something but personally I am not looking for a journalling or a task management app. The second brain and a shared one is what the current gap is where I am. But do not let me distract you. 🙂

so I've got an import that appears not to be completing. Anyone got a pointer to how I might add trace/debug/info logging to a pod while I winnow my repro steps?

import can be fickle. can you try on a sample directory with a few markdown files and make sure that the basics works? https://wiki.dendron.so/notes/f23a6290-2dec-45dc-b616-c218ee53db6b.html#summary

Can anyone help with running the dendron-next-server?

I'm experiencing this error when trying to run next-server from inside VS Code

but it seems that something is running on port :3005

but when I run > Dendron Configure, it gets stuck with a message "still starting up"

I think it's related to some kind of launch configuration with vscode, but I'm not really familiar with that. related issue: https://github.com/microsoft/vscode/issues/109561

Any idea on the "still starting up" error? Getting it whenever I'm trying to run Dendron Configure

Not quite sure but I'm thinking that engine isn't running?

Not sure what I'm missing, can you point me to a doc somewhere? Could be the case that my setup is outdated

did you end up figuring this out? source map issues usually won't stop the application from running. have you tried running the next-server in the CLI?

nope, the server is running most probably (localhost:3005 is accessible), but Dendron Configure command shows still starting up

and did you start the test-workspace using

cd test-workspace && ./scripts/dev.sh

?

did that, got my binary search down to a few files, should have a ticket together today or tomorrow.

Got a pointer to vscode extension debugging guide (my lousy google-fu is just finding how to debug other programs using vscode, not debug itself) and an example test case I might start from?

we have a debugging guide here -> https://wiki.dendron.so/notes/cb22bd36-d45a-4ffd-a31e-96c4b39cb7fb.html#debugging-tests

woo, I've traced it down to the one file, nearly there!

invalid yaml in the frontmatter:

--- tags: [#archives] --- body

that would do it. frontmatter needs to be valid YAML and # is considered a comment character