From: Tassilo Horn <tsdh@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Posting to my university's nntp server hangs
Date: Wed, 05 Mar 2014 19:16:53 +0100 [thread overview]
Message-ID: <87mwh4y0h6.fsf@gnu.org> (raw)
In-Reply-To: <87lhwotw0t.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Wed, 05 Mar 2014 18:06:42 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
>>> After you `C-g', what's in the " *server <something> nntp...*"
>>> buffer (note leading space)?
>>
>> The buffer " *server news.uni-koblenz.de nntp *nntpd**" is completely
>> empty.
>
> Hm. And you only have one of those buffers?
No, one for each nntp server (gmane and my university).
- " *server news.uni-koblenz.de nntp *nntpd**"
- " *server news.gmane.org nntp *nntpd**"
And the " *server news.uni-koblenz.de nntp *nntpd**" buffer sometimes
contains stuff, e.g., after a `g' in *Group* it contains:
--8<---------------cut here---------------start------------->8---
infko.softtech 0000003697 0000000034 y
infko.oopm 0000003087 0000000001 m
infko.mac 0000002661 0000000001 y
infko.linux 0000001959 0000000001 y
infko.jobs 0000000978 0000000001 y
infko.intern 0000000932 0000000003 y
infko.info 0000000620 0000000003 y
infko.infm 0000014289 0000000001 y
infko.inf 0000008373 0000000001 y
infko.general 0000092970 0000000003 y
infko.easy-coding 0000000015 0000000001 y
infko.cv 0000014423 0000000087 y
comp.lang.java.programmer 0000704049 0000703949 y
de.comp.text.tex 0000251110 0000251080 y
alt.religion.emacs 0000001961 0000001962 y
infko.test 0000004336 0000000030 y
--8<---------------cut here---------------end--------------->8---
> What about the " *nntpd*" buffer?
That's also empty.
Bye,
Tassilo
next prev parent reply other threads:[~2014-03-05 18:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 9:41 Tassilo Horn
2014-03-05 14:02 ` Lars Ingebrigtsen
2014-03-05 14:12 ` Tassilo Horn
2014-03-05 17:06 ` Lars Ingebrigtsen
2014-03-05 18:16 ` Tassilo Horn [this message]
2014-03-05 18:25 ` Lars Ingebrigtsen
2014-03-06 7:37 ` Tassilo Horn
2014-03-06 12:19 ` Tassilo Horn
2014-03-06 12:56 ` Steinar Bang
2014-03-07 8:42 ` Tassilo Horn
2014-03-07 9:30 ` Steinar Bang
2014-03-07 10:19 ` Tassilo Horn
2014-03-07 11:45 ` Steinar Bang
2014-03-06 13:02 ` Eric S Fraga
2014-03-06 18:15 ` Andreas Schwab
2014-03-07 10:32 ` Eric S Fraga
2014-03-07 15:04 ` Lars Ingebrigtsen
2014-03-07 15:43 ` Tassilo Horn
2014-03-07 15:49 ` Tassilo Horn
2014-03-06 18:14 ` Andreas Schwab
2014-03-07 15:04 ` 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=87mwh4y0h6.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=ding@gnus.org \
--cc=larsi@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).