From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.187.5 with SMTP id fo5cs233315vdc; Wed, 11 May 2011 07:39:43 -0700 (PDT) Received: by 10.142.208.12 with SMTP id f12mr4952665wfg.92.1305124780774; Wed, 11 May 2011 07:39:40 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id r17si412412qcs.3.2011.05.11.07.39.40; Wed, 11 May 2011 07:39:40 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 78BCF18583A7 for ; Wed, 11 May 2011 10:39:40 -0400 (EDT) Received: from mail-pv0-f178.google.com (mail-pv0-f178.google.com [74.125.83.178]) by rubyforge.org (Postfix) with ESMTP id 7715F1858376 for ; Wed, 11 May 2011 10:13:55 -0400 (EDT) Received: by pvg7 with SMTP id 7so428223pvg.23 for ; Wed, 11 May 2011 07:13:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:sender:content-type:cc:subject:from:to :in-reply-to:references:date:message-id:user-agent :content-transfer-encoding; bh=qkiD30Q2u6c3a2eHiaTLLIZuwNcXCsUt59ETTXE+6KQ=; b=pMA9SSKggQFJYqk9u8A/BF0WGn1IlBwDoCSbAe+vWs/XWgDK+V4uAfRJKoMd9Hzlfh irYT3swMs0h5DX6atsLWovdr6pF6/IHPzGFxu8rxTeKt/9c8hvJGnt2wczCFg2dXssMr h6i0zktdZW7DNfjvcJ02Lb3udZapu17tWahDE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:content-type:cc:subject:from:to:in-reply-to:references:date :message-id:user-agent:content-transfer-encoding; b=YPflYgYKGe4epZYoSxq5cHiuWAFZQH9m6mWZxmK2GMP0aOZ5k20RZbf8Rn+nyQOn+P uTqxV467FdfrEwmrQKkd9vGA6a16e/lABe16+LUqrji7vTQ0AYcKkxIMEneDLdNgBWn9 EK2Fm1FTwNCwnCvl6qe9ey3FKmbBUx0UM0AJM= Received: by 10.142.170.19 with SMTP id s19mr1130227wfe.401.1305123234443; Wed, 11 May 2011 07:13:54 -0700 (PDT) Received: from localhost (c-24-63-93-125.hsd1.vt.comcast.net [24.63.93.125]) by mx.google.com with ESMTPS id p10sm206977wfl.21.2011.05.11.07.13.51 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 May 2011 07:13:52 -0700 (PDT) From: Mark Alexander To: Steve In-reply-to: References: Date: Wed, 11 May 2011 10:13:49 -0400 Message-Id: <1305123144-sup-2758@bloovis.org> User-Agent: Sup/0.12.1 Cc: sup-devel Subject: Re: [sup-devel] How to deal with HTML attachments? X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Excerpts from Steve's message of Wed May 11 09:53:27 -0400 2011: > How do you recommend dealing with HTML attachments? I use a text-mode browser called w3m to view HTML. Sup will invoke it as necessary (on Ubuntu, at least) if you put the following in your ~/.mailcap file: text/html; /usr/bin/w3m -o confirm_qq=false -T text/html '%s'; needsterminal; description=HTML Text; nametemplate=%s.html _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel