From: Steven L Baur <steve@miranova.com>
Cc: ding@ifi.uio.no
Subject: Re: Gnus v5.2.3 is released
Date: 30 May 1996 13:17:36 -0700 [thread overview]
Message-ID: <m2ivdd531b.fsf@deanna.miranova.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 29 May 1996 20:51:52 -0700
The .custom.el written by XEmacs appears to be incompatible with GNU
Emacs 19.31. Prior to attempting byte compilation with 19.31 I had
been experimenting with it on XEmacs, and had a new .custom.el created.
$ make
rm -f *.elc ; emacs -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-compile
Wrote /usr/local/share/emacs/site-lisp/gnus-5.2/lisp/browse-url.elc
Wrote /usr/local/share/emacs/site-lisp/gnus-5.2/lisp/custom.elc
Wrote /usr/local/share/emacs/site-lisp/gnus-5.2/lisp/dgnushack.elc
Loading /home/steve/.custom.el...
While compiling toplevel forms in file /usr/local/share/emacs/site-lisp/gnus-5.2/lisp/gnus-cache.el:
!! Wrong number of arguments ((#[(face pixmap &optional frame) "À Â
%‡" [internal-set-face-1 face background-pixmap pixmap 6 frame] 6 289395 (internal-face-interactive "stipple")] 1))
I still don't think it's a good idea for Gnus to be loading a
.custom.el from the account doing the byte compiling.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.
next prev parent reply other threads:[~1996-05-30 20:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-30 3:51 Lars Magne Ingebrigtsen
1996-05-30 7:29 ` Steven L Baur
1996-05-30 10:14 ` Per Abrahamsen
1996-05-30 16:43 ` Steven L Baur
1996-05-30 20:17 ` Steven L Baur [this message]
1996-05-30 21:15 ` Per Abrahamsen
1996-05-31 1:09 ` Lars Magne Ingebrigtsen
1996-05-31 1:14 ` Lars Magne Ingebrigtsen
1996-05-31 2:35 ` Steven L Baur
1996-05-31 3:03 ` Lars Magne Ingebrigtsen
1996-05-31 15:12 ` Scott Blachowicz
1996-05-31 16:19 ` Per Abrahamsen
1996-05-31 23:30 ` Lars Magne Ingebrigtsen
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=m2ivdd531b.fsf@deanna.miranova.com \
--to=steve@miranova.com \
--cc=ding@ifi.uio.no \
/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).