From 408ee62162021f707d58f7401a91d5ba750dfa39 Mon Sep 17 00:00:00 2001 From: Laurence Rochfort Date: Wed, 6 Apr 2016 15:25:46 +0000 Subject: [PATCH] Re: Order of messages --- ec/5094da7820edfda35540d2f324a5ff831377e8 | 151 ++++++++++++++++++++++ 1 file changed, 151 insertions(+) create mode 100644 ec/5094da7820edfda35540d2f324a5ff831377e8 diff --git a/ec/5094da7820edfda35540d2f324a5ff831377e8 b/ec/5094da7820edfda35540d2f324a5ff831377e8 new file mode 100644 index 000000000..2bc8f7308 --- /dev/null +++ b/ec/5094da7820edfda35540d2f324a5ff831377e8 @@ -0,0 +1,151 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by arlo.cworth.org (Postfix) with ESMTP id BD1C96DE01F7 + for ; Wed, 6 Apr 2016 08:26:06 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at cworth.org +X-Spam-Flag: NO +X-Spam-Score: -0.617 +X-Spam-Level: +X-Spam-Status: No, score=-0.617 tagged_above=-999 required=5 tests=[AWL=0.202, + DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, + HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, + RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled +Received: from arlo.cworth.org ([127.0.0.1]) + by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id CW1hFIAbhrFH for ; + Wed, 6 Apr 2016 08:25:59 -0700 (PDT) +Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com + [209.85.215.48]) + by arlo.cworth.org (Postfix) with ESMTPS id A36D86DE0130 + for ; Wed, 6 Apr 2016 08:25:58 -0700 (PDT) +Received: by mail-lf0-f48.google.com with SMTP id g184so36615281lfb.3 + for ; Wed, 06 Apr 2016 08:25:58 -0700 (PDT) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; + h=mime-version:references:in-reply-to:from:date:message-id:subject:to; + bh=iY4dWci3B3OJlu3gh0hWofjzsWtzF0IRe8SlCLP5SrQ=; + b=LxA98I9o3Zlhh3hbdhfLGoTKHon9ViR1D7W7qvbzP2dhsVrIfK9Ro9d4AHdIg0AD+I + bM4iJXhaMUxpOWg3m7vZt1PdaVAb0O2iVi3PMooEnbEage1PR9wl0neCCYs6deSAHLl0 + mjH906e9YOG+4SttmCyRdeWsnS0STBXWfg7uqaeNd4vCHjTmQwCY372OM69kFkthmUs3 + gbmeU/QnK+Vv7B2GJ1oQQLqAogK8+x3rs6IFX6SWmyWL2U4jBiUJz9F0fROCyQDGyACw + v52J/XbThe4tBm100Dne0sAViwZc3lCsaVCyl1AvDIA0y2uvqwCVWao1WSo2vSIq/I/l + I2dg== +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20130820; + h=x-gm-message-state:mime-version:references:in-reply-to:from:date + :message-id:subject:to; + bh=iY4dWci3B3OJlu3gh0hWofjzsWtzF0IRe8SlCLP5SrQ=; + b=Fc6Hyq683NrZMr2MoK+TAJU5EtbsSnZfJaA/MjmEjB5Y/xD9gbl5VB5bNz23qCaRzR + Idb0mXEM+nzw2VfG+Bb+eZJHydO1M76LSmrvK6NtImHr8+yFaMi2bGBIMELadpFnyM27 + +RaLqC/ECPobAMERbhjTKCrwECxZpc+NVEdojNWJLRUzXUQHn5/zAxHCbFHeahioMU0Q + X2NtBbLtWxm/xITFOxtM8pGaLnls2QWZJz2G5uhubNI7uc4boVjNZFl3ive2b6CALSrF + d+V9ybAxKowddQ/YMsd83sgg24ZHmWTE4Zz8q69YRj9r8WvD94xILM1XWI5AWLy98OYT + o5jQ== +X-Gm-Message-State: AD7BkJLPkQj2AxymPdP9foH3Pu8x78FwCuMyf9JnaLb0iOLsvN+5k4rjlgqu01nlUVgkTY3K0nXpwiOKlxRhcQ== +X-Received: by 10.25.15.105 with SMTP id e102mr1970437lfi.103.1459956356687; + Wed, 06 Apr 2016 08:25:56 -0700 (PDT) +MIME-Version: 1.0 +References: + + +In-Reply-To: + +From: Laurence Rochfort +Date: Wed, 06 Apr 2016 15:25:46 +0000 +Message-ID: + +Subject: Re: Order of messages +To: Alex Dunn , + "notmuch@notmuchmail.org" +Content-Type: multipart/alternative; boundary=001a113fbe60072e6e052fd294e8 +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.20 +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: Wed, 06 Apr 2016 15:26:06 -0000 + +--001a113fbe60072e6e052fd294e8 +Content-Type: text/plain; charset=UTF-8 + +Thanks Alex, + +I tried that and it seemed to only affect the search results. I there +anyway to set the ordering everywhere, so in threaded and message view for +instance? + +Cheers, +Laurence. + +On Wed, Apr 6, 2016 at 4:21 PM Alex Dunn wrote: + +> You should be able to set `notmuch-search-oldest-first` to nil, either +> manually or in the Customize menu. +> +> Laurence Rochfort writes: +> +> > Hello, +> > +> > In the notmuch emacs client, messages are always shown oldest at the top +> > and newest at the bottom. This seems to be the case for both search +> results +> > and when viewing a message content. +> > +> > How can I set the default to be newest first in all cases? +> > +> > Cheers, +> > Laurence. +> > _______________________________________________ +> > notmuch mailing list +> > notmuch@notmuchmail.org +> > https://notmuchmail.org/mailman/listinfo/notmuch +> + +--001a113fbe60072e6e052fd294e8 +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +
Thanks Alex,

I tried that and it seemed= + to only affect the search results. I there anyway to set the ordering ever= +ywhere, so in threaded and message view for instance?

<= +div>Cheers,
Laurence.

<= +div dir=3D"ltr">On Wed, Apr 6, 2016 at 4:21 PM Alex Dunn <dunn.alex@gmail.com> wrote:
You should be able to set `notmuch-search-oldest-f= +irst` to nil, either
+manually or in the Customize menu.
+
+Laurence Rochfort <laurence.rochfort@gmail.com> writes:
+
+> Hello,
+>
+> In the notmuch emacs client, messages are always shown oldest at the t= +op
+> and newest at the bottom. This seems to be the case for both search re= +sults
+> and when viewing a message content.
+>
+> How can I set the default to be newest first in all cases?
+>
+> Cheers,
+> Laurence.
+> _______________________________________________
+> notmuch mailing list
+> notmuch@n= +otmuchmail.org
+> https://notmuchmail.org/mailman/listinfo/notmuc= +h
+ + +--001a113fbe60072e6e052fd294e8-- -- 2.26.2