about summary refs log tree commit homepage
path: root/Documentation/lei-overview.pod
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2021-03-30 09:39:27 +0000
committerEric Wong <e@80x24.org>2021-03-30 19:15:17 +0000
commit54da988cfb049ea2ffcc7abeaa3d026224656516 (patch)
tree69b3385acbbade2ce1736937864fefa49cf3c940 /Documentation/lei-overview.pod
parentb40f4f1f81f79577e19e9926e14979625303eb59 (diff)
downloadpublic-inbox-54da988cfb049ea2ffcc7abeaa3d026224656516.tar.gz
I've decided "tag" is a better verb since it seems more
widely-used term for associating metadata with data.

Not only is it analogous to the "notmuch tag" command, but
also makes sense when compared to tooling for manipulating
metadata for non-mail data (e.g. audio metadata tags).

There's even a Wikipedia entry for it:
https://en.wikipedia.org/wiki/Tag_(metadata)
whereas "mark" is used in the description, but has no
entry of its own with regards to metadata.
Diffstat (limited to 'Documentation/lei-overview.pod')
-rw-r--r--Documentation/lei-overview.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/lei-overview.pod b/Documentation/lei-overview.pod
index f74a228a..c1f952c9 100644
--- a/Documentation/lei-overview.pod
+++ b/Documentation/lei-overview.pod
@@ -33,7 +33,7 @@ Show message with the git blob OID of 59ec517f9.  If a message with
 that OID isn't found, check if the current git repository has the
 blob, trying to reconstruct it from a message if needed.
 
-=item $ lei blob 59ec517f9 | lei mark - -F eml +kw:flagged +L:next
+=item $ lei blob 59ec517f9 | lei tag - -F eml +kw:flagged +L:next
 
 Set the "flagged" keyword and "next" label on the message with the
 blob OID of 59ec517f9.