[CLUE-Tech] Re: Mutt [Was: Replys with broken HTML]

[Sean LeBlanc]

On 06-09 12:46, Jed S. Baer wrote:
> On Sun, 9 Jun 2002 09:56:39 -0600 Sean LeBlanc <seanleblanc at attbi.com>
> wrote:
> 
> > <deletia> Now, if I could just get a macro to put top-posts into the
> > correct format. :) Who knows, maybe one exists. I may even ask on the
> > Mutt mailing list.
> 
> I was just recently musing about how easy/difficult it would be to write a
> mailing list manager that would automate things like this. Maybe a plugin
> for GNU/Mailman. Parsing incoming mail which doesn't go through some
> centralized facility, like a list manager, would be pretty tough, I think,
> given the variance in quoting styles. 
<snip>

I happened to stumble across something for Mutt, even though my post on
mutt-users wasn't too fruitful: T-Prot, which stands for TOFU protection.
It doesn't really do what I want, but who knows, it might be a good start or
at least a base to work from. It's written in Perl, and so can probably work
with other mailers.

It *is* featureful in other ways besides dealing with top-posters - it can
hide long .sigs, as well as look for and hide common things tacked on by a
lot of mail services these days. When I get some time, I'm going to play
with it a bit to try to take more of those rough edges off. :) What it
definitely does not do (yet) is alter the text of a message you are
responding to, which is unfortunate. 

I'm not so sure that something that did The Right Thing for correction in
reponse style would be sooo difficult for someone who was good at such
things(i.e., not me). For example, the gqap macro in vim will adjust line
wrap in quoted text, and KEEP the ">"'s in the proper place. Maybe it
wouldn't work for any old character used in place of ">", I don't know, but
I've used this macro a lot to clean up others' emails when responding to
them, and have been quite impressed with that ability. Whatever they are
using to determine that some chars are quoting chars they could use to
determine the depth they are at, and where they should go. The really tough
case would be a thread in which some people have top-posted throughout a
conversation in which people also used the correct style. 

-- 
Sean LeBlanc:seanleblanc at attbi.com Yahoo:seanleblancathome 
ICQ:138565743 MSN:seanleblancathome AIM:sleblancathome 
Never laugh at live dragons. 
-J.R.R. Tolkien, "The Hobbit" 


Received: from mail.c.bus.net (65-85-139-3.client.dsl.net [65.85.139.3])
	by clue.denver.co.us (8.9.3/8.9.3) with ESMTP id LAA06490
	for <clue-tech at clue.denver.co.us>; Wed, 12 Jun 2002 11:57:45 -0600
Received: from ws100.c.bus.net (ws100.c.bus.net [192.168.1.10])
	by mail.c.bus.net (Postfix) with ESMTP
	id 2BC5276308; Wed, 12 Jun 2002 14:02:05 -0400 (EDT)
Received: (from cao at localhost)
	by ws100.c.bus.net (8.11.3/8.11.3) id g5CI25004592;
	Wed, 12 Jun 2002 14:02:05 -0400 (EDT)
	(envelope-from cao)
Date: Wed, 12 Jun 2002 14:02:04 -0400
From: "Chuck O'Donnell" <cao at bus.net>
To: Dave Price <davep at kinaole.org>
Cc: clue-tech at clue.denver.co.us, mutt-users at mutt.org
Message-ID: <20020612180204.GA4503 at bus.net>
References: <20020610191614.A6236 at kinaole.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020610191614.A6236 at kinaole.org>
Subject: [CLUE-Tech] Re: solved: viewing in-line text/html with mutt and lynx
Sender: clue-tech-admin at clue.denver.co.us
Errors-To: clue-tech-admin at clue.denver.co.us
X-BeenThere: clue-tech at clue.denver.co.us
X-Mailman-Version: 2.0beta2
Precedence: bulk
Reply-To: clue-tech at clue.denver.co.us
List-Id: CLUE technical discussions, questions and answers. <clue-tech.clue.denver.co.us>

On Mon, Jun 10, 2002 at 07:16:14PM -0600, Dave Price wrote:
> ok,
> 
> I finally got it working right.  I am using mutt and 
> lynx Version 2.8.1rel.2 
> 
> In ~/.muttrc I put:
> 
> auto_view text/html text/enriched
> 
> and I made a ~/.mailcap with:
> 
> text/html;/usr/bin/lynx -dump -force_html %s ;copiousoutput
> 
> My lynx likes -dump, not --dump and the -force_html deals with the case
> where the attachment filename is not .html, without it I got raw
> (uninterpreted) html.
> 

My version of lynx indents the text output, which is no big deal, but
can be fixed pretty easily by piping through sed and stripping the
leading 3 space characters:

text/html;/usr/local/bin/lynx -localhost -force_html -nolist -dump %s | sed 's/^   //'; copiousoutput;


Cheers,

Chuck