From mboxrd@z Thu Jan  1 00:00:00 1970
From: johnbent@lanl.gov (John Bent)
Date: Thu, 24 Jan 2008 14:40:08 -0700
Subject: [sup-talk] missing run-mailcap
In-Reply-To: <1201041081-sup-6034@tangerine.lanl.gov>
References: <1201019996-sup-8960@tangerine.lanl.gov>
	<1201041081-sup-6034@tangerine.lanl.gov>
Message-ID: <1201210323-sup-6116@tangerine.lanl.gov>

Excerpts from John Bent's message of Tue Jan 22 15:33:22 -0700 2008:
> Excerpts from John Bent's message of Tue Jan 22 09:40:05 -0700 2008:
> > I saw some earlier discussion in the list archives about a missing run-mailcap
> > script.  I had this same problem too on my mac (10.4.11 Power PC).  It's sort
> > of a kluge but I dealt with this by writing my own /usr/bin/run-mailcap which
> > just does a simple hash lookup of mime type to rename the file with an
> > appropriate extension and then uses the mac 'open' command.  

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?  Although my preference would be to use
the fullname which is presumably what the file is named on the originating
machine.  Often I'll open an attachment first and if I like it, then I'll save
it using whichever viewer it's in (e.g. someone sends me an MS Word, I open it
in word, and then save it through word).  I then get a dialog about how to
save it which has as a starting point the current path which is 
/tmp/sup-attachment-ID which I'll always have to change.  But if it was the
original attached name, I'd probably often be happy and would prefer 
to keep that name.  

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!