From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] sup wishlist
Date: Wed, 16 May 2007 13:44:51 -0400 [thread overview]
Message-ID: <20070516174451.GA3387@mona.jeffcovey.net> (raw)
william,
thanks again for all the work on sup! i'm looking forward to trying it on
my actual mail once a system for physically deleting sup-deleted messages is
in place.
in the meantime, i checked out the todo list, and am glad to see so many of
my wishes already there! :) just to add some ideas, here are a few things
i would miss from mutt:
- the ability to pipe a message to a process.
i often use this, for example, to run a message through urlview to get a
list of urls to launch in a browser.
- an equivalent to mutt's display_filter.
i like to have messages run through my own filter before they're displayed
on the screen. i think sup's method of collapsing comments and signatures
works beautifully, but it can't catch everything. for example, i like to
remove the ads at the bottoms of yahoo! group posts and ridiculously long
signatures about "this message was sent by an employee of yada yada and
was intended for foo foo, if it was sent to you in error, please blah blah
blah".
- gpg support would be nice someday. :)
again, best wishes for your work. i think it has terrific potential.
sincerely,
--
jeff covey
http://jeffcovey.net/
-------------- 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/20070516/aa747200/attachment.bin
next reply other threads:[~2007-05-16 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 17:44 jeff covey [this message]
2007-05-16 19:36 ` William Morgan
2007-05-18 13:39 ` jeff covey
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=20070516174451.GA3387@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