From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: issues with new gnus nnimap
Date: Fri, 01 Oct 2010 09:34:00 -0500 [thread overview]
Message-ID: <877hi2yobr.fsf@lifelogs.com> (raw)
In-Reply-To: <m3y6aifbm8.fsf@verona.se>
On Fri, 01 Oct 2010 12:31:11 +0200 joakim@verona.se wrote:
j> Noticing the enourmous code churn in gnus, I tried a new Emacs snapshot
j> the other day. I then got different behaviour. Old emails from 2006
j> showed up as new ones. I tried to do catch up on them. They seemed gone,
j> and then I did M-g on the group, and they came back again.
j> Then I got too scared to continue, and reverted to my old Emacs.
j> Any hints how to provide better debugging info apreciated.
(you may want to use the Ding Mailing List <ding@gnus.org> to report
Gnus problems or bugs, although Lars has been knocking off Emacs and
Gnus bug reports as well lately)
I reported something very similar for old/new e-mails. I think it's
related to the new (correct) way nnimap stores Gnus marks in IMAP, since
it only affects articles I received before the nnimap rewrite.
Ted
parent reply other threads:[~2010-10-01 14:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m3y6aifbm8.fsf@verona.se>]
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=877hi2yobr.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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).