From: James Thomas <jimjoe@gmx.net>
To: ding@gnus.org
Subject: Re: bug#72949: Gnus sometimes reports new messages but not showing them on IMAP server
Date: Thu, 12 Sep 2024 12:55:49 +0530 [thread overview]
Message-ID: <861q1p1gg2.fsf@gmx.net> (raw)
In-Reply-To: <868qvx1xst.fsf@gmx.net> (James Thomas's message of "Thu, 12 Sep 2024 06:40:58 +0530")
(Forgot to cc this here:)
James Thomas wrote:
> Dan Christensen wrote:
>
>> On Sep 11, 2024, James Thomas via "Bug reports for GNU Emacs, the
>> Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> wrote:
>>
>>> James Thomas wrote:
>>>
>>>> I haven't tested this patch (don't really know how to), but this could
>>>> very well be the cause of this long-standing bug:
>>>
>>> Could you check if this patch (the 1st one, which swaps the 0 and 1),
>>> makes any difference?
>>
>> I've noticed a long-standing bug, and tried this patch. Here's the bug:
>> If I use `B m' or `B c' to move or copy a message from an nnimap group
>> to a non-existent nnimap group, Gnus asks if I want to create the group.
>> I say yes, and then it gets created with some faulty parameters that
>> make the *Group* buffer show odd numbers:
>>
>> ("nnimap+rocky:testmove1" 3
>> ((1 . 1))
>> ((unexist 0) (seen 1)) "nnimap:rocky"
>> ((modseq . "3") (uidvalidity . "1549221829") (active 0 . 1) (permanent-flags %Answered %Flagged %Deleted %Seen %Draft %*)))))
>>
>> Note that article 0 is mentioned twice there. If I close Gnus, get
>> rid of the "(unexist 0)", and change the active range to 1 . 1, then
>> things are good again.
>>
>> I can consistently reproduce this.
>>
>> I wondered if the patch in this thread would help, but after applying
>> it, I'm unable to create the new group in this way. After hitting `y'
>> to agree to creating a new group, I get:
>>
>> Debugger entered--Lisp error: (error "Couldn’t create group nnimap+rocky:testmove4")
>> signal(error ("Couldn’t create group nnimap+rocky:testmove4"))
>> error("Couldn't create group %s" "nnimap+rocky:testmove4")
>> gnus-read-move-group-name("Copy" "nnimap+rocky:testmove1" (50086) "nn:")
>> gnus-summary-move-article(nil nil nil copy)
>> gnus-summary-copy-article(nil)
>> funcall-interactively(gnus-summary-copy-article nil)
>> call-interactively(gnus-summary-copy-article nil nil)
>> command-execute(gnus-summary-copy-article)
>>
>> So this patch makes Gnus worse for me, rather than better. I hope this
>> reproducible strategy helps pin down a solution.
>
> Sorry! I got confused again... Please try the other patch in that bug
> report (the one that swaps the car and cdr). I find that it works with
> your use case!
>
> --
--
next prev parent reply other threads:[~2024-09-12 7:26 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 0:57 Xiyue Deng
2024-04-17 0:03 ` Greg Troxel
2024-04-17 6:47 ` Xiyue Deng
2024-04-17 19:51 ` Dan Christensen
2024-04-18 12:13 ` Greg Troxel
2024-04-19 22:55 ` Dan Christensen
2024-04-21 12:08 ` Arash Esbati
2024-04-21 12:43 ` Dan Christensen
2024-04-21 13:14 ` Andreas Schwab
2024-04-21 16:18 ` Eric Abrahamsen
2024-04-21 18:16 ` Arash Esbati
2024-04-22 0:00 ` Greg Troxel
2024-04-22 2:35 ` Eric Abrahamsen
2024-04-27 19:46 ` Xiyue Deng
2024-05-02 5:47 ` Xiyue Deng
2024-05-02 15:08 ` Eric Abrahamsen
2024-05-02 17:24 ` Xiyue Deng
2024-05-02 17:41 ` Dan Christensen
2024-05-02 18:41 ` Xiyue Deng
2024-05-05 20:18 ` Xiyue Deng
2024-05-05 21:01 ` Dan Christensen
2024-05-05 22:10 ` Xiyue Deng
2024-05-08 18:36 ` Xiyue Deng
2024-05-08 18:41 ` Xiyue Deng
2024-05-09 23:11 ` Andrew Cohen
2024-05-10 7:45 ` Xiyue Deng
2024-05-10 8:16 ` Andrew Cohen
2024-05-10 8:26 ` Xiyue Deng
2024-05-10 9:13 ` Andreas Schwab
2024-05-10 0:43 ` Greg Troxel
2024-05-10 1:20 ` Xiyue Deng
2024-05-10 12:24 ` Greg Troxel
2024-05-10 20:06 ` Xiyue Deng
2024-05-11 19:08 ` Greg Troxel
2024-05-11 22:33 ` Eric Abrahamsen
2024-05-12 11:14 ` Gnus sometimes fails to see a message that is actually in IMAP Greg Troxel
2024-05-13 14:39 ` Eric Abrahamsen
2024-05-24 15:58 ` Eric Abrahamsen
2024-05-24 17:29 ` Eric Abrahamsen
2024-04-24 15:23 ` Gnus sometimes reports new messages but not showing them on IMAP server James Thomas
2024-04-25 2:59 ` Eric Abrahamsen
[not found] ` <868qwar3yn.fsf@gmx.net>
2024-09-11 1:25 ` James Thomas
[not found] ` <87r09q1i0s.fsf@uwo.ca>
[not found] ` <868qvx1xst.fsf@gmx.net>
2024-09-12 7:25 ` James Thomas [this message]
2024-09-14 14:20 ` bug#72949: " Dan Christensen
2024-09-14 16:28 ` Dan Christensen
2024-09-14 19:02 ` Adam Sjøgren
[not found] ` <87frq2xh4c.fsf@uwo.ca>
[not found] ` <86h6ah2q47.fsf@gmx.net>
2024-09-15 12:49 ` Dan Christensen
2024-09-15 21:55 ` James Thomas
2024-09-15 23:07 ` Dan Christensen
2024-09-16 0:51 ` James Thomas
[not found] ` <86plp4ovgj.fsf@gmx.net>
2024-09-16 12:42 ` Dan Christensen
[not found] ` <86zfo69b52.fsf@gmx.net>
[not found] ` <86setx3o07.fsf@gmx.net>
2024-09-17 23:03 ` Dan Christensen
2024-09-18 2:27 ` James Thomas
2024-09-24 12:50 ` Dan Christensen
2024-10-01 20:50 ` Dan Christensen
2024-10-01 21:30 ` Stefan Kangas
2024-10-01 22:25 ` Dan Christensen
2024-10-02 16:55 ` Robert Pluim
2024-10-11 13:36 ` Robert Pluim
2024-10-11 13:45 ` Dan Christensen
2024-10-11 13:51 ` Robert Pluim
2024-10-11 15:39 ` Eli Zaretskii
2024-10-15 8:28 ` Robert Pluim
[not found] ` <87jzfexh4k.fsf@uwo.ca>
[not found] ` <878qvu58fc.fsf@igel.home>
[not found] ` <87ldzuvt97.fsf@uwo.ca>
[not found] ` <874j6h6g09.fsf@igel.home>
2024-09-14 23:17 ` Dan Christensen
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=861q1p1gg2.fsf@gmx.net \
--to=jimjoe@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).