Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: Unread count not updated
Date: Sat, 06 Apr 2019 10:05:34 +0100	[thread overview]
Message-ID: <xuu6zhp3cxlt.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87y34oxk2r.fsf@tullinup.koldfront.dk>

On Friday,  5 Apr 2019 at 22:39, Adam Sjøgren wrote:
> Could it be related to the recent hash-table changes? It sounds a little
> like what Katsumi Yamaoka wrote about here:

I'd seen this but hadn't considered it as affecting me because I'd
(maybe mistakenly) assumed that a Debian package could have recompiled
all .el files. But I do note that this problem with my unread count does
not appear to happen on the one system I use where I have built emacs
directly from git.

>> I'm tracking emacs-snapshot on Debian so the gnus is relatively
>> up-to-date.
>
> What's the newest commit included? Before or after:
>
>   commit c1b63af4458e92bad33da0def2b15c206656e2fa
>   Author: Eric Abrahamsen <eric@ericabrahamsen.net>
>   Date:   Thu Apr 26 16:26:27 2018 -0700

No idea. I'll explore. Thanks for the suggestion of the possible
source of this problem.

-- 
Eric S Fraga via Emacs 27.0.50 & org 9.2.2 on Debian 9.8




  reply	other threads:[~2019-04-06  9:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05 15:34 Eric S Fraga
2019-04-05 20:39 ` Adam Sjøgren
2019-04-06  9:05   ` Eric S Fraga [this message]
2019-04-06  9:23     ` Adam Sjøgren
2019-04-07 10:15       ` Eric S Fraga
2019-04-08  9:43       ` Eric S Fraga
2019-04-08 15:40         ` Eric S Fraga
2019-04-09  2:47           ` Eric Abrahamsen
2019-04-10  6:13             ` Eric S Fraga
2019-04-10 17:09               ` Eric Abrahamsen
2019-04-11 13:32                 ` Eric S Fraga
2019-06-22 10:48                   ` Lars Ingebrigtsen

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=xuu6zhp3cxlt.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).