From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: nntps and posting.
Date: Wed, 17 Jan 2007 12:44:41 +0900 [thread overview]
Message-ID: <b4md55ee2qe.fsf@jpl.org> (raw)
In-Reply-To: <87ac0lrea5.fsf@lrde.org>
>>>>> In <87ac0lrea5.fsf@lrde.org> Michaël Cadilhac wrote:
>> --- nntp.el 05 Feb 2006 14:56:44 +0100 1.31
>> +++ nntp.el 25 Dec 2006 13:48:53 +0100
>> @@ -451,10 +451,11 @@
>> wait-for nnheader-callback-function)
>> ;; If nothing to wait for, still remove possibly echo'ed commands.
>> ;; We don't have echos if nntp-open-connection-function
>> - ;; is `nntp-open-network-stream', so we skip this in that case.
>> + ;; is `nntp-open-network-stream' or `nntp-open-ssl-stream',
>> + ;; so we skip this in that cases.
>> (unless (or wait-for
>> - (equal nntp-open-connection-function
>> - 'nntp-open-network-stream))
>> + (memq nntp-open-connection-function
>> + '(nntp-open-network-stream nntp-open-ssl-stream)))
>> (nntp-accept-response)
>> (save-excursion
>> (set-buffer buffer)
>>
>> Without it, I'm getting stuck after my message is posted (it is,
>> actually).
>>
>> I don't know if the patch makes sense, but can we discuss this bug?
> Second ping :-)
Well, I have no account on nntps servers. It will be necessary
to verify that this change is harmless for every nntps server.
Can anyone do that?
Regards,
next prev parent reply other threads:[~2007-01-17 3:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-25 12:53 Michaël Cadilhac
2007-01-08 8:30 ` Michaël Cadilhac
2007-01-14 12:20 ` Michaël Cadilhac
2007-01-17 3:44 ` Katsumi Yamaoka [this message]
2007-01-29 7:33 ` Michaël Cadilhac
2007-02-13 23:23 ` Michaël Cadilhac
2007-02-14 3:24 ` Katsumi Yamaoka
2007-02-15 10:39 ` Michaël Cadilhac
2007-02-27 1:56 ` Katsumi Yamaoka
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=b4md55ee2qe.fsf@jpl.org \
--to=yamaoka@jpl.org \
/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).