From: jorge.alfaro-murillo@yale.edu (Jorge A. Alfaro-Murillo)
To: emacs-orgmode@gnu.org
Subject: Re: Best practices to get reminders?
Date: Mon, 06 Apr 2015 23:06:49 -0400 [thread overview]
Message-ID: <87a8ykiqly.fsf@yale.edu> (raw)
In-Reply-To: 87wq1o8xac.fsf@vostro.rath.org
Nikolaus Rath writes:
> 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?
You can put this after your org-agenda-files configuration in your
.emacs:
#+BEGIN_SRC emacs-lisp
(appt-activate 1)
(org-agenda-to-appt)
#+END_SRC
Then you will be reminded of things in your org files, before the
appointment time (I think 12 min is the default).
You could also add this, so that the appointments refresh and new
get added every time that you call the agenda:
#+BEGIN_SRC emacs-lisp
(add-hook 'org-agenda-finalize-hook (lambda ()
(org-agenda-to-appt t)))
#+END_SRC
Best,
--
Jorge.
next prev parent reply other threads:[~2015-04-07 3:07 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 [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8ykiqly.fsf@yale.edu \
--to=jorge.alfaro-murillo@yale.edu \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.