Thanks, but it searches only file names. What if I wanted to search a specific folder name?

I believe

Ctrl+P

will also take sub-folder/directory names into account, so you can search by vault folders, and within the assets directories

Hi there, I have the following files: lang.metapractices.md lang.metapractices.code-review.md I would like to refactor them into: lang.metaskills.md lang.metaskills.code-review.md I matched the files with lang.metapractices.* but I didn't find how to refactor them to the desired output

Could you try doing "Dendron: Refactor Hierarchy"? For the first prompt write

lang.metapractices

, then for the second prompt write

lang.metaskills

. You don't need the

*

, the unmatched parts remain unchanged so just match the part you want to replace.

How to do that without overwritting files?

Could you try

lang.metapractices.

and

lang.metaskills.

(same, but with dots at the end)? That will only rename

lang.metapractices.codereview

, and you can manually merge

lang.metapractices

into

lang.metaskills

yourself

Is there a way to merge a note into a new one with dendron?

You can copy and paste the contents, I don't think there's a command

Love the new Dendron sidebar, but I find it annoying that if I reload VSCode, the Dendron sidebar loses focus and the Explorer gets the focus instead. I have other extensions that add additional sidebars and it seems they keep the focus on reload, but they do load almost immediately. It take a bit for Dendron to load the additional sibebar icon to appear at all. Is this the problem? Is it possible to somehow keep the Dendron sidebar focused after reloading VSCode?

It doesn't solve that specific issue, but I have created a keyboard shortcut to focus it (I chose ctrl+# as I had nothing mapped to that) at least

Thanks for the workaround! I think I'll open a new issue about this.

@jyeung is working to make the sidebar persistent across reloads

Wonderful, thank you. So, since you are already tracking this, you don't need a separate Github issue.

@User! It's CROP time (every other Wednesday). 🙂 Please vote for your favored community issue 👨‍🌾👩‍🌾: 1. [Journal Sibling navigation does not cross month threshold](https://github.com/dendronhq/dendron/issues/688) 2. [Move Note between vaults should move assets as well](https://github.com/dendronhq/dendron/issues/525) and its duplicate [Move note leads to broken images](https://github.com/dendronhq/dendron/issues/2202) 3. [Allow doctor to differentiate between notes in different vaults](https://github.com/dendronhq/dendron/issues/2540) and its duplicate [Additional scopes for Doctor commands](https://github.com/dendronhq/dendron/issues/2809) 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.

I wrote about dendron: https://dev.to/mshiltonj/my-personal-weekly-reviews-in-dendron-3929

I finally read the atlassian outage report, and started thinking about what are the some of the(frontend only, excluding all the enterprise stuff like I’d need to be able to switch from confluence for publicly shareable forms of team documentation. I think these are - option to insert a generated page table of contents for headers in a long docs (rather than the current sidebar) - collapsible blocks where it’s clear the block is clickable (the native HTML detail/summary element is decent but people routinely don’t notice it’s expandable, I use confluence expandable blocks heavily - Colorful “status blocks” (info, status, warn, error) - obsidian and several doc frameworks call them “admonitions”

we're working on it 😇

Nice writeup and liking the weekly journal + schema setup. A bunch of folks seem to prefer the weekly over/with the daily - we might add better native integration for the use case in the future. Also if you're so inclined, considering adding your entry here to share more broadly with future dendronites 🙂 https://github.com/dendronhq/awesome-dendron/blob/main/README.md#read

As you're doing theme work, you might want to add some kind of CSS indicators for the html / elements, since I've also run into that "it's not obviously expandable" problem @cameron mentions. If it's any help, here's my attempt to make them more obviously interactive from a few months ago: https://infolit-idaho.github.io/infolit-for-everyone/sift/#sift-details Quickly looking at the source, I think I mostly just added: - underlining to the elements -a border around the entire element - and maybe a triangle for the list item / disclosure indicator?

tag @SeriousBug for visibility

Sure, I'll go ahead and add it to the built-in theme. You'll be able to override that with a custom theme too since custom themes are just CSS

Doctor: fixFrontmatter removes

stub: false

now, awesome!

now any note that persists in the file system will remove the

stub

property if it exists (true and false both)

Journal Sibling navigation does not cros...

@TomDuffield @nickolay-kond FYI > latest release (v0.94) now supports navigating uri's of frontmatter: [Go to](https://wiki.dendron.so/notes/vikda112zw2sss8lbit4qey)

Kudos for the improved tree view! It feels super snappy.

@hikchoi did the bulk of the work there 🙂

@SeriousBug thank you so much for the cli bugfix my work flow is so much nicer again

@rlh1994 heads up (coming next release or this friday for early seed) > https://github.com/dendronhq/dendron/pull/2887

I was thinking you would be saving this until the 100 release! Fantastic news!