From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 53AB36DE16E4 for ; Thu, 15 Feb 2018 10:18:40 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.019 X-Spam-Level: X-Spam-Status: No, score=-0.019 tagged_above=-999 required=5 tests=[AWL=-0.019] 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 dYA34fzHsV5i for ; Thu, 15 Feb 2018 10:18:39 -0800 (PST) Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by arlo.cworth.org (Postfix) with ESMTPS id 82D466DE16A6 for ; Thu, 15 Feb 2018 10:18:39 -0800 (PST) Received: from fifthhorseman.net (unknown [38.109.115.130]) by che.mayfirst.org (Postfix) with ESMTPSA id 9527EF99A; Thu, 15 Feb 2018 13:18:35 -0500 (EST) Received: by fifthhorseman.net (Postfix, from userid 1000) id 9213420315; Thu, 15 Feb 2018 11:06:16 -0500 (EST) From: Daniel Kahn Gillmor To: Brian Sniffen Cc: Notmuch Mail Subject: Re: a temporary nmweb view of notmuch mailing list archive In-Reply-To: <878tbzs39i.fsf@fifthhorseman.net> References: <87o9l4yt4w.fsf@fifthhorseman.net> <87a7wivlbj.fsf@fifthhorseman.net> <6E19C3B1-9D1A-46E4-984B-DE5B97D13407@evenmere.org> <878tbzs39i.fsf@fifthhorseman.net> Date: Thu, 15 Feb 2018 11:06:16 -0500 Message-ID: <87y3junsp3.fsf@fifthhorseman.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.26 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: Thu, 15 Feb 2018 18:18:40 -0000 On Sun 2018-02-11 15:03:05 -0500, Daniel Kahn Gillmor wrote: > On Sat 2018-02-10 13:57:34 -0500, Brian Sniffen wrote: >> It looks like you have thread next/pref turned off. Is there a reason, >> including the reason that I hadn’t documented it? > > nope, i just didn't fiddle with it much beyond setting it up and trying > to make sure the system integration didn't seem wildly dangerous. happy > to tweak it further, and will take any recommendations. :) hm, looking into this a little bit, i don't actually see how to turn it on. if you've got pointers or documentation, i would be happy to read it. --dkg