/tmp being littered with *.{gif,jpg} (by mm-*?)

/tmp being littered with *.{gif,jpg} (by mm-*?)

[Karl Kleinpaste]

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.

p0.97, XEmacs 21.2.b19, RH6 Linux.

Re: /tmp being littered with *.{gif,jpg} (by mm-*?)

[Lars Magne Ingebrigtsen]

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.

This means that the cleanup forms for the MIME handlers are not being
called.  When does this happen?  They seem to be called OK for me,
which means that I'm not doing it right.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: /tmp being littered with *.{gif,jpg} (by mm-*?)

[Shenghuo ZHU]

>>>>> "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