Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: Unable to see nntp lists when added to secondary sources
Date: Tue, 22 Dec 2015 17:23:40 +0100	[thread overview]
Message-ID: <874mfa4flf.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <87egeev6d3.fsf@think.bvr.lan>

B.V. writes:

> I started `emacs -Q' `M-x gnus' and `^'
> Then `M-x gnus-server-add-server' followed by
> `nntp RET <server-host-name> RET'
> The server is listed and marked open. However, there are no newsgroups
> shown.

It is unclear to me where you look for the list of newsgroups. You press
RET on the server in *Server* buffer, right?

> Is there a way to enable detailed logs or something like that?

There is:

,----[ C-h v nntp-record-commands RET ]
| nntp-record-commands is a variable defined in `nntp.el'.
| Its value is nil
| 
| Documentation:
| *If non-nil, nntp will record all commands in the "*nntp-log*" buffer.
|
`----

ngrep(8) is also good for this kind of debugging (if you're using an
unencrypted connection to the nntp server).


  Best regards,

    Adam

-- 
 "Vejen ender, bålet brænder                                  Adam Sjøgren
  Det brænder for dig, Alexander"                        asjo@koldfront.dk


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2015-12-22 16:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-21 16:52 B.V. Raghav
2015-12-21 16:57 ` Adam Sjøgren
2015-12-22  3:38   ` B.V. Raghav
2015-12-22 12:45     ` Adam Sjøgren
2015-12-22 15:18       ` B.V. Raghav
2015-12-22 15:40         ` B.V. Raghav
2015-12-22 16:23           ` Adam Sjøgren [this message]
2015-12-22 17:07             ` B.V. Raghav
2015-12-22 18:10               ` Adam Sjøgren
2015-12-23  2:44                 ` B.V. Raghav

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=874mfa4flf.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --cc=info-gnus-english@gnu.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).