🚀 go-pugleaf

Michael Welle wrote:
 > Kevin Rodgers <ihs_4664@yahoo.com> writes:
 >>`vm-mime-use-image-strips' defaults to t.  Does the problem occur if
 >>you set it to nil?
 >
 > Ah, that seems to be much better. There is only a tmp file with
 > restricted permissions. I have looked at the code yesterday and find
 > the place with the stripping. But my knowledge about list is very
 > vague. Is the handling of png images so different from the handling of
 > other image types?

No, none of vm-mime-display-internal-image-xemacs-xxxx,
vm-mime-display-internal-image-fsfemacs-21-xxxx, or
vm-make-image-strips reference "png".  VM passes a new empty temp
output file (presumably with the correct permissions) to the
ImageMagick convert program, which I suspect is re-creating the file
(with the incorrect default permissions).  But I don't understand why
VM isn't deleting the temp files: they're registered by the
vm-mime-display-internal-image-*-xxxx functions in
vm-message-garbage-alist; perhaps delete-file is failing but it goes
unnoticed since vm-garbage-collect-message wraps it in condition-case,
or perhaps the asyncronous way that the ImageMagick convert program is
called has something to do with it.

Since both vm-mime-display-internal-image-*-xxxx functions call
vm-make-image-strips with t as the ASYNC arg, I think the only place
where the strip temp files can reliably have their permissions reset
is the process filter (if vm-mime-display-image-strips-incrementally
is set) and/or the process sentinel.

-- 
Kevin Rodgers