Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Gmail question
Date: Mon, 21 Dec 2009 08:56:19 -0800	[thread overview]
Message-ID: <1261414173-sup-9168@masanjin.net> (raw)
In-Reply-To: <314cf0830912210828i278fd9efxd8d688c10a2a4b73@mail.gmail.com>

Reformatted excerpts from Joel Esler's message of 2009-12-21:
> Obviously I'd like to be able to mash the "L" and see all these labels
> and their unread counts, however, I am obviously missing how to
> configure this, and I am sure it's quite easy.  Heck, I don't mind if
> you guys RTFM me to the right section of the 'manual', but please do.

I believe that Gmail exposes those types of things to IMAP clients as
IMAP folders with funny names. (If you see these messages in Sup's
inbox, then I am wrong about that.)

So the easiest approach to duplicate them in Sup is add each source by
hand as sup-add, and have Sup auto-apply labels when it sees new
messages in those "folders". (And auto-archive them.)

Unfortunately Sup's stupid URI syntax for sources combines very poorly
with Gmail's names for these types of folders, so you'll have to do
something horrible like:

  sup-add imaps://imap.gmail.com/%5BGmail%5D%2FSent+Mail
  sup-add imaps://imap.gmail.com/%5BGmail%5D%2Flabelname

etc., with the appropriate arguments to sup-add for auto-archiving and
auto-applying labels.

Anyone more familiar with Gmail+Sup, please correct me if I'm wrong.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2009-12-21 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 16:28 Joel Esler
2009-12-21 16:56 ` William Morgan [this message]
2009-12-21 23:45   ` Ben Walton
2009-12-27 15:45     ` Joel Esler
2009-12-27 15:48       ` William Morgan
2009-12-27 23:05         ` Joel Esler

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=1261414173-sup-9168@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    --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