all good

Also done 😄 https://github.com/dendronhq/dendron-site/pull/536 Though the garden itself is of course totally a WIP

Finally had a reason to refactor about 150 notes yesterday. Just wanted to thank whoever worked on that interface / feature! The "this is what will happen" preview pane definitely helped me feel comfortable doing something that would otherwise have made me either very anxious (if I tried regex on my own) or very frustrated (if I renamed the files all manually).

Haha, yeah that's one of those "oh I thought it was normal" kinda pages, that isn't normal, so take for granted. So much software nowadays just does stuff and goes "welp, hope we didn't ruin your day", rather than a good dry run report before-hand.

Absolutely! It's good to design with error-prone users in mind, and I wish more people did. I know, because I'm a very error-prone user!

@hikchoi ☝️ 🙂

any progress on https://discord.com/channels/717965437182410783/739186036495876126/979822093443170334 ?

I'm seeing this popup when starting any workspace in VSCode, not only for a Dendron one.

It looks like something in the extension is, on Windows at least, enumerating through the root directories and when it hits one that has the attributes I describe in that thread, the popup appears.

Sorry about that, I'll make sure to look into it today. A fix wouldn't make it into the release this Tueday, but should be out by the next one.

👍

If I do Command+L and then type the identifier of a note that doesn't exist, and then press enter before the preview updates, it creates a partial version of what I typed

e.x. "books.fiction.some-book" becomes "books.fiction.some-bo"

so I end up having to create a note and then immediately rename it, which is frustrating :(

especially since sometimes the internal cache of dendron state thinks that "books.fiction.some-book" was created (?????) so I can't rename until I restart vscode

not sure if there's anything y'all can do about the first bug but the second one seems solvable maybe (this smells like a race condition from reading the text box multiple times)

Hey, thanks for the report. Would you create an issue for this? We are planning to push some changes that will fix the lookup sluggishness but I don't think what you described is handled there.

Just wanted to say: I've been away for a bit, and wow! All these new features and updates. I'll be tweaking and updating my vaults. Awesome work!

The plus symbol dosen't go away even after creating the file and also refreshing the index

Check you have

stub: true

in your frontmatter for these files. Sometimes it sticks around for whatever reason.

Is it possible to somehow to configure keybinding to change task status (https://wiki.dendron.so/notes/SEASewZSteDK7ry1AshNG/#setting-task-status--marking-a-task-as-complete) to use the same key combinations as in the bujo extension (https://github.com/mihaiconstantin/bujo#keybindings-for-updating-entry-symbols) ?

yeah - the keybindings are completely customizable. see https://wiki.dendron.so/notes/c8e99b84-8a5a-42d3-838d-3d5cdebf32e5

great update! thanks you!

@User we're refactoring the dendron docs to adhere to a standard format so that all features, configuration, commands, etc are just one lookup away. the goal is to make it unambiguous to either find or add information on new features and capabilities. we would love to get everyone's input on this - if you have opinions on the structure of the dendron docs, please leave feedback in the github discussion https://github.com/dendronhq/dendron/discussions/3088 @nickolay-kond @ScriptAutomate @foureyedsoul @hikchoi

ServerNotify! It's CROP time (every other Wednesday). 🙂 Please vote for your favored community issue 👨‍🌾👩‍🌾: 1. [Merge Notes command](https://github.com/dendronhq/dendron/issues/906) 2. [Vault rename command](https://github.com/dendronhq/dendron/issues/840) 3. [Enable setting Katex options from dendron](https://github.com/dendronhq/dendron/issues/1535) 4. None of these (if there's an issue you'd like to add to rotation, please reply with a Github issue). To vote, respond with a 1️⃣ 2️⃣ 3️⃣ or 4️⃣ to this message. Voting closes Monday at noon Pacific Time.

CROP 2022-06-15

Not sure if this already a known issue or if a new issue needs to be opened: - I created a new note for a new user via goto note on

@Example

- Because

@Example

starts with a capital letter, Dendron made the note as

user.Example

, which I wasn't expecting. I was expecting it to be

user.example

- Dendron doesn't let me rename the note to a lower-case version, giving me the error message

my-vault/user.example exists

This may be two issues, I suppose, one where Dendron is making a note with capital letters, and the other issue being that you can't change the file name with rename note. I'm not sure how this may impact backlinks

The rename makes sense, Dendron is case-insensitive so

user.Example

and

user.example

are the same note. The note being created with a capital letter is a bug I would guess

depending on operating system, if windows you are renaming for the same name (not case sensitive)... have tried user.example1 and after user.example ?

Okay, good to know that Dendron is case-insensitive, which means things like backlinks would still function as expected, etc.