Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Vitalie Spinu <spinuvit.list@gmail.com>
Cc: ding@gnus.org
Subject: Re: Mails read in other gnusae still showing in gnus as unread
Date: Tue, 03 Jan 2012 21:34:40 +0100	[thread overview]
Message-ID: <m3ehvgjzj3.fsf@stories.gnus.org> (raw)
In-Reply-To: <87bor7jw18.fsf@gmail.com> (Vitalie Spinu's message of "Sat, 17 Dec 2011 12:08:03 +0100")

Vitalie Spinu <spinuvit.list@gmail.com> writes:

> I have gnus files .gnus.el, .gnus.eld, .newsrc .newsrc.eld and also News
> and Mail folders synchronized through Dropbox. After having read mails on
> one machine I still can see on another machine in the *group* buffer
> these mails as unread.

.newsrc-dribble may also be relevant...

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



  parent reply	other threads:[~2012-01-03 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 11:08 Vitalie Spinu
2011-12-17 14:21 ` Vitalie Spinu
2012-01-03 20:34 ` Lars Magne Ingebrigtsen [this message]
2012-01-07 18:14   ` Vitalie Spinu

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=m3ehvgjzj3.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=ding@gnus.org \
    --cc=spinuvit.list@gmail.com \
    /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).