emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Leo Ufimtsev <lufimtse@redhat.com>
To: Nikolaus Rath <Nikolaus@rath.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Best practices to get reminders?
Date: Mon, 13 Apr 2015 14:12:08 -0400 (EDT)	[thread overview]
Message-ID: <2081019172.12049946.1428948728431.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <87wq1o8xac.fsf@vostro.rath.org>

I haven't read all of the replies, but I use todochiku (cross platform) with some configs:

** Notification snystem
*** About
Get libnotify notifcations for  Org-dates. 
I.e anthying that is scheduled/has deadline or 
just has a <date time> stamp like: <2011-03-13 Fri 10:10>
Will generate a popup.

I have it set to not-time out. The reason is sometimes I go to get tea
and want to see the notifcation when I get back.

It works with repeating dates like < 2011-03-13 Fri 20:00 .+1d>
Note, while it works with org-habit, it doesn't work with
org-habit ranges in the repeat intervals, like: <2011-03-13 Fri 21:00 +1d/5d>
For such situations, add an extra time stamp with repeater.

*Required Packages:* 
 - appt [build-in]
 - todochiku     (I should remove this guy, generates an annoying popup).
*** Code
#+begin_src emacs-lisp
  ; Configure package requirements:
  (require 'appt)
  (require 'todochiku)

  ; Configure what goes into appt:
  (setq org-agenda-include-diary t)

  ;interval is bigger than warning time so that notification appears only once.
  (setq appt-display-interval 3)  
  (setq appt-message-warning-time 1)

  ; (setq appt-display-duration 100000000)  ;Seconds. ; NOTE: this doesn't override todochiku
  (setq todochiku-timeout 36000) ;in seconds. ~10 hours or till clicked-away.

  ; Refresh function.
  ; (called also by hooks below)
  ; This includes only entries on a given day. It doesn't schedule days in advance.
  (defun my/refresh-org-agenda-appts ()
    "Clear previous appt list and update it with new entries. Note this is per-day/on-the-day"
    (setq appt-time-msg-list nil)

  ;---- Refresh appoinments Under various situations.
  ; This is needed for proper scheduling.
  ; To check if your appointments were re-scheduled properly, 
  ; check the "appt-time-msg-list" variable.

  ; run when starting Emacs 

  ;  everyday at 12:05am
  (run-at-time "12:05am" (* 24 3600) 'my/refresh-org-agenda-appts)

  ; Upon reloading of agenda with 'r'
  (defadvice  org-agenda-redo (after org-agenda-redo-add-appts)
    "Pressing `r' on the agenda will also add appointments."
  (ad-activate 'org-agenda-redo) ;activate the advice. 

  ; Upon loading of agenda initially
  (add-hook 'org-finalize-agenda-hook 'my/refresh-org-agenda-appts)

Leo Ufimtsev | Intern Software Engineer @ Eclipse Team

----- Original Message -----
From: "Nikolaus Rath" <Nikolaus@rath.org>
To: emacs-orgmode@gnu.org
Sent: Monday, April 6, 2015 10:52:43 PM
Subject: [O] Best practices to get reminders?


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

      parent reply	other threads:[~2015-04-13 18:12 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
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 [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=2081019172.12049946.1428948728431.JavaMail.zimbra@redhat.com \
    --to=lufimtse@redhat.com \
    --cc=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).