[slrn] sometimes all articles are marked read on entering a group

[Brian H. Damage]

Hi,

slrn 1.0.2

Sometimes I go into an as yet unvisited group, but all posts are marked as read
already, with a 'D'. It doesn't do it all the time, but enough to be annoying.

Any ideas why this happens?

I'm going to turn off auto_mark_article_as_read to see if it makes any
difference.

[Brian H. Damage]

Post by Brian H. Damage
Hi,
slrn 1.0.2
Sometimes I go into an as yet unvisited group, but all posts are marked as
read already, with a 'D'. It doesn't do it all the time, but enough to be
annoying.
Any ideas why this happens?
I'm going to turn off auto_mark_article_as_read to see if it makes any
difference.

Nope.

[J.B. Nicholson]

Post by Brian H. Damage
Sometimes I go into an as yet unvisited group, but all posts are
marked as read already, with a 'D'. It doesn't do it all the time,
but enough to be annoying.
Any ideas why this happens?

Here are a couple of common reasons that get to what you describe:

1. Perhaps you have a score entry in your scorefile which matches the
group and sets the score of every article to some value below
max_low_score (which is 0 by default). For example:

[rec.arts.*]
Score: =-1000
From: .

will be used in every rec.arts.* newsgroup and probably match every
article (virtually all articles have a From: header) setting that
article's score to -1000 points.

To diagnose this try commenting out any "set scorefile" lines in your
slrnrc by making those lines read "%set scorefile" (the leading
percent sign will make that line a comment). If you do this and
re-launch slrn then enter an unvisited newsgroup and see some unread
articles, you're likely looking at a score issue.



2. You have installed a macro which is setting marking articles to
read or catching up the group as soon as you enter it.

To diagnose this try commenting out any "interpret" lines in your
slrnrc by making them "%interpret" (thus commenting them out). If you
do this and re-launch slrn then enter an unvisited newsgroup and see
some unread articles, you're likely looking at a macro issue.




You could be looking at a combination score/macro issue too. It's
tough to say without looking at your slrnrc, scorefile, and seeing
what macros you're running (perhaps you can post those somewhere so we
can help with more detail to your particular setup). But you can
easily check for this behavior with a skeleton slrnrc that only
specifies credentials needed to connect to your news server.

[Brian H. Damage]

This post might be inappropriate. Click to display it.

[J.B. Nicholson]

Post by Brian H. Damage
I've only just started using a scorefile today, and I've only used
it on some specific subjects or from matches, but it was happening
before I start using one.

It wouldn't hurt to comment that out just to eliminate that as a
variable since, as I said, there's more than one route to get to what
you're seeing.

Post by Brian H. Damage
I do have this bind for spacebar, but it happens when I use [enter]
in the normal way too, unless using this does something that it
setkey group "set_prefix_argument(4); () = select_group();" " "

It looks like you might have been trying to routinely enter a group
and see previously read articles (as described in
http://slrn.sourceforge.net/docs/slrn-manual-7.html#gkey_select_group). This
could achieve the effect you describe where you enter a group and see
a bunch of articles already marked read. It would be worth checking
your newsrc for the previously-unread newsgroups you test with to see
which articles are marked as read.

What happens when you comment this out?


Regarding the slrnrc you posted: You posted the following attribution

Post by Brian H. Damage
On Wed, 15 Apr 2020 04:28:55 -0000 (UTC) J.B. Nicholson

But I don't see that followup_string listed in the slrnrc you
posted.

[Brian H. Damage]

This post might be inappropriate. Click to display it.

[J.B. Nicholson]

Post by Brian H. Damage
set followup_string "On %d %r\nin %m ejaculated"
But I might change it yet. Commenting it out didn't help.

The point being that what you sent out earlier wasn't your complete
slrnrc. We don't know what your environment is so it is difficult for
us to help you without all of the details. Therefore you'll need to
put your own environment back to default settings for everything and
retest.

You should check to make sure you're running the latest slrn. I also
recommend commenting out every line in your slrnrc except the
nnrpaccess and server lines which will let slrn authenticate to your
news server. That should give you a 2-line slrnrc to work with.

Also confirm that you haven't already marked read the articles in the
(presumably unsubscribed) group you enter for testing. Perhaps make a
new newsrc with only one subscribed group in it, then enter another
group and see if all the articles appear read in that other group. That
should give you a 1-line newsrc.

I can't duplicate your experience with slrn -- any group I haven't been
in before shows unread articles by default.

[Lewis]

Post by Brian H. Damage
Hi,
slrn 1.0.2
Sometimes I go into an as yet unvisited group, but all posts are marked as read
already, with a 'D'. It doesn't do it all the time, but enough to be annoying.
Any ideas why this happens?

All I can say is that I have never seen this happen, so I suspect
something in your config is triggering it.

Is confirm_actions set to an odd number?

[Brian H. Damage]

Post by Lewis
All I can say is that I have never seen this happen, so I suspect
something in your config is triggering it.
Is confirm_actions set to an odd number?

15