From: Nikolaus Rath <Nikolaus@rath.org>
Subject: Re: Best practices to get reminders?
Date: Mon, 06 Apr 2015 21:16:15 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Carlos Sosa's message of "Mon, 06 Apr 2015 20:11:07 -0700")
On Apr 06 2015, Carlos Sosa <firstname.lastname@example.org> wrote:
> Nikolaus Rath <Nikolaus@rath.org> writes:
>> How do other people handle this? Is everyone else opening and working on
>> their org files daily so that this becomes a non-issue?
> Have you tried (org-agenda-to-appt) and (appt-activate t)?
> If you do end up using those functions, and you're using Emacs 24.x,
> checkout desktop notifications:
I am using Emacs 24, but I'm still not sure how how you are using
this. For example, if you'd like to get some reminder if a project is
due in 3 days, how exactly do you set things up?
Do you show the notification just once (but what if I'm not at the
screen what that happens)? Or do you show it periodically until I've
somehow told Emacs that I've seen it?
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.«
next prev parent reply other threads:[~2015-04-07 4:16 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 [this message]
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
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).