Sorry for being confusing 😚 Here is my try to paraphrase. Instead of writing a python script in a code block with triple backticks, I wrote it in a gist stored in GitHub [0] then I paste the shareable link into the markdown note. I hope that the link will be rendered as a little windows like in [1], when the note is published with Dendron. However, there is nothing, just a blank line in place of that gist’s link. [0]: https://docs.github.com/en/get-started/writing-on-github/editing-and-sharing-content-with-gists/creating-gists#about-gists [1]: https://towardsdatascience.com/github-gists-101-making-code-sharing-pretty-163d9321a0af

Oh that's very cool, but you're right that Dendron doesn't support that at the moment.

Thanks for confirmation. I will write a FR in Dendron backlog queue for future then

I’m evaluating Dendron from the perspective of a technical user who doesn’t want to be technical when doing something simple like making notes. I’d also like to bring in other collaborators, but currently Dendron has a hacker appeal. Or at least that’s the vibe I get. So, several questions: Can we hide the YAML header, to make each note cleaner? Can a vault be stored on Google Drive (for example), so that it’s easy to access from multiple computers? (For those who don’t know anything about Github.) How does one import a massive number of files from another system, ensuring the notes have the correct YAML headers, etc.? Would you consider setting up a forum (Discourse, etc.), so there’s a cleaner way of getting help than Discord?

Google Drive question is maybe dumb, since that software itself will handle sync. So long as there's a top folder to point to, this functionality has little or nothing to do with Dendron.

1. Maybe the preview panel would be good? It looks less "technical" and does not render the YAML header. 2. Yes, Google Drive should sync things automatically like you said 3. There's a Dendron extension (we call them "pods") that allows you to import markdown, json, etc. Here's the documentation in our wiki: https://wiki.dendron.so/notes/3e519113-5820-4a84-bef8-85103a7b296b/ Once it's imported you can just initialize the folder as a Dendron workspace and use it like normal. 4. That's interesting, what are the problems you're experiencing with Discord that Discourse better addresses?

I store my Dendron stuff on Dropbox, instead of syncing through Git. (I haven't ever tried syncing my Dendron notes via Drive, Box, etc, but I do at least know Dropbox works quite well.) Perhaps that's functionally equivalent for the non-technical folks you've got in mind?

>Can we hide the YAML header, to make each note cleaner? You can edit the dendron.yml by running

Dendron: Configure (yaml)

and set the

enableAutoFoldFrontmatter

property to

true

which will automatically fold the frontmatter when opening new notes. https://wiki.dendron.so/notes/3i4ABJutl7NGeXRHTnUEC/#enableautofoldfrontmatter

Discord is better for current conversations; a forum is better for persistent answers. A forum is embedded on the same website where people go to download your application, read documentation etc. It's handy. Discord is a separate space that not all users are comfortable with. In fact, my only identity here is as a gamer... which says a lot about the ecosystem.

Is there a way to automatically render text blocks of backlink mentions? I know how to do it manually, but that requires writing the stuff, then remembering to make a reference back to it etc. I get backlinks section can sorta do this with links in an extra pane which you need to click-through to see, but it'd be nice to auto-generate the mentions within the page itself.

Hello, I have a note, where Preview is not generated. When I re-open preview, I only see "Loading...". When I click other notes - preview is rendered quickly. This note doesn't look different from other notes I have in the same category. How can I troubleshoot what's wrong there?

we have a github discussions for non-discord and more persistent conversations > https://github.com/dendronhq/dendron/discussions

Hi team, for some reason dendron won't start anymore. When I open vscode, I get {"errno":-2,"code":"ENOENT","syscall":"stat","path":""}

If I remove a certain symbolic link in the directory tree it works

but then the preview for files does not work

Error starting with: {"stack":"DendronError: Unable to render note root.md in dir-function(e){return s.default.posix.format(s.default.parse(e))}\n at h.renderNote (/Users/user/.vscode/extensions/dendron.dendron-0.94.0/dist/server.js:2:311927)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async c.render

And when attempting to create a note named e.g. "foo" I get "not root found for foo"

Could you use "Dendron:Dev: Open Logs" and message me the output? Let me see if I can figure out more details about the error

'ENOENT' is a common stupid error term for when an env path variable doesn't resolve. Often caused by installing a new version of Node or Python or some SDK or wearing socks n sandals etc.

If anyone else gets this error, it was caused by a vault configuration that used an absolute path for the vault, like:

yaml
vaults:
  - fsPath: /absolute/path/to/the/vault

This is not supported,

fsPath

must be a relative path from the root of the workspace. The root is where the

dendron.yml

file is located.

so, i updated to 94 and have warning about duplicate IDs but i am not clear which notes and what to do

The warning should tell you the note file name and vault, does it not? For the solution, you can manually change the

id

in the frontmatter, or use the Dendron Doctor command and pick the regenerateId option.

hi, so i have a markdown repo that i am converting to dendron. the steps i have taken are 1) turned on self contained vaults experimental feature 2) initialize workspace command 3) select code workspace with option to use existing workspace. i see that in my markdown repo a folder

notes/

was created, and

dendron.yml

and

dendron.code-workspace

were created in the root folder of the markdown repo (one level above

notes/

). is that expected behavior? is there a way to just make the flat root of my markdown repo the single self contained vault instead of creating a

notes/

directory?

You can remove the

selfContained: true

option from the vault configuration, which will take you back to a regular vault. You can then move the notes into the vault root then. We are considering eventually making self contained vaults required though, is there any reason why you don't want the notes under a folder? We want to make sure we can cover everyones usecases

honestly, i don't have a great reason, and for the sake of keeping it as a self contained vault, i think i will use the notes folder

but the reason is because the naming for the repo is already

docs

, so having a

notes

folder within feels redundant and would prefer to just have the repo itself be the root of the vault

another redundancy is the .vscode folder within the

notes/

directory, i already have a .vscode directory in the root of the repo

Yes, it gives vaults and note names but not all notes it lists seem there. Anyway, trying. Meanwhile, can we please have a warning before allowing the user to apply Doctor to ALL notes. Second time I am doing this by mistake. Also the safer default is the current note...

I wonder what the fastest way to revert might be, it is a few vaults...

actually it looks nice in the notes repo. separating a lot of config files from the markdown notes. i prefer it this way