From: "Philipp Überbacher" <hollunder@lavabit.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] sup 0.11 - re-appearing thread
Date: Tue, 13 Jul 2010 20:08:10 +0200 [thread overview]
Message-ID: <1279044401-sup-3293@eris> (raw)
In-Reply-To: <1279040060-sup-4045@pinkfloyd.chass.utoronto.ca>
Excerpts from Ben Walton's message of 2010-07-13 18:55:59 +0200:
> Excerpts from Philipp's message of Tue Jul 13 12:46:40 -0400 2010:
>
> Hi Philipp,
>
> > everytime I start sup, one particular thread appears. I can archive it,
> > and next time I start sup it's there again.
> > Is this a known bug? Is there anything I can do about it?
>
> I'm going to guiltily raise my hand and note that I'm aware of this
> issue and have simply been working around it instead of digging into
> the code to see why it happens...
>
> You can (for now) work around it by altering the message state in some
> other way. I typically add a * and then remove it again. If you do
> this and then archive the thread, the archive will now 'stick.'
>
> I may have time in the next few days to try and see why this happens.
>
> HTH.
> -Ben
> --
> Ben Walton
> Systems Programmer - CHASS
> University of Toronto
> C:416.407.5610 | W:416.978.4302
Ah, thanks for looking into this. If it helps anything I can forward the
messages of that particular thread or something, it's around 5 messages.
--
Regards,
Philipp
--
"Wir stehen selbst enttäuscht und sehn betroffen / Den Vorhang zu und alle Fragen offen." Bertolt Brecht, Der gute Mensch von Sezuan
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2010-07-13 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 16:46 Philipp
2010-07-13 16:55 ` Ben Walton
2010-07-13 18:08 ` Philipp Überbacher [this message]
2010-07-13 18:17 ` Ben Walton
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=1279044401-sup-3293@eris \
--to=hollunder@lavabit.com \
--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