From mboxrd@z Thu Jan 1 00:00:00 1970 From: wmorgan-sup@masanjin.net (William Morgan) Date: Thu, 24 Jan 2008 15:26:20 -0800 Subject: [sup-talk] missing run-mailcap In-Reply-To: <1201210323-sup-6116@tangerine.lanl.gov> References: <1201019996-sup-8960@tangerine.lanl.gov> <1201041081-sup-6034@tangerine.lanl.gov> <1201210323-sup-6116@tangerine.lanl.gov> Message-ID: <1201216741-sup-4105@south> Reformatted excerpts from John Bent's message of 2008-01-24: > When sup opens an attachment, it copies the attachment to > /tmp/sup-attachment-ID and then calls run-mailcap. But sup knows what > name the file was attached as. Could sup save the attachment to > /tmp/filename? Or at least append the extension? In 0.4 you should see the extension being preserved. Let me know if that's not the case. So you should be able to simply call "open" on that file, rather than having to use your Perl script. > Although my preference would be to use the fullname which is > presumably what the file is named on the originating machine. This might be doable. I've been using the tempfile Ruby library to handle these files, which does two things: it obfuscates the name to avoid collisions, and it ensures the file is deleted once all references to the variable are garbage-collected. It might not be hard to replace this with something that only does the latter behavior. I might be able to programmatically delete the files too, instead of waiting for garbage collection. > By the way, sup works so well that I've now imported my old school > emails which I'd previously given up on. I now have blazing fast > search over my last ten years of email! Excellent! -- William