Gnus development mailing list
 help / color / mirror / Atom feed
From: Leon <sdl.web@gmail.com>
Subject: Re: Customize the location and name of .newsrc.eld
Date: Sun, 23 Apr 2006 17:14:29 +0100	[thread overview]
Message-ID: <m264l0e0be.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: <x77j5gs426.fsf@davestoy.homelinux.org>

Dave Goldberg <david.goldberg6@verizon.net> writes:

> Would a combination of gnus-topic-mark-topic and
> gnus-group-set-current-level work?  You could write a funtion that
> that marks all the groups in a topic, set the level to something high,
> but not unsubscribed or killed, and then limit displayed groups to a
> lower level.  Along with the topic hiding variables, I think you might
> be able to get what you want.  I've never automated this, but I have
> used the basic idea in the past to make my .newsrc.eld transportable
> between work and home (though now that I no longer ever want my home
> machine to touch my mail and news servers at work, I don't do it any
> more).

Dave,

Thanks to your suggestion, I think I'm getting close to find a
solution. I have set all the important groups to a level of 2.

Is there a variable that controls when a group with a level less or
equal to the variable, it will be visible?

My idea is when it's weekday set this variable to 2 while weekend set
it to 5.

-- 
Leon




  reply	other threads:[~2006-04-23 16:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 20:59 Leon
2006-04-22  0:29 ` Lars Magne Ingebrigtsen
2006-04-22  2:06   ` Leon
2006-04-23 14:10     ` Lars Magne Ingebrigtsen
2006-04-23 14:50       ` Leon
2006-04-23 15:24         ` Lars Magne Ingebrigtsen
2006-04-23 15:29         ` Dave Goldberg
2006-04-23 16:14           ` Leon [this message]
2006-04-23 19:35             ` Adrian Aichner
2006-04-23 19:53               ` Leon
2006-04-23 20:10                 ` Leon
2006-04-26 13:03                   ` recent trouble with html parsing gdt
2006-04-26 22:48                     ` Katsumi Yamaoka

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=m264l0e0be.fsf@sl392.st-edmunds.cam.ac.uk \
    --to=sdl.web@gmail.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).