From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: /tmp being littered with *.{gif,jpg} (by mm-*?)
Date: 08 Nov 1999 12:20:08 -0500 [thread overview]
Message-ID: <5br9i0dho7.fsf@giga.cs.rochester.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "06 Nov 1999 03:06:23 +0100"
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
LMI> Karl Kleinpaste <karl@justresearch.com> writes:
>> My /tmp is being overrun by directories named things like emm.peBJuj,
>> each containing exactly 1 *.{gif,jpg} from a couple mailing lists I'm
>> needing to receive these days.
>>
>> This XEmacs also has gained " *mm*<X>" buffers, for X between 2 and
>> 346. Each one contains a single blob of base64-encoded data.
LMI> This means that the cleanup forms for the MIME handlers are not
LMI> being called. When does this happen? They seem to be called OK
LMI> for me, which means that I'm not doing it right. :-)
It should have been fixed in 0.98. It was because
gnus-article-setup-buffer forgot to clean up those handles.
--
Shenghuo ZHU
prev parent reply other threads:[~1999-11-08 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-29 21:30 Karl Kleinpaste
1999-11-06 2:06 ` Lars Magne Ingebrigtsen
1999-11-08 17:20 ` Shenghuo ZHU [this message]
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=5br9i0dho7.fsf@giga.cs.rochester.edu \
--to=zsh@cs.rochester.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).