From: Lars Ingebrigtsen <larsi@gnus.org>
To: Sam Steingold <sds@gnu.org>
Cc: 36697@debbugs.gnu.org
Subject: bug#36697: 27.0.50; gnus: some articles with score 0 are killed
Date: Thu, 23 Jul 2020 15:56:08 +0200 [thread overview]
Message-ID: <87lfjanxmv.fsf@gnus.org> (raw)
In-Reply-To: <m1o8o9n5no.fsf@gnu.org> (Sam Steingold's message of "Mon, 20 Jul 2020 19:11:23 -0400")
Sam Steingold <sds@gnu.org> writes:
> The problem is still there as reported originally.
> I am at a loss as to how to debug it - I looked at the scoring code and
> could not figure out what is going on there. Sorry.
OK, reopening.
> If you tell me something like "function foo should return A in your
> case, figure out why it returns B", I am more than willing to debug.
The scoring that the "Y-" stuff is coming from is done in the
`gnus-score-headers' function. If you have a summary buffer that
displays this problem, and there's just a couple of messages in it, it
should be possible to edebug through that long function and see where it
goes wrong, I think.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-07-23 13:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 20:51 bug#36697: 27.0.50; gnus: some articles with score 0 are killed Sam Steingold
2019-09-23 23:15 ` Lars Ingebrigtsen
2019-09-23 23:39 ` Sam Steingold
2019-09-24 7:34 ` Lars Ingebrigtsen
2019-09-24 18:24 ` Sam Steingold
2019-09-25 13:07 ` Lars Ingebrigtsen
2020-01-08 17:13 ` Sam Steingold
2020-01-08 17:19 ` Sam Steingold
2020-01-15 16:09 ` Sam Steingold
2020-01-22 12:53 ` Lars Ingebrigtsen
2020-07-19 15:40 ` Lars Ingebrigtsen
2020-07-20 23:11 ` Sam Steingold
2020-07-23 13:56 ` Lars Ingebrigtsen [this message]
2020-07-23 20:04 ` Sam Steingold
2020-07-24 15:27 ` Lars Ingebrigtsen
2020-07-24 18:37 ` Sam Steingold
2020-07-27 21:45 ` Lars Ingebrigtsen
2022-04-17 18:08 ` 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=87lfjanxmv.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=36697@debbugs.gnu.org \
--cc=sds@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.