From: Daniel Pittman <daniel@rimspace.net>
Subject: Re: Fun with article highlighting
Date: Sun, 30 Sep 2001 22:51:15 +1000 [thread overview]
Message-ID: <8766a0alks.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <iluadzez5cy.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Sat, 29 Sep 2001 11:57:49 +0200")
On Sat, 29 Sep 2001, Simon Josefsson wrote:
> [\b[[\b[P\bPG\bGP\bP \b S\bSi\big\bgn\bne\bed\bd \b P\bPa\bar\brt\bt:\b:O\bOK\bK]\b]]\b]
>
> So, is this message properly signed or not?
No, but that's because I customized my faces. :p
[...]
> (Some out-of-band mechanism to signal security status would be nice,
> such as arrows in the fringe. O well.)
Something in the modeline for the article and summary buffers would be
nice. Summary, for me, anyway. :)
Daniel
--
Man has a limited biological capacity for change. When this capacity is
overwhelmed the capacity is in future shock.
-- Alvin Toffler, _Future Shock_
next prev parent reply other threads:[~2001-09-30 12:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-29 9:57 Simon Josefsson
2001-09-30 12:51 ` Daniel Pittman [this message]
2001-09-30 13:58 ` Raja R Harinath
2001-09-30 15:37 ` Simon Josefsson
2001-10-01 5:06 ` Jorge Godoy
2001-10-01 20:14 ` 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=8766a0alks.fsf@inanna.rimspace.net \
--to=daniel@rimspace.net \
/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).