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: Wed, 23 Mar 2011 14:56:02 -0400 [thread overview]
Message-ID: <3351.1300906562@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from "Mark S" <throaway@yahoo.com> of "Wed, 23 Mar 2011 10:02:41 -0800." <op.vss5qrwazpgdil@hermione2008.sd.cox.net>
Mark S <throaway@yahoo.com> wrote:
>
> Lisp tends to bring out my inner dyslexic, but is it possible to use
> a "while" or other construct instead of "mapcar" and then make the
> "if" construction inside of the lambda check for the :omitted symbol
> and return it as nil? And it would need to break out of the loop as
> soon as it encountered a date equal or greater to the present.
>
> Philosophically, the way I think the calendar should work for
> recurring events is that they only occur until the last event in the
> calendar UNLESS an argument has been given to specify how far out the
> calendar is to be drawn OR there is a global end-date / end-range
> variable.
>
The bug is indeed easy to fix. What's harder is to figure out how things
*should* work as you point out:
o where should it start? should the timeline include past dates by
default? when the user says so? should it *ever* include past dates?
o where should it stop? The last explicit entry is one possibility,
user-input is another (but this would require changes to the user
interface), a time limit specified by the user in some configuration
variable is a third.
The more one looks at these things, the more one marvels at the choices
that Carsten and Bastien and Nicolas and the Babel developers (and on and
on) have made: getting things so that they work *just* right most of the
time and providing enough flexibility to cover most of the remaining
cases is hard work.
Nick
next prev parent reply other threads:[~2011-03-23 18:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 18:02 Bug: Recurring items NEVER show up in timeline unaccompanied Mark S
2011-03-23 18:56 ` Nick Dokos [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-29 21:59 Mark S
2011-03-29 17:38 Mark S
2011-03-29 17:50 ` Carsten Dominik
2011-03-14 19:02 Recurring items don't always show up in timeline Mark S
2011-03-14 22:55 ` Mark S
2011-03-18 19:58 ` Bug: " Mark S
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
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
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=3351.1300906562@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).