From: Peter John Hartman <peterjohnhartman@gmail.com>
To: Michal Sojka <sojkam1@fel.cvut.cz>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] Have --format=mbox insert Status:
Date: Mon, 7 Feb 2011 09:22:44 -0500 [thread overview]
Message-ID: <20110207142244.GA10529@triltoucheee.wireless.utoronto.ca> (raw)
In-Reply-To: <87sjw0xljq.fsf@steelpick.2x.cz>
On Mon, Feb 07, 2011 at 10:04:41AM +0100, Michal Sojka wrote:
> > [mbox]
> > synchronize_flags=true
>
> I would call this differently - perhaps 'export_flags'. In maildir
> section of config file synchronize_flags has the meaning of
> bi-directional synchronization and this is only uni-directional.
I agree.
>
> > xstatus_A=replied
> > xstatus_F=flagged
> > xstatus_T=draft
> > #xstatus_D=deleted
> > status_R=-unread
> > status_O=unread
>
> Is it necessary for this to be configurable? Given the list bellow, it
> seems it is already defined by the "standard", so users would rarely
> want different mapping.
I agree. In fact, I would think we don't need to add anything to the
notmuch config file at all. I can't think of a use case where we'd want
show --format=mbox to *not* also replicate/export the Status/X-Status tags.
I personally don't use X-Status: but I don't have a problem with my patch
being patched to include them. It won't cause any problems.
Peter
--
sic dicit magister P
PhD Candidate
Collaborative Programme in Ancient and Medieval Philosophy
University of Toronto
http://individual.utoronto.ca/peterjh
prev parent reply other threads:[~2011-02-07 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 23:47 [PATCH] Have --format=mbox insert Status: Peter John Hartman
2011-02-05 23:08 ` Michal Sojka
2011-02-06 20:26 ` Peter John Hartman
2011-02-07 9:04 ` Michal Sojka
2011-02-07 14:22 ` Peter John Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110207142244.GA10529@triltoucheee.wireless.utoronto.ca \
--to=peterjohnhartman@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=sojkam1@fel.cvut.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).