Re: [The saga continues...] This bug is killing me!

[Dave Abrahams <dave@boostpro.com>]

on Tue Aug 30 2011, Tassilo Horn <tassilo-AT-member.fsf.org> wrote:

> Dave Abrahams <dave@boostpro.com> writes:
>
>>>>> BTW: I think, that the default of this variable should be t
>>>>> nowadays,
>>>
>>> Mark propagation is not universally supported.  
>>
>> By what? (not challenging; just not understanding yet).
>
> By backends: Server-side marks are something that's basically only
> supported by IMAP (and thus the nnimap backend).
>
>>> Setting it to t would certainly break things here.
>>
>> Where; what things?
>
> I don't know the answer but have another question: if it would break
> things, why is it a defcustom then?  And if only nnimap supports mark
> propagation, and the code already has an exception to enable MP for IMAP
> servers (*), why do we have that variable anyway?
>
> (*) ... which doesn't seem to work for Dave ...
>
>>> Gnus needs to work correcly with gnus-propagate-marks nil.
>>
>> Perhaps so.  Can you define what "correctly" means in this case?
>
> Marks should be propagated to your IMAP server, no matter the value of
> that variable.  And what we've discovered so far is that this seems to
> happen when you mark an article and then exit the summary, while the
> mark is lost when you hit M-g, thus updating the summary without exiting
> it.
>
> Well, that's at least some perimeter of the issue.  I have no clue about
> all that backend code, but hopefully someone who has is helped on with
> it.

Okay, so I just exited Gnus and decided to answer `n' to the "update
summary buffer INBOX" question.  Restarted Emacs and Gnus and nearly all
my marks were gone, even in some NNTP groups.  So I set (and saved)
`gnus-propagate-marks' back to nil, and did a `M-g', and all my marks
came back.  

something-is-rotten-in-the-state-of-Denmark-ly y'rs,

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com