Re: HEADS UP! Unplugged (agent) marks handling changed

[Ralf Angeli <dev.null@iwi.uni-sb.de>]

[I already answered this message, but the article did not show up on
Gmane for several hours, so here is a second try.]

* Kevin Greiner (2004-09-25) writes:

> If you run into any unexpected behavior with offline flags, please
> post so that I can address it.

For me it does not fix the original problem.  Gnus is still forgetting
marks with the described usage pattern.

I tried to debug `gnus-agent-possibly-synchronize-flags' again and saw
that `gnus-find-method-for-group' (called in `gnus-request-set-mark')
returns `(nnnil)' for groups which are accessed through NNTP.
(`nnnil' is my primary select method.)  The resulting backend function
to be called will be `nnnil-request-set-mark' which obviously is not
bound.  I am assuming this is the cause for the marks not getting set,
but maybe I am just babbling as I haven't looked deeper into the code.

Here is a backtrace which probably shows the cause:

Debugger entered--returning value: nil
  string-match(":" "de.comp.editoren")
* gnus-group-name-to-method("de.comp.editoren")
* gnus-find-method-for-group("de.comp.editoren")
* gnus-request-set-mark("de.comp.editoren" (((13149) add (read))))
* gnus-agent-synchronize-group-flags("de.comp.editoren" (((13149) add (read))) "news.individual.net")
* eval((gnus-agent-synchronize-group-flags "de.comp.editoren" (quote (...)) "news.individual.net"))
[byte-code snipped]
* gnus-agent-synchronize-flags-server((nntp "news.individual.net"))
* gnus-agent-possibly-synchronize-flags-server((nntp "news.individual.net"))
[byte-code snipped]
* gnus-agent-possibly-synchronize-flags()

-- 
Ralf