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 6B81E6DE0247 for ; Tue, 30 Jan 2018 20:05:55 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.01 X-Spam-Level: X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[AWL=-0.010] 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 sHLQNir-DTEh for ; Tue, 30 Jan 2018 20:05:54 -0800 (PST) Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by arlo.cworth.org (Postfix) with ESMTPS id 967556DE0246 for ; Tue, 30 Jan 2018 20:05:54 -0800 (PST) Received: from fifthhorseman.net (ool-6c3a0662.static.optonline.net [108.58.6.98]) by che.mayfirst.org (Postfix) with ESMTPSA id EB448F99B; Tue, 30 Jan 2018 23:05:49 -0500 (EST) Received: by fifthhorseman.net (Postfix, from userid 1000) id 15D3120251; Tue, 30 Jan 2018 22:04:18 -0500 (EST) From: Daniel Kahn Gillmor To: Matthew Lear , Jani Nikula Cc: notmuch@notmuchmail.org Subject: Re: trouble searching with unix timestamps In-Reply-To: References: <874ln4zm7x.fsf@nikula.org> Date: Tue, 30 Jan 2018 22:04:17 -0500 Message-ID: <87bmhaafv2.fsf@fifthhorseman.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.24 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, 31 Jan 2018 04:05:55 -0000 On Mon 2018-01-29 16:13:38 +0000, Matthew Lear wrote: > [ Jani wrote: ] >> Alternatively, you can use @ in date: queries, although this >> seems to be completely undocumented: > > I guess this relates to similar syntax requirements of date -d in that a > unix timestamp is required to be preceded by an @ agreed, it seems in line with that. Matthew, since you've been reading the docs there most recently, maybe you'd be up for sending a patch to make sure this feature is findable in the documentation? --dkg