From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Peter John Hartman <peterjohnhartman@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: [PATCH] Have --format=mbox insert Status:
Date: Mon, 07 Feb 2011 10:04:41 +0100 [thread overview]
Message-ID: <87sjw0xljq.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <20110206202614.GA3743@triltoucheee.wireless.utoronto.ca>
On Sun, 06 Feb 2011, Peter John Hartman wrote:
> > Hi Peter,
> >
> > would this output be compatible with all mbox consumers or only with
> > those who expect the Status: line? If the latter, we would probably want
> > a command line option to enable this.
>
> Hi,
>
> As far as I've been able to tell everyone respects RO in mbox, so I don't
> see this as a problem. In any case, having the Status: line there won't
> cause problems if an MUA doesn't recognize it. That said, it would be nice
> to think of a place to allow the user to easily "map" notmuch tags to
> Status: or X-Status: rules, perhaps in the notmuch config file as follows:
>
> [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.
> 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.
> Reference: http://wiki.dovecot.org/MailboxFormat/mbox:
> Status: R (\Seen) and O (non-\Recent) flags
> X-Status: A (\Answered), F (\Flagged), T (\Draft) and D (\Deleted) flags
>
> (I know that alpine/pine and mutt recognize at least RO, and probably AFTD.)
-Michal
next prev parent reply other threads:[~2011-02-07 9:04 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 [this message]
2011-02-07 14:22 ` Peter John Hartman
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=87sjw0xljq.fsf@steelpick.2x.cz \
--to=sojkam1@fel.cvut.cz \
--cc=notmuch@notmuchmail.org \
--cc=peterjohnhartman@gmail.com \
/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).