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 12E6A429E5B for ; Tue, 31 Jan 2012 01:25:36 -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 BzF23vBzOBRw for ; Tue, 31 Jan 2012 01:25:35 -0800 (PST) Received: from guru.guru-group.fi (guru-group.fi [87.108.86.66]) by olra.theworths.org (Postfix) with ESMTP id 703DD429E34 for ; Tue, 31 Jan 2012 01:25:35 -0800 (PST) Received: by guru.guru-group.fi (Postfix, from userid 501) id 2AFDF68056; Tue, 31 Jan 2012 11:25:36 +0200 (EET) From: Tomi Ollila To: Dmitry Kurochkin , David Edmondson , notmuch@notmuchmail.org Subject: Re: [PATCH 1/2] emacs: If archiving the last message in a thread, show the next thread. In-Reply-To: <871uqgntjz.fsf@gmail.com> References: <1327996914-9644-1-git-send-email-dme@dme.org> <1327996914-9644-2-git-send-email-dme@dme.org> <871uqgntjz.fsf@gmail.com> User-Agent: Notmuch/0.11+146~geb6dc33 (http://notmuchmail.org) Emacs/23.3.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ 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: Tue, 31 Jan 2012 09:25:36 -0000 On Tue, 31 Jan 2012 12:51:44 +0400, Dmitry Kurochkin wrote: > On Tue, 31 Jan 2012 10:43:10 +0200, Tomi Ollila wrote: > > On Tue, 31 Jan 2012 08:01:53 +0000, David Edmondson wrote: > > > When archiving the last message in a thread (a), rather than just > > > moving the pointer to the next thread in the parent search buffer, > > > actually display the next thread. > > > --- > > > > -1. Magic! Rather some customization option which lets user choose > > consistent behaviour (i.e. 'a' either jumps to search buffer or > > goes to next thread always (default?)). > > > > FWIW this behavior is consistent with how archiving worked before > earlier today. For those who uses archiving, the new behavior is a > surprise. So I would argue that this patch makes it less "magic". And > consistent with the current "A" behavior. Yes, I had a thinko there. 'a' progresses to next message after archiving and not back to search buffer... I like David's alternative suggestion (in IRC) where cursor is left at the end of buffer in case last message is archived with 'a'. > Regards, > Dmitry Thanks, Tomi