From: Stephen Berman <Stephen.Berman@gmx.net>
To: ding@gnus.org
Subject: Re: [gmane.emacs.devel] gnus-read-mark not preserved
Date: Mon, 02 Jul 2007 22:34:03 +0200 [thread overview]
Message-ID: <87ir921r5w.fsf@escher.local.home> (raw)
In-Reply-To: <b4my7hzc87s.fsf@jpl.org>
On Mon, 02 Jul 2007 21:15:35 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote:
>>>>>> In <87ejjukg6s.fsf@florent.maison> Florent Rougon wrote:
>
>> With your recipe and without the patch, I can reproduce the bug. Again
>> with the same recipe but with the patch applied, the bug doesn't happen.
>> I'll now start reading again some nntp newsgroups and tell you if
>> anything wrong happens, but I think you did spot and fix the problem I
>> was experiencing.
>
> Thanks for verifying the patch. However, what I did might be
> a kludge. That is, making nnagent handle marks of the specific
> back ends looks ill-mannered, since to abstract the actual back
> ends seems to be one of the aims of nnagent. The reason I changed
> my idea is because I found the variable:
>
> gnus-agent-synchronize-flags
>
> The default value is nil. See (info "(gnus)Agent and flags").
> Does setting it to t solve the problem that you all are troubled
> with? Could someone, who uses Gnus v5.11, try it? (I couldn't
> reproduce the problem with Gnus v5.11 so far, though.)
I am using Gnus 5.11 as included in the Emacs CVS trunk (currently GNU
Emacs 22.1.50.6 (i686-pc-linux-gnu, GTK+ Version 2.10.6) of 2007-06-30
on escher). Here gnus-agent-synchronize-flags has the default value
t[1] (and the Gnus info lacks a node "Agents and flags"). I am still
experiencing this problem and I haven't changed the value of this
variable, so setting it to t is not the solution, at least in 5.11.
Unfortunately, I still have found no reliable recipe for reproducing
the problem. For whatever reason, I have sometimes gone through
several Emacs sessions without seeing it, then it shows up again in
some group. Throughout, I've been consistently using gnus-unplugged.
Steve Berman
Footnotes:
[1] But the code has this rather puzzling comment [sic]:
;; If the default switches to something else than nil, then the function
;; should be fixed not be exceedingly slow. See 2005-09-20 ChangeLog entry.
next prev parent reply other threads:[~2007-07-02 20:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 6:52 Stephen Berman
2007-06-22 9:51 ` Stephen Berman
2007-06-22 10:45 ` Katsumi Yamaoka
2007-06-22 10:57 ` Stephen Berman
2007-06-22 9:58 ` Stephen Berman
2007-06-22 10:33 ` Stephen Berman
2007-06-28 16:34 ` Florent Rougon
2007-06-29 11:06 ` Katsumi Yamaoka
2007-06-29 14:07 ` Florent Rougon
2007-07-02 12:15 ` Katsumi Yamaoka
2007-07-02 20:34 ` Stephen Berman [this message]
2007-07-04 9:21 ` Katsumi Yamaoka
2007-07-06 1:08 ` Katsumi Yamaoka
2007-07-06 9:04 ` Stephen Berman
2007-09-02 9:27 ` Florent Rougon
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=87ir921r5w.fsf@escher.local.home \
--to=stephen.berman@gmx.net \
--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).