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 491A14196F3 for ; Sat, 10 Apr 2010 06:48:17 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001] autolearn=ham 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 Q+d2xqakGwKQ for ; Sat, 10 Apr 2010 06:48:16 -0700 (PDT) Received: from homiemail-a17.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by olra.theworths.org (Postfix) with ESMTP id 78C33431FC1 for ; Sat, 10 Apr 2010 06:48:16 -0700 (PDT) Received: from sspaeth.de (unknown [195.190.188.219]) by homiemail-a17.g.dreamhost.com (Postfix) with ESMTPA id DF3A07A8063; Sat, 10 Apr 2010 06:48:13 -0700 (PDT) Received: by sspaeth.de (sSMTP sendmail emulation); Sat, 10 Apr 2010 15:48:11 +0200 From: "Sebastian Spaeth" To: Jesse Rosenthal , Carl Worth , notmuch@notmuchmail.org Subject: Re: [notmuch] [PATCH v2] notmuch.el: Make notmuch-show buffer name first subject, instead of thread-id In-Reply-To: <878w8wafoa.fsf@jhu.edu> References: <87zl1f5f6u.fsf@yoom.home.cworth.org> <878w8wafoa.fsf@jhu.edu> Date: Sat, 10 Apr 2010 15:48:11 +0200 Message-ID: <871venbeqs.fsf@SSpaeth.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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, 10 Apr 2010 13:48:17 -0000 On 2010-04-09, Jesse Rosenthal wrote: > sporadic access. However, one question: it looks like it was V2 of the > patch that you pushed -- was it? Unfortunately, there was a subtle bug > that kept on popping up (when you call notmuch-show interactively, which > rarely happens). Later in this same thread, I offered V4 (yep, there was > a problematic V3 too) which fixes this: I think I picked v4 for merging, however removing the comment (supercedes v1-3) from the commit messages. I hope that was ok with you. Sebastian