From: Greg Troxel <gdt@lexort.com>
To: ding@gnus.org
Subject: Re: Gnus sometimes reports new messages but not showing them on IMAP server
Date: Thu, 18 Apr 2024 08:13:37 -0400 [thread overview]
Message-ID: <rmiplumc1hq.fsf@s1.lexort.com> (raw)
In-Reply-To: <878r1blqcg.fsf@uwo.ca> (Dan Christensen's message of "Wed, 17 Apr 2024 15:51:59 -0400")
Dan Christensen <jdc@uwo.ca> writes:
> On Apr 11, 2024, Xiyue Deng <manphiz@gmail.com> wrote:
>
>> I'm having some issues that Gnus sometimes reports that there are new
>> messages on an IMAP server but it doesn't show them.
>
> On Apr 16, 2024, Greg Troxel <gdt@lexort.com> wrote:
>
>> Often, I get a message on my phone that I just leave (marked read) to
>> deal with later. Sometimes, maybe 1 in 50, I can't find it in gnus, and
>> on looking harder find that it is just not showing up there.
>
> For both of you, does hitting `M-g' with point on the group in the
> *Group* buffer fix things?
I will try that, but I have been exiting the group and ^U SPC to
re-enter and display all, and when a message has gone missing, I have
not even once been able to get gnus to show it. I have exited and
restarted gnus, and done "g".
> I regularly have similar problems, and I've resorted to binding the
> following function to a key:
>
> (defun jdc-gnus-update-IMAP ()
> (interactive)
> ; Only run this in the group buffer or it corrupts other buffers:
> (switch-to-buffer gnus-group-buffer)
> (gnus-topic-jump-to-topic "IMAP groups")
> (gnus-topic-get-new-news-this-topic)
> (gnus-group-list-groups) ; "l", as previous command shows all groups in topic
> )
>
> I think it's doing the equivalent of `M-g' on all groups in the topic
> I have that contains my IMAP groups. For the record, I'm also using
> dovecot and k9-mail.
Are you saying that "g" in the summary does not allow viewing a missing
article, but M-g will?
To me, the problem is that these message are somehow invisible, even
after multiple attempts to fetch/display them.
next prev parent reply other threads:[~2024-04-18 12:14 UTC|newest]
Thread overview: 24+ 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 [this message]
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-04-24 15:23 ` James Thomas
2024-04-25 2:59 ` Eric Abrahamsen
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=rmiplumc1hq.fsf@s1.lexort.com \
--to=gdt@lexort.com \
--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).