From: Alessandro Bertulli <alessandro.bertulli96@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Strangely similar docstrings for mu4e
Date: Tue, 06 Sep 2022 12:22:20 +0200 [thread overview]
Message-ID: <875yi0bxy1.fsf@gmail.com> (raw)
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
next reply other threads:[~2022-09-06 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-06 10:22 Alessandro Bertulli [this message]
2022-09-06 12:34 ` Strangely similar docstrings for mu4e Po Lu
2022-09-06 13:28 ` Alessandro Bertulli
2022-09-08 12:18 ` Alessandro Bertulli
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yi0bxy1.fsf@gmail.com \
--to=alessandro.bertulli96@gmail.com \
--cc=help-gnu-emacs@gnu.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).