Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Minor maildir change
Date: Sun, 23 Sep 2007 19:29:35 -0700	[thread overview]
Message-ID: <1190600285-sup-4801@south> (raw)
In-Reply-To: <20070919220200.GA3436@die.therning.org>

Excerpts from Magnus Therning's message of Wed Sep 19 15:02:00 -0700 2007:
> What's gotten from the source is useful for an unseen message, but why
> not mark known messages with the labels from the index?

If your question is, why does Source#add_messages_from yield what it
does, the answer is because all consumers either need the source labels
(for polling) or need both (for syncing---check out sup-sync for the
gory details). Thread-view-mode and all its decendents (inbox-mode, etc)
all talk directly to the index and don't use that method at all.

> >>  - Make all sets of labels actual sets.
> >
> >Not sure what you mean by "actual sets", but I think this is pretty
> >much the way Sup works now.
> 
> What I mean is the type set gotten from "require 'set'" :)  Currently
> labels are lists, not sets.

Honestly, I don't see a real advantage to retrofitting that class onto
things. It doesn't appeal to my Ruby instincts. :)

-- 
William <wmorgan-sup at masanjin.net>


      reply	other threads:[~2007-09-24  2:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-09 22:40 Magnus Therning
2007-09-14  3:33 ` William Morgan
2007-09-16 18:19   ` Magnus Therning
2007-09-19 15:59     ` William Morgan
2007-09-19 22:02       ` Magnus Therning
2007-09-24  2:29         ` William Morgan [this message]

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=1190600285-sup-4801@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