Thanks, now I tried viewing an html attachment from qvc with lynx and pine. Ended up having to take the first line out of .mailcap because /usr/bin/htmlview didn't exist and pine got upset about that. The output was loaded with all kinds of <table> kind of code so dump wasn't able to handle that. Probably the dump command in lynx could use improvement so all that table and frame junk is filtered out of the dump command and never makes it to text output. Unless lynx is planning on supporting tables and frames in future.On Wed, 27 Aug 2003, Dave Mielke wrote: > Date: Wed, 27 Aug 2003 00:36:47 -0400 > From: Dave Mielke <dave@xxxxxxxxx> > Reply-To: blinux-list@xxxxxxxxxx > To: blinux-list@xxxxxxxxxx > Subject: Re: html messages and pine > > [quoted lines by dashielljt on 2003/08/27 at 00:24 -0400] > > >Forgot to ask, will those rules handle files with the .htm extension as > >well or should another couple lines be added with nametemplate=%s.htm? > > The purpose of the nametemplate specification isn't to filter the name of the > given file, but, rather, to tell the application, e.g. pine, what to name the > file before giving it to lynx. The rule tells the application to make sure that > it puts text/html data into a file with an extension of .html before letting > lynx see it, which is how you force lynx to believe that it's html. By default, > applications (including pine) give the file a name with random junk on the end > (like mktemp does), and then lynx doesn't believe that the file contains html > source. One would think that such applications would be sensitive to mime.types > in the first place, but, unfortunately, they don't seem to be. > > -- ----- Microsoft; mismanagement, and stupidity are all weapons of mass destruction. _______________________________________________ Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list