* [sup-talk] Kill thread doesn't seem to work
@ 2008-03-17 16:50 Kendall Grant Clark
2008-03-19 2:16 ` William Morgan
0 siblings, 1 reply; 10+ messages in thread
From: Kendall Grant Clark @ 2008-03-17 16:50 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [sup-talk] Kill thread doesn't seem to work
2008-03-17 16:50 [sup-talk] Kill thread doesn't seem to work Kendall Grant Clark
@ 2008-03-19 2:16 ` William Morgan
2008-03-19 13:59 ` Kendall Grant Clark
2008-03-19 15:20 ` Kendall Grant Clark
0 siblings, 2 replies; 10+ messages in thread
From: William Morgan @ 2008-03-19 2:16 UTC (permalink / raw)
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>
^ permalink raw reply [flat|nested] 10+ messages in thread
* [sup-talk] Kill thread doesn't seem to work
2008-03-19 2:16 ` William Morgan
@ 2008-03-19 13:59 ` Kendall Grant Clark
2008-03-19 14:51 ` John Bent
2008-03-19 16:20 ` William Morgan
2008-03-19 15:20 ` Kendall Grant Clark
1 sibling, 2 replies; 10+ messages in thread
From: Kendall Grant Clark @ 2008-03-19 13:59 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [sup-talk] Kill thread doesn't seem to work
2008-03-19 13:59 ` Kendall Grant Clark
@ 2008-03-19 14:51 ` John Bent
2008-03-19 15:17 ` Kendall Grant Clark
2008-03-19 16:20 ` William Morgan
1 sibling, 1 reply; 10+ messages in thread
From: John Bent @ 2008-03-19 14:51 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [sup-talk] Kill thread doesn't seem to work
2008-03-19 13:59 ` Kendall Grant Clark
2008-03-19 14:51 ` John Bent
@ 2008-03-19 16:20 ` William Morgan
2008-03-19 16:45 ` Kendall Grant Clark
1 sibling, 1 reply; 10+ messages in thread
From: William Morgan @ 2008-03-19 16:20 UTC (permalink / raw)
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>
^ permalink raw reply [flat|nested] 10+ messages in thread
* [sup-talk] Kill thread doesn't seem to work
2008-03-19 16:20 ` William Morgan
@ 2008-03-19 16:45 ` Kendall Grant Clark
0 siblings, 0 replies; 10+ messages in thread
From: Kendall Grant Clark @ 2008-03-19 16:45 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [sup-talk] Kill thread doesn't seem to work
2008-03-19 2:16 ` William Morgan
2008-03-19 13:59 ` Kendall Grant Clark
@ 2008-03-19 15:20 ` Kendall Grant Clark
2008-03-19 15:24 ` Giorgio Lando
1 sibling, 1 reply; 10+ messages in thread
From: Kendall Grant Clark @ 2008-03-19 15:20 UTC (permalink / raw)
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
^ permalink raw reply [flat|nested] 10+ messages in thread
* [sup-talk] Kill thread doesn't seem to work
2008-03-19 15:20 ` Kendall Grant Clark
@ 2008-03-19 15:24 ` Giorgio Lando
2008-03-19 19:23 ` William Morgan
0 siblings, 1 reply; 10+ messages in thread
From: Giorgio Lando @ 2008-03-19 15:24 UTC (permalink / raw)
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>
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2008-03-19 19:23 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-03-17 16:50 [sup-talk] Kill thread doesn't seem to work Kendall Grant Clark
2008-03-19 2:16 ` William Morgan
2008-03-19 13:59 ` Kendall Grant Clark
2008-03-19 14:51 ` John Bent
2008-03-19 15:17 ` Kendall Grant Clark
2008-03-19 16:20 ` William Morgan
2008-03-19 16:45 ` Kendall Grant Clark
2008-03-19 15:20 ` Kendall Grant Clark
2008-03-19 15:24 ` Giorgio Lando
2008-03-19 19:23 ` William Morgan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox