emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: James Harkins <jamshark70@qq.com>
To: emacs-orgmode@gnu.org
Subject: org-habit for multiple arbitrary days in a week
Date: Mon, 13 Oct 2014 14:11:41 +0800	[thread overview]
Message-ID: <87bnpgbisi.wl-jamshark70@qq.com> (raw)

I have a task that I want to track using org-habit. I've spent about an hour looking through the manual and other sites, but so far the problem remains intractable.

With org-habit, it's easy to track something that should be done on one particular day of the week: .+1w.

It appears not to be easy to track something that should be done on two arbitrary days of the week.

It's easy to schedule something for two specific days of the week using a sexp. But, org-habit (for sensible reasons) doesn't support sexps.

I can also add multiple SCHEDULED lines. But org-habit doesn't work well with this either.

** TODO Update lesson gradesheet					       :Comp:
   SCHEDULED: <2014-10-13 Mon +1w>
   SCHEDULED: <2014-10-17 Fri +1w>
   :PROPERTIES:
   :STYLE:    habit
   :LOGGING:  TODO MAYBE INPROG MTG | DONE(!) POSTPONED
   :END:

Now, if I mark this item DONE, org-habit moves *both* scheduled dates forward to next week, even though 10-17 is still in the future and it's neither needed nor desirable to advance it. That is, scheduled dates that are today or in the past should move up, while scheduled dates in the future should be left alone. I guess the issue with that would be that you couldn't set a task DONE earlier than scheduled. That's not an issue for this specific task, but maybe for others.

I suppose the worst case is that I could create two "Update lesson gradesheet" entries, but that seems highly inelegant...?

Thanks in advance for any advice.

hjh

next             reply	other threads:[~2014-10-13  6:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13  6:11 James Harkins [this message]
2014-10-13 15:56 ` org-habit for multiple arbitrary days in a week Nicolas Goaziou
2014-10-14  1:19   ` James Harkins

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bnpgbisi.wl-jamshark70@qq.com \
    --to=jamshark70@qq.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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).