From: Stefanie Teufel <s.teufel@ndh.net>
Subject: Re: XEmacs 21.2-b12 + PGnus v0.80 + leafnode 1.8.1 = no server
Date: 07 Mar 1999 21:27:31 +0100 [thread overview]
Message-ID: <lwk8wtcafg.fsf@diabolo.ndh.net> (raw)
In-Reply-To: "Robin S. Socha"'s message of "07 Mar 1999 02:12:44 +0100"
"Robin S. Socha" <robin@socha.net> writes:
> Subject says all (I hope) - the above setup cannot connect to the
> newsserver. If someone could tell me how to set debug-on-error for
> this, I could give a more meaningful error message ;-) XEmacs 21.2-b11
> and 21.0-b6x work, though.
I cannot confirm this. Works like a charm here.
Stefanie
--
Stefanie Teufel http://linux01.gwdg.de/~steufel
"Hetzer, Anmacher, Dauerspotter, Dauerclowns duze ich deshalb nicht,
weil ich in der physischen Welt Menschen sieze, die tausendfach
anstaendiger sind." Norbert Harry Marzahn <71Zks9p5bXB@nm01.vision.IN-BRB.DE>
next prev parent reply other threads:[~1999-03-07 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-07 1:12 Robin S. Socha
1999-03-07 20:27 ` Stefanie Teufel [this message]
1999-03-14 15:50 ` 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=lwk8wtcafg.fsf@diabolo.ndh.net \
--to=s.teufel@ndh.net \
/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).