I was looking at the Bullet Journaling info on dendron.so. When i try to watch the loom videos, i get this error: "An error occurred on the page: TypeError: Cannot read property 'catch' of undefined". Is there any way for me to resolve this?

hmm, is this on the dendron page or the loom page? can you send a link?

When i click the video on the dendron page, it comes to loom:

When i click the video here, i get:

What browser are you using? It seems to work fine for me on Firefox and Chrome

ok, strange, when i click the link here in discord, it works.

I am using Chrome.

Just brought up Firefox, put link in there. It works, so i am ok. Just wonder why Chrome is behaving that way for me. I am ok for now i guess.

strange. don't know if there's an action step here unless it happens again. meanwhile, i would check if refreshing your chrome cache and deleting all cookies would help

ok, maybe that will help. thanks. I am just really trying to get things figured out and get up-n-running on dendron. It is a very nice piece of software! thanks!

if you have a non-chrome related question, might be able to give more helpful advice next time 😅

😆

I don't know if this is something that anyone else faces, but essentially when I type

[[]]

to create a note link, the link window showing them is too small. Combined with the fact that I have been adding dates towards the end of the hierarchy, this means that it makes it hard for me to select the right note. I should probably change this organisation, but even without this, I may accidentally select a stub instead of a real note because I can't see the entirety of the note name. Is there any way I can adjust the size of the link window? I think the main reason this happens is because I use VSCode on two screens - my MacBook screen and a 4k monitor. The problem occurs on my monitor because I have to increase the font size to actually be able to read the text on the screen, which increases the size of the font in the link window without increasing the size of the window.

Could you try adjusting the Zoom Level in the settings rather than font size? That adjusts the size of everything, so it should resize that window too I think.

iirc you can drag the edge of the popup to resize it. I think it remembers the popup size after you resized it too.

Oh nice, that seems to work too

just did a quick test and it seems like it does remember the size even after quitting vscode 🙂

thanks! resizing worked great!

> Could you try adjusting the Zoom Level in the settings rather than font size? That adjusts the size of everything, so it should resize that window too I think. Yeah this would be ideal except I am using VSCode on two screens at the same time and changing the zoom level changes it on both unfortunately... and then it's too big for my MacBook Pro I guess I could have a workspace setting or something on one of them

Ah also on that line of thought, would you do something along the lines of

cooking.meal-planning.2021.05

or

cooking.2021.05.meal-planning

or something entirely different?

I think it's totally up to you. I would personally go with the former but if it was part of a daily journal I would do something like

daily.journal.2021.06.18.meal-planning

based on the fact that my journals are firstly a temporal thing.

I think Dendron (or maybe VSCode?) updated itself today. Now I see a message "Issue initializing Dendron" and no other information on how to proceed. See attached screenshot

Could you try running the command

Dendron:Dev: Diagnostics Report

and DMing me the output?

To prevent a poor user experience, would it be possible to 1. Get additional tips in the error message on what the user can actually do ? E.g. look at the logs which are at or Unroll update (if that's possible) 2. Can we prevent auto-updates as default and instead resort to, "Hi, an update is available. Please update when you have some time." or something like that? In my case, this happened when I was in "production mode" i.e. wanted to actually use Dendron for something urgent and it is a bit annoying to think, "Great. Now my tool of choice is not working.. I need to pull up some other text editor or something." I know Dendron is still in beta, but still...

@User doing that now..

autoupdate is part of vscode and unfortunately not something we have control over. you can turn of auto updates in general . see https://code.visualstudio.com/docs/editor/extension-marketplace#_extension-autoupdate

Done. Thank you. Meanwhile, @User also helped me resolve the initialization error (turns out there was a file in the vault with bad front matter.. a few extra : symbols had appeared.. )

Hi. Some comments for context, then I have a question: I'm refreshed to learn about Dendron, coming from a strictly ZK/wiki-linking background. There was always something missing from searches and wiki. It seems our brains are very much wired for hierarchy (though, linking also has a place). Upon first look (without trying the software), it seems Dendron's naming system can be implemented in any file system. Soon, one realizes the maintenance of such system would become nearly impossible the more files and branches that are added that need updated/re-branched. My question -- why not just use this hierarchy naming schema for tags? As such, when a branch needs to change, changing the hierarchical tag would change all instances of it in all notes. This isn't a challenge to those invested in this project. Admittedly ,it's exposing my naivety such that I can gain an understanding of Dendron's value I cannot perceive just yet. Thanks for any insight.

We have ways to quickly refactor and rename notes so the maintenance could be easier, and we are continuously improving its features. See the

Refactor Hierarchy

section of the note here: https://wiki.dendron.so/notes/eea2b078-1acc-4071-a14e-18299fc28f47.html#refactor-hierarchy and in fact, our current way of implementing tags is to create a

tag.*

hierarchy and using backlinks like

[[tag.foo]]

when you want to tag (see: https://wiki.dendron.so/notes/8bc9b3f1-8508-4d3a-a2de-be9f12ef1821.html). This could be somewhat misleading to folks who are used to the typical implementation of tags in other systems so we are considering introducing a special syntax around it that could be used in the frontmatter of the note in the future. (Note that once you have a

tag.foo

hierarchy, running

Refactor Hierarchy

on it to change it to let's say

tag.bar

, it would find all occurrence of it and change it as well so it will achieve what you have described there 🙂 )