From mboxrd@z Thu Jan 1 00:00:00 1970 From: wmorgan-sup@masanjin.net (William Morgan) Date: Sun, 02 Sep 2007 16:03:29 -0700 Subject: [sup-talk] on sup In-Reply-To: <20070831171234.GD8312@die.therning.org> References: <1188557360-sup-7369@bryma> <1188573751-sup-6067@south> <20070831171234.GD8312@die.therning.org> Message-ID: <1188773706-sup-1502@south> Excerpts from Magnus Therning's message of Fri Aug 31 10:12:34 -0700 2007: > On Fri, Aug 31, 2007 at 08:31:04 -0700, William Morgan wrote: > >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 :-) The signature selection algorithm is tied to Sup's multiple account support: the signature file Sup uses is based on the From: address you select. You can get the simpler mutt-style behavior by specifying :edit_signature: true in config.yaml, which always takes the signature of the default account and dumps it into the editor, or you can now specify more complicated behavior now with the signature hook. > >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? There were patches submitted by I think Christian Lee a while ago, but they never made it into the svn, mostly because I was waiting for multiple account support to stabilize a bit. Which it now pretty much has. > Given this I want to control where sent mails end up so that I can > access those mails from all those locations. Sup stores its sent mail in ~/.sup/sent.mbox by default. I'm not opposed to making that filename configurable, but the quickest fix might be just to make that a symlink to the actual destination file. > 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). Yeah, Sup doesn't sync back any state changes to the original sources. The Sup philosophy has been to treat the sources as dumb, which means Sup doesn't play well with others. I won't turn aside patches which do sync back (partial) message state to the sources, but I'm not planning on implementing that stuff myself. -- William