Re: [PATCH 0/5] lib: make folder: prefix literal

Subject: Re: [PATCH 0/5] lib: make folder: prefix literal

Date: Fri, 24 Jan 2014 19:21:18 -0400

To: Austin Clements, Jani Nikula, notmuch@notmuchmail.org

Cc:

From: David Bremner


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

Thread: