Replies: 1 comment 2 replies
-
This is certainly something I have thought about supporting! It would have worked really nicely with the way boards used to be defined as (as you have said) it would be an option for a special type of tag board. Now I have moved away from defining boards in this way (a board is now more of a collection of separately defined columns) this fits in less well (the main reason I moved to a board being a collection of separate columns was for easy tracking of their order for drag and drop). I can still think of ways of doing this, but they are all a bit more awkward than they were, both conceptually and in implementation - hah, progress! Before this change, there were some aspects I never bottomed out, like what to do if a tag/subtag combination is removed from the vault (because all lines with it on are deleted), should I remove the column from the board. Should I only look at tasks when picking the tag/sub-tag combinations or should I look at the complete vault? I am definitely still mulling this over! |
Beta Was this translation helpful? Give feedback.
-
This feature would automatically create a column in the tagboard named after the marked section in the nested tag. It would also allow for a negative prompt to specify tags that should not auto-generate lists in the tagboard.
The proposed settings naming scheme for automatic population:
These settings would create columns for any nested tags with the parent tag
#parent-tag/...
but not the tag#parent-tag/ignored-tag
or the tag#parent-tag
without nesting.Using these settings, the tag
#parent-tag/suggestions
would create the columnsuggestions
but the tag#parent-tag/ignored-tag
would not create a column.For reference this is the official naming scheme for tags:
Beta Was this translation helpful? Give feedback.
All reactions