Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
Subject: Re: XEmacs hangs in rfc2047-encode-string
Date: Sat, 01 Jan 2005 20:25:45 +0100	[thread overview]
Message-ID: <87652hrlxi.fsf@dod.no> (raw)
In-Reply-To: <86y8fd6n8m.fsf@santinel.home.ua>

>>>>> Andrey Slusar <anrays@gmail.com>:

>   Original report is http://thread.gmane.org/gmane.emacs.xemacs.beta/17437

From looking at the thread, what's needed is a minimal test case,
that'll provoke the loop.

I'm wondering if calling rfc2047-encode-string with a string
containing a problem header would be enough?




  reply	other threads:[~2005-01-01 19:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03 16:55 XEmacs, Gnus and mm-coding-system priorities Aidan Kehoe
2004-12-06  2:30 ` Katsumi Yamaoka
2004-12-06 13:35   ` Aidan Kehoe
2004-12-06 15:19   ` Katsumi Yamaoka
2004-12-06 22:30   ` Katsumi Yamaoka
2004-12-07  1:03     ` Katsumi Yamaoka
2004-12-07  0:10   ` Aidan Kehoe
2004-12-07  1:04     ` Katsumi Yamaoka
2004-12-07 12:32       ` Katsumi Yamaoka
2004-12-17 12:21         ` Aidan Kehoe
2004-12-17 12:46           ` Katsumi Yamaoka
2004-12-17 16:09             ` Katsumi Yamaoka
2004-12-31  9:01         ` XEmacs hangs in rfc2047-encode-string (Was: XEmacs, Gnus and mm-coding-system priorities.) Steinar Bang
2004-12-31 11:47           ` XEmacs hangs in rfc2047-encode-string Reiner Steib
2004-12-31 14:41             ` Steinar Bang
2004-12-31 19:10               ` Andrey Slusar
2005-01-01  9:04                 ` Steinar Bang
2005-01-01 18:03                   ` Andrey Slusar
2005-01-01 19:25                     ` Steinar Bang [this message]
2005-01-01 22:05                       ` Andrey Slusar
2005-01-02  7:49                         ` Steinar Bang
2004-12-31 12:53           ` Steinar Bang
2004-12-31 13:42           ` Arnaud Giersch
2004-12-31 14:45             ` Steinar Bang
2004-12-07  1:03 ` XEmacs, Gnus and mm-coding-system priorities Katsumi Yamaoka

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=87652hrlxi.fsf@dod.no \
    --to=sb@dod.no \
    /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).