emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Welle <mwe012008@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Managing appts with org-mode, diary
Date: Wed, 26 Jan 2011 13:17:01 +0100	[thread overview]
Message-ID: <tuf518x46f.ln2@news.c0t0d0s0.de> (raw)

Hello,

currently I create diary entries for my appointments, the appointments
are marked in the calendar. This is handy because if I want to create a
new appointment I can overview a three month period and I can see at a
glance which days are already blocked.

Now I want to manage my appointments in a more project centric
way. For instance I work at ten projects that have ten corresponding org
files. Now I note appointments for a certain project in the
corresponding org file. The appointments are still marked in my
calendar, but that is unusable slow. If I use the per month org agenda
view the display is way to confusing to get an overview and decide on
which day I can make a new appointment. 

How do you deal with this problem? I can imagine to generate a ~/.diary
file every time I add or change an appointment in org mode. This would
speed up the process of displaying the calendar. An agenda view that
shows a three month period or so and that has all the sub nodes of the
days hidden might help, too. Then days, that have already appointments,
are marked and you have to show the sub nodes if you need detailed
information about appointments of that day. Is somethind like that
already implemented and I haven't found it yet ;)? Any hints are welcome.


Regards
hmw

-- 
biff4emacsen - A biff-like tool for (X)Emacs
http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html
Flood - Your friendly network packet generator
http://www.c0t0d0s0.de/flood/flood.html

             reply	other threads:[~2011-01-26 12:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26 12:17 Michael Welle [this message]
2011-01-29 17:42 ` Managing appts with org-mode, diary Matt Lundin
2011-01-30  7:56   ` Michael Welle

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=tuf518x46f.ln2@news.c0t0d0s0.de \
    --to=mwe012008@gmx.net \
    --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).