From: Carsten Dominik <dominik@science.uva.nl>
To: Nicholas S-A <novanasa@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Remind functionality?
Date: Mon, 26 Jan 2009 05:36:55 +0100 [thread overview]
Message-ID: <3DC0ACEE-62AB-47FE-A680-9227E3EDCB06@uva.nl> (raw)
In-Reply-To: <20090125233219.GA2288@Edwards.local>
On Jan 26, 2009, at 12:32 AM, Nicholas S-A wrote:
> Hi,
>
> * Carsten Dominik <dominik@science.uva.nl> [2009-01-25 22:17:16
> +0100]:
>
>> It is unlikely that this can be make faster in a significant way.
>> Why is it a problem???? Even if it takes 10 seconds?
>> Ah, I see, you do this in every new shell?????? This sounds
>> unnecessary, to say the least.
>> Maybe you have to explain better what exactly your are doing....
>
> So, the way I currently use remind is run it as "remind ~/.remind"
> in my
> .bash_profile. It reminds me of deadlines and events at any login
> shell,
> so that I don't forget about them (and also so they are fast to
> access).
> This works well, as it is quick to load and doesn't contribute
> significantly to the login time at e.g. a Terminal window or SSH
> connection. The problem comes because I now use org-mode agenda to
> schedule everything, so I have to enter upcoming events twice --
> once in
> my agenda files, and once in ~/.remind. As such, I thought I could
> improve my workflow by just printing the emacs agenda instead of
> running
> remind -- but this is slow. I also tried with emacsclient, but that
> didn't improve it any.
A work-around would be to use a cronjob to dump the the agenda output
to a file, maybe once a minute or even once every hour, and then to
cat this file into your shells.
- Carsten
next prev parent reply other threads:[~2009-01-26 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 16:36 Remind functionality? Nicholas S-A
2009-01-25 21:17 ` Carsten Dominik
2009-01-25 23:32 ` Nicholas S-A
2009-01-26 4:36 ` Carsten Dominik [this message]
2009-01-26 18:14 ` Oliver Charles
2009-01-26 8:31 ` Taru Karttunen
2009-01-26 16:37 ` Nicholas S-A
2009-01-27 11:27 ` Daniel Clemente
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=3DC0ACEE-62AB-47FE-A680-9227E3EDCB06@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=novanasa@gmail.com \
/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).