From: wmperry@aventail.com (William M. Perry)
Cc: Alexandre Oliva <oliva@dcc.unicamp.br>,
Kai.Grossjohann@CS.Uni-Dortmund.DE, ding@gnus.org
Subject: Re: Manage todo items with Gnus
Date: 24 Feb 1999 10:42:20 -0500 [thread overview]
Message-ID: <86k8x7g65f.fsf@kramer.bp.aventail.com> (raw)
In-Reply-To: François Pinard's message of "23 Feb 1999 09:02:03 -0500"
François Pinard <pinard@iro.umontreal.ca> writes:
> "William M. Perry" <wmperry@aventail.com> écrit:
>
> > You could use automatic expiry so you never feel too far behind in your todo
> > list! I like it!
>
> A good laugh to start the day :-). Thanks!
>
> > You could also do less useful things, like eventually honor outlook schedule
> > requests from within gnus or something like that.
>
> By "eventually", you mean that the possibility does not exist, don't you?
Correct.
> Where I often work, I'm taking care of a little island of Unix systems
> plain lost in a sea of WinNT servers and stations, filling offices on
> every floor. Those Outlook schedule requests do fly around like hell,
> without touching me. I sometimes feel like the Christ walking over the
> water :-). Yet, if something exists in or around Gnus that would remove
> this supra-natural protection, I might try to lift it and see how quickly
> I will then drawn...
Some people at our office have started using exchange for scheduling, and
it is already annoying. My stance is typically to tell them to send me
something I can actually use. By just ignoring all those MS-Word files
that get sent around, I can get a lot more work done. :)
But it might be handy to deal with meeting requests from gnus or vm.
-Bill P.
next prev parent reply other threads:[~1999-02-24 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-14 22:27 Kai.Grossjohann
1999-02-17 12:03 ` Alexandre Oliva
1999-02-23 3:04 ` François Pinard
1999-02-23 13:03 ` William M. Perry
1999-02-23 14:02 ` François Pinard
1999-02-24 15:42 ` William M. Perry [this message]
1999-02-23 22:22 ` Alexandre Oliva
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=86k8x7g65f.fsf@kramer.bp.aventail.com \
--to=wmperry@aventail.com \
--cc=Kai.Grossjohann@CS.Uni-Dortmund.DE \
--cc=ding@gnus.org \
--cc=oliva@dcc.unicamp.br \
/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.
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 NNTP newsgroup(s).