Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: ding@gnus.org
Subject: Re: This bug is killing me!
Date: Tue, 30 Aug 2011 11:27:18 +0200	[thread overview]
Message-ID: <pknei039rm1.fsf@this.is.really.invalid> (raw)
In-Reply-To: <87pqjnqt5k.fsf@thinkpad.tsdh.de>

Tassilo Horn <tassilo@member.fsf.org> writes:

> Could you check if it works for you if you enable propagating marks?
>
> ,----[ C-h v gnus-propagate-marks RET ]
> | gnus-propagate-marks is a variable defined in `gnus-sum.el'.
> | Its value is t
> | Original value was nil
> | 
> | Documentation:
> | If non-nil, Gnus will store and retrieve marks from the backends.
> | This means that marks will be stored both in .newsrc.eld and in
> | the backend, and will slow operation down somewhat.
> | 
> | You can customize this variable.
> | 
> | [back]
> `----
>
> BTW: I think, that the default of this variable should be t nowadays,
> where it's pretty common that people use different clients for accessing
> their mail (Gnus on "real" computers, Whatever on their phones, the web
> interfaces of their mail providers, etc.).


I just tried setting that to true, and all the unread counts on my nntp
groups (which I access only via Gnus), became wrong (as in much too
high). Does this mean there is stale info in the backend that I need to
regenerate or delete?

Robert




  reply	other threads:[~2011-08-30  9:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 21:51 Dave Abrahams
2011-08-30  7:01 ` Tassilo Horn
2011-08-30  9:27   ` Robert Pluim [this message]
2011-08-30 10:12     ` Tassilo Horn
2011-08-30  9:33   ` [Workaround/Solved] " Dave Abrahams
2011-08-30 10:18     ` Tassilo Horn
2011-08-30 10:33       ` Dave Abrahams
2011-08-30 11:20         ` Tassilo Horn
2011-08-30 18:09           ` Dave Abrahams
2011-08-30 18:17             ` Tassilo Horn
2011-09-10 21:59         ` Lars Magne Ingebrigtsen
2011-08-30 10:39       ` Dave Abrahams
2011-08-30 11:50         ` Tassilo Horn
2011-08-30 18:40           ` Dave Abrahams
2011-08-30 15:04     ` James Cloos
2011-08-30 19:02       ` Dave Abrahams
2011-08-30 19:19         ` Tassilo Horn
2011-08-30 19:53           ` Dave Abrahams
2011-08-30 22:07           ` [The saga continues...] " Dave Abrahams
2011-09-10 22:01             ` Lars Magne Ingebrigtsen
2011-08-30 21:36         ` [Workaround/Solved] " James Cloos
2011-08-31  6:40           ` Dave Abrahams
2011-08-31  7:51           ` Tassilo Horn
2011-08-31  8:27             ` James Cloos
2011-08-31 16:51 ` Andrew Cohen
2011-08-31 19:49   ` Dave Abrahams
2011-08-31 20:05     ` Andrew Cohen
2011-09-10 22:01   ` Lars Magne Ingebrigtsen
2011-09-10 22:12     ` Andrew Cohen
2011-09-10 22:11       ` Lars Magne Ingebrigtsen

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=pknei039rm1.fsf@this.is.really.invalid \
    --to=rpluim@gmail.com \
    --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).