From: "Steven L. Baur" <steve@miranova.com>
Subject: Re: September Gnus 0.58 is released
Date: 26 Mar 1996 22:21:18 -0800 [thread overview]
Message-ID: <m2d95zjbtt.fsf_-_@deanna.miranova.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 26 Mar 1996 20:23:20 -0800
Expect major breakage in XEmacs. I got only about half the files byte
compiled with no apparent error message, and attempting to recompile
``some'' gives a nasty message in one of the new files:
$ make some
xemacs -batch -q -no-site-file -l ./dgnushack.el -f dgnushack-recompile
Loading /usr/lib/xemacs/sgnus-0.58/lisp/dgnushack.el...
Loading gnus...
Loading mail-utils...
Loading timezone...
Loading nnheader...
Loading sendmail...
Loading message...
Loading mail-header...
Wrong type argument: listp, #<keymap 0 entries 0x49d>
XEmacs exiting.
make: *** [some] Error 255
Presumably this is due to incompatibility in XEmacs/Emacs mail modes.
Coming at the same time as the second consecutive uncompilable alpha
test Linux kernel is synchronicity I guess. :-(
Regards,
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
prev parent reply other threads:[~1996-03-27 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-27 4:23 Lars Magne Ingebrigtsen
1996-03-27 6:21 ` Steven L. Baur [this message]
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=m2d95zjbtt.fsf_-_@deanna.miranova.com \
--to=steve@miranova.com \
/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).