to move all [or as selected by date specifier] from completed.data to (append to) archive.data file.
this command ties into
PROPOSED NEW ID# HANDLING BEHAVIOR;
ID#s should remain static, and not be recycled until either "purge" command, or until the ID number is forced to add another digit.
That is to say that on rollover from 99 to 100, users should be prompted to purge and thereby recycle available ID#s, which are otherwise static. Same thing as ID#s threaten to roll over from 999 to 1000.
As task IDs roll over from 9999 to 10000, balloons and pidgins should be released, and a marching band should play outside your house.
This way task IDs can remain static for a longer time.
David Patrick on 2009-06-22T12:32:02Z says:
task purge [# | date | dateref]
to move all [or as selected by date specifier] from completed.data to (append to) archive.data file.
this command ties into PROPOSED NEW ID# HANDLING BEHAVIOR; ID#s should remain static, and not be recycled until either "purge" command, or until the ID number is forced to add another digit. That is to say that on rollover from 99 to 100, users should be prompted to purge and thereby recycle available ID#s, which are otherwise static. Same thing as ID#s threaten to roll over from 999 to 1000. As task IDs roll over from 9999 to 10000, balloons and pidgins should be released, and a marching band should play outside your house.
This way task IDs can remain static for a longer time.