From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Inactive groups got unshown by `l'
Date: Tue, 07 Sep 2010 16:09:11 +0900 [thread overview]
Message-ID: <b4meid6m3mw.fsf@jpl.org> (raw)
In-Reply-To: <b4miq2i83bn.fsf@jpl.org>
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
Katsumi Yamaoka wrote:
> Katsumi Yamaoka wrote:
>> Katsumi Yamaoka wrote:
>> [...]
>>> I haven't yet investigated what changed the behavior. But which
>>> do you think reasonable?
>>> 1. `l' shows only active groups of which the levels are less than
>>> or equal to `gnus-group-default-list-level'.
>>> 2. `l' shows active and inactive groups of which the levels are
>>> less than or equal to `gnus-group-default-list-level'.
>>> If the former is adopted, only `L' is the means to recall what
>>> inactive groups a user subscribes to are. A user cannot browse
>>> inactive servers (i.e., servers that have never been opened) to
>>> know what groups are there because they are not listed in the
>>> server buffer.
>>> I can live with `L', though. ;-)
>> The patch below seems to achieve `2', that is the previous
>> behavior that Gnus has been going for years. When I start Gnus
>> with the prefix argument 2, the inactive level 4 groups don't
>> appear in the group buffer, but `l' shows them with `*'s as
>> numbers of those groups.
> Please ignore it, too. Sorry.
> By the patch, `l' doesn't show groups that have never been read
> if the server is opened for the other groups that the server
> provides. (Even if it worked, `gnus-group-method' used in the
> patch should have been replaced with `gnus-group-name-to-method'.)
> Sigh.
This may be the third time lucky:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 411 bytes --]
--- gnus-group.el~ 2010-09-05 22:46:18 +0000
+++ gnus-group.el 2010-09-07 07:03:23 +0000
@@ -1350,7 +1350,7 @@
group (gnus-info-group info)
params (gnus-info-params info)
newsrc (cdr newsrc)
- unread (gnus-group-unread group))
+ unread (or (gnus-group-unread group) t))
(when not-in-list
(setq not-in-list (delete group not-in-list)))
(when (gnus-group-prepare-logic
next prev parent reply other threads:[~2010-09-07 7:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-06 7:55 Katsumi Yamaoka
2010-09-06 20:26 ` Lars Magne Ingebrigtsen
2010-09-07 4:25 ` Katsumi Yamaoka
2010-09-07 5:07 ` Katsumi Yamaoka
2010-09-07 16:25 ` Lars Magne Ingebrigtsen
2010-09-07 5:48 ` Katsumi Yamaoka
2010-09-07 6:39 ` Katsumi Yamaoka
2010-09-07 7:09 ` Katsumi Yamaoka [this message]
2010-09-07 8:48 ` Lawrence Mitchell
2010-09-07 23:18 ` Katsumi Yamaoka
2010-09-07 16:26 ` Lars Magne Ingebrigtsen
2010-09-07 23:08 ` Katsumi Yamaoka
2010-09-09 6:10 ` Katsumi Yamaoka
2010-09-09 13:06 ` Lars Magne Ingebrigtsen
2010-09-07 23:31 ` Katsumi Yamaoka
2010-09-07 16:24 ` 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=b4meid6m3mw.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).