Recursively linkTo?

[Pete]

Ahh, sorry! Updated the file above.

@mwra

if this task is important enough to need to work correctly

It’s not important, just would be nice if it would be possible. It’s more of an experiment whether temporarily using a rule or an edict would allow to act on nested notes. Meanwhile I think that won’t work at the moment, see the updated file and this post.

@mwra

@Pete

Don’t want to create a user attribute just for this task.

Why?

I hesitate to create a user attribute for this as it would probably irritate me in every new file - but I now figured I should simply prefix such “setup” user attributes with e.g. “sys” which would make it clearer.

@mwra

I don’t think it is a rule vs edict thing, but rather that you can’t set a rule, run it and void it all in one action code cycle as the last voids the action before it gets to runs.

Probably. I already tried this some years ago but can’t recall whether it worked or not. Maybe it’s simply not possible.

Meanwhile I’ve found the reason why the stamp below sets the selected “notes” note’s $MyList

$MyList=collect(descendants,$Path);

$MyList.each(X) {
	$MyString(X)=$Rule(X);
	$MyBoolean(X)=$RuleDisabled(X);
	$MyList(X)=;
	$Rule(X)='linkTo(children); $MyList="executedRule"';
	$RuleDisabled(X)=false
};

This line

$Rule(X)='linkTo(children); $MyList="executedRule"';

isn’t used as a whole to set the rule, instead Tinderbox stops after linkTo(children). So what the stamp actually does is setting the X’s $Rule to linkTo(children) and then the following $MyList="executedRule" sets the “notes” notes $MyList to executedRule.

Rewritting it with a technique I learned from you works:

$Rule(X)="linkTo(children);"+" $MyList='executedRule'";

But that won’t help if the rule doesn’t fire immediately (or stops to work).

@mwra

Without a test file it’s hard to replicate the scenario.

I’m curious whether the rule also stops to run automatically with your setup.