Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] sup wishlist
Date: Wed, 16 May 2007 12:36:22 -0700	[thread overview]
Message-ID: <1179344168-sup-5879@south> (raw)
In-Reply-To: <20070516174451.GA3387@mona.jeffcovey.net>

Hi Jeff,

Excerpts from jeff covey's message of Wed May 16 10:44:51 -0700 2007:
> thanks again for all the work on sup!

You're welcome, and thanks for the positive comments. Keeps me
motivated. :)

> just to add some ideas, here are a few things i would miss from mutt:
> 
> - the ability to pipe a message to a process.

Sounds good. Should be pretty easy to do.

> - 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".

This should'nt be hard to do either, but the question is whether we
should just improve the signature detection in Sup. Do you use this for
other things?

> - gpg support would be nice someday.  :)

Someone is actually working on this right now!

-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2007-05-16 19:36 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 [this message]
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=1179344168-sup-5879@south \
    --to=wmorgan-sup@masanjin.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