unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Michal Sojka <sojkam1@fel.cvut.cz>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [RFC] database: get and set mapping of dovecot compatible maildir	keywords
Date: Sat, 27 Sep 2014 21:43:53 +0200	[thread overview]
Message-ID: <87iok8vog6.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <1411805835-3563-1-git-send-email-david@tethera.net>

Hi David,

On Sat, Sep 27 2014, David Bremner wrote:
> A future modification of notmuch_message_tags_to_maildir_flags and
> notmuch_message_maildir_flags_to_tags could allow 26 more tags to be
> synced via maildir.
> ---
>
> I'm not sure if this is worth pursuing or not, but I thought I'd toss
> it out there.  On IRC the other day the topic of syncing IMAP keywords
> to notmuch tags came up again, in particular the dovecot variant that
> maps 26 user defined keywords to characters a-z on the end of the
> maildir info.  One roadblock I saw at the time was the need for
> configuration of mapping of letters to tags.  This patch is the result
> of my realizing that at least that part is not hard (unlike the rabbit
> hole we seemed to get into for e.g. log configuration).
>
> Some downsides of this approach are fairly obvious
>
>     - only 26 tags. It turns out I don't have that many non-nmbug tags
>       that I really care about. YMMV, of course.
>
>     - nonstandard. this won't roundtrip via offlineimap (unless
>       offlineimap is modified).  Directly syncing the maildir or using
>       some dovecot specific syncer would work.
>
> Some upsides are:
>
>     - Provides an IMAP bridge solution; compatible with dovecot; my
>       impression is this is the most common imap solution among
>       notmuch users.  
>     - relatively simple implementation, just need to
>       update the maildir name synching routines. Of course no
>       implementation is as simple as possible
>
>  lib/database.cc | 61 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++

I'd prefer having the mapping stored in the config file rather than in
the database. This would allow me to synchronize the configuration
between multiple computers. Would there be some benefit of having the
mapping (also) in the database?

-Michal

  reply	other threads:[~2014-09-27 19:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-27  8:17 [RFC] database: get and set mapping of dovecot compatible maildir keywords David Bremner
2014-09-27 19:43 ` Michal Sojka [this message]
2014-09-28  6:27   ` David Bremner
2014-09-28  6:36     ` David Bremner
2014-09-28 18:28   ` David Bremner
2014-09-28 18:28     ` [WIP 1/3] util: move chomp_newline to string-util.h David Bremner
2014-09-28 18:28     ` [WIP 2/3] cli/insert: move several file/directory manipulation routines into a new util file David Bremner
2014-09-28 18:28     ` [WIP 3/3] lib: add configuration framework David Bremner

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=87iok8vog6.fsf@steelpick.2x.cz \
    --to=sojkam1@fel.cvut.cz \
    --cc=david@tethera.net \
    --cc=notmuch@notmuchmail.org \
    /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).