cc/40c4a2f6d6f7676d161c3f6f8155d6206344c2

   1 Return-Path: <sshilovsky@gmail.com>\r
   2 X-Original-To: notmuch@notmuchmail.org\r
   3 Delivered-To: notmuch@notmuchmail.org\r
   4 Received: from localhost (localhost [127.0.0.1])\r
   5         by olra.theworths.org (Postfix) with ESMTP id 156BE431FB6\r
   6         for <notmuch@notmuchmail.org>; Tue,  7 Oct 2014 04:00:52 -0700 (PDT)\r
   7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
   8 X-Spam-Flag: NO\r
   9 X-Spam-Score: -0.799\r
  10 X-Spam-Level: \r
  11 X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5\r
  12         tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
  13         FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
  14 Received: from olra.theworths.org ([127.0.0.1])\r
  15         by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
  16         with ESMTP id friTSaOC8CSI for <notmuch@notmuchmail.org>;\r
  17         Tue,  7 Oct 2014 04:00:48 -0700 (PDT)\r
  18 Received: from mail-oi0-f51.google.com (mail-oi0-f51.google.com\r
  19         [209.85.218.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
  20         (No client certificate requested)\r
  21         by olra.theworths.org (Postfix) with ESMTPS id AA294431FAF\r
  22         for <notmuch@notmuchmail.org>; Tue,  7 Oct 2014 04:00:48 -0700 (PDT)\r
  23 Received: by mail-oi0-f51.google.com with SMTP id h136so2161387oig.10\r
  24         for <notmuch@notmuchmail.org>; Tue, 07 Oct 2014 04:00:47 -0700 (PDT)\r
  25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
  26         h=mime-version:reply-to:date:message-id:subject:from:to:content-type\r
  27         :content-transfer-encoding;\r
  28         bh=LqB8w9rvkWjX4kLN3rLTwjVOYzv6MwfdCXYqhZvFIkg=;\r
  29         b=luqqHshEDKqBTBAJPIljHNzZDeKjh0IPiepv9Evh1kpSF8ypiI4nENNwUINNwDIRAi\r
  30         hoPME1pM3NciQz+1pep/RP7eK9dNlG3erwI27H4FguzWnmfpRu6pVaG/VvtNQVrJqQI8\r
  31         GFnrH0Q2wvPEOmIOLlCIsMgk2uw2YHcG7nRrl43sjAWNeoZI8bPKtpe1Y28UPxNdt+Pr\r
  32         IL0SC1+VWT491hD9vsrtfafOtNWfmhe7B/vJQh6q5J2yFAlrGIYH3IQPtjXDO6VShMHW\r
  33         xyKiYelQG69dNn+95Zb9Knk2cV5fsRN9DhBkjzQYIP0Sm3xWpTjU52hEc3EQOH9fJyAu\r
  34         r9EQ==\r
  35 MIME-Version: 1.0\r
  36 X-Received: by 10.182.191.102 with SMTP id gx6mr3013513obc.60.1412679647129;\r
  37         Tue, 07 Oct 2014 04:00:47 -0700 (PDT)\r
  38 Received: by 10.76.41.3 with HTTP; Tue, 7 Oct 2014 04:00:47 -0700 (PDT)\r
  39 Date: Tue, 7 Oct 2014 15:00:47 +0400\r
  40 Message-ID:\r
  41  <CAHc2pO2_mQZzG7TqntSLEY78YEZSVEwDSesgpCn1ZbngJvM0dQ@mail.gmail.com>\r
  42 Subject: Backward scrolling notmuch_messages_t and notmuch_threads_t\r
  43 From: Sergei Shilovsky <sshilovsky@gmail.com>\r
  44 To: notmuch@notmuchmail.org\r
  45 Content-Type: text/plain; charset=UTF-8\r
  46 Content-Transfer-Encoding: quoted-printable\r
  47 X-BeenThere: notmuch@notmuchmail.org\r
  48 X-Mailman-Version: 2.1.13\r
  49 Precedence: list\r
  50 Reply-To: sshilovsky@gmail.com\r
  51 List-Id: "Use and development of the notmuch mail system."\r
  52         <notmuch.notmuchmail.org>\r
  53 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
  54         <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
  55 List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
  56 List-Post: <mailto:notmuch@notmuchmail.org>\r
  57 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
  58 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
  59         <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
  60 X-List-Received-Date: Tue, 07 Oct 2014 11:00:52 -0000\r
  61 \r
  62 Lets consider messages first.\r
  63 \r
  64 As far as I get there is no straightforward\r
  65 notmuch_messages_move_to_previous. One can usually implement such\r
  66 behaviour with caching previous messages which is slightly inefficient\r
  67 in memory consumption terms.\r
  68 \r
  69 But we can sort messages either date asc or date desc.\r
  70 \r
  71 Suppose, we're currently at the 1000th message in query "tag:whatever".\r
  72 \r
  73 So if we need to go to the previous message we could do something like\r
  74 \r
  75     notmuch search --sort=3Doldest-first tag:whatever and \\r
  76         date:..<here is the date of the 1000th message>\r
  77 \r
  78 This query's result should start with our 1000th message following its\r
  79 previous message (in terms of the original request). So backward\r
  80 scrolling with no cache looks to be at least possible.\r
  81 \r
  82 Any idea of would that be fine? Is it possible to implement similar\r
  83 thing at low-level?\r
  84 \r
  85 --=20\r
  86 =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC,\r
  87 =D0=A1=D0=B5=D1=80=D0=B3=D0=B5=D0=B9 =D0=A8=D0=B8=D0=BB=D0=BE=D0=B2=D1=81=\r
  88 =D0=BA=D0=B8=D0=B9\r
  89 Sergei Shilovsky\r