I canot recall how I made it possible, but they all seem notes. Unfortunately these are not aliases. All notes. Does it mean I have to erase them manually?
Create a note at the the root whose name is “Trash”. (Or call it whatever you want, it makes no difference.)
Create an agent whose query is:
$Name.contains("Title of notes I want to delete");<-- obviously use the correct name here
and whose action is
$Container(original)="/Trash";
When the notes have been moved by the action, inspect the contents of “Trash”. When you’re satisfied, delete the “Trash”.
HOWEVER – you will possibly capture something in “Trash” you don’t want to be there, so you’ll need to put it back where it belongs. Actions that change containers run the risk of destroying your work and the structure of your document. With NO possibility of undoing the action. Be very careful and do not use what I recommend unless you are certain you understand the consequences. Test this on a duplicate of your main file and make sure you have multiple backup copies.
Of course agree on the caution --and the recommendation.
Question: could you build in a protection against this irreversibility, with a sequence like this?
Create a new string attribute, like $OldPath
Set up an agent to deal with all items, or just the ones you think might be deleted, and have its action be $OldPath=$Path(original). (Which would assign the existing container structure to an attribute – and save it for later reference.) Obviously you would want to run this agent only once, or maybe apply it as a stamp, so it wouldn’t get updated and overwritten if you moved the originals.
Then apply the agent that would move the notes to the \Trash container.
As a failsafe, you could send things back to where they started with an undo-style agent, whose action was $Path(original)=$OldPath(original). Right? Or is there a step I am not understanding?
Correction to my earlier post: if you had saved the previous note location with $OldPath=$Path(original), then the way to restore it would be $Container(original)=$OldPath rather than the other formulation I had. (I think.)
Agree on trying this out thoroughly on a copy of the real file to be sure it does what it’s supposed to.
I believe you’ll want your agent to always operate on the “original” and not change the agent’s aliases paths. So the safety agent’s action is $OldPath(original)=$Path(original) and the restoration agent’s action is $Container(original)=$OldPath(original).
Otherwise Tinderbox will assume “this” for $OldPath in the action $OldPath=$Path(original) and the restoration agent will send the originals to the wrong place.
(I’m making assertions I haven’t tested, which isn’t a great idea – although speak-first-research-later-or-never seems consistent with our times .)
That thread is about drag/drop addition of text files. Such an event would create a new note per dropped text file. That’s the source. The duplicated title is due to an error either at source (outside Tinderbox) or in action code you’ve made to rename the newly added notes.