From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: problem in `nnheader-report'?
Date: 30 Apr 2001 17:39:23 -0400 [thread overview]
Message-ID: <2nk842vzhw.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <87lmoiurbl.church.of.emacs@space-ghost.verbum.org> (Colin Walters's message of "30 Apr 2001 15:21:18 -0400")
Colin Walters <walters@cis.ohio-state.edu> writes:
> In CVS, there seems to be a problem with either the function
> `nnheader-report', or some of the calls to it in
> `nntp-retrieve-groups'. For example, the code:
>
> (unless (gnus-buffer-live-p buf)
> (error
> (nnheader-report 'nntp "Connection to %s is closed." server)))
>
> in nntp.el seems to expect nnheader-report to return a string, but it
> currently always returns nil. So here's a patch which should make it
> return the string. I'm not sure if this is the correct fix or not,
> but it seems to work.
It's my fault for adding these error codes. Actually, nnheader-report
should always return nil, because most backends use nnheader-report to
return nil. I'll install a patch in minutes.
ShengHuo
prev parent reply other threads:[~2001-04-30 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-30 19:21 Colin Walters
2001-04-30 21:39 ` ShengHuo ZHU [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=2nk842vzhw.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).