It currently doesn't. I've recently opened an issue for this here: https://github.com/dendronhq/dendron/issues/963 I've described what would be a good default behavior there, but would love to get more input on this if you have other ideas 🙂

I am not really sure. Previewing actions before commitment if always good, I think. Deleting links, propagating links to the parent note, if any; listing links for easy refactoring all makes sense as options... Sounds complex but if previewing becomes more systematic it will become habitual, I guess... Have to try in practice for form an opinion. 🙂

I've had some funny things going on with my notes since the new .50 release. First of all, my journal note seems to have lots its customisation - my dendron.config has reverted to an old version. Trying to figure out what was happening, I've found it git is broken too. Is this just me, or have there been any changes that might have caused this?

Turns out, git was half broken. Still apparently working in VScode, but not actually working or pushing to the remote repo. Very odd

But that still doesn't explain why my journal note settings changed unexpectedly. I can fix this, but I'd love to get to the bottom of what happened as unexplained changes make me very nervous.

how did your journal note settings change? journal settings are now set in

dendron.yml

instead of vscode. we fixed a bug in 0.50 were we were not looking at

dendron.yml

for the new values https://wiki.dendron.so/notes/9bc92432-a24c-492b-b831-4d5378c1692b.html#bug-fixes

Ah, that explains it, thanks Kevin! It reverted to defaults. Which makes sense, that's what's was in dendron.yml.

Is there a way to move more than a single note to a different vault at a time?

not currently. you can run the ‘mv’ command to manually move with * and then reload workspace afterwards (note this won’t update links)

feel free to submit feature request 😇

Got it, thanks.

This is tangentially related to one of my questions. So I will ask here. Beyond retaining the headers and not modifying the IDs, what other considerations should one have when manually manipulating the vault?

I am thinking about scripting some periodic tasks that would modify existing .md and generate new .md files.

see here -> https://wiki.dendron.so/notes/683740e3-70ce-4a47-a1f4-1f140e80b558.html#can-i-manually-move-notes

Dang it! I have been reading a lot of your documentation but missed that. Sorry and thanks. 🙏

actually added it when I saw your question 😅 "sustainability" is part of our values which means avoiding one offs https://handbook.dendron.so/notes/b89ba854-72fb-4ebc-a8a0-55960b89e9dc.html#sustainability

Hey there, I'm having some trouble publishing on GitHub, getting a no data DendronError, I assume because it's not pulling my vault down for the main bios-garden Dendron project. https://gist.github.com/BiosElement/87cb9e74ddb05ba49fd973bfb3d4bf42 'Root' Repo: https://github.com/BiosElement/bios-garden Vault Repo: https://github.com/BiosElement/Dendron Likely just something I'm entirely misunderstanding on configuration.

ah - so dendron will automatically pull down remote vaults when the plugin initializes but that doesn't happen when you run buildSite. the dendron action tutorial is written with the idea that your workspace and vault are in one repo. you'll need to add a step to manually clone your garden before running buildSite if your doing it via github action

Ah (I see we like the same verbage!) That makes sense, I'll do so 🙂

Is there any practical advantage to splitting the vault from the core workspace? I only did so because it looked like the 'correct' way, but have little preference otherwise.

@User So uh yeah, my first attempt at updating the GitHub workflow action with a git clone step worked first-try...so apparently you have the magic touch at giving good support! 🙂

for splitting vault, we document reasons to do so here -> https://wiki.dendron.so/notes/24b176f1-685d-44e1-a1b0-1704b1a92ca0.html

the way to think about it is the amoeba pattern -> https://wiki.dendron.so/notes/e780000d-c784-4945-8e42-35218a3ecf10.html start simple and expand to multi-vault as needed

will also be relevant when we get this more developed -> https://blog.dendron.so/notes/qTeL51LFD0Y8uC9ect7QV.html

I'm looking for suggestion about

Markdown Table formatter

Extension I saw a few in the market place, but I use VSCodium so number of downloads and ratings may not be accurate. I trust folks here more than numbers of some market place 😄 Please suggest based on the ones you use personally

i recently saw a warning notification in vscodium stating that > The extension

Dendron Markdown Preview Enhanced

took a very long time to complete its last operation and it has prevented other extension from running is this normal?

this is only when we make an update to the extension (we just did last week). moving forward, we're actually going to be using our own preview which is 1/10th the size which is going to make this problem go away

i don't use a table formatter but a few thoughts: 1) since this has come up a few times, you could give us a feature request and we can add it to our roadmap to have it built-in 2) vsx allows anyone to upload an extension and since the existing table extensions are open source, you could also package and upload it to vsx

Hey guys, got a small issue I can't figure out. Since the last Dendron update, the internal links [[like.this]] are not highlighted blue anymore, and it's hard for me to find them in the text. Is there a way to turn that back on? edit: Internal links to notes that don't exist yet DO get highlighted in yellow, so that's handy

hmm, not able to reproduce. can you provide some more context with an example note and a diagnostics report via DM?