From: Carsten Dominik <carsten.dominik@gmail.com>
To: throaway@yahoo.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Recurring items NEVER show up in timeline unaccompanied
Date: Mon, 28 Mar 2011 19:05:27 +0200 [thread overview]
Message-ID: <4D680B7A-9723-415B-9AD2-119A3CE61FCD@gmail.com> (raw)
In-Reply-To: <op.vsuyyibvzpgdil@hermione2008.sd.cox.net>
On 24.3.2011, at 18:31, Mark S wrote:
> Hello Carsten et al,
>
> --- On Thu, 3/24/11, Carsten Dominik <carsten.dominik@gmail.com> wrote:
>
>> 1. Be satisfied with the way things are, just realize
>> that repeaters only show up on the first date when
>> the event happens for the first time.
>
> This would mean that you could never *trust* the
> timeline when dealing with events more than a week or
> two out. You would always have that lingering worry
> that you forgot to bump one of the repeaters.
>
>> 2. Use the agenda, restricted to a single file, for a
>> time range you specify. This has the advantage
>> that also diary sexps will work properly - the
>> timeline currently has no way to deal with these.
>
> This would be great if there were a "sparse"
> agenda. There isn't a way to make the agenda not show
> empty days is there? As it is, if you make an agenda
> extending out a year, you will have to wade through
> several hundred lines worth of empty days.
>
>> 3. Change the section of the timeline code that
>> produces the list of interesting dates.
>
> That seems like a good solution. Is it difficult?
>
>> 4. Define a variable that will make the timeline
>> always look at *every* date in the range covered
>> by the file. And live with the fact that
>> constructing the view might take long. Maybe it
>> will not even to terribly long if you really use
>> this view for single projects. This would be easy
>> to implement.
>
> This would work too, I think. Creating an agenda that
> goes out one year only took about 3 seconds on my
> not-state-of-the-art machine. Presumably the timeline
> would be faster, since it wouldn't produce all the
> extra gap lines.
>
> Actually, when I tried to make a year long agenda using
> v-y I spent just about as much getting past the "are
> you sure" screens as it took to build the agenda.
>
> The ideal solution would be that the Timeline view
> would process dates exactly like the agenda, including
> multiple-files, but display them like the traditional
> timeline, with ranges of dates omitted.
This is already possible, by binding the variable
org-agenda-show-all-dates to nil around the call to make
the agenda (for examples using the options section of a
custom agenda command). So the only missing piece for
your preferred solution is the determination of starting
dates and end date in a useful and automatic way. Maybe
I can take a look some time this week and see if
there is a simple way to replace the time line with
something better.
- Carsten
>
> Mark
>
next prev parent reply other threads:[~2011-03-28 17:05 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
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 [this message]
-- 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=4D680B7A-9723-415B-9AD2-119A3CE61FCD@gmail.com \
--to=carsten.dominik@gmail.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).