oh, cool :D

I thought there was a way to link my Discord to my GitHub or something, as I saw that the other folks in the announcement had their Discord @ in there as well

no, that's currently a manual process we do in our end 😅

moving forward, you're now in our system so it'll be linked

alright

thanks for the quick reaction :)

its to make up for my delay in your pull request 😅

haha no worries

definitely not in a hurry

I am seeing two instances of back links is that expected ?

nope. do you have another note taking tool installed? (eg. foam, markdown notes)

yup i had markdown notes installed. thanks

Does dendron have any support for filename extensions like

.todo.md

or

.bookmark.md

without showing these as an additional hiearchy?

No. They will be recognized as the base name of the note in Dendron. Are you exporting/importing them to a different tool?

I want to use a few different tools of which dendron is one to manage my data. Specifically I really like nb for its bookmarking functionality, so I'm considering loading my nb bookmark archive as a vault in dendron.

I see. currently there would be no way to do this out of the box. However I can see how this could be very useful. If one would dedicate a single vault to interface with one external tool of choice, the ability to mark a vault so that it specifically recognizes files and syntax that the tool uses would save a lot of effort. Do you mind submitting a feature request? We have briefly discussed similar ideas internally and it would be great to track an actual use case for this 🙂

Sure, will submit a feature request now. I'd personally favour adding a config option to my workspace or my vault which says "ignore this suffix as a hierarch". In the same way that

.schema.yml

is used.

That would be a good starting point. We can always generalize this later when we identify more use cases of interfacing with different tools 👍

I spent a good amount of time in VS Code today, working on python scripts and documenting in Dendron. - It is doable (coding and km'ing). - Had a workspace open for Dendron docs - Then

File/Open File

to work on the python script. - And a terminal in the python script's directory - Some stuff I wrote: - https://github.com/GjjvdBurg/labella.py/issues/20 - https://github.com/GjjvdBurg/labella.py/issues/19 - https://github.com/GjjvdBurg/labella.py/issues/18 - https://github.com/GjjvdBurg/labella.py/issues/14#issuecomment-1021672875

One thing that wish was easier, was capturing the GH Issues in Dendron INCLUDING SCREENSHOTS and transfer them to GH. That was hard. Otherwise pretty decent

Can you elaborate on the workflow for submitting the issues / issue comments? Did you compose the post as a Dendron note, then copy paste them to submit them? What was the painpoint with screenshots in this process?

@User , yes that about right. I also edit GH Issue posts too, so I would go back and edit in GH, then update the change in Dendron, etc. The pain was having images with local paths. I use Snagit so after one post from Dendron to GH, I opened the screenshot library in Snagit and replace the images by pasting them into the GH Issue post.

(basically replacing

![](\assets\img.png)

with

![](uploaded_to_github)

)

We have a built in Github Issues Pod that could import existing issues into Dendron and also update the imported issues. Unfortunately there is no export pod that will directly submit a github issue yet. I would imagine this would need to go through Github's API if we don't want to skip the step of copying the asset to clipboard and pasting them in the browser so it gets uploaded to GH before submitting. @User Do we have plans to add support for github issue exporting?

Actually we do have a Github Publish Pod that lets you create/update a github issue. Unfortunately it does not support exporting assets yet. https://wiki.dendron.so/notes/8JECQzntY2P5ha3U/

Ah I see. I misread the note and didn't think it can create.

Yeah, it would create a new issue and populate the note frontmatter with issue Id and status on successful creation.

VSCodium often becomes unusably slow, like it hangs for multiple seconds. I've never seen this in VSCode (where I don't use dendron), so I assume it has to be dendron related. Is there anything I can do to improve performance? Or any steps to debug? Somebody mentioned the extension bisect option before, but by now I'm pretty sure that dendron is the issue. It seems like dendron "hangs" the whole editor. I read something about that in the server package. Are there any experimental performance optimisations I could try?

I only have ~2k notes, maybe less.

Oh shoot, I've just discovered that dendron deleted all of my notes from one vault. Thankfully there's a git commit. It's a dendron sync commit and it wiped everything, reset the whole vault, including the

root.md

file. Uh oh...