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
In the todo list, the order of inactive items seems confusing (#3). So I considered adding visual cues for them, such as gray backgrounds (ref). I once implemented this, but I gave up...
Its implementation is a bit tricky due to internal structure of existing code.
The visual cues need to suggest inactiveness obviously without explanations, but such cues are annoying when I actually want to browse inactive items.
I'd rather say "aim not to overmanage the exact order of items as it can be unnecessarily stressful and goes beyond what this tool is designed for".
I plan to publish a new version of the manual. It will have an extended chapter on Task Management. I expect that it will be finished within a maximum of one week. IMHO, there is no need for additional improvements from your end. The manual should be more comprehensive, considering the information you provided. So this work is on me :)
FYI, I'm planning to merge 632172c (time machine simulation of the todo list) into the master branch soon and make it available on MELPA, though this may be late for your revision.
I'm also testing an interactive simulation feature locally, using < and > keys to simulate the previous/next day. If it works successfully, I'll push it in a few days.
In the todo list, the order of inactive items seems confusing (#3). So I considered adding visual cues for them, such as gray backgrounds (ref). I once implemented this, but I gave up...
I'd rather say "aim not to overmanage the exact order of items as it can be unnecessarily stressful and goes beyond what this tool is designed for".
See also #4.
The text was updated successfully, but these errors were encountered: