From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: all nnimap flags lost again
Date: Fri, 24 Sep 2010 10:48:42 -0400 [thread overview]
Message-ID: <87pqw3nqnp.fsf@uwo.ca> (raw)
In-Reply-To: <m3mxr8ow2h.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Dan Christensen <jdc@uwo.ca> writes:
>
>> If you ignore the order of the data, the only difference is that there
>> is no (active 67 . 3689) in the first output.
>
> That's really intriguing. What on earth could be removing the active
> entries from the Gnus info?
No idea. Can you recommend what functions I should step through during
Gnus start-up to figure out what is happening?
>> I'm running git from yesterday. If you think it would be helpful (and
>> safe) to redo this test after upgrading to current git, let me know.
>
> I'm really mystified here. You have no special code or settings that
> alter the infos in any way -- from a hook, or any other settings that
> deal with marks or flags or something?
Not that I can think of, but I do have a lot of cruft, so if I'm the
only one experiencing this, it's probably something local to my set-up.
I'll try to investigate it more closely over the next few days.
Dan
next prev parent reply other threads:[~2010-09-24 14:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 1:04 Dan Christensen
2010-09-23 1:10 ` Lars Magne Ingebrigtsen
2010-09-23 1:17 ` Lars Magne Ingebrigtsen
2010-09-23 1:17 ` Dan Christensen
2010-09-23 1:24 ` Lars Magne Ingebrigtsen
2010-09-23 2:15 ` Dan Christensen
2010-09-23 16:01 ` Lars Magne Ingebrigtsen
2010-09-23 18:41 ` Dan Christensen
2010-09-23 18:45 ` Lars Magne Ingebrigtsen
2010-09-23 18:57 ` Dan Christensen
2010-09-23 19:04 ` Dan Christensen
2010-09-23 19:43 ` Lars Magne Ingebrigtsen
2010-09-23 19:45 ` Lars Magne Ingebrigtsen
2010-09-23 23:34 ` Dan Christensen
2010-09-23 23:54 ` Lars Magne Ingebrigtsen
2010-09-24 14:48 ` Dan Christensen [this message]
2010-09-24 16:06 ` 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=87pqw3nqnp.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).