Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: vincent.belaiche@gmail.com (Vincent Belaïche)
To: info-gnus-english@gnu.org
Cc: "Vincent Belaïche" <vincent.belaiche@gmail.com>
Subject: Re: My gnus does not fetch articles
Date: Fri, 21 Jun 2013 19:37:58 +0200	[thread overview]
Message-ID: <80k3lnmkjt.fsf@gmail.com> (raw)
In-Reply-To: <m2ppvucw3r.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Mon, 10 Jun 2013 07:27:23 +0200 vincent.belaiche@gmail.com (Vincent Belaïche) wrote: 
>
> VB> What I did is:
> VB> 1. I exited gnus with `q'
> VB> 2. I edited the ~/.newsrc file and deleted both lines with
> VB>    fr.comp.text.tex and comp.soft-sys.math.scilab
> VB> 3. I reentered gnus with `M-x gnus', and re-subscribed both these groups
> VB>    with `U' or `S S'
> VB> 4. Both groups still have the same issue, whether I endter with `RET' or
> VB>    `C-u RET', I do not get the latest news. Surprising the last message
> VB>    I get is exactly the same as before cleanign the ~/.newsrc.
>
> Huh.  Could you check if the Agent is on for those groups?
>

Sorry for the delay in feedbacking --- I have been quite busy with a few
new bugs on jPicEdt these days.

Having said that, I did not really know about the Agent... I will read
the manual and check that.

> Can you try as a completely new user and see if anything changes?
>

Well, I am accessing through a free server named news.gegeweb.org that
is provided by a good willed person --- so I would not like to bother
this kind person again to create a new account just for the sake of
debugging my gnus. So, I will do that as a last resort.

> It really seems like your state is being saved somewhere.
>

Hopefully there is an explanation, as I wrote it is quite surprising
that for some groups like comp.lang.perl.misc or gnu.emacs.gnus, things
seem normal, and for others like fr.comp.text.tex,
comp.soft-sys.math.scilab or fr.comp.applications.emacs that does not
work. Curiously it seems that those group that do not work are those for
which the server it probably located in France --- ?! --- like myself.

> Ted

  Vincent.

  reply	other threads:[~2013-06-21 17:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-08 13:59 Vincent Belaïche
2013-06-08 14:03 ` Vincent Belaïche
2013-06-10  4:18   ` Ted Zlatanov
2013-06-10  5:24     ` Vincent Belaïche
2013-06-10  5:27     ` Vincent Belaïche
2013-06-10  5:31       ` Vincent Belaïche
2013-06-10  5:38         ` Vincent Belaïche
2013-06-10  6:34       ` Ted Zlatanov
2013-06-21 17:37         ` Vincent Belaïche [this message]
2013-06-30 20:10           ` Vincent Belaïche
2013-07-02 15:32             ` Ted Zlatanov
2013-07-05  4:13               ` Vincent Belaïche
2013-06-10 10:50       ` Adam Sjøgren
     [not found]       ` <mailman.1324.1370861462.22516.info-gnus-english@gnu.org>
2013-06-21 17:45         ` Vincent Belaïche
2013-06-08 15:03 ` Adam Sjøgren
     [not found] ` <mailman.1220.1370703834.22516.info-gnus-english@gnu.org>
2013-06-09  4:03   ` Vincent Belaïche

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=80k3lnmkjt.fsf@gmail.com \
    --to=vincent.belaiche@gmail.com \
    --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).