From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] sup wishlist
Date: Fri, 18 May 2007 09:39:09 -0400 [thread overview]
Message-ID: <20070518133908.GA1759@mona.jeffcovey.net> (raw)
In-Reply-To: <1179344168-sup-5879@south>
on Wed, May 16, 2007 at 12:36:22PM -0700%, William Morgan said:
> > - an equivalent to mutt's display_filter.
>
> This should'nt be hard to do either, but the question is whether we should
> just improve the signature detection in Sup.
no, there's no way to make the signature detection handle all the arbitrary
problems that people present in their messages. some of them just have to
be handled manually on a case-by-case basis. for example, one of the
regular posters on one mailing list i read considers this a valid signature
(and doesn't demarcate it with "-- "):
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> VISTA SOFTWARE, DESIGNED TO RESTRICT WHAT YOU CAN DO. www.badvista.org
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> "They that can give up essential liberty to obtain a little temporary
> safety deserve Neither liberty nor safety", Benjamin Franklin
> - - - - - - - - - - - - - - - - - - -
> ASCII Ribbon Campaign. . . . . . . . . . . . accessBob
> .NO HTML/PDF/RTF/MIME in e-mail. . . . . . . accessys at smartnospam.net
> .NO MSWord docs in e-mail . . . .. . . . . . Access Systems, engineers
> .NO attachments in e-mail, .*LINUX powered*. access is a civil right
> *#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#*#
> THIS message and any attachments are CONFIDENTIAL and may be
> privileged. They are intended ONLY for the individual or entity named
no poor regexp should be taxed with handling things like this.
> Do you use this for other things?
i do assorted minor cleanup and generally remove things i don't need to see.
i'll attach the script i use, based on one from a friend.
i don't know what other people do with it, but i imagine some people format
messages with par and otherwise make other people's mail look like what they
would want to send themselves.
i find it a very useful feature for limiting what's displayed on the screen
to just the meaningful information. for a thread-based display like sup's,
i think it would be doubly useful when dealing with screens full of replies.
i wouldn't want to scroll past bob's signature again and again.
> > - gpg support would be nice someday. :)
>
> Someone is actually working on this right now!
awesome! :)
thanks,
--
jeff covey
http://jeffcovey.net/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: display_filter.sh
Type: application/x-sh
Size: 3000 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070518/01d411d9/attachment.sh
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 229 bytes
Desc: Digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070518/01d411d9/attachment.bin
next prev parent reply other threads:[~2007-05-18 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 17:44 jeff covey
2007-05-16 19:36 ` William Morgan
2007-05-18 13:39 ` jeff covey [this message]
2007-05-20 23:44 ` William Morgan
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=20070518133908.GA1759@mona.jeffcovey.net \
--to=jeff.covey@pobox.com \
/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