From: Myles English <mylesenglish@gmail.com>
To: David Belohrad <david@belohrad.ch>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: timeline of tags
Date: Mon, 14 Oct 2013 21:46:30 +0100 [thread overview]
Message-ID: <87bo2rzil5.fsf@gmail.com> (raw)
In-Reply-To: <871u3n1xh5.fsf@pcbe13433.cern.ch>
Hi David,
david@belohrad.ch writes:
> Dear All,
>
> could someone help me with following problem?
>
> - have multiple org files, where I tag by names, e.g. @Erik
>
> - I want to construct a timeline of all items having this tag through
> all the org files (as @Erik can be dispersed everywhere)
>
> Example:
>
> I use tag @Erik to note at which times my son has school holidays. Hence
> one such entry would be e.g.:
>
> ** TODO erik autumn holidays :@Erik:
> :PROPERTIES:
> :ID: 26f5503f-3db6-481a-b384-395625e39333
> :END:
> <2013-10-17 Thu>--<2013-10-27 Sun>
>
> there are many entries like this. Now, my wife asks me: I wonder when
> Erik has holidays.
>
> I enter org-agenda, press 'm', type @Erik and voila - I get list of his
> holidays (and other stuff).
>
> Trouble is, that this list does not show it in timeline, but only
> headings without these dates. Hence to get each datum I have to _open_
> the item, which is not desired.
>
> Any hint how to solve it?
This is how I do something similar. Essentially you treat an
event/appointment differently to a task (TODO) and store it in the diary
file (with the help of a capture template) so it looks like this:
* 2013
** 2013-05-30 Thursday
**** Might go fishing :event:
<2013-06-22 Sat>--<2013-06-23 Sun> [2013-05-30 Thu 23:57]
and in the init file you have this:
;; not sure which of these are necessary:
(setq org-agenda-include-diary t)
(setq org-agenda-diary-file "~/org/org/diary.org")
;; so any time strings in the heading are shown in the agenda
(setq org-agenda-insert-diary-extract-time t)
(setq org-capture-templates (quote (
("a" " - Appointment (compulsory)" entry
(file+datetree (concat org-directory "/diary.org")) "* %? :appt:\n%^T %U %a")
("e" " - Event (optional)" entry
(file+datetree (concat org-directory "/diary.org")) "* %? :event:\n%^T %U %a"))))
(setq org-agenda-custom-commands
(quote (("v" "Events" agenda ""
((org-agenda-span 28)
(org-agenda-files '((concat org-directory "/diary.org")))))
If your diary.org has at the top:
#+FILETAGS: diary
Then a C-a v gives you:
Wednesday 19 June 2013
Thursday 20 June 2013
Friday 21 June 2013
Diary: 6:03...... Summer Solstice (BST)
Saturday 22 June 2013
diary: (1/2): Might go fishing :diary::event:
Sunday 23 June 2013
diary: (2/2): Might go fishing :diary::event:
Monday 24 June 2013 W26
Tuesday 25 June 2013
Wednesday 26 June 2013
Myles
next prev parent reply other threads:[~2013-10-14 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 19:08 timeline of tags David Belohrad
2013-10-14 20:46 ` Myles English [this message]
2013-10-16 9:36 ` David Belohrad
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=87bo2rzil5.fsf@gmail.com \
--to=mylesenglish@gmail.com \
--cc=david@belohrad.ch \
--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).