From: David Bremner <david@tethera.net>
To: Austin Clements <aclements@csail.mit.edu>, Jani Nikula <jani@nikula.org>, 
	notmuch@notmuchmail.org
Subject: Re: [PATCH 0/5] lib: make folder: prefix literal
In-Reply-To: <87y525m649.fsf@awakening.csail.mit.edu>
References: <cover.1389304779.git.jani@nikula.org>
	<87y525m649.fsf@awakening.csail.mit.edu>
User-Agent: Notmuch/0.17+35~g3b36898 (http://notmuchmail.org) Emacs/24.3.1
	(x86_64-pc-linux-gnu)
Date: Fri, 24 Jan 2014 19:21:18 -0400
Message-ID: <874n4totjl.fsf@zancas.localnet>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: list

Austin Clements <aclements@csail.mit.edu> writes:

> On Thu, 09 Jan 2014, Jani Nikula <jani@nikula.org> wrote:
>
> I strongly disagree with requiring the cur/new component.  The cur/new
> directory is an internal implementation detail of Maildir (and a rather
> broken one at that) and no more a part of the "folder" of a piece of
> mail than its final file name component.  It's also the less obvious
> user interface; if we require the cur/new component, we *will* get
> people asking why their folder searches aren't working, but if we strip
> the cur/new component, nobody will be surprised.
>

My gut instinct agrees with Austin here, at least for a prefix named
"folder". Some factors I remember

- are there some corner cases for people not using Maildir?
- isn't there some information encoded in whether a message is in cur or
  new? there was some discussion of mutt presenting this information

d