Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: Gnus sometimes reports new messages but not showing them on IMAP server
Date: Sun, 21 Apr 2024 08:43:06 -0400	[thread overview]
Message-ID: <87cyqi51k5.fsf@uwo.ca> (raw)
In-Reply-To: <m2ttjugbp4.fsf@macmutant.fritz.box>

On Apr 21, 2024, Arash Esbati <arash@gnu.org> wrote:

> Dan Christensen <jdc@uwo.ca> writes:
>
>> I don't know what is going on behind the scenes, but `M-g' is necessary
>> for me to see up-to-date information sometimes.
>
> I haven't tried to read/understand the code, but in the Group buffer,
> neither 'g' nor 'C-u g' does what 'M-g' does inside the Summary buffer
> of an IMAP group.

Just to clarify, I use `M-g' in the Group buffer, but looking at the
code I think using it in the Summary buffer does the same thing.

Aside:  While looking at the code, I think I noticed an error in the doc
string of the function that ends up getting called:

  (defun gnus-group-get-new-news-this-group (&optional n dont-scan)
    "Check for newly arrived news in the current group (and the N-1 next groups).
  The difference between N and the number of newsgroup checked is returned.
  If N is negative, this group and the N-1 previous groups will be checked.
  If DONT-SCAN is non-nil, scan non-activated groups as well."

I think the description of DONT-SCAN is inverted (as its name suggests).
It should say:

  If DONT-SCAN is nil, scan non-activated groups as well.

Or

  If DONT-SCAN is non-nil, then non-activated groups are not scanned.

Dan



  reply	other threads:[~2024-04-21 12:43 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
2024-04-19 22:55     ` Dan Christensen
2024-04-21 12:08       ` Arash Esbati
2024-04-21 12:43         ` Dan Christensen [this message]
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=87cyqi51k5.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).