Or maybe related. See the comment I added here. https://github.com/dendronhq/dendron/issues/2702

CROP - 2022-04-20

is Dendron planned to have a feature to order notes?

it would really help, possibly allowing for navigating them like a book

(each note a "page")

though these are 2 features of their own: - order - paging (of the hierarchy)

You can control the order in the tree view and publishing using the `nav_order`: https://wiki.dendron.so/notes/f2ed8639-a604-4a9d-b76c-41e205fb8713/#nav_order

oh I hadn't seen it

lol and forgot about the tree view, thanks! 👍

Oh, wow,

nav_order

affects the tree view! I thought it was only for publishing 🤦‍♂️ The docs are not very clear on that: > If set, denote order that item appears in the published nav bar

yeah, it wasn't always the case. we've been doing a bunch of improvements, will make sure to clear up docs

Does anyone else find the wording "tried pulling 1 and pushing 1 repo" to be too ambiguous (especially the word "tried" 😉 )? I'm always in doubt if it actually succeeded or not. A better way (imo) would be to clearly print that the push/pull succeeded or not. That way I can see at a glance if my notes are synced or not.

I agree. do you mind creating an issue for this so we can track it? 🙂 https://github.com/dendronhq/dendron/issues/new/choose

done! https://github.com/dendronhq/dendron/issues/2816

Instead of a 100x increase in graph speed i see this in 92 in response to the Show Note Graph command

was the graph working pre-92?

yes, i can downgrade and check if you want

Hey, I just finished documenting how to configure where task notes are created. It's not published yet, but you can read it here: https://github.com/dendronhq/dendron-site/commit/dbd1e5722f3d1c0f0ac3e5e5111001b1056eb780 I think the following settings will do what you were looking for:

yaml
workspace:
  task:
    name: 'task'
    dateFormat: 'y.MM.dd'
    addBehavior: asOwnDomain

Let me know if I can help with your setup. For the sane defaults, I agree and this is how the defaults originally were I think. I'll see why it was changed, and if we should change it back.

I experienced a weird bug the other day - I started a notebook/vault using capital letters in the note filename/hierarchy. After I made a whole bunch of notes I realized that wasn't the standard hierarchy format, so I used the Refactor Hierarchy command to rename them - just down-casing (no structural changes). The notifications for the command listed through the files and reported success, but then when I tried to look at the Tree View, it appeared that Dendron had crashed. When I went into finder directory two copies of each file corresponding to the before & after refactor. The Tree View entirely refused to load until I manually deleted all the old files, and the FILE_VAULT pane only showed the new (refactored) files. I know this is perhaps an unusual edge case and could be VSCode weirdness, maybe? But it was super confusing and took me some time to figure out how to repair things.

not sure how this happened but im thinking dendron didn't update this property in my yaml?

oh it got resolved on reload! nice!

holding command when trying to click on a backlink that is kebab-cased only underlines the delimited portions of the kebab casing, i.e. kebab-case (if i hold command hover kebab, only kebab is underlined)

i was just told that scratch notes have no siblings when doing ctrl + option + bracket, i don't think that is correct and we can travel across the scratch hierarchy by year, month etc.

I think this might be related to this issue: https://github.com/dendronhq/dendron/issues/688

@hikchoi is currently looking into this issue

How can I search the file title names of my dendron workspace?

You can use the

Go to File

command, Ctrl+P by default. This is built into VSCode so it should work in all workspaces.

I get this if I try to move a note too recently after moving a previous one. It appears to let me move another note either after restarting vscode. Or... if i wait a little while?

There're some bugs with the rename/move that should be fixed with the next release I think ( @hikchoi do you know if your fix is included in the next release?), please do file a bug report if that doesn't fix it though

There is a fix for this waiting to be released next week. Sorry about the inconvenience!