From: Simon Josefsson <jas@extundo.com>
Cc: The Gnus Mailing List <ding@gnus.org>
Subject: Re: WIBNI gnus-article-wash-status's result was documented
Date: Fri, 12 Oct 2001 19:08:39 +0200 [thread overview]
Message-ID: <ilusncowzu0.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <m1bwv20gafo.fsf@blackbird.mitre.org> (david.goldberg6@verizon.net's message of "Fri, 12 Oct 2001 11:11:39 -0400")
david.goldberg6@verizon.net (David S. Goldberg) writes:
> I searched the info files, but it appears the only place to find out
> what those letters in the article mode line mean are by reading the
> source.
I added this to the documentation:
`w'
The "wash status" of the article. This is a short string
with one character for each possible article wash operation
that may have been performed. The characters and their
meaning:
`c'
Displayed when cited text is hidden in the article
buffer.
`h'
Displayed when headers are hidden in the article buffer.
`p'
Displayed when article is digitally signed or encrypted,
and Gnus has hidden the security headers. (N.B. does
not tell anything about security status, i.e. good or
bad signature.)
`s'
Displayed when the signature has been hidden in the
Article buffer.
`o'
Displayed when Gnus has treated overstrike characters in
the article buffer.
`e'
Displayed when Gnus has treated emphasised strings in
the article buffer.
> And the source is confusing. I have all treatment turned on, so I'd
> expect to see the bits for overstrike and emphasis on nearly all
> articles, but they're always blank. When should they be turned on?
> Also, I get an `h' in there much of the time, presumably because I
> hide boring headers by default. However, I also hide citations and
> signatures (manually, not by default) but never does the status line
> change.
Try again.
next prev parent reply other threads:[~2001-10-12 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 15:11 David S. Goldberg
2001-10-12 17:08 ` Simon Josefsson [this message]
2001-10-12 17:37 ` David S. Goldberg
2001-10-12 18:56 ` Simon Josefsson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ilusncowzu0.fsf@barbar.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.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 NNTP newsgroup(s).