emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: throaway@yahoo.com
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Bug: Recurring items NEVER show up in timeline unaccompanied
Date: Tue, 22 Mar 2011 16:10:55 -0400	[thread overview]
Message-ID: <3965.1300824655@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from Nick Dokos <nicholas.dokos@hp.com> of "Tue, 22 Mar 2011 14:59:18 EDT." <3491.1300820358@alphaville.usa.hp.com>

Some more comments and another bug in org-timeline:

o a repeater always gets reported on its initial date - it only gets reported
  on subsequent instances iff it coincides with some other entry that will be
  reported on that date.

o the initial comment of org-timeline says "Only entries with a time
  stamp of today or later will be listed." However, in the let*, we have
    (let* ((dopast t)
           ...
  so by default we get past dates as well.

o [the additional bug] if dopast is set to nil in the let*, then we run the
  following code to get rid of past dates:

    (if (not dopast)
	;; Remove past dates from the list of dates.
	(setq day-numbers (delq nil (mapcar (lambda(x)
					      (if (>= x today) x nil))
					    day-numbers))))

  But day-numbers isn't just numbers: it's a list of day numbers
  interspersed with gap information:

   (733451 (:omitted . 28) 733479 (:omitted . 5) 733484 (:omitted . 21) 733505 (:omitted . 15) 733520 ...)
  and the mapcar function chokes when it has to deal with a gap argument.


Since there is no way to set dopast from the outside, perhaps the thing
to do is to remove both it and the above code (as well as one additional
instance of the variable) and declare that org-timeline will always do
both past and future. Or, given some global option variable, it can be
set to that value, in which case the code above needs to be fixed to
deal with the gaps.

Also, some stopping point will need to be provided. Right now, that is
the last explicit date in the file, but in the presence of repeaters
(and assuming that org-timeline gets modified to deal with them), that
natural stopping point gets pushed all the way to infinity, so some
other way will need to be provided to stop the enumeration.

Comments?

Nick

  

  reply	other threads:[~2011-03-22 20:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 19:02 Recurring items don't always show up in timeline Mark S
2011-03-14 20:36 ` Chris Randle
2011-03-14 22:36 ` Mark S
2011-03-15 15:39   ` Chris Randle
2011-03-14 22:55 ` Mark S
2011-03-14 23:29   ` Nick Dokos
2011-03-15 15:57   ` Chris Randle
2011-03-15 16:59     ` Nick Dokos
2011-03-15 18:17       ` Chris Randle
2011-03-15 17:34   ` Mark S
2011-03-15 18:20     ` Chris Randle
2011-03-16 17:06   ` Mark S
2011-03-18 19:58   ` Bug: " Mark S
2011-03-18 21:20     ` Nick Dokos
2011-03-19 17:45       ` Chris Randle
2011-03-19 18:46         ` Nick Dokos
2011-03-22 18:43     ` Bug: Recurring items NEVER show up in timeline unaccompanied Mark S
2011-03-22 18:59       ` Nick Dokos
2011-03-22 20:10         ` Nick Dokos [this message]
2011-03-24  7:08           ` Carsten Dominik
2011-03-24 18:40             ` Nick Dokos
2011-03-24 17:31       ` Mark S
2011-03-28 17:05         ` Carsten Dominik
  -- strict thread matches above, loose matches on Subject: below --
2011-03-23 18:02 Mark S
2011-03-23 18:56 ` Nick Dokos
2011-03-29 17:38 Mark S
2011-03-29 17:50 ` Carsten Dominik
2011-03-29 21:59 Mark S

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=3965.1300824655@alphaville.usa.hp.com \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=throaway@yahoo.com \
    /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 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).