Khalid Rafi <[email protected]> writes: > But, one can have a case as simple as: > #+begin_example > * TODO read 20 pages of the book [10/20] > #+end_example
This feels not reliable because one may later add a checkbox or subheadings. Then, whatever information is stored in the cookie will be lost by auto-updates. > If this is impossible, we would need: > #+begin_example > * TODO read book [10/20] > ** DONE read 20 pages > :PROPERTIES: > :COOKIE_COUNT: 10 > :COOKIE_COUNT_MAX: 20 > :END: > #+end_example > > We are modifying the cookie via the properties COOKIE_COUNT and > COOKIE_COUNT_MAX. If a certain entry with cookie has no subheading and > contains those properties, we can additionally use that to calculate the > cookie. Then, if changing the cookie [/] values by hand and doing C-c C-c (or > org-shiftup) could modify those properties, this might work. The idea is > similar to LOGBOOK. An alternative idea could be merging the two properties into one :COOKIE_COUNT: [10/20] Yet another possibility would be having a new cookie type like [!10/20] to guard it against updates. But that may get complex I am afraid. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
