From: Mike Fabian <mike.fabian@gmx.de>
Subject: Re: Problem with the latest CVS build
Date: 04 Dec 1999 12:18:06 +0100 [thread overview]
Message-ID: <m3903bnedt.fsf@nozomi.rhein-neckar.de> (raw)
In-Reply-To: Shenghuo ZHU's message of "04 Dec 1999 04:02:57 -0500"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> Where should these files go?
>
> Two other files, base64.el and md5.el, may face the same problem,
> since w3 also has those files, but two copies are different.
I recently had the w3 directory before the gnus directory in my
load-path, which caused problems in Gnus because of the differences in
base64.el. The Gnus version of the function base64-encode-region has
an additional optional parameter which the w3-version of this function
doesn't have:
(defun base64-encode-region (start end &optional no-line-break)
Therefore I got errors about a wrong number of parameters while
accidentally using the w3-version of base64.el.
Mike
--
Mike Fabian <mike.fabian@gmx.de> <mike@nozomi.rhein-neckar.de>
In der Neckarhelle 81, D-69118 Heidelberg-Ziegelhausen
Telephone: +49(0)6221/809222
next prev parent reply other threads:[~1999-12-04 11:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-04 8:12 Daniel Pittman
1999-12-04 8:31 ` Lars Magne Ingebrigtsen
1999-12-04 8:40 ` Daniel Pittman
1999-12-04 9:02 ` Shenghuo ZHU
1999-12-04 11:18 ` Mike Fabian [this message]
1999-12-04 13:27 ` William M. Perry
1999-12-05 0:21 ` Dave Love
1999-12-05 0:19 ` Dave Love
1999-12-05 1:45 ` Lloyd Zusman
1999-12-05 8:38 ` Hans de Graaff
1999-12-05 18:28 ` Lloyd Zusman
1999-12-05 18:41 ` Lloyd Zusman
1999-12-05 21:02 ` Hans de Graaff
1999-12-06 17:44 ` Hrvoje Niksic
1999-12-06 19:13 ` Jan Vroonhof
[not found] ` <ltr9h1s01u.fsf@ <byhfhvubli.fsf@urysohn.math.ethz.ch>
1999-12-07 8:20 ` Hrvoje Niksic
1999-12-07 12:27 ` Jan Vroonhof
1999-12-05 22:58 ` Kai Großjohann
1999-12-05 23:03 ` Lloyd Zusman
1999-12-05 23:24 ` Lloyd Zusman
1999-12-06 10:33 ` Gunnar Evermann
1999-12-06 15:48 ` Lloyd Zusman
1999-12-06 22:42 ` Kai Großjohann
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=m3903bnedt.fsf@nozomi.rhein-neckar.de \
--to=mike.fabian@gmx.de \
/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).