From: Michael Piotrowski <mxp@dynalabs.de>
To: ding@gnus.org
Subject: Re: Read messages unmarked, once again
Date: Wed, 02 Mar 2011 23:25:47 +0100 [thread overview]
Message-ID: <x6aahdf9ck.fsf@eurus.zrh.dynalabs.de> (raw)
In-Reply-To: <878vwx5q2d.fsf@sycorax.lbl.gov>
On 2011-03-02, Alex Romosan <romosan@sycorax.lbl.gov> wrote:
>> It appears to me that the issue of read messages getting unmarked is
>> not yet completely solved, at least on XEmacs (I'm using 21.4.22). It
>> now only seems to happen after some time. I haven't been able to find
>> out exactly *when* this is happening, e.g., whether it depends on the
>> number of times I enter a group or on something else. Over the course
>> of today, this happens about 5 times; I then restart Gnus, mark the
>> messages as read again, and then for some time it is ok.
>>
>> Is anybody else seeing this?
>
> are you using slave gnus?
No, I don't.
> i saw the same behaviour when using gnus-slave and i was told i was
> supposed to use (setq gnus-propagate-marks t). that solved the problem
> for me.
I played with gnus-propagate-marks, but didn't see any change in
behavior, but I'll have another look. In any case, thanks for the
suggestion.
Greetings
--
Dr.-Ing. Michael Piotrowski, M.A. <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt> (ID 0x1614A044)
next prev parent reply other threads:[~2011-03-02 22:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 17:23 Michael Piotrowski
2011-03-02 17:37 ` Michael Strauss
2011-03-02 22:27 ` Michael Piotrowski
2011-03-02 18:34 ` Alex Romosan
2011-03-02 22:25 ` Michael Piotrowski [this message]
2011-03-03 0:33 ` Michael Strauss
2011-03-04 4:03 ` Eric Abrahamsen
2011-03-04 7:31 ` Antoine Levitt
2011-03-04 9:19 ` Steinar Bang
2011-03-04 14:42 ` Ted Zlatanov
2011-03-05 14:36 ` Kan-Ru Chen
2011-03-05 17:56 ` Kan-Ru Chen
2011-03-05 10:34 ` Lars Magne Ingebrigtsen
2011-03-05 16:35 ` Antoine Levitt
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=x6aahdf9ck.fsf@eurus.zrh.dynalabs.de \
--to=mxp@dynalabs.de \
--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).