From: Hans de Graaff <hans@degraaff.org>
Subject: Re: 5.8.8 and bbdb at XEmacs startup
Date: 05 Jan 2001 22:20:40 +0100 [thread overview]
Message-ID: <87u27dr907.fsf@graaff.xs4all.nl> (raw)
In-Reply-To: <ulmsr56we.fsf@uto.dec.com>
On 04 Jan 2001, Han Pilmeyer wrote:
>
> I was so happy today when I say the 5.8.8 kit. I compiled it
> immediately and that seemed to work fine. Unfortunately I now have
> a problem when I start XEmacs (21.1.9 on W2K) in combination with
> bbdb (I think).
>
> Any suggestions?
>
> Signaling: (end-of-file "internal input stream")
> load-internal("d:\\Documents and Settings\\pilmeyer\\My
> Documents\\Emacs\\gnus.elc" nil t t binary)
It looks to me like there is a problem loading your gnus.elc
file. Maybe there was some sort of problem during compilation?
Hans
next prev parent reply other threads:[~2001-01-05 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-04 21:44 Han Pilmeyer
2001-01-05 21:20 ` Hans de Graaff [this message]
2001-01-05 22:17 ` Eddie McCreary
2001-01-06 20:43 ` Han Pilmeyer
2001-01-30 16:30 ` Han Pilmeyer
2001-02-01 0:05 ` Eddie McCreary
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=87u27dr907.fsf@graaff.xs4all.nl \
--to=hans@degraaff.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).