Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id F054B431FBD for ; Sat, 25 Jan 2014 03:52:41 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 GWQtX8kkLsJ6 for ; Sat, 25 Jan 2014 03:52:35 -0800 (PST) Received: from guru.guru-group.fi (guru.guru-group.fi [46.183.73.34]) by olra.theworths.org (Postfix) with ESMTP id B10B2431FBC for ; Sat, 25 Jan 2014 03:52:35 -0800 (PST) Received: from guru.guru-group.fi (localhost [IPv6:::1]) by guru.guru-group.fi (Postfix) with ESMTP id 501541000B3; Sat, 25 Jan 2014 13:52:31 +0200 (EET) From: Tomi Ollila To: Jani Nikula , Austin Clements , notmuch@notmuchmail.org Subject: Re: [PATCH 0/5] lib: make folder: prefix literal In-Reply-To: <87ob30fhhq.fsf@nikula.org> References: <87y525m649.fsf@awakening.csail.mit.edu> <87r47wfltb.fsf@nikula.org> <87ob30fhhq.fsf@nikula.org> User-Agent: Notmuch/0.17+41~g8e7fabf (http://notmuchmail.org) Emacs/24.3.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ MIME-Version: 1.0 Content-Type: text/plain 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, 25 Jan 2014 11:52:42 -0000 On Sat, Jan 25 2014, Jani Nikula wrote: > On Sat, 25 Jan 2014, Tomi Ollila wrote: >> On Sat, Jan 25 2014, Jani Nikula wrote: >>> Perhaps we need to have two prefixes, one of which is the literal >>> filesystem folder and another which hides the implementation details, >>> like I mentioned in my mail to Peter [1]. But consider this: my proposed >>> implementation does cover *all* use cases. >> >> I challenge that with my use case: my mails are arranged as follows: > > [snip] > >> For me the current folder: works as I don't have collisions. > > Fair enough, your use case would be *very inconvenient* with the > proposed changes to the folder: prefix, *regardless* of whether the leaf > cur/new is indexed and required or not. > > (Very inconvenient, or practically impossible, as you'd have to include > all those 01..ff directories in your searches.) Well, I currently run notmuch via a wrapper anyway, I can make it expand folder:foo to '(' folder:foo/00 or folder:foo/01 or ... folder:foo/ff ')' ;) >> For me a folder: search which would just work as a prefix i.e. match >> anything under given directory hierarchy would work best. > > Indeed. Your use case is not an argument in whether cur/new should be > included or not. > > That "recursive folder prefix" suggestion is, I think, incompatible with > the requirements for the literal folder: prefix we've been considering. Yes, I am late in this discussion as I realized that just today. I don't want to hinder progress there... > > BR, > Jani. Tomi