From: "Juraj Kubelka" <Juraj.Kubelka@email.cz>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: (BUG?) Problem with proper time frame in agenda.
Date: Tue, 8 Aug 2006 16:08:00 +0200 [thread overview]
Message-ID: <f54511ec0608080708n2d3db8c7g66be872320759bd5@mail.gmail.com> (raw)
In-Reply-To: <40e94bde2da43c1e6b30f500c72d2d10@science.uva.nl>
On 8/8/06, Carsten Dominik <dominik@science.uva.nl> wrote:
>
> On Aug 8, 2006, at 12:26, Juraj Kubelka wrote:
>
> > Hi All!
> >
> > I have org file like example below. But some time stamps are not
> > correctly displayed (see example below) in agenda view (org-agenda). I
> > use emacs snapshot (22.0.51.1) and Org-mode version 4.43. Is it
> > Org-mode bug or just my mistake?
> > + <2006-08-11 Pá 09:16>--<2006-08-12 So 13:20>
> > - doesn't work: there is "2006-08-11 13:20" in agenda.
>
> This is a bug in parsing, when looking for a time it just takes one,
> not checking if this is a range. I'll see if I can do something,
> probably removing the time-of-day display for ranges entirely.
...or be sure it always takes the right one. In some cases it does.
>
> > + <2006-08-14 Po 10:08>--<2006-08-16 St 11:20>
> > - doesn't work: it is not displayed in agenda.
>
> The agenda assumes that there is only one agenda-relevant time stamp or
> range associated with any headline in the buffer. When it has found
> one, it jumps to the next headline, skipping anything in between, to
> speed up parsing. That's why each time you have several stamps or
> ranges, only the first is taken seriously. Hmmm. need to think about
> this, what the right course of action would be. Comments welcome.
Thanks for your explanation. For me would be more useful to have this
possibility. Example:
1. An activity has two parts: one from Monday to Tuesday, second from
Thursday to Saturday... or more parts. (an course)
2. I have several possibilities for the same activity, but I want to
decide later according to other activities.
+ better to have all possibilities in agenda. Then I can look for collisions.
+ maybe have possibility to say this timestamp is not important (will
not be in agenda view). But it is likely better just remove <>
characters around.
3. Kick off meeting notes:
======
** kick off meeting
+ early ideas
1. something
+ I have to ask John no late then DEADLINE: <2006-08-11 Fr>.
2. something2
+ i will prepare it tomorrow SCHEDULE: <2006-08-09 We>.
3. something3
+ ........... <2006-08-14 Mo>
....
======
Of course all examples can be (re)written by headlines. But org file
without these restrictions can be more powerful. I don't have to
rewrite my notes from meeting just because of org mode limitations.
Thanks.
Juraj
next prev parent reply other threads:[~2006-08-08 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 10:26 (BUG?) Problem with proper time frame in agenda Juraj Kubelka
2006-08-08 11:29 ` Carsten Dominik
2006-08-08 14:08 ` Juraj Kubelka [this message]
2006-08-08 14:06 ` 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=f54511ec0608080708n2d3db8c7g66be872320759bd5@mail.gmail.com \
--to=juraj.kubelka@email.cz \
--cc=dominik@science.uva.nl \
--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 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).