Hi, I’m a new convert to Dynalist from Workflowy. Just started tripping over some tag problems.
I have lots of lists where the first word is both a tag and bolded: **@Tag** fails to be a tag at all! Actually all bolded tags are not tags. I was wondering why tags and locations i knew were missing. It seems straightforward to not count * and _ (for italics) in making tags.
Steps to reproduce (3 different ways)
Select a tag in an item and cmd-B bold it: #oldtag → **#oldtag**
Create a new tag bold or italics: **#newtag1** __newtag2__
Put a tag in parentheses: #ptag → (#ptag)
Expected result
working bolded #oldtag
working #newtag1newtag2
working (#ptag)
Actual result
#oldtag isn’t a tag anymore!
#newtag1newtag2 aren’t tags anymore!
(#ptag) isn’t a tag anymore!
In all of these cases, the # is there but it no longer functions as a tag. Doesn’t show up in autocomplete, tag window, or when searched for.
As an academic writer who uses references a lot, i often have `(#ref-Kuhn2014, #ref-Kuhn2016)’ since these both link me to my notes on that reference, and can later be replaced with actual references. But now the first one isn’t even a tag, and the second one includes the parentheses. Is there any solution?
1 & 2 Fixed: Tags that are bolded or italics are now properly tags
Not fixed: Tags interact inconsistently with other punctuation:
3.1 Leading parentheses for a tag (#tag fails to be a tag at all
3.2 Trailing parentheses for a tag #paren) become part of the tag = #paren) not #paren
3.3 Trailing commas are not part of tag #comma, => tag is #comma
3.4 Trailing periods are part of tag #period. => tag is #period. not #period
3.5 Trailing colon is not part of tag #colon: => tag is #colon
3.6 Trailing exclamation point is part tag of #exclaim! => tag is #exclaim! not #exclaim
See the png summary of the problem, only bold and italics have been fixed. Copy and paste the above list into dynalist to see behavior
I see, thanks for the feedback! We’ll work on the others.
One thing though, we’re not sure if colons can be isolated from the tag at the moment, given that Powerpack relies on it for sorting purposes. Hopefully we’ll figure out a way to reconcile the two.
Actually, the colon has a specific behavior that is consistent and i think the example to follow. It is only part of a tag if it is immediately followed by another character. I think that behavior is fine and could work for all punctuation, and would solve a lot of these problems. The rule should be that trailing punctuation is not part of tag, but embedded punctuation is part of tag. Exception is that parentheses are never part of tag (tags can begin after ( and end before ) so (#this) is seen as the tag #this
i think this preserves Powerpack as intended (which only has embedded : in tags)
Currently colons behave the following way which is correct. The other punctuation like ,.!|; should all behave similarly! and therefore should be easy to implement.
#s:one => tag is #s:one #s: => tag is #s not #s: #s:: => tag is #s: (only one colon) #s::h => tag is #s::h