From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Gnus v5.2.3 is released
Date: 30 May 1996 23:15:47 +0200 [thread overview]
Message-ID: <rjg28hdfr0.fsf@kleene.dina.kvl.dk> (raw)
In-Reply-To: Steven L Baur's message of 30 May 1996 13:17:36 -0700
>>>>> "SLB" == Steven L Baur <steve@miranova.com> writes:
SLB> The .custom.el written by XEmacs appears to be incompatible with GNU
SLB> Emacs 19.31.
No. The Gnus 5.2 custom.el is just broken. It cannot read anything.
If you use the custom.el bundled with Emacs 19.31, you will probably
find that it can read your the XEmacs generated ".custom.el" file with
no problems.
next prev parent reply other threads:[~1996-05-30 21:15 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
1996-05-30 21:15 ` Per Abrahamsen [this message]
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=rjg28hdfr0.fsf@kleene.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).