Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@charcoal.com>
Subject: Last evening's 0.17 infloops in find-charset-string
Date: Tue, 18 Mar 2003 07:31:49 -0500	[thread overview]
Message-ID: <vxkbs08zwi2.fsf@cinnamon.vanillaknot.com> (raw)

XEmacs 21.4.10 (mule) w/Oort 0.17 updated immediately after 0.16
release was announced.

Very long articles will no longer display at all for me, as
find-charset-string is reproducibly getting stuck.  This wasn't
happening with Oort until I updated last evening.  (I hadn't
previously done "cvs update" in perhaps 10 days.)

Interestingly, the 0.16 release announcement itself is one such
article which will not display due to find-charset-string getting
stuck.  I let XEmacs sit for about 3 minutes, waiting for this article
to display; it never did, and I caught the stack trace with
debug-on-quit.

Signaling: (quit)
  find-charset-string("Mainly mostly misc mush.\n\nGnus 5.10 is probably ...\n\n")
  mm-decode-coding-region-safely(1910 37207 iso-8859-1)
  mm-decode-body("iso-8859-1" 8bit "text/plain" nil)
  article-decode-charset()
  run-hooks(article-decode-charset)
  gnus-request-article-this-buffer(52046 "list.ding")
  gnus-article-prepare(52046 nil)
  gnus-summary-display-article(52046 nil)
  gnus-summary-select-article(nil force)
  gnus-summary-show-article(nil)
  call-interactively(gnus-summary-show-article)



             reply	other threads:[~2003-03-18 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 12:31 Karl Kleinpaste [this message]
2003-03-18 17:10 ` Jesper Harder
2003-03-18 18:38   ` Karl Kleinpaste
2003-03-18 19:44     ` Jesper Harder

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=vxkbs08zwi2.fsf@cinnamon.vanillaknot.com \
    --to=karl@charcoal.com \
    /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).