Merge branch 'doc' into third-time

This commit is contained in:
contrapunctus 2022-02-13 02:54:26 +05:30
commit a8f213bbd2
1 changed files with 8 additions and 5 deletions

View File

@ -866,10 +866,11 @@ Records not used for time tracking, but to store data associated with a date or
[<keyword-value pair>] ...)
#+END_SRC
** tagging dates with key-values :feature:
** STARTED tagging dates with key-values :feature:
:PROPERTIES:
:CREATED: 2022-02-10T22:59:45+0530
:CUSTOM_ID: date-key-values
:branch: date-properties
:END:
Straightforward enough for the plist group backend -
#+BEGIN_SRC elisp
@ -910,6 +911,7 @@ The plist backend could theoretically be extended to support it, but I'd rather
* STARTED Support for the Third Time System [57%] :extension:
:PROPERTIES:
:CREATED: 2022-02-10T14:12:12+0530
:branch: third-time
:END:
[[https://www.lesswrong.com/posts/RWu8eZqbwgB9zaerh/third-time-a-better-way-to-work][Third Time: a better way to work]]
#+BEGIN_QUOTE
@ -933,10 +935,11 @@ Additional rules:
3. [X] on clock out, increment =break-time= and start timed notification
4. [X] on clock in, calculate duration of latest break (duration between last =:stop= and now), and subtract it from =break-time=; if the resulting time is negative, set it to zero.
5. [ ] "big break" command - user enters a time, for which we set an alarm. User must resume working around that time.
6. [ ] define work hours?
* As a custom variable - this is easy to implement, but cannot vary over time without affecting (the interpretation of) past data.
* [[#date-key-values][Key values associated with a day?]] The user could define the default in a custom variable.
7. [ ] displaying/recording breaks. Probably done implicitly - when work hours are defined, any time not spent working can be interpreted as break time.
6. [ ] Define work hours
* [ ] Custom variable for default work hours.
* [ ] Hook function which inserts default work hours.
* [ ] Hook function which prompts for work hours whenever you first clock in on a date. If work hours are defined in the custom variable, ask whether to use them - on negative answer, prompt for today's work hours. If work hours are not defined, prompt for today's work hours.
7. [ ] Displaying/recording breaks. Probably done implicitly - when work hours are defined, any time not spent working can be interpreted as break time.
Extras
1. persist =break-time= between Emacs sessions