Closed naringas closed 6 years ago
This is not easily done. From a discussion thread on the topic:
Hi, thanks Jan. That's an interesting suggestion and I've considered things along those lines, but I always get hung up on how to treat the archived tasks.
For instance, if you have a list with some hierarchy to it, say something like this:
- refactor sketchy js
- comments
- img upload
- char limiter
- dashboard chart
- build configs
- document flask blueprints
- img upload
- metrics dashboard
- logback config
Then, you a finish a couple of items:
- refactor sketchy js
- comments +- img upload +- char limiter
- dashboard chart
- build configs
- document flask stuff +- img upload +- metrics dashboard
- logback config
If they're simply moved to the bottom of the file, it will be tough to know what parent task an archived task was associated with. Trying to avoid a situation like this:
- refactor sketchy js
- comments
- dashboard chart
- build configs
document flask blueprints
- logback config
::Archive +- img upload +- char limiter +- img upload +- metrics dashboard
I think it would get worse as new things are added to the bottom because tasks that were previously associated would not be grouped together:
refactor sketchy js
- dashboard chart
- build configs
::Archive +- img upload +- char limiter +- img upload +- metrics dashboard +- comments +- document flask blueprints +- logback config
In the archive above, there are duplicate entries and tasks that were previously related (like "document flask blueprints" and "metrics dashboard") are not grouped anymore. I haven't thought of a way to add some kind of archiving and avoid this scenario. What do you think?
LMK if you have any suggestions for how to handle this type of situation...
Closing due to inactivity.
I tried to do it with
Find
and a regex^\t*+
but then I cannot easily delete multi-line tasks. Their comments stay there.