emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nikolaus Rath <Nikolaus@rath.org>
To: emacs-orgmode@gnu.org
Subject: Best practices to get reminders?
Date: Mon, 06 Apr 2015 19:52:43 -0700	[thread overview]
Message-ID: <87wq1o8xac.fsf@vostro.rath.org> (raw)


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?

GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

             reply	other threads:[~2015-04-07  2:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07  2:52 Nikolaus Rath [this message]
2015-04-07  3:06 ` Best practices to get reminders? 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
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

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=87wq1o8xac.fsf@vostro.rath.org \
    --to=nikolaus@rath.org \
    --cc=emacs-orgmode@gnu.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).