From: Andy Moreton <andrewjmoreton@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: GNUS hide group from *Group* buffer when there no unread messages...
Date: Tue, 28 Aug 2012 13:01:25 +0100 [thread overview]
Message-ID: <vz14nnnns2y.fsf@gmail.com> (raw)
In-Reply-To: <878vd4l4mj.fsf@gavenkoa.example.com>
On Fri 24 Aug 2012, Oleksandr Gavenko wrote:
> On 2012-08-14, Eric Abrahamsen wrote:
>> And 'j' for `gnus-group-jump-to-group' will find any group, visible or
>> not! This is my main method for *Group* buffer navigation, and for your
>> exact use-case: 'j' to find a group, then 'C-u a' to compose a message
>> to it.
>>
> Thanks for explaining of your workflow. I try it but seems that I need to use
> ido completion or something similar as default completion require entering
> many symbols and TAB pressing, for this:
>
> nntp+news.gmane.org-ephemeral:gmane.emacs.gnus.user
> nntp+news.gmane.org:gmane.comp.window-managers.fvwm
> nntp+news.gmane.org:gmane.emacs.help
>
> TAB : TAB e TAB RET
>
> As I avoid using IDO-mode until have time to learn it dipper I still use such
> approach: C-s KEYWORD and C-s C-s ... as many time until find looked group in
> *Groups* buffer.
>
> That's why I look (and still look!!) for way to prevent hiding groups with
> zero unread articles.
Try this:
(setq gnus-permanently-visible-groups ".*")
and if you use topics:
(setq gnus-topic-display-empty-topics t)
HTH
AndyM
next prev parent reply other threads:[~2012-08-28 12:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 9:17 Oleksandr Gavenko
2012-08-14 9:26 ` Oleksandr Gavenko
2012-08-14 9:32 ` Adam Sjøgren
2012-08-14 13:13 ` Eric Abrahamsen
2012-08-14 14:44 ` Kevin Brubeck Unhammer
2012-08-15 3:10 ` Eric Abrahamsen
2012-08-15 6:12 ` Kevin Brubeck Unhammer
2012-08-24 14:57 ` Oleksandr Gavenko
2012-08-28 12:01 ` Andy Moreton [this message]
2012-08-30 10:12 ` Oleksandr Gavenko
[not found] ` <mailman.7811.1346321591.855.info-gnus-english@gnu.org>
2012-09-07 17:27 ` Randal L. Schwartz
2012-09-09 19:04 ` Lars Ingebrigtsen
2012-08-24 17:10 ` Oleksandr Gavenko
2012-08-15 7:03 ` XeCycle
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=vz14nnnns2y.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=info-gnus-english@gnu.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).