Wm., et. al., I''m using v0.4 on Fedora and when I &-mark a thread to kill it, I''m expecting that new replies to that thread will *not* come back to my inbox view. Except, that they do come back, and I''m puzzled as to whether this is a bug, an artifact of my setup, etc. I looked through sup-talk archives, but didn''t see anything about this issue. I have a single source (imaps://...) being fed to sup; I sup-sync every morning from a cron job, and, otherwise, everything "just works". Any pointers or requests for further info would be great. And, FWIW, other than this issue, I love-love-love sup! Thx!! -- Cheers, Kendall
Reformatted excerpts from Kendall Grant Clark''s message of 2008-03-17:> I''m using v0.4 on Fedora and when I &-mark a thread to kill it, I''m > expecting that new replies to that thread will *not* come back to my > inbox view. Except, that they do come back, and I''m puzzled as to > whether this is a bug, an artifact of my setup, etc. I looked through > sup-talk archives, but didn''t see anything about this issue.This should work. Can you try against git next? There have been a couple commits that probably affected this. -- William <wmorgan-sup at masanjin.net>
Excerpts from William Morgan''s message of Tue Mar 18 22:16:02 -0400 2008:> Reformatted excerpts from Kendall Grant Clark''s message of 2008-03-17: > > I''m using v0.4 on Fedora and when I &-mark a thread to kill it, I''m > > expecting that new replies to that thread will *not* come back to my > > inbox view. Except, that they do come back, and I''m puzzled as to > > whether this is a bug, an artifact of my setup, etc. I looked through > > sup-talk archives, but didn''t see anything about this issue. > > This should work. Can you try against git next? There have been a couple > commits that probably affected this.I''m a Python programmer, only marginally a Ruby src code reader... Is there some kind of sandbox I can use to test the git next version, w/out borking my existing (and working, except for this one issue) sup install? -- Cheers, Kendall
Excerpts from Kendall Grant Clark''s message of Wed Mar 19 07:59:14 -0600 2008:> I''m a Python programmer, only marginally a Ruby src code reader... Is > there some kind of sandbox I can use to test the git next version, > w/out borking my existing (and working, except for this one issue) sup > install? >So this is from: http://sup.rubyforge.org/wiki/wiki.pl?Contributing I set this up previously, so I''m not positive about the initial setup syntax but the rest of it is definitely correct: # initial setup git clone git://repo.or.cz/sup.git git branch --track next origin/next git checkout next # getting current, building, running local copy git pull rake gem ruby -I lib -w bin/sup This will then use a local next version w/out affecting your existing sup install. If you then decide you want to fully install the next version: sudo gem install pkg/sup-999.gem John
Excerpts from John Bent''s message of Wed Mar 19 10:51:29 -0400 2008:> So this is from: http://sup.rubyforge.org/wiki/wiki.pl?ContributingDoh. Sorry, I should have rechecked the wiki for this.> I set this up previously, so I''m not positive about the initial setup > syntax but the rest of it is definitely correct:It worked for me; thx! Testing now. :> -- Cheers, Kendall
Excerpts from William Morgan''s message of Tue Mar 18 22:16:02 -0400 2008:> This should work. Can you try against git next? There have been a couple > commits that probably affected this.Doesn''t work for me w/ git next either. I asked a coworker to send me a message, I replied. Then I killed the thread. He replied to my reply, and it popped right up in my INBOX with the +killed tag on it. -- Cheers, Kendall
Excerpts from Kendall Grant Clark''s message of Wed Mar 19 16:20:37 +0100 2008:> Doesn''t work for me w/ git next either. I asked a coworker to send me > a message, I replied. Then I killed the thread. He replied to my > reply, and it popped right up in my INBOX with the +killed tag on it.I confirm, at some point killed threads stopped working for me (they are back in the INBOX when a new message is received). Both git next and git master have this problem for me. -- Giorgio Lando <patroclo7 at gmail dot com>
Reformatted excerpts from Kendall Grant Clark''s message of 2008-03-19:> I''m a Python programmer, only marginally a Ruby src code reader... Is > there some kind of sandbox I can use to test the git next version, > w/out borking my existing (and working, except for this one issue) sup > install?Once you have git next in a directory somewhere (top part of http://sup.rubyforge.org/wiki/wiki.pl?Contributing), the HACKING file has instructions on how to run it locally. Please let me know if anything is unclear in either... -- William <wmorgan-sup at masanjin.net>
Excerpts from William Morgan''s message of Wed Mar 19 12:20:50 -0400 2008:> Once you have git next in a directory somewhere (top part of > http://sup.rubyforge.org/wiki/wiki.pl?Contributing), the HACKING file > has instructions on how to run it locally. Please let me know if > anything is unclear in either...Yes, I ran git next version and it still doesn''t handle +killed tagged threads correctly; that is, they show up in searches, which I expect, but new messages in the thread also cause the thread to reappear in INBOX. (FWIW, this test thread is tagged: +/INBOX +inbox +killed +sent.) -- Cheers, Kendall
Reformatted excerpts from Giorgio Lando''s message of 2008-03-19:> I confirm, at some point killed threads stopped working for me (they > are back in the INBOX when a new message is received). Both git next > and git master have this problem for me.Ok, I''ll take a look. -- William <wmorgan-sup at masanjin.net>