* [sup-talk] Saving status of merged threads with '#' on next branch
@ 2009-04-08 20:44 =?UNKNOWN?Q?Bj=C3=B8rn?= Michelsen
2009-04-09 15:39 ` Mark Alexander
2009-04-09 18:02 ` William Morgan
0 siblings, 2 replies; 7+ messages in thread
From: =?UNKNOWN?Q?Bj=C3=B8rn?= Michelsen @ 2009-04-08 20:44 UTC (permalink / raw)
Hi all,
For some reason, the '#' command isn't saving the status of tagged
threads being forced to merge. I get a visual feedback that the threads
have been put into the same one, but when I come back to the view after
killing the buffer, they're separated again.
I'm currently running sup from the next branch. But, I also checked the
command on the 0.7 gem version without any luck.
I'm a bit lost as to where I should begin troubleshooting, so I'm
wondering if someone else have had the same problem?
Maybe I have misinterpreted the command?
--
Mvh.
Bj?rn Michelsen
MOB: +47 934 55 474
^ permalink raw reply [flat|nested] 7+ messages in thread
* [sup-talk] Saving status of merged threads with '#' on next branch
2009-04-08 20:44 [sup-talk] Saving status of merged threads with '#' on next branch =?UNKNOWN?Q?Bj=C3=B8rn?= Michelsen
@ 2009-04-09 15:39 ` Mark Alexander
2009-04-09 18:02 ` William Morgan
1 sibling, 0 replies; 7+ messages in thread
From: Mark Alexander @ 2009-04-09 15:39 UTC (permalink / raw)
2009/4/8 Bj?rn Michelsen <bm at bjornmichelsen.com>:
> For some reason, the '#' command isn't saving the status of tagged
> threads being forced to merge. I get a visual feedback that the threads
> have been put into the same one, but when I come back to the view after
> killing the buffer, they're separated again.
I've noticed this as well. I figured it was a feature, not a bug :-) .
^ permalink raw reply [flat|nested] 7+ messages in thread
* [sup-talk] Saving status of merged threads with '#' on next branch
2009-04-08 20:44 [sup-talk] Saving status of merged threads with '#' on next branch =?UNKNOWN?Q?Bj=C3=B8rn?= Michelsen
2009-04-09 15:39 ` Mark Alexander
@ 2009-04-09 18:02 ` William Morgan
2009-04-15 15:58 ` Bjorn Michelsen
1 sibling, 1 reply; 7+ messages in thread
From: William Morgan @ 2009-04-09 18:02 UTC (permalink / raw)
Reformatted excerpts from =?UNKNOWN?Q?Bj=C3=B8rn?= Michelsen's message of 2009-04-08:
> I'm a bit lost as to where I should begin troubleshooting, so I'm
> wondering if someone else have had the same problem?
It's a known problem. I'm not sure why it isn't saved. If you want to
start investigating, ThreadSet#join_threads in lib/sup/threads.rb is the
joining code. Maybe the call to Message#add_ref is wrong somehow.
I'm also curious about your From: line, which is RFC2047-encoded but
with the "UNKNOWN" charset. What produces that? Surely not Sup!
--
William <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [sup-talk] Saving status of merged threads with '#' on next branch
2009-04-09 18:02 ` William Morgan
@ 2009-04-15 15:58 ` Bjorn Michelsen
2009-04-15 17:33 ` William Morgan
0 siblings, 1 reply; 7+ messages in thread
From: Bjorn Michelsen @ 2009-04-15 15:58 UTC (permalink / raw)
Excerpts from William Morgan's message of to. april 09 20:02:08 +0200 2009:
> > I'm a bit lost as to where I should begin troubleshooting, so I'm
> > wondering if someone else have had the same problem?
>
> It's a known problem. I'm not sure why it isn't saved. If you want to
> start investigating, ThreadSet#join_threads in lib/sup/threads.rb is the
> joining code. Maybe the call to Message#add_ref is wrong somehow.
Thanks for clearing that up, as well as the additional information
regarding where to start looking.
> I'm also curious about your From: line, which is RFC2047-encoded but
> with the "UNKNOWN" charset. What produces that? Surely not Sup!
I haven't replied earlier because I've been trying to figure out what
causes the strange From: address.
locale outputs the following:
LANG=nb_NO.UTF-8
LC_CTYPE=nb_NO.UTF-8
LC_NUMERIC="nb_NO.UTF-8"
LC_TIME="nb_NO.UTF-8"
LC_COLLATE="nb_NO.UTF-8"
LC_MONETARY="nb_NO.UTF-8"
LC_MESSAGES=en_US.UTF-8
LC_PAPER="nb_NO.UTF-8"
LC_NAME="nb_NO.UTF-8"
LC_ADDRESS="nb_NO.UTF-8"
LC_TELEPHONE="nb_NO.UTF-8"
LC_MEASUREMENT="nb_NO.UTF-8"
LC_IDENTIFICATION="nb_NO.UTF-8"
LC_ALL=
And Vim is saying that all files related to sup is encoded as utf8.
So, at the moment I don't know why this is happening. Maybe someone
using special characters can let me in on their secret?
--
Mvh.
Bj?rn Michelsen
MOB: +47 934 55 474
^ permalink raw reply [flat|nested] 7+ messages in thread
* [sup-talk] Saving status of merged threads with '#' on next branch
2009-04-15 15:58 ` Bjorn Michelsen
@ 2009-04-15 17:33 ` William Morgan
2009-04-16 9:53 ` Bjorn Michelsen
0 siblings, 1 reply; 7+ messages in thread
From: William Morgan @ 2009-04-15 17:33 UTC (permalink / raw)
Reformatted excerpts from Bjorn Michelsen's message of 2009-04-15:
> I haven't replied earlier because I've been trying to figure out what
> causes the strange From: address.
Is the weird encoding also present in the files in ~/.sup/sent.mbox? If
so, it's could be Rubymail... AFAICT, Rubymail doesn't do anything with
rfc2047, but I could have missed it.
If not, are you using some funky sendmail?
--
William <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 7+ messages in thread
* [sup-talk] Saving status of merged threads with '#' on next branch
2009-04-15 17:33 ` William Morgan
@ 2009-04-16 9:53 ` Bjorn Michelsen
2009-04-21 13:28 ` William Morgan
0 siblings, 1 reply; 7+ messages in thread
From: Bjorn Michelsen @ 2009-04-16 9:53 UTC (permalink / raw)
Excerpts from William Morgan's message of on. april 15 19:33:24 +0200 2009:
> > I haven't replied earlier because I've been trying to figure out what
> > causes the strange From: address.
>
> Is the weird encoding also present in the files in ~/.sup/sent.mbox? If
> so, it's could be Rubymail... AFAICT, Rubymail doesn't do anything with
> rfc2047, but I could have missed it.
No, everything is encoded correctly in ~/.sup/sent.mbox
> If not, are you using some funky sendmail?
I'm using sSMTP at the moment. Maybe it has something to do with the
following bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341952#10 ?
--
Mvh.
Bj?rn Michelsen
MOB: +47 934 55 474
^ permalink raw reply [flat|nested] 7+ messages in thread
* [sup-talk] Saving status of merged threads with '#' on next branch
2009-04-16 9:53 ` Bjorn Michelsen
@ 2009-04-21 13:28 ` William Morgan
0 siblings, 0 replies; 7+ messages in thread
From: William Morgan @ 2009-04-21 13:28 UTC (permalink / raw)
Reformatted excerpts from Bjorn Michelsen's message of 2009-04-16:
> No, everything is encoded correctly in ~/.sup/sent.mbox
Then this is almost definitely your MTA, not Sup. But you could also try
sending a message to yourself with another MUA and see what happens.
(Probably what will happen is that the MUA will RFC2047-encode your
headers, and sSMTP will see that and leave them alone, and this problem
will be hidden. So the right answer is really for Sup to RFC2047-encode
headers in outgoing email.)
> I'm using sSMTP at the moment. Maybe it has something to do with the
> following bug
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=341952#10 ?
The problem could be someone trying to fix that bug (which is basically
"we should add RFC2047 support"). Somehow it's not picking up your
locale settings.
--
William <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2009-04-21 13:28 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-04-08 20:44 [sup-talk] Saving status of merged threads with '#' on next branch =?UNKNOWN?Q?Bj=C3=B8rn?= Michelsen
2009-04-09 15:39 ` Mark Alexander
2009-04-09 18:02 ` William Morgan
2009-04-15 15:58 ` Bjorn Michelsen
2009-04-15 17:33 ` William Morgan
2009-04-16 9:53 ` Bjorn Michelsen
2009-04-21 13:28 ` William Morgan
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox