Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Luis Henriques <henrix@camandro.org>
Cc: dick.r.chiang@gmail.com,  ding@gnus.org
Subject: Re: Annoying issue with group not showing new messages
Date: Sun, 21 Feb 2021 14:29:26 -0800	[thread overview]
Message-ID: <8735xpcawp.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <20210221173828.GA86830@camandro.org> (Luis Henriques's message of "Sun, 21 Feb 2021 17:38:28 +0000")

Luis Henriques <henrix@camandro.org> writes:

> On Fri, Feb 19, 2021 at 07:50:43AM -0500, dick.r.chiang@gmail.com wrote:
>> One cannot practically use gnus without stepping through functions.  This is
>> why mu4e has effectively halted new gnus adoption.
>> 
>> Send yourself a mail to a good inbox.  `C-u C-M-x` on
>> `nnimap-request-group-scan`.  Then `M-g` on the group, and SPC step to see how
>> it's supposed to look.
>> 
>> Now do the same for the problematic inbox.  Inspect variables and function
>> calls with `e variable-or-function-call RET`.
>> 
>> `C-M-x` on `nnimap-request-group-scan` to turn off debugging.
>> 
>> This general strategy holds you in good stead for your entire
>> emacs lifetime.  Google around for more (onerously longwinded) info.
>
> Thank you for your suggestion.  Unfortunately, I tried that... and gave
> up.  I'm not (e)lisp literate so debugging such complex code isn't
> something I'm ready to do.  And no, I'm not moving to mu4e :-)

Something that works sometimes with nnimap is to edit the full group
parameters ("G E"), and just blast all the mark information, maybe the
active cons as well. That would be the third and fourth elements of the
list -- I think you can just replace them with nil, though it's been a
while since I had to do this. That should trigger a full initial sync of
the group, which usually flushes out the kinds of problems you're
seeing.

No promises! But it's worth trying.

Eric


      parent reply	other threads:[~2021-02-21 22:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 12:06 Luis Henriques
2021-02-19 12:50 ` dick.r.chiang
2021-02-21 17:38   ` Luis Henriques
2021-02-21 17:59     ` dick.r.chiang
2021-02-21 20:41       ` Bob Newell
2021-02-21 22:29     ` Eric Abrahamsen [this message]

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=8735xpcawp.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=dick.r.chiang@gmail.com \
    --cc=ding@gnus.org \
    --cc=henrix@camandro.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).