unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Adam Wolfe Gordon <awg+notmuch@xvx.ca>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH v2 0/2] Replying to HTML-only emails, v2
Date: Sun, 6 May 2012 08:29:36 -0600	[thread overview]
Message-ID: <CAMoJFUv6WcFKZVobqLk8tbmZ2GiXHh-fMhhukChBtXVK3brSxQ@mail.gmail.com> (raw)
In-Reply-To: <878vh5bja3.fsf@zancas.localnet>

On Sun, May 6, 2012 at 6:12 AM, David Bremner <david@tethera.net> wrote:
> I pushed this series, but it seems to have a test failure on the
> buildbot (it's fine on my Debian wheezey box)
>
> http://buildbot.notmuchmail.org/builders/master/builds/198/steps/tests/logs/problems
>
> Maybe you and Tom could try to figure out what is different about his
> environment?

The failure is on the new HTML reply test, and the difference in the
output is just indentation - the quoted HTML text has an extra three
spaces at the beginning of each line. So, it's almost certainly a
difference in emacs versions or packages. I'm running Ubuntu Oneiric
with emacs 23.3.

It looks like the relevant variable in mm is
mm-text-html-renderer-alist, which defines various methods of parsing
HTML. For me it's:

((w3 . mm-inline-text-html-render-with-w3)
 (w3m . mm-inline-text-html-render-with-w3m)
 (w3m-standalone . mm-inline-text-html-render-with-w3m-standalone)
 (links mm-inline-render-with-file mm-links-remove-leading-blank
"links" "-dump" file)
 (lynx mm-inline-render-with-stdin nil "lynx" "-dump" "-force_html"
"-stdin" "-nolist")
 (html2text mm-inline-render-with-function html2text))

I get the behavior seen on the buildbot if the only option available
on my machine is lynx, so I'm guessing that's what's happening.

I'm not sure what the best option is for fixing this. A few possible options:

* Only run the test if links, w3m, or w3m.el is available.
* Make the test accept differences in whitespace.
* Try to produce HTML for the test that renders the same in every method.

Opinions from anyone?

-- Adam

  reply	other threads:[~2012-05-06 14:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05 19:24 [PATCH v2 0/2] Replying to HTML-only emails, v2 Adam Wolfe Gordon
2012-05-05 19:24 ` [PATCH v2 1/2] test: Replying to an HTML-only message in emacs Adam Wolfe Gordon
2012-05-05 19:24 ` [PATCH v2 2/2] emacs: Correctly quote non-text/plain parts in reply Adam Wolfe Gordon
2012-05-05 19:30   ` [PATCH v2.1 " Adam Wolfe Gordon
2012-05-05 22:30 ` [PATCH v2 0/2] Replying to HTML-only emails, v2 Austin Clements
2012-05-06 12:12 ` David Bremner
2012-05-06 14:29   ` Adam Wolfe Gordon [this message]
2012-05-06 14:56     ` [PATCH] test: Force reply to use html2text for consistency Adam Wolfe Gordon
2012-05-06 23:52       ` David Bremner
2012-05-07  6:17         ` Tomi Ollila

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMoJFUv6WcFKZVobqLk8tbmZ2GiXHh-fMhhukChBtXVK3brSxQ@mail.gmail.com \
    --to=awg+notmuch@xvx.ca \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).