From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: No longer can enter groups in 0.82 and 0.83 ... ???
Date: 18 Apr 1999 22:33:21 -0400 [thread overview]
Message-ID: <ltvhetz6dq.fsf@asfast.com> (raw)
In-Reply-To: Lloyd Zusman's message of "18 Apr 1999 21:36:19 -0400"
Lloyd Zusman <ljz@asfast.com> writes:
> I just got the same problem with pgnus-0.83 (please read what I have
> quoted below). Also note that I always get the "no unread articles"
> message in each group I try to enter, irrespective of how many unread
> articles there really are.
>
> Everything has worke fine for me up to and including pgnus-0.81, but
> this started happening in pgnus-0.82 and, as I have noted, is
> continuing in pgnus-0.83
>
> Any ideas what could be causing this?
Well, I figured out a workaround to the problem I'm describing, but I
have a feeling that this is not the ultimate solution:
I noticed that in version 0.81, the `gnus-summary-expunge-below'
variable was not marked as `global' in gnus-sum.el, but in versions
0.82 and 0.83, it is marked as `global'. This seems to be causing the
problem I'm seeing.
I have `gnus-use-scoring' set to `t' in my `.gnus.el' file, and I
specify `all.SCORE' for my score file. However, that score file
doesn't exist (and hasn't for eons). For some reason, this causes
everything to be scored to some number below 1 (probably 0).
In versions 0.82 and 0.83, the `gnus-summary-expunge-below' variable
gets set to 1 when I'm in summary mode. In version 0.81, it gets set
to `nil'. This variable interacts with the scoring that I described
in the previous paragraph to cause all my articles to look like they
have been read.
So, I have come up with three possible workarounds for this, all of
which are probably not the "real" solution:
(1) Put this line into my gnus summary mode hook:
`(setq gnus-summary-expunge-below nil)'
(2) Create an `all.SCORE' file that scores every article in all groups
to 1 or above.
(3) Turn off `gnus-use-scoring'
I don't really like number (3) because I do use scoring for a subset
of the groups I read. I don't like (2) because then I'm needlessly
scoring everything just to compensate for this behavior. I don't like
(1) because I think that I'm just covering up the real problem.
Any ideas?
Thanks in advance.
--
Lloyd Zusman
ljz@asfast.com
next prev parent reply other threads:[~1999-04-19 2:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-17 16:42 Pterodactyl Gnus v0.82 is released Lars Magne Ingebrigtsen
1999-04-17 17:50 ` Michael Cook
1999-04-18 6:26 ` Lars Magne Ingebrigtsen
1999-04-18 0:24 ` No longer can enter groups! (Re: Pterodactyl Gnus v0.82 is released) Lloyd Zusman
1999-04-18 0:35 ` Lloyd Zusman
1999-04-19 1:36 ` No longer can enter groups in 0.82 and 0.83 ... ??? Lloyd Zusman
1999-04-19 2:33 ` Lloyd Zusman [this message]
1999-04-19 6:26 ` Lars Magne 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=ltvhetz6dq.fsf@asfast.com \
--to=ljz@asfast.com \
/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).