From: Stefan Kamphausen <skampi@gmx.net>
To: emacs-orgmode@gnu.org
Subject: Re: Ringing the alarm bell in orgmode
Date: Tue, 06 Nov 2007 09:48:11 +0100 [thread overview]
Message-ID: <85abpriwtw.fsf@usenet.my.skamphausen.de> (raw)
In-Reply-To: <u3avjvl2d.fsf@uni-konstanz.de> (Uwe Jochum's message of "Tue\, 06 Nov 2007 09\:23\:54 +0100")
Hi Uwe,
"Uwe Jochum" <uwe.jochum@uni-konstanz.de> writes:
> Hi all,
>
> using entries in my diary file I get an alarm bell ten minutes before a
> meeting or an appointment. That's useful.
and should be more flexible...
> But indeed orgmode is much more flexible
:-)
> for dealing with appointments and scheduled items, so I
> wanted to do more time management in orgmode. But I cannot figure out
> how to set an alarm bell in Emacs for scheduled stuff in orgmode. I
> tried to do it by integrating my orgmode file in the diary file (see
> orgmode FAQ, sec. 9), but that doesn't work (and it is not recommended
> by Carsten). So is there any other way to get the notification mechanism
> to co-operate with orgmode?
And what is more: you need to rely on Emacs running. OK, since I read
EMails with Gnus Emacs /is/ always running, but nevertheless. I
prefer my alarm bell being an informative reminder email.
Shouldn't it be possible to have a small elisp file which checks for
alarms to trigger in `org-agenda-files' and performs some reminder
action (like sending an email, ring the bell, start some external
application to create a popup ... whatever) if needed? This small
extra elisp file could then be called from cron using emacs --script
command line option (only available in Gnu Emacs 22 if I am not
mistaken but something similar could probably achieved using -l, -batch
or -f, etc) every -say- 5 minutes.
To find out whether an alarm has to be triggered there could be a
global option which then refers to the scheduled date-times but one
might also think about a syntax how to defined multiple reminders for
one todo item.
Being but a beginner with org this may be a stupid idea, but it
/sounds/ reasonable to me. I haven't started writing some elisp,
though. And of course this is slightly OT :-)
Best Regards
Stefan
--
Stefan Kamphausen --- http://www.skamphausen.de
a blessed +42 regexp of confusion (weapon in hand)
You hit. The format string crumbles and turns to dust.
next prev parent reply other threads:[~2007-11-06 8:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 8:23 Ringing the alarm bell in orgmode Uwe Jochum
2007-11-06 8:48 ` Stefan Kamphausen [this message]
2007-11-06 14:37 ` Bastien
2007-11-06 9:43 ` Bastien
2007-11-06 10:23 ` Uwe Jochum
2007-11-06 14:22 ` Bastien
2007-11-06 13:55 ` Richard G Riley
2007-11-06 15:41 ` Bastien
2007-11-06 15:16 ` William Henney
2007-11-06 15:34 ` Chris Leyon
2007-11-06 15:35 ` Richard G Riley
2007-11-06 16:43 ` Sivaram Neelakantan
2007-11-06 16:47 ` Bastien
2007-11-06 16:58 ` William Henney
[not found] ` <uzlxrfphs.fsf@uni-konstanz.de>
2007-11-06 15:31 ` Bastien
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
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=85abpriwtw.fsf@usenet.my.skamphausen.de \
--to=skampi@gmx.net \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).