Re: Detecting attachment types by file extension.. how to change exmh's behaviour?

>I don't have much experience with MacOS-X but it looks to me like the
>problem is with /usr/bin/open and not with exmh.  I've never heard of a
>unix command that operates based on file extensions before (rather than
>determining type based on file contents (eg file)).

Well, you have now.  I also occasionally use exmh under MacOS X, and
I run into the same problem.

Right or wrong, MacOS X made the concious decision to determine file type
by file extension (I read the article describing that decision and I at
least understood their reasoning; they had a lot of issues to deal with).
open is not a simple shell script; it's a program which uses the registered
application to open a particular file.  While it's possible for you to
run the correct application directly, open(1) makes life so much easier.

I've never understood why exmh creates a wacky name when it does it's own
MIME handling.  It knows what the name SHOULD be (it fills that in when
you use the Save dialog, which is what I end up doing), but instead the
names it creates are always something strange.  I guess there was a concern
about name collision, but it seems like you could easily work around that.

--Ken