From: Christopher Dimech <dimech@gmx.com>
To: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Time Slots in Org-Agenda
Date: Wed, 9 Dec 2020 20:50:29 +0100 [thread overview]
Message-ID: <trinity-90176603-cc66-4d77-b69a-e94c1519e268-1607543429101@3c-app-mailcom-bs11> (raw)
It would be good if the following org-agenda problem could be addressed.
Here is a section of a diary
Dec 05, 2020
06:13-08:34 Gnu Hackers Meeting
10:21-12:00 Richard Stallman Talk
12:00-12:34 Lunch
14:21-17:34 Hacking Session
This gives the following in Org-Agenda.
Saturday 5 December 2020
5:06...... now - - - - - - - - - - - - - - - - - - - - - - - - -
Diary: 7:55- 9:34 Gnu Hackers Meeting *
8:00...... ----------------
10:00...... ----------------
Diary: 10:21-12:00 Richard Stallman Talk
12:00...... ----------------
Diary: 12:00-12:34 Lunch
14:00...... ----------------
Diary: 14:21-17:34 Hacking Session *
16:00...... ----------------
18:00...... ----------------
20:00...... ----------------
Loking at the entries with a star, end later than the
next time thresholds of 08:00 and 16:00, yet the entries
are not being populated for the later times.
I would be grateful if the slots at the later times would
also be filled. For instance, according to the setup below
(see the ** entries)
Saturday 5 December 2020
5:06...... now - - - - - - - - - - - - - - - - - - - - - - - - -
Diary: 7:55- 8:00 Gnu Hackers Meeting **
8:00...... ----------------
Diary: 8:00- 9:34 Gnu Hackers Meeting **
10:00...... ----------------
Diary: 10:21-12:00 Richard Stallman Talk
12:00...... ----------------
Diary: 12:00-12:34 Lunch
14:00...... ----------------
Diary: 14:21-16:00 Hacking Session **
16:00...... ----------------
Diary: 17:00-17:34 Hacking Session **
18:00...... ----------------
20:00...... ----------------
next reply other threads:[~2020-12-09 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 19:50 Christopher Dimech [this message]
2020-12-10 19:31 ` Time Slots in Org-Agenda pietru
2020-12-11 4:59 ` steve-humphreys
2020-12-11 5:43 ` Ihor Radchenko
2020-12-11 6:35 ` steve-humphreys
2020-12-11 6:52 ` Ihor Radchenko
2020-12-11 7:18 ` steve-humphreys
2020-12-15 11:06 ` Tim Landscheidt
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=trinity-90176603-cc66-4d77-b69a-e94c1519e268-1607543429101@3c-app-mailcom-bs11 \
--to=dimech@gmx.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
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).