Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id E9689431FD2 for ; Sat, 22 Feb 2014 15:56:33 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rEMdT3wl+V1P for ; Sat, 22 Feb 2014 15:56:33 -0800 (PST) Received: from yantan.tethera.net (yantan.tethera.net [199.188.72.155]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 85A56431FCF for ; Sat, 22 Feb 2014 15:56:33 -0800 (PST) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1WHMQq-0003lY-3J; Sat, 22 Feb 2014 19:56:32 -0400 Received: (nullmailer pid 6411 invoked by uid 1000); Sat, 22 Feb 2014 23:56:28 -0000 From: David Bremner To: Austin Clements , notmuch@notmuchmail.org Subject: Re: [PATCH 0/4] Bug fixes for identity handling in Emacs In-Reply-To: <1392923797-17045-1-git-send-email-amdragon@mit.edu> References: <1392923797-17045-1-git-send-email-amdragon@mit.edu> User-Agent: Notmuch/0.17 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Sat, 22 Feb 2014 19:56:28 -0400 Message-ID: <87lhx2zopf.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain Cc: bjonnh-nm@bjonnh.net X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Feb 2014 23:56:34 -0000 Austin Clements writes: > This series fixes several bugs surrounding identity handling in Emacs. > It was inspired by a problem that bjonnh on IRC had where forwarding > from an address where the full name matched the mailbox would crash > `notmuch-mua-new-forward-message'. While it was possible to work > around that specific problem with a simple fix, it revealed that the > code was subtly broken in many ways. I pushed the first 3. I wasn't sure what the concencus was on patch 4. d