1 Return-Path: <awg@xvx.ca>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 9390C431FAF
\r
6 for <notmuch@notmuchmail.org>; Mon, 14 Jan 2013 16:37:32 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5
\r
12 tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
13 Received: from olra.theworths.org ([127.0.0.1])
\r
14 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
15 with ESMTP id vIPPhn0lQWLH for <notmuch@notmuchmail.org>;
\r
16 Mon, 14 Jan 2013 16:37:31 -0800 (PST)
\r
17 Received: from mail-vb0-f43.google.com (mail-vb0-f43.google.com
\r
18 [209.85.212.43]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
19 (No client certificate requested)
\r
20 by olra.theworths.org (Postfix) with ESMTPS id B0F8C431FAE
\r
21 for <notmuch@notmuchmail.org>; Mon, 14 Jan 2013 16:37:31 -0800 (PST)
\r
22 Received: by mail-vb0-f43.google.com with SMTP id fs19so4235961vbb.30
\r
23 for <notmuch@notmuchmail.org>; Mon, 14 Jan 2013 16:37:31 -0800 (PST)
\r
24 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
\r
25 d=google.com; s=20120113;
\r
26 h=mime-version:sender:x-originating-ip:in-reply-to:references:date
\r
27 :x-google-sender-auth:message-id:subject:from:to:cc:content-type
\r
28 :x-gm-message-state;
\r
29 bh=1DNz/8K7tNsB6EQkJM9s+7zn1+EEYWLr+QVAEuBONf4=;
\r
30 b=DCFwKpReqB+2RIOnQa1m98uCgvi44vAHKjqFMP++xVb/NomzB8iB8xgN7Kdn7FnMf3
\r
31 0Ivbeeph5/9DXrCM9DZ7CRp1zzI/lhSdP/n/+TtQbivmUDozMdwLdJJzW1C68AqN51P9
\r
32 oWHXNlrJ4Twknqs0Mk51ohwnp7cPYHG8T4wGhcPBPX8eC5SEpCrpKEsrArOp0heptYqR
\r
33 O4dqj0HpQjAwIhTs06IF8QZg8xV/g3jfb5YeX07ZgijVuL6+mvu6qqqIAj6NDsfpxxR1
\r
34 anxta/qqGWkRYqMtqhnmupUdLDdttMQ+rRb5NUm6faK3M9Hh25b6OlK7usy53pvcei82
\r
37 Received: by 10.220.140.143 with SMTP id i15mr102640283vcu.15.1358210249963;
\r
38 Mon, 14 Jan 2013 16:37:29 -0800 (PST)
\r
40 Received: by 10.220.233.135 with HTTP; Mon, 14 Jan 2013 16:37:29 -0800 (PST)
\r
41 X-Originating-IP: [2001:470:b:2bb::2]
\r
42 In-Reply-To: <87libvpbjd.fsf@zancas.localnet>
\r
43 References: <1357862220-1219-1-git-send-email-markwalters1009@gmail.com>
\r
44 <1358081032-3066-1-git-send-email-markwalters1009@gmail.com>
\r
45 <87libvpbjd.fsf@zancas.localnet>
\r
46 Date: Mon, 14 Jan 2013 17:37:29 -0700
\r
47 X-Google-Sender-Auth: 89TrpwSgcJ-geQ9Ud--3kvi8jkY
\r
49 <CAMoJFUsyFw1O3TjCC0UCBnYh_eW1F5tz5_N_vEnkhSQ4+fufbg@mail.gmail.com>
\r
50 Subject: Re: [PATCH v3] emacs: show: possible w3m/invisibility workaround
\r
51 From: Adam Wolfe Gordon <awg+notmuch@xvx.ca>
\r
52 To: David Bremner <david@tethera.net>
\r
53 Content-Type: text/plain; charset=ISO-8859-1
\r
55 ALoCoQnBaA5QWanqhSmyKTNBKA1Ltm+lf4s7Hwl1jSsIOnmo113smTHin+llTRfBZt+/YeOkE2TA
\r
56 Cc: notmuch@notmuchmail.org
\r
57 X-BeenThere: notmuch@notmuchmail.org
\r
58 X-Mailman-Version: 2.1.13
\r
60 List-Id: "Use and development of the notmuch mail system."
\r
61 <notmuch.notmuchmail.org>
\r
62 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
63 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
64 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
65 List-Post: <mailto:notmuch@notmuchmail.org>
\r
66 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
67 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
68 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
69 X-List-Received-Date: Tue, 15 Jan 2013 00:37:32 -0000
\r
71 On Mon, Jan 14, 2013 at 4:52 PM, David Bremner <david@tethera.net> wrote:
\r
72 > Mark Walters <markwalters1009@gmail.com> writes:
\r
74 >> There is a bug in the current notmuch code with w3m and invisible
\r
75 >> parts. w3m sets a keymap, and if we have a hidden [text/html] point
\r
76 >> at the start of the following line still gets this w3m keymap which
\r
77 >> causes some strange effects. For example, RET gives an error "No URL
\r
78 >> at Point" rather than hiding the message, <down> goes to the next link
\r
79 >> rather than just down a line.
\r
81 > pushed to relaese and master.
\r
83 I can confirm this solves the bug I was seeing.
\r