Gnus development mailing list
 help / color / mirror / Atom feed
From: jidanni@jidanni.org
To: ding@gnus.org
Cc: acid@debian.org, debian-emacsen@lists.debian.org
Subject: gnus 20110821 will CoRrUpT your .newsrc.eld, you have been XwarnedX burned
Date: Mon, 22 Aug 2011 19:37:00 +0800	[thread overview]
Message-ID: <87aab1k78j.fsf@jidanni.org> (raw)

Use emacs-snapshot 1:20110821-1 and you won't be able to start gnus, as
your .newsrc.eld got corrupted last session.

Here's what wdiff(1) and uni2ascii(1) say now gets plastered into our
.newsrc.eld files starting with emacs-snapshot 1:20110821-1

{+(if (gnus-lrm-string-p gnus-tmp-qualified-group) (concat+}
======================================================================
 {+#
  ("0x200E" 0 1 (invisible t))) (gnus-correct-substring gnus-tmp-qualified-group 0 61))+}
======================================================================
 {+(if (gnus-lrm-string-p val) (concat+}
======================================================================
 {+#
  ("0x200E" 0 1 (invisible t))) (gnus-correct-substring val 0 6))+}
======================================================================
 {+(if (gnus-lrm-string-p val) (concat+}
======================================================================
 {+#
  ("0x200E" 0 1 (invisible t))) (gnus-correct-substring val 0 14))+}
=================================================================

Now this will result in
Error in /home/jidanni/.newsrc.eld line 32
when you start gnus,
as e.g., the # alone will cause it to be invalid lisp.
The cure is to downgrade your emacs-snapshot to a previous version,
and replace the (setq gnus-format-specs ... of your .newsrc.eld with a
previous version from your backups. You did make backups...

You know isn't it rather silly/dangerous to trust everything to the
fragile monolithic .newsrc.eld file not getting damaged. If the gnus
designers are going to play so dangerously, maybe they should split it
into several different files.



             reply	other threads:[~2011-08-22 11:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-22 11:37 jidanni [this message]
2011-08-22 23:58 ` Katsumi Yamaoka

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=87aab1k78j.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=acid@debian.org \
    --cc=debian-emacsen@lists.debian.org \
    --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).