From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 1A4CE431E82 for ; Sat, 16 Nov 2013 00:05:37 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0.201 X-Spam-Level: X-Spam-Status: No, score=0.201 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 KE8OjEhVxGhX for ; Sat, 16 Nov 2013 00:05:29 -0800 (PST) Received: from mail-we0-f176.google.com (mail-we0-f176.google.com [74.125.82.176]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by olra.theworths.org (Postfix) with ESMTPS id 5A2A6431E64 for ; Sat, 16 Nov 2013 00:05:29 -0800 (PST) Received: by mail-we0-f176.google.com with SMTP id w62so4361723wes.21 for ; Sat, 16 Nov 2013 00:05:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:in-reply-to:references; bh=RO6XgD3/AJDm0mILG0+j50kTgKgOVvep8DnbjF08OQE=; b=UNEDbL5wUvXXnbJI+aeM5Szt4zW4wnIoH9+3STcsm90QnMvpeL92qo2cwB4fPiUY1D V/8bLVsd58h9p4VT0nJhctS1kfJEnkQ4YGXQ9hmqC1pvCYTdTPQuvIJO3hKUuVF8b4DL rv31yDX/stZFamLVmURpsXDjzHIuhh6Jomax0TQ2yB4A34qQKM9ixNkCZj+4Z2AdcFrt rWtK/K+ucApSybm4qIZjsLnoxcKGssqanEn2SwUPOk1lVR2GTSmjOHZKf+OOuWUz91oC c+M/V2/bfoM80BNpx0nSr8A/1FNHwaA3+9VfSk39lGg53nhphIlLw1WIIhb2C3PqTFoq KJaQ== X-Received: by 10.180.205.194 with SMTP id li2mr9836366wic.57.1384589125402; Sat, 16 Nov 2013 00:05:25 -0800 (PST) Received: from localhost (93-97-24-31.zone5.bethere.co.uk. [93.97.24.31]) by mx.google.com with ESMTPSA id e1sm2737376wij.6.2013.11.16.00.05.24 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Sat, 16 Nov 2013 00:05:24 -0800 (PST) From: Mark Walters To: notmuch@notmuchmail.org Subject: [PATCH v2] News for tree-view Date: Sat, 16 Nov 2013 08:05:16 +0000 Message-Id: <1384589116-23155-1-git-send-email-markwalters1009@gmail.com> X-Mailer: git-send-email 1.7.9.1 In-Reply-To: References: 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, 16 Nov 2013 08:05:37 -0000 --- Update following Tomi's suggestions. Best wishes Mark NEWS | 32 ++++++++++++++++++++++++++++++++ 1 files changed, 32 insertions(+), 0 deletions(-) diff --git a/NEWS b/NEWS index 9434af9..d0d5300 100644 --- a/NEWS +++ b/NEWS @@ -33,6 +33,38 @@ Improved `notmuch new` performance for unchanged folders Emacs Interface --------------- +`notmuch-tree` (formerly `notmuch-pick`) has been added to mainline + + `notmuch-tree` is a threaded message view for the emacs + interface. Each message is one line in the results and the thread + structure is shown using UTF-8 box drawing characters (similar to + Mutt's threaded view). It comes between search and show in terms of + amount of output and can be useful for viewing both single threads + and multiple threads. + + Using `notmuch-tree` + + The main key entries to notmuch tree are + + 'z' enter a query to view using notmuch tree (works in hello, + search, show and tree mode itself) + + 'Z' view the current query in tree notmuch tree (works from search + and show) + + Once in tree mode, keybindings are mostly in line with the rest of + notmuch and are all viewable with '?' as usual. + + Customising `notmuch-tree` + + `notmuch-tree` has several customisation variables. The most + significant is the first notmuch-tree-show-out which determines the + behaviour when selecting a message (with RET) in tree view. By + default tree view uses a split window showing the single message in + the bottom pane. However, if this option is set then it views the + whole thread in the complete window jumping to the selected message + in the thread. In either case command-prefix selects the other option. + Tagging threads in search is now race-free Previously, adding or removing a tag from a thread in a search -- 1.7.9.1