From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] [ANN] Sup 0.1 released
Date: Thu, 19 Jul 2007 13:29:30 -0700 [thread overview]
Message-ID: <1184875869-sup-9220@south> (raw)
In-Reply-To: <1184871475-sup-2598@eugen-laptop>
Hi Eugen,
Excerpts from Eugen Minciu's message of Thu Jul 19 11:58:49 -0700 2007:
> Thanks for a wonderful program William. Here are a few of my desired
> features:
> - color schemes.
On the todo list, along with customizable keybindings, but they're both
pretty far down. :)
> - incoming message filters
> I'd like to be able to apply filters on incoming messages: label them,
> archive some of them and so on
The way to do this currently is to use procmail to sort mail into
different folders, and then set labels, auto-archive/auto-read, etc. for
each source in Sup.
I realize that's not ideal (in particular, users whose mail is delivered
to IMAP servers not under their control are left out in the cold), but I
really really don't want to write a slow, buggy, Ruby procmail clone as
part of Sup.
Is there another option? I would really like the full power of procmail.
> - polling with fetchmail
> I use fetchmail and I'd like to be able to add some sort of hook before
> polling that would run fetchmail first.
I use fetchmail too, so I agree this would be nice. A near-term goal is
to have a good system of user-defined hooks, and I think this would be
the right place for that.
> - moving archived articles to another mbox
> This would be very useful because it would let me run biff programs.
This could be done easily, at least in a batch fashion, with a few
changes to sup-sync-back. I'm not sure if that's what you want. How do
you want to use biff with this?
(This reminds me that there is still a completely unresolved question of
how sup-sync-back should lock mboxes. It doesn't do any locking at all
currently, which means you should be probably very careful with it.)
> I might be able to give you a hand (or patch) for one or two of these.
> Which ones would you like and which would be the easiest?
If batch moving of archived messages is useful to you, that's probably
the easiest one to do.
Making the colors configurable wouldn't be too hard either. I'm
imagining a yaml config file that can override the color setup in
sup.rb. What do you think?
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-07-19 20:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 18:58 Eugen Minciu
2007-07-19 20:29 ` William Morgan [this message]
2007-08-19 0:12 ` William Morgan
-- strict thread matches above, loose matches on Subject: below --
2007-07-19 20:49 William Morgan
2007-07-18 1:42 William Morgan
2007-07-18 22:21 ` jeff covey
2007-07-19 18:01 ` William Morgan
2007-07-19 18:18 ` nicholas a. evans
2007-07-19 18:55 ` William Morgan
2007-08-01 16:15 ` 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=1184875869-sup-9220@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