help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnus error reading on some emails


From: Xiao-Yong Jin
Subject: gnus error reading on some emails
Date: Wed, 25 Feb 2009 13:02:05 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.90 (gnu/linux)

Hi, I'm using gnus bundled with emacs from current cvs

Gnus v5.13
GNU Emacs 23.0.90.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.14.7) of 
2009-02-24

I'm not sure it is a bug or some error caused by my
configuration.  But it happens with a few emails.  The
following is the back trace.

Debugger entered--Lisp error: (wrong-number-of-arguments (lambda (target old 
new) (replace-regexp-in-string old new target)) 4)
  mm-replace-in-string("Content-Type: text/plain; charset=US-ASCII; 
format=flowed\nContent-Transfer-Encoding: 7bit\n\nOn 2009 Feb 25, at 5:23, John 
Lato wrote:\n> Brandon Allbery wrote:\n>> I have to second this; I'm a Unix 
sysadmin, 98% of the time if I'm\n>> writing a program it's for Unix *and* 
requires POSIX APIxs, and even\n>> if it could apply to Windows the program 
needed there would be very\n>> significantly different.  And we have a Windows 
group for that.\n>\n> 2.  As of now, the \"Windows Group\" seems to be mostly 
Duncan.  And\n\nWrong Windows group:  Duncan doesn't work for us.\n\n-- 
\nbrandon s. allbery [solaris,freebsd,perl,pugs,haskell] 
allbery@kf8nh.com\nsystem administrator [openafs,heimdal,too many hats] 
allbery@ece.cmu.edu\nelectrical and computer engineering, carnegie mellon 
university    KF8NH\n\n\n" "\n" "
\n" t)
  byte-code("Ælj‰‰‰ÈÉÊË@#†  mml2015-epg-verify(((#<buffer  *mm*<7>> 
("text/plain" ... ...) 7bit nil nil nil nil nil) (#<buffer  *mm*<8>> 
("application/pgp-signature" ... ...) 7bit nil ("inline" ...) "This is a 
digitally signed message part" nil nil)) (#("multipart/signed" 0 16 (boundary 
"Apple-Mail-6--424928763" micalg "pgp-sha1" protocol 
"application/pgp-signature" buffer #<buffer  *mm*<6>> from 
"allbery@ece.cmu.edu" start nil)) (boundary . "Apple-Mail-6--424928763") 
(micalg . "pgp-sha1") (protocol . "application/pgp-signature")))
  mml2015-verify(((#<buffer  *mm*<7>> ("text/plain" ... ...) 7bit nil nil nil 
nil nil) (#<buffer  *mm*<8>> ("application/pgp-signature" ... ...) 7bit nil 
("inline" ...) "This is a digitally signed message part" nil nil)) 
(#("multipart/signed" 0 16 (boundary "Apple-Mail-6--424928763" micalg 
"pgp-sha1" protocol "application/pgp-signature" buffer #<buffer  *mm*<6>> from 
"allbery@ece.cmu.edu" start nil)) (boundary . "Apple-Mail-6--424928763") 
(micalg . "pgp-sha1") (protocol . "application/pgp-signature")))
  mm-possibly-verify-or-decrypt(((#<buffer  *mm*<7>> ("text/plain" ... ...) 
7bit nil nil nil nil nil) (#<buffer  *mm*<8>> ("application/pgp-signature" ... 
...) 7bit nil ("inline" ...) "This is a digitally signed message part" nil 
nil)) (#("multipart/signed" 0 16 (boundary "Apple-Mail-6--424928763" micalg 
"pgp-sha1" protocol "application/pgp-signature" buffer #<buffer  *mm*<6>> from 
"allbery@ece.cmu.edu" start nil)) (boundary . "Apple-Mail-6--424928763") 
(micalg . "pgp-sha1") (protocol . "application/pgp-signature")))
  mm-dissect-multipart((#("multipart/signed" 0 16 (boundary 
"Apple-Mail-6--424928763" micalg "pgp-sha1" protocol 
"application/pgp-signature" buffer #<buffer  *mm*<6>> from 
"allbery@ece.cmu.edu" start nil)) (boundary . "Apple-Mail-6--424928763") 
(micalg . "pgp-sha1") (protocol . "application/pgp-signature")) 
"allbery@ece.cmu.edu")
  mm-dissect-buffer(t nil "allbery@ece.cmu.edu")
  mm-dissect-multipart((#("multipart/mixed" 0 15 (boundary 
"===============0483791337==" buffer #<buffer  *mm*<5>> from 
"allbery@ece.cmu.edu" start nil)) (boundary . "===============0483791337==")) 
"allbery@ece.cmu.edu")
  mm-dissect-buffer(nil t)
  gnus-display-mime()
  gnus-article-prepare-display()
  gnus-article-prepare(24756 nil)
  gnus-summary-display-article(24756)
  gnus-summary-next-page(nil)
  call-interactively(gnus-summary-next-page nil nil)

I'm not sure where to report the bug.  But feel free to
forward this email to whoever/whichever list may solve the
issue.

Best,
Xiao-Yong
-- 
    c/*    __o/*
    <\     * (__
    */\      <




reply via email to

[Prev in Thread] Current Thread [Next in Thread]