I'd like TAGS to stay with the parent stem when I split a line, or be copied to both new siblings
I'd like TAGS to stay with the parent stem when I split a line, or be copied to both new siblings
at the moment, when I split a line, the tags are migrated to the new line rather than staying with the original. If I can have only one, I'd prefer them to stay with the original stem.
-
This hasn't been addressed at all, and it's increasingly painful.
I'm tagging everything now, and splitting nodes into individual points. Having to manually copy tags back to the original node when I split it, and sometimes having to delete the tags on the new node is just tedious.
I can't see any justification for divorcing a parent node from its tags when splitting it.
Please advise!
-
Hey Adam,
While I understand the dynamic you're speaking of, this is a very specific workflow that you have in mind... meaning that if the above behavior had to happen for all users, it would be a tad confusing for many folk. When people split a bullet's text by hitting Enter, they'd expect all of the text to split where the cursor is at. Tags are also just text. This is a rather unique use case that I must say I haven't come across other users asking for.
Perhaps a solution would be to prepend your tag to a list as opposed to creating it at the end of a bullet?
Also, I am sure there are a couple of WFx PowerPack solutions... perhaps the Multi-tagger (for part of your workflow)... and perhaps you could ask @rawbytz to put together a script that does what you're asking. It certainly does not sound like a behavior that I would want myself.
~ Frank
-
Hi Frank
My bad - I forgot to say that the tags I'm referring to are in the notes, not in the node text itself
Here's the current and desired behaviour in screenshots:
1. node with tags in note. I want to split the node into two separate nodes, so I cursor before "node" and hit return.
2. node split, with tags migrating to new node by default
3. this is what I want to see - node split, with tags retained by parent node
4. or this, with tags duplicated into new node:
Please sign in to leave a comment.
Comments
5 comments