pgnus-0.37: write-region gets 7 args

pgnus-0.37: write-region gets 7 args

[Morgan Fletcher]

I'm running pgnus-0.37 & gnu emacs 20.2.2 on i386 linux (debian). I open an
e-mail containing these attachments:

  [1. text/plain]...
  [2. image/jpeg (67FJ45.jpg)]
  [3. image/gif (FJ-45 - 1.gif)]...
  [4. image/gif (FJ-45 - 2.gif)]...
  [5. image/gif (FJ-45 - 3.gif)]...
  [6. image/gif (FJ-45 - 4.gif)]...
  [7. image/gif (FJ-45 - 5.gif)]...
  [8. image/gif (FJ-45.gif)]...

Attachment #1 displays fine, but if I attempt to view attachment #2 with 
`2 b` I get this:

Signaling: (wrong-number-of-arguments #<subr write-region> 7)
  write-region(1 219416 "/tmp/emm.e00635/67FJ45.jpg" nil nomesg nil no-conversion)
  mm-display-external((#<buffer  *mm*<2>> ("image/jpeg" (name . "67FJ45.jpg")) base64 nil ("attachment" (filename . "67FJ45.jpg")) nil) "/usr/bin/zgv %s")
  mm-display-part((#<buffer  *mm*<2>> ("image/jpeg" (name . "67FJ45.jpg")) base64 nil ("attachment" (filename . "67FJ45.jpg")) nil))
  gnus-mm-display-part((#<buffer  *mm*<2>> ("image/jpeg" (name . "67FJ45.jpg")) base64 nil ("attachment" (filename . "67FJ45.jpg")) nil))
  gnus-article-view-part(2)
* call-interactively(gnus-article-view-part)

(The same is true for attachments 3-8.)

If I do `C-h f write-region RET`, it says it takes up to six args:

  (write-region START END FILENAME &optional APPEND VISIT LOCKNAME)

But the call in mm-display-external (mm-decode.el) looks like this:

  (write-region (point-min) (point-max)
	        file nil 'nomesg nil 'no-conversion)

How come they don't match? Could it be that pgnus needs a different version
of write-region than the one it's finding? My load-path has
/home/morgan/pgnus-0.37/lisp as its first element.

I'm an elisp ignoramus, so I don't know what else to offer. I can uuencode
the message and send it to you, Lars, if you'd like.

morgan
-- 
VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
>> M o r g a n   F l e t c h e r         http://www.hahaha.org <<
>> Tibi gratias agimus quod nihil fumas.     morgan@hahaha.org <<

Re: pgnus-0.37: write-region gets 7 args

[Lars Magne Ingebrigtsen]

Morgan Fletcher <morgan@hahaha.org> writes:

> Signaling: (wrong-number-of-arguments #<subr write-region> 7)
>   write-region(1 219416 "/tmp/emm.e00635/67FJ45.jpg" nil nomesg nil no-conversion)

This is way weird.  This is a subr, so if there's a bug somewhere,
it's in the C layer.  Isn't it?

> I'm running pgnus-0.37 & gnu emacs 20.2.2 on i386 linux (debian).

Ooh.  Emacs 20.2.  The Dreaded Release.  I'd suggest upgrading to
Emacs 20.3, it fixes oodles and oodles and oodles of bugs in Emacs
20.2.

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

Re: pgnus-0.37: write-region gets 7 args

[Morgan Fletcher]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> > Signaling: (wrong-number-of-arguments #<subr write-region> 7)
> >   write-region(1 219416 "/tmp/emm.e00635/67FJ45.jpg" nil nomesg nil no-conversion)
> 
> This is way weird.  This is a subr, so if there's a bug somewhere,
> it's in the C layer.  Isn't it?

Yep.

> > I'm running pgnus-0.37 & gnu emacs 20.2.2 on i386 linux (debian).
> 
> Ooh.  Emacs 20.2.  The Dreaded Release.  I'd suggest upgrading to
> Emacs 20.3, it fixes oodles and oodles and oodles of bugs in Emacs
> 20.2.

Just upgraded to 20.3.2, and now it works fine. Sorry for the false alarm,
and: Thanks!

morgan
-- 
VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
>> M o r g a n   F l e t c h e r         http://www.hahaha.org <<
>> Tibi gratias agimus quod nihil fumas.     morgan@hahaha.org <<

Re: pgnus-0.37: write-region gets 7 args

[Jason R Mastaler]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Ooh.  Emacs 20.2.  The Dreaded Release.  I'd suggest upgrading to
> Emacs 20.3, it fixes oodles and oodles and oodles of bugs in Emacs
> 20.2.

Maybe this should go into the FAQ?  Upgrading from Emacs 20.2 seems to 
fix alot of "mysterious" Gnus problems.

Re: pgnus-0.37: write-region gets 7 args

[Justin Sheehy]

Jason R Mastaler <jason@4b.org> writes:

> Maybe this should go into the FAQ?  Upgrading from Emacs 20.2 seems to 
> fix alot of "mysterious" Gnus problems.

Good call.  The FAQ has been updated to reflect this.

-Justin