we use the following regex to match files to move

js
const re = new RegExp(`(.*)(${match})(.*)`);
notes.map(n => re.exec(n.name))

for what you wanted to do, you would use something like the following:

- match: ^(?!root) # match beginning of file except for `root`, dendron doesn't let you move it
- replace: fooparent. # replace beginning of line with fooparent

the nice thing about using

Refactor Hierarchy

is that it also updates all links pointing to those files

ya. i realized that

mv

-ing files wont update internal links. the native method works. thanks again!

> and i've been telling other members, because dendron can be a little much to get started with, i'm doing 30min onboarding sessions with new users. that's where i try to understand your primary purpose for adopting dendron, go through any questions you might have as well as show some popular use cases and ways of setting up your dendron. link below in case you're interested 🙂 > > https://calendly.com/thence/meet @User It looks like i have to stay up late, if i want to meet you 😆

@User If you are on the CET timeline, you should find some day where kevins8 is available at 10pm.

once i have some more free time to play with denron, i'll do that 🙂

i think the calendly has a cut off but we can always coordinate a time via direct message 🙂

That's very nice of you. I need ro find some time to really play with it but work keeps me quite busy

Hey guys I need some help. I am trying to get my vscode on two machines setup to sync with github. I have one machine setup and working but I can't seem to get it working on the second machine. The second machine will need to pull from github before it starts pushing

any ideas?

when you say you can't get it working, do you mean you can't pull the repo or dendron isn't recognizing it?

if its the latter, instead of initializing a workspace, you can use

Change Workspace

to switch to it

I finally got it!

It was a vscode issue not a dendron issue

thanks

It's probably already on your roadmap but is it/will it be possible to use wildcards in header refs? Something like: ((ref:[[journal.*]]#Tasks))

@Buxel im interested in what you think this ref would point to exactly; every file with

journal.*#Tasks

in it?

Yep, i thought of it as a way of quickly getting all tasks from journals. Similar what the vscode search does in your TODO example video

> It's probably already on your roadmap but is it/will it be possible to use wildcards in header refs? Something like: > > ((ref:[[journal.*]]#Tasks)) @Buxel yep, that’s the plan. probably will land sometime next week

currently, you can do the same thing using the search editor as per the todo video

you just won’t be able to pass in a range

Kevin: Have you seen this by chance? https://isene.org/hyperlist/

Would kinda be cool if Dendron could do this!

> currently, you can do the same thing using the search editor as per the todo video @kevins8 I might be mistaken but the search feature didn't list all the todos below #Tasks

oh, you're right, didn't show that in the video. so looking for

Tasks

and then increasing context lines. not ideal because you also get context for lines above the

Tasks

header

> Kevin: Have you seen this by chance? https://isene.org/hyperlist/ @User haven't seen it, thanks for the tip. looks like a more structured approach to doing lists. probably won't have built in support for this in dendron anytime soon unless there's demand but the nice thing is that anyone can create a standard vscode extension to support it 😉

Kevin: What would the syntax be for my schema file for this: pro.home.personal. I want it to use a template of pro.home.personal.template ?

I currently have this in a pro.schema.yml file: