Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: nntps and posting.
Date: Tue, 27 Feb 2007 10:56:09 +0900	[thread overview]
Message-ID: <b4mk5y48iti.fsf@jpl.org> (raw)
In-Reply-To: <b4mfy99beux.fsf@jpl.org>

>>>>> In <b4mfy99beux.fsf@jpl.org> Katsumi Yamaoka wrote:

>>>>>> --- nntp.el	05 Feb 2006 14:56:44 +0100	1.31
>>>>>> +++ nntp.el	25 Dec 2006 13:48:53 +0100

[...]

>  	  (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)))

> Let us do it and wait for the response.  I've installed the
> patch in the trunk.  What I can do when someone complains is
> only to remove it, though.

I got a response from a person who uses `nntp-open-ssl-stream'
(I Bcc this message to the person).  He wrote that the recent
change stops Gnus from connecting to the nntps server while
Michaël requires it.  It is obvious that some nntps servers
don't echo commands but others do.  So, we have to make it
change the behavior according to the version of the nntps server
automatically or make it customizable by a user.  Since there
seems to be no person to work with nntps servers for the moment,
I've added the following two server variables to the trunk and
the v5-10 branch.

`nntp-never-echoes-commands'
     Non-`nil' means the nntp server never echoes commands.  It is
     reported that some nntps server doesn't echo commands.  So, you
     may want to set this to non-`nil' in the method for such a server
     setting `nntp-open-connection-function' to `nntp-open-ssl-stream'
     for example.  The default value is `nil'.  Note that the
     `nntp-open-connection-functions-never-echo-commands' variable
     overrides the `nil' value of this variable.

`nntp-open-connection-functions-never-echo-commands'
     List of functions that never echo commands.  Add or set a function
     which you set to `nntp-open-connection-function' to this list if
     it does not echo commands.  Note that a non-`nil' value of the
     `nntp-never-echoes-commands' variable overrides this variable.  The
     default value is `(nntp-open-network-stream)'.

It might not have been necessary to have made the later a server
variable but you can use it to have the default value.  For
instance, if all the nntps servers that Michaël connects to don't
echo commands, you can simply set it as follows:

(setq nntp-open-connection-functions-never-echo-commands
      '(nntp-open-network-stream nntp-open-ssl-stream))

Otherwise, you can use `nntp-never-echoes-commands' per server
like the following:

(setq gnus-select-method
      '(nntp "server"
	     (nntp-address "server.example.com")
	     (nntp-open-connection-function nntp-open-ssl-stream)
	     (nntp-never-echoes-commands t)
	     ...
	     ...))

The person who sent a mail to me has nothing to do of course.

Regards,



      parent reply	other threads:[~2007-02-27  1:56 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
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 [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=b4mk5y48iti.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.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).