Subject: [sup-talk] how to avoid adding labels based on source names

From: [email-masked] (jeff covey)
Date: Sun, 27 May 2007 15:50:13 -0400

i haven't been quiet this week because i forgot about sup, but because i've
been preparing for it.  :)

i took part of my first week of post-spring-commitments time to tackle a
two-year old project, going through 10+ years of email, deleting the truly
unnecessary, and letting formail+procmail sort the rest by sender (or
listid) and date instead of my arbitrary organizing system.

so i'm taking part of the resulting archive to test the latest svn commit of
sup, and my first question is:

how do i stop sup-sync from adding a label to each message based on the name
of its source?

i have over 10,000 mbox files to add to sup's index.  the labeling feature
will be useless to me if i have to search for my labels (not to mention
"Draft", "Starred", etc.) among all those sup-sync added.

thanks!

-- 
jeff covey
http://jeffcovey.net/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 229 bytes
Desc: Digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070527/90093bcd/attachment.bin

---

From: [email-masked] (William Morgan)
Date: Sun, 27 May 2007 21:12:05 -0700

Excerpts from jeff covey's message of Sun May 27 12:50:13 -0700 2007:
> how do i stop sup-sync from adding a label to each message based on
> the name of its source?

There is currently no way to do this. This is my top priority change at
the moment. I'm going to make the auto-added labels be a per-source
field in sources.yaml, and remove the current magic that generates them
without giving you a choice in the matter.

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

---

From: [email-masked] (jeff covey)
Date: Sun, 3 Jun 2007 14:14:02 -0400

on Sun, May 27, 2007 at 09:12:05PM -0700%, William Morgan said:

> > how do i stop sup-sync from adding a label to each message based on the
> > name of its source?
> 
> the moment.

is there any news on this?  there's no rush, but it is the one thing that's
keeping me from trying sup.  :)

thanks,

-- 
jeff covey
http://jeffcovey.net/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 229 bytes
Desc: Digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070603/8025892a/attachment.bin

---

From: [email-masked] (William Morgan)
Date: Sun, 03 Jun 2007 12:20:47 -0700

Excerpts from jeff covey's message of Sun Jun 03 11:14:02 -0700 2007:
> is there any news on this?  there's no rush, but it is the one thing
> that's keeping me from trying sup.  :)

I have a patch for it. Going to do a little more testing and then I'll
commit, probably later today.

---

From: [email-masked] (jeff covey)
Date: Sun, 3 Jun 2007 21:11:34 -0400

> commit, probably later today.

thanks!  i updated with svn and am trying it out.  i've run into this
problem when sup tries to load a source which no longer exists:

./lib/sup/buffer.rb:45: warning: already initialized constant KEY_CANCEL
./lib/sup/mbox/loader.rb:20:in `initialize': No such file or directory - /home/jeff/mail/dogabulten at dogadernegi.org-2007-06 (Errno::ENOENT)
        from ./lib/sup/mbox/loader.rb:20:in `open'
        from ./lib/sup/mbox/loader.rb:20:in `initialize'
        from ./lib/sup.rb:28:in `new'
        from ./lib/sup.rb:28:in `yaml_properties'
        from /usr/lib/ruby/1.8/yaml.rb:133:in `call'
        from /usr/lib/ruby/1.8/yaml.rb:133:in `transfer'
        from /usr/lib/ruby/1.8/yaml.rb:133:in `node_import'
        from /usr/lib/ruby/1.8/yaml.rb:133:in `load'
        from /usr/lib/ruby/1.8/yaml.rb:133:in `load'
        from /usr/lib/ruby/1.8/yaml.rb:144:in `load_file'
        from /usr/lib/ruby/1.8/yaml.rb:143:in `open'
        from /usr/lib/ruby/1.8/yaml.rb:143:in `load_file'
        from ./lib/sup.rb:84:in `load_yaml_obj'
        from ./lib/sup/index.rb:278:in `load_sources'
        from ./lib/sup/index.rb:29:in `load'
        from bin/sup:58

i have a cron job which deletes zero-length files under ~/mail so they don't
clutter.  could sup handle no-longer-existent sources gracefully, either
ignoring them or (perhaps better) offering to remove them from sources.yaml?

thanks,

-- 
jeff covey
http://jeffcovey.net/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 229 bytes
Desc: Digital signature
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20070603/2ca68556/attachment.bin