From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: nntp-status-string vs (nntp-status-message)
Date: 12 Apr 1996 05:16:04 +0200 [thread overview]
Message-ID: <w8sd95ef7yj.fsf@hler.ifi.uio.no> (raw)
In-Reply-To: <vafratu3bvu.fsf@dusty.i-have-a-misconfigured-system-so-shoot-me>
Kai Grossjohann <grossjoh@ls6.informatik.uni-dortmund.de> writes:
> What I would like to do is to nntp-send-command. If the response code
> is 442 I want to do something special. Now, (nntp-status-message)
> does not return the code, it only returns the informational message
> after that. nntp-status-string has the code, but I'm not supposed to
> be using it.
(nnheader-get-report 'nntp)
will get the status message from the `nntp' backend. (It really just
returns the `nntp-status-string' variable.) The comment in nntp.el is
outdated, and I've now removed it.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-04-12 3:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-11 17:32 Kai Grossjohann
1996-04-12 3:16 ` Lars Magne Ingebrigtsen [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=w8sd95ef7yj.fsf@hler.ifi.uio.no \
--to=larsi@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).