Strangely similar docstrings for mu4e

Strangely similar docstrings for mu4e

[Alessandro Bertulli]

Hi all!

Quick question. On my mu4e headers buffer, I see threads grouped with
characters like |, |>, L, o. I can get more or less the sense of them,
and they are usually very useful. However, my question is: what is the
difference between L and o? Using apropos I find:

mu4e-headers-thread-first-child-prefix
  Variable: Prefix for messages in sub threads that do not have a
            following sibling.
  Value: ("o " . "⚬ ")
  Properties: variable-documentation
mu4e-headers-thread-last-child-prefix
  Variable: Prefix for messages in sub threads that do not have a
            following sibling.
  Value: ("L" . "└ ")
  Properties: variable-documentation

Why are the two docstrings the same?

Alessandro

Re: Strangely similar docstrings for mu4e

[Po Lu]

Alessandro Bertulli <alessandro.bertulli96@gmail.com> writes:

>   Variable: Prefix for messages in sub threads that do not have a
>             following sibling.

I guess the "following" here is a copy error and should be "preceeding"
instead?  (I don't use mu4e, so this could be terribly wrong.)

Re: Strangely similar docstrings for mu4e

[Alessandro Bertulli]

>>   Variable: Prefix for messages in sub threads that do not have a
>>             following sibling.
>
> I guess the "following" here is a copy error and should be "preceeding"
> instead?  (I don't use mu4e, so this could be terribly wrong.)

Probably, but from the text you quoted it's unclear which variable you
are referring to, sorry 😅

Alessandro

Re: Strangely similar docstrings for mu4e

[Alessandro Bertulli]

Sorry for the late reply!

> I guess the "following" here is a copy error and should be "preceeding"
> instead?  (I don't use mu4e, so this could be terribly wrong.)

Probably. I'm going to open an issue, thanks.

-- 
Alessandro Bertulli