From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: gnus-insert-mime-security-button
Date: 29 Dec 2000 15:16:39 +0100 [thread overview]
Message-ID: <m3vgs3xqgo.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <vaf7l4jnxfs.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> But the buttons provide information: they tell you if the verification
> was okay or not. Hm. OTOH, right now Gnus doesn't verify
> automatically at all. Whee. Hm. But omitting the button means that
> there is nothing you can click on to tell Gnus you want to verify.
>
> Also, you might get a message with two text/plain parts, one of which
> verifies okay and the other doesn't. Then you want to know which part
> of the message you can trust.
But I kinda consider all that debugging info. When I'm reading, I'm
reading, and I don't care about encoding, encryption, verification and
all that jazz. Whether it's a fifteen-part HTML multipart/related, an
encrypted message/rfc822 or a plain text/plain, I just want to read
it. Gnus should present it in a manner that pleasing to read by
default.
If I'm interested in the details, we have `K b', and if I'm really
really interested, we have `C-d', and if I'm totally paranoid, we have
`C-u g'. :-)
(Besides, the PGP messages have "p" in the mode line. :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2000-12-29 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 12:54 gnus-insert-mime-security-button Lars Magne Ingebrigtsen
2000-12-29 13:56 ` gnus-insert-mime-security-button Kai Großjohann
2000-12-29 14:16 ` Lars Magne Ingebrigtsen [this message]
2000-12-29 15:06 ` gnus-insert-mime-security-button Kai Großjohann
2000-12-29 18:13 ` gnus-insert-mime-security-button Andreas Fuchs
2000-12-29 18:46 ` gnus-insert-mime-security-button Graham Murray
2000-12-29 18:58 ` gnus-insert-mime-security-button Andreas Fuchs
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=m3vgs3xqgo.fsf@quimbies.gnus.org \
--to=larsi@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).