From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: VA <dev+notmuch@indigo.re>, notmuch@notmuchmail.org
Subject: Re: [PATCH] python: bind add_property/remove_property and related methods
Date: Tue, 11 Jun 2019 10:31:57 +0100 [thread overview]
Message-ID: <87sgsgeacy.fsf@fifthhorseman.net> (raw)
In-Reply-To: <63593141-a89a-a086-4e80-a314a095946f@indigo.re>
[-- Attachment #1: Type: text/plain, Size: 2276 bytes --]
On Mon 2019-06-10 14:55:48 +0200, VA wrote:
> Le 09/06/2019 à 21:58, Daniel Kahn Gillmor a écrit :
>> We do expose this functionality in the library, so it's not the end of
>> the world to expose it in the python bindings, but i do worry a little
>> bit about encouraging people to fiddle with markers set by the indexer.
>
> Conflicts could be easily avoided by recommending a prefix like
> "x-<project>-" to property names (see link below).
That makes sense -- we'd also want to encourage projects to note their
project name someplace central; having a namespace registry helps to
avoid collisions, and also helps to advertise the projects that derive
from notmuch :)
maybe update the wiki for that?
That said, if a given property is concretely useful, i don't want to
have it languish permanently in the x-<project>- namespace, or to force
users to adopt that particular MUA to use it -- i'd like to make it
available to all the notmuch-derived mail user agents. Maybe that
happens only when the feature gets added to libnotmuch itself? How do
we incentivize projects into getting that kind of widely-useful feature
into the libnotmuch mainstream instead of having it as a differentiating
factor for their specific MUA?
how should we think about managing these parts of the ecosystem?
> I'm writing a MUA, and am using properties to store an excerpt of each
> message, so the MUA can show a preview of each message (like the Gmail
> web app, or Apple mail client).
cool, this sounds super useful. if you have a chance to write up how
you're generating/selecting this extract, i'd love to read more.
> Some pleople recently suggested sync info or other MUA metadata:
> https://notmuchmail.org/pipermail/notmuch/2019/027403.html
Thanks for the pointer, i'd missed that thread back in February.
I agree that there's sufficient interest to take this use case more
seriously.
> I took the documentation from notmuch.h but only edited to be consistent
> with Python. Those warnings should also be added in notmuch.h, right?
Yeah, that's probably a good idea. Is it asking too much to ask you to
update notmuch.h as well when you resubmit this series?
Thanks for helping make notmuch better!
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-06-11 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 15:37 [PATCH] python: bind add_property/remove_property and related methods VA
2019-06-09 19:58 ` Daniel Kahn Gillmor
2019-06-10 12:55 ` VA
2019-06-11 9:31 ` Daniel Kahn Gillmor [this message]
2019-06-14 20:34 ` VA
2019-06-15 23:52 ` Daniel Kahn Gillmor
2019-06-17 4:31 ` Daniel Kahn Gillmor
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=87sgsgeacy.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=dev+notmuch@indigo.re \
--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).