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 1956C431FB6 for ; Tue, 10 Sep 2013 04:23:53 -0700 (PDT) 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 wugmBlkx4BBz for ; Tue, 10 Sep 2013 04:23:45 -0700 (PDT) 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 D841E431FAF for ; Tue, 10 Sep 2013 04:23:45 -0700 (PDT) Received: from remotemail by yantan.tethera.net with local (Exim 4.80) (envelope-from ) id 1VJM2r-0007lV-04; Tue, 10 Sep 2013 08:23:45 -0300 Received: (nullmailer pid 23723 invoked by uid 1000); Tue, 10 Sep 2013 11:23:41 -0000 From: David Bremner To: Ramakrishnan Muthukrishnan , notmuch@notmuchmail.org Subject: Re: search order In-Reply-To: References: User-Agent: Notmuch/0.16+71~gfd656d7 (http://notmuchmail.org) Emacs/24.3.1 (x86_64-pc-linux-gnu) Date: Tue, 10 Sep 2013 08:23:41 -0300 Message-ID: <8738pcq5s2.fsf@zancas.localnet> MIME-Version: 1.0 Content-Type: text/plain 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, 10 Sep 2013 11:23:53 -0000 Ramakrishnan Muthukrishnan writes: > > If I startup notmuch and then do a M-x notmuch-search and then *, I see > the messages with the newest on the top. But if I instead, startup > notmuch and then hit "s", I see that the new messages are at the > bottom. The value of notmuch-search-oldest-first is t. > This should be fixed in the latest git master. Thanks for the report, and thanks to Austin for the fix. d