Gnus development mailing list
 help / color / mirror / Atom feed
From: Mark Hovey <hovey@picard.math.wesleyan.edu>
Subject: (unknown)
Date: Thu, 15 Oct 1998 12:32:46 -0400	[thread overview]
Message-ID: <199810151632.MAA02872@picard.math.wesleyan.edu> (raw)

Sender: hovey@picard.math.wesleyan.edu
To: ding@gnus.org
Subject: Re: pgnus-0.34 bug
From: Mark Hovey <mhovey@wesleyan.edu>
Date: 15 Oct 1998 12:32:46 -400
Message-ID: <yl67dlg501.fsf@picard.math.wesleyan.edu>
Lines: 28
User-Agent: Gnus/5.0700000000000003 (Pterodactyl Gnus v0.34) Emacs/20.2

Thanks to Karl Kleinpaste for fixing the bug I mentioned before, which
is apparently well-known.  However, I now have another bug.  

Invalid coding system: iso-8859-1 

This happens when I try to read a mail message in one my nnbabyl
groups.  Eventually it lets me read the message, but still complains.  
I use  Emacs 20.2.1.  

Here is the backtrace.

Signaling: (coding-system-error iso-8859-1)
  mm-decode-coding-region(1061 1669 iso-8859-1)
  mm-decode-body("us-ascii" nil)
  article-decode-charset()
  run-hooks(gnus-article-decode-hook)
  gnus-request-article-this-buffer(19 "nnbabyl:kendra")
  gnus-article-prepare(19 nil)
  gnus-summary-display-article(19)
  gnus-summary-next-page(nil)
* call-interactively(gnus-summary-next-page)

In my .Xdefaults i have a line

Emacs*font: -adobe-courier-medium-r-normal--*-110-*-*-m-*-iso8859-1

which must be where iso8859-1 comes from.
          Mark Hovey


             reply	other threads:[~1998-10-15 16:32 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-15 16:32 Mark Hovey [this message]
1998-10-17 21:25 ` none Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
2021-09-17 20:35 Bob Newell
2021-09-18  6:15 ` (unknown) Andreas Schwab
2006-07-29 14:11 (unknown) Daiki Ueno
2003-04-02  5:43 (unknown) Ben Brown
2003-01-21  2:44 (unknown) Jason L Tibbitts III
2002-10-20 20:14 (unknown) Unknown
2002-05-10 20:40 (unknown) joseph edward
2002-05-09  4:49 (unknown) laurent mpeti kabila
2002-05-07  6:06 (unknown) laurent mpeti kabila
2002-05-03 15:51 (unknown) laurent mpeti kabila
2002-01-21  5:19 (unknown) Ä£±¸¿¡°Ô
2001-12-09  3:15 (unknown) Harry Putnam
2001-11-11 17:39 (unknown) owner-ding
2001-11-05 15:25 (unknown) Harry Putnam
2001-11-04 18:05 (unknown) Harry Putnam
2001-11-02  8:06 (unknown) BALABAN ADRIAN
2001-04-03 17:25 (unknown) Harry Putnam
2000-12-13 15:18 (unknown) colman
2000-10-09  9:20 (unknown) Umesh Biradar
2000-08-15 15:32 (unknown) Abuse
1999-04-19 16:15 (unknown) karthy
1998-11-29 23:54 (unknown) Jason L Tibbitts III
1998-10-17  6:59 (unknown) Mark Hovey
1998-10-15 15:29 (unknown) Mark Hovey
1998-09-19 15:34 (unknown) Michael Harnois
1997-06-08  2:23 (unknown) anonymous
1997-03-26 14:37 (unknown) Thomas Bopp
1996-11-28  1:50 (unknown) lars
1996-08-19  5:16 (unknown) Michael Harnois
1996-02-21 23:26 (unknown) Steven L. Baur
1996-02-21 23:06 (unknown) Steven L. Baur

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=199810151632.MAA02872@picard.math.wesleyan.edu \
    --to=hovey@picard.math.wesleyan.edu \
    /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).