From: Neil Stewart <neil.stewart@warwick.ac.uk>
To: Richard Heycock <rgh@topikality.com>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sent mail
Date: Thu, 8 Apr 2010 22:44:30 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.10.1004082207140.26765@stewart.warwick.ac.uk> (raw)
In-Reply-To: <1270727373-sup-8902@roughage.com.au>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1589 bytes --]
>>> In sup 0.11, sent mail does not get the inbox label anymore (AFAIK). Are you
>>> using 0.11?
>>
>> I'm using 0.10.2-1 from Debian testing. I've had a go at getting 0.11, but
>> it's not available in Debian. I've failed to compile it several times using
>> "gems install sup". I finally got it to work using ruby1.9, but can't work
>> out how to run sup. I tried
Here is some more information on sent mail appearing in the inbox. First, it
was discussed a while ago. Apologies for missing it.
http://www.mail-archive.com/sup-talk@rubyforge.org/msg03227.html
Second, I've downloaded the development sup from the gitorious.org and built and
installed a sup gem. Using this, sent mail does get the inbox tag and appear
in the inbox after sending. I've found that by changing line 52 in sent.rb
from
def labels; [:inbox, :sent]; end
to
def labels; [:sent]; end
this behaviour can be disabled, so sent mail goes straight into the archive
and is not included in the inbox.
I've not used ruby before, but I've added an option
:sent_appears_in_inbox: true
to config.yaml.
So the critical lines in sent.rb are now
if $config[:sent_appears_in_inbox] then
def labels; [:inbox, :sent]; end
else
def labels; [:sent]; end
and I added
:sent_appears_in_inbox => true
to the bit of sup.pl that writes the default config.yaml.
So the default is the current behaviour---sent appearing in the inbox, but
one can turn this off by altering the default config.yaml.
I've attached trivial patches for sup.rb and sent.rb if these are of any
use.
Best,
Neil.
[-- Attachment #2: Type: APPLICATION/x-ruby, Size: 350 bytes --]
[-- Attachment #3: Type: APPLICATION/x-ruby, Size: 343 bytes --]
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-04-08 21:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 10:08 Neil Stewart
2010-04-08 12:01 ` Richard Heycock
2010-04-08 12:54 ` Neil Stewart
2010-04-08 13:27 ` Richard Heycock
[not found] ` <alpine.DEB.1.10.1004092231370.4476@stewart.warwick.ac.uk>
2010-04-09 21:37 ` Neil Stewart
2010-04-09 22:09 ` Rich Lane
2010-04-14 13:06 ` William Morgan
2010-04-08 21:44 ` Neil Stewart [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-06 14:13 Neil Stewart
2010-04-06 16:23 ` Michael Stapelberg
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=alpine.DEB.1.10.1004082207140.26765@stewart.warwick.ac.uk \
--to=neil.stewart@warwick.ac.uk \
--cc=rgh@topikality.com \
--cc=sup-talk@rubyforge.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