Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: James Cloos <cloos@jhcloos.com>,
	 ding@gnus.org,  John Wiegley <johnw@boostpro.com>
Subject: Re: [Workaround/Solved] This bug is killing me!
Date: Tue, 30 Aug 2011 21:19:44 +0200	[thread overview]
Message-ID: <87ty8y906n.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <m2hb4ywwm6.fsf@boostpro.com> (Dave Abrahams's message of "Tue, 30 Aug 2011 11:02:57 -0800")

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.

Bye,
Tassilo
-- 
Sent from my Emacs



  reply	other threads:[~2011-08-30 19:19 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
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 [this message]
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=87ty8y906n.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --cc=cloos@jhcloos.com \
    --cc=dave@boostpro.com \
    --cc=ding@gnus.org \
    --cc=johnw@boostpro.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).