From 0838a8f458b45ccf568c83343fec57e5d064eb21 Mon Sep 17 00:00:00 2001 From: Kevin McCarthy Date: Thu, 3 Nov 2022 14:01:12 -0700 Subject: Clarify $uncollapse_new documentation. Indicate more clearly it is talking about "delivered" messages that arrive in a thread, not about the unread-status of those messages. --- init.h | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/init.h b/init.h index 08283eb1..e160d3d3 100644 --- a/init.h +++ b/init.h @@ -4746,10 +4746,11 @@ struct option_t MuttVars[] = { { "uncollapse_new", DT_BOOL, R_NONE, {.l=OPTUNCOLLAPSENEW}, {.l=1} }, /* ** .pp - ** When \fIset\fP, Mutt will automatically uncollapse any collapsed thread - ** that receives a new message. When \fIunset\fP, collapsed threads will - ** remain collapsed. the presence of the new message will still affect - ** index sorting, though. + ** When \fIset\fP, Mutt will automatically uncollapse any collapsed + ** thread that receives a newly delivered message. When + ** \fIunset\fP, collapsed threads will remain collapsed. The + ** presence of the newly delivered message will still affect index + ** sorting, though. */ { "use_8bitmime", DT_BOOL, R_NONE, {.l=OPTUSE8BITMIME}, {.l=0} }, /* -- cgit v1.2.3