emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matthew Lundin <mdl@imapmail.org>
To: Ian Barton <lists@manor-farm.org>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Keeping Your Appointments in org
Date: Thu, 08 Jan 2009 07:52:53 -0600	[thread overview]
Message-ID: <m2wsd59a6i.fsf@fastmail.fm> (raw)
In-Reply-To: <4965C946.7050805@manor-farm.org> (Ian Barton's message of "Thu\, 08 Jan 2009 09\:37\:10 +0000")

Hi Ian,

Ian Barton <lists@manor-farm.org> writes:
> Searching back through the list there are quite a lot of snippets
> describing how people use org to keep appointments, but no overview. I
> would like to write a tutorial on how you can keep your appointments
> in org, so I thought that I would ask list members if they would post
> some details of their system.

In the past I've used the Emacs diary, which integrates quite nicely
into the agenda views. It's really easy to add entries to the diary
from the agenda by typing "i". And the format for basic diary entries
is very simple, e.g.:

Jan 8, 2009 6:00pm Go for a walk

But recently, I've begun entering all my diary entries into org-mode
files because (a) it makes it very easy to put scheduling directly in
my project plans (b) org-mode supports complex diary expressions
within org files and (c) it's nice to add notes to scheduled events.
And, of course, org-modes active timestamps are also very easy.

Generally, I maintain a distinction between scheduled tasks and
appointments. For tasks I add a SCHEDULE or DEADLINE date. For the
appointments I add a simple timestamp, as in:

* Go for a walk <2009-01-08 Thu 18:00>


* 6:00pm Go for a walk <2009-01-08 Thu>
> I am intending to keep my appointments in a dedicated org file
> (calendar.org). 

Since the agenda's so powerful I just leave my appointment entries
scattered among several files - i.e., in their relevant context by

> At the moment I am using a remember template which adds them with a
> tag of APPT. I the use a custom agenda view if I only want to see
> appointments.

I do the same---i.e., use a custom agenda view to see only
appointments. In case it's of interest to anyone, here's the command I
use to view a weekly calendar consisting only of appointments.

(setq org-agenda-custom-command s
	'(("c" "Weekly schedule" agenda ""
	   ((org-agenda-ndays 7)
	    (org-agenda-start-on-weekday 1)
	    (org-agenda-repeating-timestamp-show-all t)
	    (org-agenda-skip-function '(org-agenda-skip-entry-if 'deadline 'scheduled))))
          ;; other commands here

> I am particularly interested in the best way to deal with repeating
> appointments. For example how do you deal with a weekly appointment
> that has a defined start and end date.

I use a diary S-expression within org-mode for this:

** My weekly event 7:00pm
<%%(and (= 2 (calendar-day-of-week date)) (diary-block 1 6 2009 4 4 2009))>

This event shows up in the agenda at 19:00 hours every Tuesday between
January 6 and April 4 of 2009.

I look forward to reading your tutorial on scheduling.


      parent reply	other threads:[~2009-01-08 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08  9:37 Keeping Your Appointments in org Ian Barton
2009-01-08 10:47 ` Daniel Martins
2009-01-08 22:33   ` Shelagh Manton
2009-01-08 13:52 ` Matthew Lundin [this message]

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:

  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=m2wsd59a6i.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=lists@manor-farm.org \


* 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


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).