Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Inactive groups got unshown by `l'
Date: Tue, 07 Sep 2010 18:24:30 +0200	[thread overview]
Message-ID: <m3lj7djzcx.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <b4m8w3efadx.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> 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.

Hm...  I don't see that...

> 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'.

I think 2) is how it's supposed to work.  It's what I was aiming for,
anyway.  :-)

I'll try restarting Emacs to check whether I have any artifacts going
on...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




      parent reply	other threads:[~2010-09-07 16:24 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
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 [this message]

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=m3lj7djzcx.fsf@quimbies.gnus.org \
    --to=larsi@gnus.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).