From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: score display in summary line is wrong
Date: Mon, 13 Jun 2022 14:53:38 +0200 [thread overview]
Message-ID: <87zgig3est.fsf@ucl.ac.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
Every now and again, the score shown in the summary lines is wrong and
actually corresponds to the message number + 1. Image attached. For
the first article, for instance, the actual score is -807.
My gnus-summary-line-format is
,----[ C-h v gnus-summary-line-format RET ]
| gnus-summary-line-format is a variable defined in ‘gnus.el’.
|
| Its value is
| "%6N %R%U%O%uj %3{%&user-date; %5i %4k|%}%I%(%-25,25f%) %5{%*%s%}
| "
| Original value was
| "%U%R%z%I%(%[%4L: %-23,23f%]%) %s
| "
| [...]
| %i Article score (number)
`----
Does anybody have an idea why this would happen?
Thank you,
eric
--
Eric S Fraga via gnus (Emacs 29.0.50 2022-05-19) on Debian 11.3
[-- Attachment #2: screendump-20220613144915.png --]
[-- Type: image/png, Size: 45844 bytes --]
reply other threads:[~2022-06-13 12:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87zgig3est.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).