From: Leon <sdl.web@gmail.com>
Subject: Re: Customize the location and name of .newsrc.eld
Date: Sun, 23 Apr 2006 20:53:46 +0100 [thread overview]
Message-ID: <m23bg4f4qd.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: <psj813wp.fsf@smtprelay.t-online.de>
Adrian Aichner <adrian@xemacs.org> writes:
> Leon <sdl.web@gmail.com> writes:
>
>> 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?
>
> Hi Leon, see
>
> gnus-group-default-list-level
> and
> gnus-activate-level
> which I set differently when at home (to see news groups)
> and at work (to not see these and my private mail folders).
>
> Explicitly listing at the desired level is still possible.
>
> Hope this helps!
>
> Adrian
>
>>
>> My idea is when it's weekday set this variable to 2 while weekend set
>> it to 5.
Dear Adrian,
That's exactly what I'm looking for. It works great. Thanks a lot.
For the record:
Put this in ~/.gnus.el will show only level 2 groups during Mon to
Fri.
,--------
| (if (< (string-to-number (format-time-string "%u" (current-time))) 6)
| (setq gnus-activate-level 2
| gnus-group-default-list-level 2))
`--------
Cheers,
--
Leon
next prev parent reply other threads:[~2006-04-23 19:53 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
2006-04-23 19:35 ` Adrian Aichner
2006-04-23 19:53 ` Leon [this message]
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=m23bg4f4qd.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).