You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, setting tag descriptions is done by adding an entry such as tags.acme.description = Work done for ACME Inc. to the timewarrior.cfg file (either directly or through timew config).
This works great for all tags with simple names, but not for tags such as name-with-dashes or "name with spaces".
I propose allowing constructs such as:
tags."a non-obvious name, possibly with periods.in.the.middle".description = The description
At the moment, both the above and the simpler form tags.with-dash.description = Something fail silently (no error is reported, but timewarrior does not process any further config lines).
NOTE: My use case is with tag descriptions, but I believe this problem can be generalized for all config file definitions.
The text was updated successfully, but these errors were encountered:
Ran into this issue today. Created a couple of tags with dashes couple of weeks ago and had set descriptions. Noticed that the description did not show on timew tags but didn't think much about it until today. When setting an exclusion, couldn't figure out why it didn't show up in the summary charts. Went into the configuration and moved the exclusions above the descriptions, and exclusions started showing up.
Currently, setting tag descriptions is done by adding an entry such as
tags.acme.description = Work done for ACME Inc.
to thetimewarrior.cfg
file (either directly or throughtimew config
).This works great for all tags with simple names, but not for tags such as
name-with-dashes
or"name with spaces"
.I propose allowing constructs such as:
At the moment, both the above and the simpler form
tags.with-dash.description = Something
fail silently (no error is reported, but timewarrior does not process any further config lines).NOTE: My use case is with tag descriptions, but I believe this problem can be generalized for all config file definitions.
The text was updated successfully, but these errors were encountered: