From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: nntp and authinfo working?
Date: Fri, 27 Jan 2012 13:22:57 -0600 [thread overview]
Message-ID: <87vcnx2bn2.fsf@lifelogs.com> (raw)
In-Reply-To: <87hazh6p04.fsf@gnus.org>
On Fri, 27 Jan 2012 18:20:43 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I'm pretty sure this is because nntp.el assumes there is only one server
>> buffer per machine address. Lars will have to look at it, I don't know
>> the nnoo stuff well enough.
LI> No, there's no limit to the number of nntp server buffers (per machine
LI> address). At least there shouldn't be.
They seem uniquely mapped to the nntp-address and nntp-port-number.
Consider:
#+begin_src lisp
(defun nntp-make-process-buffer (buffer)
"Create a new, fresh buffer usable for nntp process connections."
(with-current-buffer
(generate-new-buffer
(format " *server %s %s %s*"
nntp-address nntp-port-number
(gnus-buffer-exists-p buffer)))
...
(current-buffer)))
#+end_src
It should use the server's logical name too. But I'm not sure, which is
why I didn't make a fix.
Ted
next prev parent reply other threads:[~2012-01-27 19:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 0:50 Richard Riley
2012-01-10 14:38 ` Ted Zlatanov
2012-01-10 16:39 ` Richard Riley
2012-01-10 17:40 ` Stefan Nobis
2012-01-10 17:46 ` Richard Riley
2012-01-10 18:55 ` Ted Zlatanov
2012-01-10 18:59 ` Richard Riley
2012-01-10 19:04 ` Ted Zlatanov
2012-01-10 19:34 ` Richard Riley
2012-01-10 19:47 ` Ted Zlatanov
2012-01-10 19:55 ` Richard Riley
2012-01-11 13:44 ` Ted Zlatanov
2012-01-27 17:20 ` Lars Ingebrigtsen
2012-01-27 19:22 ` Ted Zlatanov [this message]
2012-01-27 18:27 ` Lars Ingebrigtsen
2012-02-01 18:27 ` Ted Zlatanov
2012-02-01 23:20 ` Lars Ingebrigtsen
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=87vcnx2bn2.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).