From: "David Z. Maze" <dmaze@GRATUITOUS-EXISTENCE-FAILURE.MIT.EDU>
Subject: Brokenness with postscript in mail-source-fetch-pop
Date: 19 May 1999 14:55:44 -0400 [thread overview]
Message-ID: <87pv3w99e7.fsf@annular-fried-pastry.mit.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
mail-source-fetch-pop, as distributed with Pterodactyl Gnus 0.84,
wants to run user-provided prescript and postscript code when pulling
mail off of a POP server. Unfortunately, the postscript code is
broken: it checks to see whether prescript is defined, and if it is,
runs postscript. This breaks if postscript is undefined. This patch
should fix it:
[-- Attachment #2: postscript fix for mail-source-fetch-pop --]
[-- Type: application/x-patch, Size: 455 bytes --]
[-- Attachment #3: Type: text/plain, Size: 222 bytes --]
--
David Maze dmaze@mit.edu http://donut.mit.edu/dmaze/
"Hey, Doug, do you mind if I push the Emergency Booth Self-Destruct Button?"
"Oh, sure, Dave, whatever...you _do_ know what that does, right?"
reply other threads:[~1999-05-19 18:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87pv3w99e7.fsf@annular-fried-pastry.mit.edu \
--to=dmaze@gratuitous-existence-failure.mit.edu \
/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).