From: magnus@therning.org (Magnus Therning)
Subject: [sup-talk] on sup
Date: Fri, 31 Aug 2007 18:12:34 +0100 [thread overview]
Message-ID: <20070831171234.GD8312@die.therning.org> (raw)
In-Reply-To: <1188573751-sup-6067@south>
On Fri, Aug 31, 2007 at 08:31:04 -0700, William Morgan wrote:
>Excerpts from Magnus Therning's message of Fri Aug 31 04:04:03 -0700 2007:
>> Hey! Sup is absolutely great!
>
>Thanks! Feel free to join the mailing list and tell all your friends.
>Especially if they can write Ruby. :)
Here I am. Not very proficient in Ruby myself, but I suppose sup offers
an incentive to check it out.
>> Here are some things I'd like to see in sup in the future:
>>
>> - support for using the output of a command as signature (I don't seem
>> to even get the contents of ~/.signature inserted into new emails)
>
>It should be trivial to add a hook for this. By default ~/.signature
>should be appended to email (not in the editor, but in Sup's review
>screen immediate post editing). If it's not, it's probably that
>~/.sup/config.yaml is pointing to a different file.
Ah, that's slightly confusing behaviour especially after being used to
mutt. I think I can adapt though :-)
>> - PGP/GPG support, this is really a show stopper for me at the moment
>
>Yep, I plan to have first-order GPG support (i.e. not just in the hooks
>system.) Not for the next release, but possibly the one after. The time
>is nigh.
Is anyone working on it already?
>> - support for choosing where to save sent messages
>
>This I'm a little curious about. Why do you care where they live on
>disk, as long as they show up in the index?
All right, here's some background :-)
I have a fairly extensive configuration of procmail for sorting mails
into maildir folders on a server at a friend's place. I then
synchronise those folders onto a few different machines. This way I can
read emails on all machines, both at home and work. When I'm travelling
I can use the web-based reader hosted on the same server at my friend's.
Given this I want to control where sent mails end up so that I can
access those mails from all those locations. And I want to keep my
hierarchy of folders so that reading emails is easy also on machines
where I can't install sup and online.
This makes me think of another little detail, it seems sup's idea of
what's read and what's new isn't based on the maildir notion of what's
read and what's new (i.e. sup doesn't move mail from /new to /cur when
it's read and doesn't recognise that mail in /cur is read).
/M
--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
magnus?therning?org Jabber: magnus?therning?gmail?com
http://therning.org/magnus
When the people fear their government, there is tyranny; when the
government fears the people, there is liberty.
-- Thomas Jefferson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070831/8ae01aa6/attachment-0001.bin
next prev parent reply other threads:[~2007-08-31 17:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1188557360-sup-7369@bryma>
2007-08-31 15:31 ` William Morgan
2007-08-31 17:12 ` Magnus Therning [this message]
2007-09-02 23:03 ` William Morgan
2007-09-05 7:48 ` Magnus Therning
2007-09-05 15:27 ` William Morgan
2007-09-06 7:02 ` Magnus Therning
2007-09-11 22:08 ` William Morgan
2007-09-11 23:04 ` Magnus Therning
2007-09-05 21:55 ` William Morgan
2007-09-06 6:50 ` Magnus Therning
2007-09-11 20:48 ` William Morgan
2007-09-03 12:33 ` [sup-talk] saving sent mail to places other than the default jeff covey
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=20070831171234.GD8312@die.therning.org \
--to=magnus@therning.org \
/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