unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: rhn <nomumali.rhn@porcupinefactory.org>
To: VA <dev+notmuch@indigo.re>
Cc: Matt Armstrong <marmstrong@google.com>, notmuch@notmuchmail.org
Subject: Re: On properties and the notmuch CLI
Date: Sun, 17 Feb 2019 21:22:44 +0100	[thread overview]
Message-ID: <20190217212244.16f7c980.rhn@porcupinefactory.org> (raw)
In-Reply-To: <c166745e-9a80-6fd7-6d8e-04febd3c673f@indigo.re>

On Sun, 17 Feb 2019 21:14:33 +0100
VA <dev+notmuch@indigo.re> wrote:

> Le 17/02/2019 à 20:35, Matt Armstrong a écrit :
> > As far as the risk of property name collisions, perhaps encourage an
> > x-<project>- prefix convention for all properties not registered with
> > the notmuch project?  That seems to have served well enough for email
> > headers.  
> 
> I'm interested in the answer. I'm writing a graphical MUA (alpha stage) 
> and am using property "x-lierre-excerpt" to store a pure-text excerpt of 
> each email, so it can be displayed in the messages list without having 
> to open the whole email file.

I'm with the others; writing a GUI client [0] I found that querying would be much more aligned with what I need if I could search arbitrary data (headers or notes).

Cheers,
rhn

[0] https://gitlab.com/rhn_mk1/quemail/

  reply	other threads:[~2019-02-17 20:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 19:35 On properties and the notmuch CLI Matt Armstrong
2019-02-17 20:14 ` VA
2019-02-17 20:22   ` rhn [this message]
2019-02-18  0:25 ` 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=20190217212244.16f7c980.rhn@porcupinefactory.org \
    --to=nomumali.rhn@porcupinefactory.org \
    --cc=dev+notmuch@indigo.re \
    --cc=marmstrong@google.com \
    --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).