From: David Bremner <david@tethera.net>
To: notmuch@notmuchmail.org
Subject: library config API
Date: Sat, 23 Jan 2016 10:59:53 -0400 [thread overview]
Message-ID: <1453561198-2893-1-git-send-email-david@tethera.net> (raw)
This is the third revision of this series, and I think the first two
patches are ready for serious review.
Some things to think about with respect to the CLI patches
- Should we include a "version" line at the top of the dump? Currently this is unused, but that
depends on the format being auto detectable?
- Should config info be included by default in the dump output?
- Should we restore config info by default?
- How about the usual bikeshedding about argument names? I'm loath to
spend time on docs until after this.
I guess a global question is what do we need this API / feature for. I
can think of three things so far
- tag aliases [1]
- making the location of the mail tree configurable (i.e. allowing
mailtree and database to live in different places).
- Some things like excludes and maildir synchonization are natural to
have in common between all clients.
A natural question is why not provide a library API to access
.notmuch-config? Having a plain text representation of the
configuration (without the extra step of dumping it) is obviously
attractive, but
- We would need to build some locking / synchronization to prevent
various clients and interactive text editors from stomping on each
other. This we have for free by using xapian metadata.
- We'd also have to provide our own key/value datastructure.
- At least for tag aliases, I think there is a second argument that
this information part of the users tagging state, and should be
backed up as part of the normal dump / restore process.
[1]: id:87mvsd7cxr.fsf@zancas.localnet
next reply other threads:[~2016-01-23 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 14:59 David Bremner [this message]
2016-01-23 14:59 ` [PATCH 1/5] lib: provide config API David Bremner
2016-01-23 14:59 ` [PATCH 2/5] lib: config list iterators David Bremner
2016-01-23 14:59 ` [PATCH 3/5] CLI: add print_status_database David Bremner
2016-01-23 14:59 ` [PATCH 4/5] CLI: add optional config data to dump output David Bremner
2016-01-23 14:59 ` [PATCH 5/5] CLI: optionally restore config data David Bremner
2016-03-12 12:31 ` library config api v4 David Bremner
2016-03-12 12:31 ` [PATCH 1/6] lib: provide config API David Bremner
2016-03-12 12:31 ` [PATCH 2/6] lib: config list iterators David Bremner
2016-03-12 12:31 ` [PATCH 3/6] CLI: add print_status_database David Bremner
2016-03-12 12:31 ` [PATCH 4/6] CLI: add optional config data to dump output David Bremner
2016-03-12 12:31 ` [PATCH 5/6] CLI: optionally restore config data David Bremner
2016-03-12 12:31 ` [PATCH 6/6] WIP: support XDG database directory David Bremner
2016-03-14 18:06 ` Tomi Ollila
2016-03-19 20:19 ` 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=1453561198-2893-1-git-send-email-david@tethera.net \
--to=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).