From: Steven L Baur <steve@aol.com>
Subject: Re: Feature wish Red Gnus
Date: 18 Jul 1996 16:46:52 -0700 [thread overview]
Message-ID: <m23f2p15w3.fsf@deanna.miranova.com> (raw)
In-Reply-To: Paul Stodghill's message of 18 Jul 1996 19:16:10 -0400
>>>>> "Kai" == Kai Grossjohann <grossjoh@ls6.informatik.uni-dortmund.de>
Kai> I wish there was a way to tell Gnus, while the message is being
Kai> composed, that the Gcc'd copy should come up ticked or read
Kai> immediately ...
>>>>> "Han" == Han Pilmeyer <han@uto.dec.com> writes:
Han> I think I agree with Kai.
>>>>> "Paul" == Paul Stodghill <stodghil@CS.Cornell.EDU>
Paul> I too would find this functionality useful.
Me too.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.
next prev parent reply other threads:[~1996-07-18 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-18 13:03 Kai Grossjohann
1996-07-18 20:27 ` Lars Magne Ingebrigtsen
1996-07-18 21:01 ` Han Pilmeyer
1996-07-18 23:16 ` Paul Stodghill
1996-07-18 23:46 ` Steven L Baur [this message]
1996-07-19 6:53 ` Mark Eichin
1996-07-19 7:21 ` Kai Grossjohann
1996-07-19 8:42 ` Jens Lautenbacher
1996-07-19 22:10 ` Lars Magne Ingebrigtsen
1996-07-19 6:22 ` Kai Grossjohann
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=m23f2p15w3.fsf@deanna.miranova.com \
--to=steve@aol.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.
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).