Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Errors parsing .newsrc
Date: Mon, 13 Jan 2014 18:04:42 +0700	[thread overview]
Message-ID: <87mwj0jg6t.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <CAMdGyq_vsY7PpbartNu-wLajectSD2c+Ury5bydz2vvT=Qu1zg@mail.gmail.com>

Chris Warburton <chriswarbo@googlemail.com> writes:

> On Sun, Jan 12, 2014 at 9:12 AM, Eric Abrahamsen
> <eric@ericabrahamsen.net> wrote:
>
>>>> I don't even have a .newsrc here, just the .newsrc.eld. If you've *also*
>>>> got the .newsrc.eld, you could try setting gnus-read-newsrc-file to nil
>>>> temporarily, which will have it ignore the plain old .newsrc.
>>>
>>> I tried that but it didn't help I'm afraid :(
>>
>> But you reported problems in gnus-newsrc-to-gnus-format... If you've
>> removed or ignored that file, how is it still not working?
>
> Ah, I've tried setting gnus-read-newsrc-file again and Gnus is now
> loading :) I thought I'd
> already tried this, after reading the "Startup Files" section of the
> manual, but I probably
> copy/pasted the wrong variable name and set gnus-save-newsrc-file to
> nil instead!

Glad it's working!

> Many thanks for helping me get up and running! I'm happy to experiment
> and find the cause
> if anyone cares. Otherwise I'll just add it to the long list of things
> I've had to fix after an
> Ubuntu upgrade (PulseAudio, Perl, MySQL, apt, ....!)

Try Arch linux -- things just break a little bit, continuously. It
spreads the pain out!




      reply	other threads:[~2014-01-13 11:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 11:51 Chris Warburton
2014-01-11  2:47 ` Eric Abrahamsen
2014-01-11 13:09   ` Chris Warburton
2014-01-12  9:12     ` Eric Abrahamsen
2014-01-13  9:20       ` Chris Warburton
2014-01-13 11:04         ` Eric Abrahamsen [this message]

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=87mwj0jg6t.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).