From: Par Kurlberg <kurlberg@math.kth.se>
To: ding@gnus.org
Subject: Re: tick marks cleared on server, but still seen as ticked by gnus
Date: Mon, 01 Jul 2013 23:22:39 +0200 [thread overview]
Message-ID: <m2mwq6nffk.fsf@math.kth.se> (raw)
In-Reply-To: <87sizyjw2r.fsf@lifelogs.com>
I've now put (setq gnus-agent nil) in my .gnus, please let me know if
there is something else I should do to disable the agent.
Anyway, I now see the following behaviour:
* Using gnus (and checking what is on the imap server by using
thunderbird):
Setting tick: works (the message is starred according to thunderbird.)
Clearing tick: works (the star is cleared according to thunderbird.)
Clearing read flag: pressing M-c (gnus-summary-clear-mark-forward):
works.
Setting read flag by pressing "d" (gnus-summary-mark-as-read-forward):
works.
To be precise: the flags are only updated when I hit q to exit
summary buffer.
* Going the other direction: setting/clearing read/star on the
thunderbird side, and noting what gnus "sees". (Note: the changes
done on the thunderbird side are noticed by our webmail frontend.)
Setting star: works once - message ticked according to gnus (after
hitting g in the group buffer). When I tried it again it did not work.
Clearing star: does not work - still ticked according to gnus. (After
hitting g in the group buffer.)
Clearing read flag: works sometimes. (The number of unread messages in
the group buffer changes.)
Setting read flag: works sometimes. (The number of unread messages in
the group buffer changes.)
Regarding the read flags working occasionally, can't spot a pattern.
This is a bit perplexing - before I set gnus-agent to nil, I'm pretty
sure read/unread was syncronized from thunderbird to gnus.
Best,
Par
next prev parent reply other threads:[~2013-07-01 21:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-29 21:58 Par Kurlberg
2013-06-30 13:47 ` Steinar Bang
2013-06-30 18:41 ` Par Kurlberg
2013-07-01 12:36 ` Ted Zlatanov
2013-07-01 21:22 ` Par Kurlberg [this message]
2013-07-02 7:14 ` Steinar Bang
2013-07-02 15:36 ` Ted Zlatanov
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=m2mwq6nffk.fsf@math.kth.se \
--to=kurlberg@math.kth.se \
--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).