[RFC][PATCH] tags_to_maildir_flags: Add option to not move messages from "new/" to "cur/"

Carl Worth cworth at cworth.org
Mon Jun 27 14:15:33 PDT 2011


On Fri, 24 Jun 2011 22:34:03 +0200, Louis Rilling <l.rilling at av7.net> wrote:
> Maybe the alternate solution could consist in simply not renaming emails having
> no flags to be changed (Currently notmuch_message_tags_to_maildir_flags()
> unconditionally moves messages from new/ to cur/). This would even lead to a
> shorter patch :) Do you think that this would be acceptable?

That could very well be acceptable.

A user would have to carefully configure notmuch to get this
behavior. Options for that could include the following in
~/.notmuch-config:

	[maildir]
	synchronize_flags=false

Or:

	[new]
	tags=

I think that if either of the above options are set that notmuch won't
need to change the message's filename. And in that case, I would feel
that it wouldn't be entirely unreasonable for notmuch to leave message
in the "new" directory.

This allows the user to effectively setup a mail-store that notmuch
treats as more-or-less "read only" and that seems like a useful thing.

Please experiment with that and feel free to send the patch or patches
that you generate.

Thanks again, and I hope you can find a way to make notmuch work for
you.

-Carl
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20110627/76c92c7b/attachment.pgp>


More information about the notmuch mailing list