From: Alberto Luaces <aluaces@udc.es>
To: ding@gnus.org
Subject: Re: gmane is always closed.
Date: Thu, 27 Nov 2014 18:33:37 +0100 [thread overview]
Message-ID: <87zjbc8s5q.fsf@eps142.cdf.udc.es> (raw)
In-Reply-To: <87ioi1akps.fsf@mat.ucm.es>
Uwe Brauer <oub@mat.ucm.es> writes:
>>> "Alberto" == Alberto Luaces <aluaces@udc.es> writes:
>
> > Uwe Brauer writes:
> >> What is wrong with my setting? Did gmane change his settings?
>
> > I don't think so; my settings are the same as yours, but I didn't set
> > gmane in gnus.el; I created it directly from the server buffer:
>
> > (nntp "news.gmane.org")
> I deleted even my .newsrc.el file and restarted, same behavior.
>
> So I set debug-on-signal to t
>
> And this is what I got.
[...]
The backtrace mentions the agent. Can you disable it to see if it
behaves differently?
--
Alberto
next prev parent reply other threads:[~2014-11-27 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 11:34 Uwe Brauer
2014-11-26 15:43 ` Alberto Luaces
2014-11-26 18:19 ` Uwe Brauer
2014-11-27 17:33 ` Alberto Luaces [this message]
2014-11-27 18:03 ` Uwe Brauer
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=87zjbc8s5q.fsf@eps142.cdf.udc.es \
--to=aluaces@udc.es \
--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).