Gnus development mailing list
 help / color / mirror / Atom feed
From: "Adam Sjøgren" <asjo@koldfront.dk>
To: ding@gnus.org
Subject: Re: Unread count not updated
Date: Sat, 06 Apr 2019 11:23:50 +0200	[thread overview]
Message-ID: <871s2f5vx5.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <xuu6zhp3cxlt.fsf@ucl.ac.uk>

Eric writes:

> 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.

I would assume that as well, for what it is worth - but I think the bugs
Katsumi reported (around #133) are not related to the .elc's, but
changes in the code? (Something about converting one type of loop to
another?)

> 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.

Ok, if that is from a new(er) git checkout than the Debian package, then
I'm afraid I'm just confusing things more :-)

I just thought it sounded like something not being updated, but...


  Best regards,

    Adam

-- 
 "Everything needs to change.                                 Adam Sjøgren
  And it has to start today."                            asjo@koldfront.dk




  reply	other threads:[~2019-04-06  9:23 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
2019-04-06  9:23     ` Adam Sjøgren [this message]
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=871s2f5vx5.fsf@tullinup.koldfront.dk \
    --to=asjo@koldfront.dk \
    --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).