Probably a good idea, but not worth keeping a task around for.
Wed, Feb 20
This is probably a natural feature if we iterate here, but not worth keeping a task around for.
We have no customer interest in this and no current plans to pursue it.
Looks good to me. I'll see about getting random_bytes and random_int into the builtins map to fix that lint thing.
Can you take a quick look at this with the added UI changes?
Update unarchive, add code to daemon console to use this new data.
I think it's fine to let dateModified update to the current time -- you're technically modifying the thing.
I'm looking at these storage/backend changes:
Presuming resolved by D19748 since we don't have an actual reproduction case.
D20196 removes this code.
I think it had some white-space removed from its end.
After D20194, expansion of tabs now uses the correct rule (expand tabs to the next tabstop) instead of the old rule (hard-coded replacement with a fixed number of spaces).
There are probably still a few remaining kinks to work out here, but I believe this is substantially resolved: