From: Eric Abrahamsen <firstname.lastname@example.org>
Subject: Re: Best practices to get reminders?
Date: Tue, 07 Apr 2015 12:09:36 +0800 [thread overview]
Message-ID: <email@example.com> (raw)
Nikolaus Rath <Nikolaus@rath.org> writes:
> I'm just starting to use org-mode. The first thing I'd like to use it
> for is to keep track of stuff that I need to do. Writing things up and
> calling up the agenda is easy enough, and I really like how-much
> functionality is available in what's essentially a plain text document.
> However, there's one thing where I feel lost. I don't expect to be
> editing my orgmode files on a daily basis (at least not yet), so how can
> I make sure that I don't miss an important deadline? It seems to me that
> it doesn't help much if instead of worrying to forget a deadline I now
> have to worry about forgetting to check my org-mode agenda...
> How do other people handle this? Is everyone else opening and working on
> their org files daily so that this becomes a non-issue?
At this point I have so much of my life (personal and professional) in
Org files that yes, checking the Agenda isn't an issue anymore. It's the
first thing I do in the morning, and the last thing I do before knocking
off at the end of the day.
If you're someone who restarts Emacs each morning, you could put a call
to `org-agenda' in your init file. The others have mentioned
`org-agenda-to-appt', but I find that if you're really using Org to
manage your time (checking where you are in the midst of longer
projects, clocking, surveying the week ahead, etc) then you'll want to
be looking at the Agenda every day.
next prev parent reply other threads:[~2015-04-07 4:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 2:52 Best practices to get reminders? Nikolaus Rath
2015-04-07 3:06 ` Jorge A. Alfaro-Murillo
2015-04-07 4:12 ` Nikolaus Rath
2015-04-07 4:28 ` Jorge A. Alfaro-Murillo
2015-04-07 3:11 ` Carlos Sosa
2015-04-07 4:16 ` Nikolaus Rath
2015-04-07 4:09 ` Eric Abrahamsen [this message]
2015-04-07 10:10 ` Marcin Borkowski
2015-04-08 9:55 ` Eric Abrahamsen
2015-04-08 17:11 ` Marcin Borkowski
2015-04-11 23:17 ` Manish
2015-04-12 1:53 ` Eric Abrahamsen
2015-04-07 14:19 ` Melleus
2015-04-07 15:15 ` Giuseppe Lipari
2015-04-07 15:27 ` Melleus
2015-04-13 18:12 ` Leo Ufimtsev
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 \
* 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).