Gnus development mailing list
 help / color / mirror / Atom feed
From: Thomas Lofgren <lofgren@sics.se>
Subject: Re: PGnus 0.9{5,7} hangs after generating summary buffer
Date: 01 Dec 1999 21:36:58 +0100	[thread overview]
Message-ID: <u2xn1ru4cut.fsf@muneca.sics.se> (raw)
In-Reply-To: lofgren@sics.se's message of "29 Sep 1999 10:26:23 +0200"

And the same is true in PGnus 0.98 and 0.99.  When invoking
gnus-thread-hide-subtree in one of my groups, it goes into an infinite
loop.  I posted the mail that causes this on Sep 29, and I can repost
it if you wish.

I'm not sure how it happens, but the way it's displayed when I don't
hide the threads make me believe that its subject line confuses the
threading quite a bit.  It looks like this:

 Subject:      =?iso-8859-1?Q?RE:_[Linux]_glibc_2.1.x_/_wu-?=
               =?iso-8859-1?Q?ftpd_<=3d2.5_/_BeroFTPD_/_lynx_/_vlo?=
               =?iso-8859-1?Q?ck=0d=0a______________?=
               =?iso-8859-1?Q?/_mc_/_glibc_2.0.x?=

Now, the article is in a thread by itself, so one would think that
hiding the threads wouldn't touch it.  However, Gnus displays the
subject correctly (or at least I don't know it to be incorrect)
encoded in the summary buffer, but there is a newline in it, which
(from the font-lock) appears to make Gnus believe that the second line
is a reply to the first line.

I hope that this can be addressed before the release version is out,
since few people like their programs to hang. :)

Thanks,
Tom
-- 
T. Lofgren <lofgren@sics.se> - Wherever I lay my .emacs, that's my ${HOME}
"Do you have CD players in Sweden?" -The always well-informed David Letterman


  parent reply	other threads:[~1999-12-01 20:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-29  8:26 Thomas Löfgren
1999-11-06  1:36 ` Lars Magne Ingebrigtsen
1999-12-01 20:36 ` Thomas Lofgren [this message]
1999-12-06  4:00   ` Lars Magne Ingebrigtsen
1999-12-07  0:43     ` Thomas Lofgren
2000-04-21 19:48       ` Lars Magne Ingebrigtsen

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=u2xn1ru4cut.fsf@muneca.sics.se \
    --to=lofgren@sics.se \
    /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;
as well as URLs for NNTP newsgroup(s).