From: cesar mena <cmena@pobox.com>
To: emacs-orgmode@gnu.org
Subject: org-agenda-scheduled-leaders and repeating tasks
Date: Tue, 13 Oct 2015 18:01:31 -0400 [thread overview]
Message-ID: <CAL+-AofR3rk0AQbnO5V_GJJ8p_y0NJa=KW+TVJ3-E3pGXBt26w@mail.gmail.com> (raw)
hello everyone,
i think what i am trying to say is best shown with an example.
so let's say that today is oct 13th.
the task
** TODO check smoke alarm
SCHEDULED: <2015-10-04 Sun .+10d>
shows up in the agenda as:
Sched.10x: TODO check smoke alarm
however, had the task been scheduled a day before (or if today was oct 14th):
** TODO check smoke alarm
SCHEDULED: <2015-10-03 Sat .+10d>
it would show up in the agenda as:
Scheduled: TODO check smoke alarm
that is to say, the marker that indicates it is overdue is gone. for
some cases, like checking the smoke alarm, i don't want the "Sched.?x"
to reset.
ie, Sched.11x: TODO check smoke alarm
i tracked this down to the function org-time-string-to-absolute. when
rendering the agenda it gets called with today as its DAYNR argument,
which causes "org-closest-date" to return "today" for the case of
repeating timestamps.
i can understand why it is done this way, and i find it useful.
however for some tasks, i'd rather the counter not reset lest i miss
something for longer than i should have (the smoke alarm case for
example).
i patched my version of org to do this (release_8.2.10); but i did it
by not calling org-closest-date in the case of repeating timestamps
with the effect they all act this way. to do this properly i'd imagine
we would need another identifier in the timestamp(?)
i am willing to do the work to contribute the proper patches and
update the doc if people are interested.
... or is there another way of doing this? :)
thank you kindly for reading!
- cesar
next reply other threads:[~2015-10-13 22:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 22:01 cesar mena [this message]
2015-10-16 16:25 ` org-agenda-scheduled-leaders and repeating tasks Nicolas Goaziou
2015-10-16 22:24 ` cesar mena
2015-10-17 7:25 ` Nicolas Goaziou
2015-10-21 14:20 ` Matt Lundin
2015-10-25 16:19 ` Nicolas Goaziou
2015-10-25 17:24 ` Nicolas Goaziou
2015-10-26 13:13 ` cesar mena
2015-10-26 19:56 ` cesar mena
2015-10-26 20:23 ` Samuel Wales
2015-10-26 20:31 ` cesar mena
2015-10-26 20:49 ` Nicolas Goaziou
2015-10-26 20:31 ` Nicolas Goaziou
2015-10-26 20:43 ` cesar mena
2015-10-27 4:25 ` Samuel Wales
2015-10-28 1:32 ` Matt Lundin
2015-10-28 13:52 ` Nicolas Goaziou
2015-10-29 16:46 ` cesar mena
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL+-AofR3rk0AQbnO5V_GJJ8p_y0NJa=KW+TVJ3-E3pGXBt26w@mail.gmail.com' \
--to=cmena@pobox.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.