Wrong type argument: listp, "iso-8859-1" (was [Re: Making w3 reasonable])

Wrong type argument: listp, "iso-8859-1" (was [Re: Making w3 reasonable])

[John Palmieri]

Pterodactyl Gnus v0.97

GNU Emacs 20.4.3 (alphaev5-dec-osf4.0f, X toolkit) of Sat Oct  9 1999 on hilbert1


I got the error message in the subject line after reading a recent
message from Hrvoje Niksic to the ding list.  More precisely: in
message <87670ivhs9.fsf@pc-hrvoje.srce.hr>, Hrvoje Niksic wrote

> I've now tried them.  The settings seem to remove most of the junk,
> but not all.  For example, this message is still rendered with some
> font and color changes:

and then there was an attachment, labeled as 'message/rfc822; bureq'.
It was part 2, so I hit '2 b' to display it.  This inserted some
rendered html into the message.  When I was done looking at it, I hit
'q' to quit the current summary buffer, and that's when I got the
error message.  Here is a backtrace:

Signaling: (wrong-type-argument listp "iso-8859-1")
  mm-remove-part((charset . "iso-8859-1"))
  mm-destroy-part((charset . "iso-8859-1"))
  mm-destroy-parts(((charset . "iso-8859-1")))
  mm-destroy-parts(("multipart/mixed" (#<killed buffer> ("text/plain") nil nil nil nil nil nil) (#<killed buffer> ("message/rfc822") nil nil ("attachment" ...) nil nil nil) #<buffer  *mm*<5>> ("text/html" (charset . "iso-8859-1")) nil (lambda nil (let ... ... ...)) nil nil nil nil))
  gnus-summary-exit()
  call-interactively(gnus-summary-exit)

Has this been seen before?

-- 
John H. Palmieri                      
Dept of Mathematics, Box 354350    palmieri@math.washington.edu
University of Washington	   http://www.math.washington.edu/~palmieri
Seattle, WA 98195-4350

Re: Wrong type argument: listp, "iso-8859-1" (was [Re: Making w3 reasonable])

[William M. Perry]

John Palmieri <palmieri@math.washington.edu> writes:

> Pterodactyl Gnus v0.97
> 
> GNU Emacs 20.4.3 (alphaev5-dec-osf4.0f, X toolkit) of Sat Oct  9 1999 on hilbert1
> 
> 
> I got the error message in the subject line after reading a recent
> message from Hrvoje Niksic to the ding list.  More precisely: in
> message <87670ivhs9.fsf@pc-hrvoje.srce.hr>, Hrvoje Niksic wrote
> 
> > I've now tried them.  The settings seem to remove most of the junk,
> > but not all.  For example, this message is still rendered with some
> > font and color changes:
> 
> and then there was an attachment, labeled as 'message/rfc822; bureq'.
> It was part 2, so I hit '2 b' to display it.  This inserted some
> rendered html into the message.  When I was done looking at it, I hit
> 'q' to quit the current summary buffer, and that's when I got the
> error message.  Here is a backtrace:
> 
> Signaling: (wrong-type-argument listp "iso-8859-1")
>   mm-remove-part((charset . "iso-8859-1"))
>   mm-destroy-part((charset . "iso-8859-1"))
>   mm-destroy-parts(((charset . "iso-8859-1")))
>   mm-destroy-parts(("multipart/mixed" (#<killed buffer> ("text/plain") nil nil nil nil nil nil) (#<killed buffer> ("message/rfc822") nil nil ("attachment" ...) nil nil nil) #<buffer  *mm*<5>> ("text/html" (charset . "iso-8859-1")) nil (lambda nil (let ... ... ...)) nil nil nil nil))
>   gnus-summary-exit()
>   call-interactively(gnus-summary-exit)
> 
> Has this been seen before?

I've seen this lately as well.

-bp

Re: Wrong type argument: listp, "iso-8859-1" (was [Re: Making w3 reasonable])

[Lars Magne Ingebrigtsen]

John Palmieri <palmieri@math.washington.edu> writes:

> I got the error message in the subject line after reading a recent
> message from Hrvoje Niksic to the ding list.  More precisely: in
> message <87670ivhs9.fsf@pc-hrvoje.srce.hr>, Hrvoje Niksic wrote
> 
> > I've now tried them.  The settings seem to remove most of the junk,
> > but not all.  For example, this message is still rendered with some
> > font and color changes:
> 
> and then there was an attachment, labeled as 'message/rfc822; bureq'.
> It was part 2, so I hit '2 b' to display it.  This inserted some
> rendered html into the message.  When I was done looking at it, I hit
> 'q' to quit the current summary buffer, and that's when I got the
> error message.  

I don't see this; is this still a problem in 0.98.1?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen