nntp-status-string vs (nntp-status-message)

nntp-status-string vs (nntp-status-message)

[Kai Grossjohann]

There is a comment in nntp.el which goes like this:

,-----
| (defvar nntp-status-string nil
|   "Save the server response message.
| You'd better not use this variable in NNTP front-end program but
| instead call function `nntp-status-message' to get status message.")
`-----

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.

I do not want to rely on the special informational message 'cause that
might be changed.

What do I do then?

tia,
kai
--
There ain't no cure for the summertime blues.

Re: nntp-status-string vs (nntp-status-message)

[Lars Magne Ingebrigtsen]

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."