From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Inactive groups got unshown by `l'
Date: Tue, 07 Sep 2010 13:25:14 +0900 [thread overview]
Message-ID: <b4m8w3efadx.fsf@jpl.org> (raw)
In-Reply-To: <m3aanu1uvn.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> I use the group level 1, 2 and 3 for the mail groups, the interesting
>> nntp groups, and the other nntp groups respectively. Furthermore,
>> I use the level 4 for some foreign groups that take time to open.
>> I usually start Gnus as `C-u 2 M-x gnus', i.e., I usually read only
>> the mail groups and some news groups. But when I want to read one
>> of the level 4 groups, I used to type `l' in the group buffer and
>> find it. Now it doesn't work although the level is less than
>> `gnus-group-default-list-level'. The server for those groups is not
>> shown in the server buffer. I can use `L' instead of `l', or
>> the following advice. But it's a bit inconvenient for me. :<
I got to think I may want to change the lifestyle in Gnus after
all. ;-)
> Yes. I've now changed the `g' function to use the explicit level for
> foreign groups, too,
By the change, Gnus got to show many native groups having no unread
article even though `gnus-permanently-visible-groups' doesn't match
those groups. I think it should be fixed (or reverted?). OTOH, `l'
still doesn't show inactive foreign groups (i.e., groups of which
the server have never been opened).
> so that `4 g' should work as advertised.
As for me that takes a long time because it updates all the level 4
groups and also the level 1, 2, 3 groups (= mostly all the groups).
Instead... the old behavior for years was that `l' shows inactive
groups with `*' (not a number) as the number of articles. And I
was able to update only some groups one by one using `M-g'
(gnus-group-get-new-news-this-group).
> However, I'm not quite sure that I'm totally seeing what you're seeing.
> The `l' command hasn't been changed at all, lately, I think, so there
> must be some kind of subtle interaction between `l' and `g' that I'm not
> quite handling right now...
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. ;-)
next prev parent reply other threads:[~2010-09-07 4:25 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 [this message]
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
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=b4m8w3efadx.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).