all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 34502@debbugs.gnu.org
Subject: bug#34502: Ask yourself, am I generating a NEW .overview file?
Date: Mon, 15 Jul 2019 13:36:16 +0200	[thread overview]
Message-ID: <m3y30z1qdr.fsf@gnus.org> (raw)
In-Reply-To: <875zo3d00n.5.fsf@jidanni.org> ("積丹尼 Dan Jacobson"'s message of "Mon, 15 Jul 2019 19:12:40 +0800")

積丹尼 Dan Jacobson <jidanni@jidanni.org> writes:

>>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> LI> I've looked through the code for the nnml regeneration code paths, and I
> LI> can't see that Gnus would do that automatically.  Are you sure you
> LI> didn't issue one of the commands to regenerate the files?
>
> All I can say is close gnus, remove the .overview file.
> Then the next day continue using gnus as normal.
> Sooner or later the .overview will grow back again, just like a toenail
> does. That's all I know.

As you receive emails, the .overview file will get the entries from that
mail, and will keep growing.  Is that what you're seeing?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-07-15 11:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16 19:26 bug#34502: Ask yourself, am I generating a NEW .overview file? 積丹尼 Dan Jacobson
2019-07-09 16:39 ` Lars Ingebrigtsen
2019-07-13 22:57   ` 積丹尼 Dan Jacobson
2019-07-14 11:58     ` Lars Ingebrigtsen
2019-07-15 11:12       ` 積丹尼 Dan Jacobson
2019-07-15 11:36         ` Lars Ingebrigtsen [this message]
2019-07-15 12:16           ` 積丹尼 Dan Jacobson
2019-07-15 12:20             ` Lars Ingebrigtsen
2019-07-15 12:56               ` 積丹尼 Dan Jacobson

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=m3y30z1qdr.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=34502@debbugs.gnu.org \
    --cc=jidanni@jidanni.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.