Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: multipart/related test
Date: 29 Nov 1998 22:55:57 +0100	[thread overview]
Message-ID: <m33e72f9jm.fsf@sparky.gnus.org> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "29 Nov 1998 19:56:10 +0100"

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

> Just installed pgnus-0.56 and w3-4.0pre.30 on Emacs 20.3, and this is
> what happened:
> 
> ,-----
> | Signaling: (wrong-number-of-arguments #<subr buffer-string> 3)
> |   (buffer-string nil nil (mm-handle-buffer part))

My bad.  Emacs 20.3's `buffer-string' doesn't take a BUFFER
parameter.

Er.  How weird.  `buffer-string' is an alias for `buffer-substring' in
XEmacs 21.2.  Has it always been that way?  And jere I just convinced
RMS to let `buffer-string' take an optional BUFFER parameter in Emacs
20.4, all for naught, it seems...

To clarify: In Emacs 20.4, `buffer-substring' takes mandatory START
and END params, while `buffer-string' takes an optional BUFFER param.
In XEmacs 21.2, there's only one function, which takes three optional
params -- start, end, and buffer.  I think the Emacs 20.4 thing makes
more sense.

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


  parent reply	other threads:[~1998-11-29 21:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-29 14:56 Lars Magne Ingebrigtsen
1998-11-29 18:56 ` Kai.Grossjohann
1998-11-29 18:56   ` Kai.Grossjohann
1998-11-29 21:55   ` Lars Magne Ingebrigtsen [this message]
1998-11-29 23:11     ` Hrvoje Niksic
1998-11-30  0:15       ` Lars Magne Ingebrigtsen
1998-11-30  0:42         ` Hrvoje Niksic
1998-11-30  1:47           ` Lars Magne Ingebrigtsen
1998-11-30 14:02             ` Jan Vroonhof
1998-11-30 14:10               ` Hrvoje Niksic
1998-11-30 14:06             ` Kai.Grossjohann
1998-11-29 19:29 ` Simon Josefsson
1998-11-29 20:50   ` William M. Perry

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=m33e72f9jm.fsf@sparky.gnus.org \
    --to=larsi@gnus.org \
    /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).