I found better solution. Don't generate a mc.ext file, just use
run-mailcap for default action for every file. And also we can keep a
few special treating files, like ie. archives.
I've attached my proposition of mc.ext and I'm going to add this to a
wishlist.
Regards.
Marcin
--
.---,
W liście z wto, 13-05-2003, godz. 12:43, Andreas Tille pisze:
> > Please, share with me with your opinions.
> If I would be you I would file a wishlist bug against mc package and
> tag it "patch" by providing your script.
But first I wanna know if it what I done is good ;)
So, I will wait for opi
On 13 May 2003, mcINEK wrote:
> I think, it's very good to automate generating mc.ext file.
Very good idea.
> Please, share with me with your opinions.
If I would be you I would file a wishlist bug against mc package and
tag it "patch" by providing your script.
Kind regards
Andreas.
Hi!
I've just wrote a script which generates a /etc/mc/mc.ext file using
information from mime.types and mailcap files.
I found it very useful. It takes a list of extensions from mime.types
then check if in mailcap we've got support for that extension.
If yes it put this extension do mc.ext and a
4 matches
Mail list logo
