From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: is "lei mark" a good name?
Date: Thu, 25 Mar 2021 21:54:44 -0400 [thread overview]
Message-ID: <87tuoysmqj.fsf@kyleam.com> (raw)
In-Reply-To: <20210325052229.GA6447@dcvr>
Eric Wong writes:
> It can set/unset volatile metadata for any number of messages.
>
> "Volatile metadata" being "labels" (aka "mailboxes" in
> JMAP-speak) and "keywords" (seen|flagged|answered|...),
> (aka "flags" in IMAP/Maildir-speak).
>
> "lei mark +kw:seen" # makes sense
> "lei mark +L:some-folder-name" # might sound odd...
>
>
> AFAIK, notmuch uses "notmuch tag" which combines both labels
> and keywords into one thing: "tags". But I'm also not a
> notmuch user...
(I am, though I still might be wrong.) Notmuch allows arbitrary tags to
be associated with message IDs. It has some automatic tags like
"attachment", "encrypted", and "signed" that it adds when indexing. By
default, it also syncs some maildir flags to its tags (e.g., "F ->
flagged", "R -> replied", "No S -> unread").
As far as I understand, tags are never connected up to the maildir
folder/location, though Notmuch does support a separate "folder:..."
search term.
So, I guess in JMAP terms, Notmuch tags would be "mailboxes" (a subset
of which are synced with maildir flags).
> Would "lei tag" be better?
Neither one really jumps out to me as better. "mark" sounds fine to me,
and I don't find "tag" any more or less odd for the +L case above.
> Anything else?
Nothing comes to mind.
next prev parent reply other threads:[~2021-03-26 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 5:22 is "lei mark" a good name? Eric Wong
2021-03-26 1:54 ` Kyle Meyer [this message]
2021-03-26 9:48 ` Eric Wong
2021-03-28 2:21 ` Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tuoysmqj.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=e@80x24.org \
--cc=meta@public-inbox.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.
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).