From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Stephen Berman <Stephen.Berman@gmx.net>
Cc: emacs-pretest-bug@gnu.org, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: 23.0.60; File corruption when Gnus reads .overview
Date: Thu, 27 Mar 2008 21:57:07 +0100 [thread overview]
Message-ID: <v91w5vopgc.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87r6edfz0u.fsf@escher.local.home> (Stephen Berman's message of "Fri, 14 Mar 2008 10:14:25 +0100")
On Fri, Mar 14 2008, Stephen Berman wrote:
> With my current build (GNU Emacs 23.0.60.1 (i686-pc-linux-gnu, GTK+
> Version 2.12.0) of 2008-03-13 on escher), the file corruption has
> disappeared, but Gnus still has a problem with the .overview file: when
> I open the gmane.emacs.help group, all my marks are gone except the one
> corresponding to the entry in the .overview file that occurs earlier
> than the first entry containing the problematic non-ascii characters.
> In other words, it appears that Gnus is not processing the .overview
> file after it reads the problematic non-ascii characters. I would be
> grateful if a Gnus hacker could look into this, as I cannot usefully
> read gmane.emacs.help with Gnus from the current trunk.
It's the agent cache overview, right? I don't use the agent, so I'm
not familiar with it, but IIRC it's no problem to delete the corrupt
overview file. Does this help?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-03-27 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y78uu7lz.fsf@escher.local.home>
2008-03-14 9:14 ` Stephen Berman
2008-03-27 20:57 ` Reiner Steib [this message]
2008-03-28 1:09 ` Leo
2008-03-28 22:00 ` Stephen Berman
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=v91w5vopgc.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=Stephen.Berman@gmx.net \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@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).