From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: Unread count not updated
Date: Sun, 07 Apr 2019 11:15:08 +0100 [thread overview]
Message-ID: <87r2aeglzn.fsf@ucl.ac.uk> (raw)
In-Reply-To: <871s2f5vx5.fsf@tullinup.koldfront.dk>
On Saturday, 6 Apr 2019 at 11:23, Adam Sjøgren wrote:
>> 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 :-)
No, it was me confusing things. The version I had on the other system
was older than the noted commit. I will post a followup when I get more
info.
Thanks,
eric
--
Eric S Fraga via Emacs 27.0.50 & org 9.2.3 on Debian buster/sid
next prev parent reply other threads:[~2019-04-07 10:15 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
2019-04-07 10:15 ` Eric S Fraga [this message]
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=87r2aeglzn.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).