about summary refs log tree commit homepage
path: root/Documentation
diff options
context:
space:
mode:
authorEric Wong <e@80x24.org>2021-02-25 10:11:06 +0000
committerEric Wong <e@80x24.org>2021-02-26 02:35:50 +0000
commit232f8e376fe2856c8d34092e33a2c0750734c285 (patch)
tree63ff6bc73aad8c09cfaf15c3782f30d47764c056 /Documentation
parentd3934150d6fef1ce90ac44298e58474913028d32 (diff)
downloadpublic-inbox-232f8e376fe2856c8d34092e33a2c0750734c285.tar.gz
This can be used to quickly distinguish messages which were
direct hits when doing thread expansion vs messages that
were merely part of the same thread.

This is NOT mairix-derived behavior, but I occasionally found
it useful when looking at results in an MUA to know whether
a message was a direct hit or not.

This makes "-t" consistent with non-"-t" cases as far as keyword
reading goes.
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/lei-q.pod8
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/lei-q.pod b/Documentation/lei-q.pod
index 75fdc613..0959beac 100644
--- a/Documentation/lei-q.pod
+++ b/Documentation/lei-q.pod
@@ -79,6 +79,14 @@ Augment output destination instead of clobbering it.
 
 Return all messages in the same thread as the actual match(es).
 
+Using this twice (C<-tt>) sets the C<flagged> (AKA "important")
+on messages which were actual messages.  This is useful to distinguish
+messages which were direct hits from messages which were merely part
+of the same thread.
+
+TODO: Warning: this flag may become persistent and saved in
+lei/store unless an MUA unflags it!  (Behavior undecided)
+
 =item -d STRATEGY, --dedupe=STRATEGY
 
 Strategy for deduplicating messages: C<content>, C<oid>, C<mid>, or