From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: mail source is noisy
Date: 26 Feb 1999 23:14:21 +0100 [thread overview]
Message-ID: <m3pv6wyfr6.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Stainless Steel Rat's message of "26 Feb 1999 16:14:06 -0500"
Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> I mean, when I wrote pop3-movemail I never intended for anyone (besides me)
> to actually use it. I resist 'improvement' in the hopes that someone will
> write a better function.
It works well (better than movemail with all its compilation problems
(well, not problems, but lack of --with-pop configuration)), so I
think it should be preferred over the other available solutions.
I've now changed the append-to-file thing that messages to
write-region with APPEND and no messaging.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-02-26 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-09 17:39 Jack Vinson
[not found] ` <m3r9rzxxtf.fsf@peorth.gweep.net>
[not found] ` <199902262006.PAA02318@icule.progiciels-bpi.ca>
1999-02-26 21:14 ` Stainless Steel Rat
1999-02-26 22:14 ` Lars Magne Ingebrigtsen [this message]
1999-02-27 1:08 ` François Pinard
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=m3pv6wyfr6.fsf@quimbies.gnus.org \
--to=larsi@gnus.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.
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).