From: David Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: Shorter/customized group names?
Date: Thu, 28 May 2009 00:42:57 -0400 [thread overview]
Message-ID: <m28wkhalda.fsf@boostpro.com> (raw)
In-Reply-To: <87zlcydxa0.fsf@randomsample.de>
on Wed May 27 2009, David Engster <deng-AT-randomsample.de> wrote:
> David Abrahams <dave@boostpro.com> writes:
>> Right now, my *Group* buffer looks like this:
> [...]
>> 48083 | nntp+news.gmane.org:gmane.comp.lib.boost.user
>
>> Is there anything I can do to clean that up and make it easier to find
>> what I'm looking for?
>
> Just a guess, but using %G instead of %g in gnus-group-line-format will
> probably do what you want.
Well, thanks; it's definitely a start. I'd like to do better, though. I
guess I can use a ~(...) clause and hand-code it, but I think there are
some things I wouldn't be able to do very easily that way. For example,
I'm currently seeing:
233 | gmane.comp.lib.boost.announce
3251 | gmane.comp.lib.boost.asio.user
20879 | gmane.comp.lib.boost.build
498 | gmane.comp.lib.boost.cmake
3788 | gmane.comp.lib.boost.documentation
65 | gmane.comp.lib.boost.interest
152 | gmane.comp.lib.boost.jam
891 | gmane.comp.lib.boost.langbinding
6353 | gmane.comp.lib.boost.testing
383 | gmane.comp.lib.boost.threads.devel
5016 | gmane.comp.lib.boost.ublas
which could be made as simple as:
233 | gmane.comp.lib.boost.announce
3251 | .boost.asio.user
20879 | .boost.build
498 | .boost.cmake
3788 | .boost.documentation
65 | .boost.interest
152 | .boost.jam
891 | .boost.langbinding
6353 | .boost.testing
383 | .boost.threads.devel
5016 | .boost.ublas
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2009-05-28 4:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-27 20:02 David Abrahams
2009-05-27 21:57 ` David Engster
2009-05-28 4:42 ` David Abrahams [this message]
2009-05-28 9:43 ` David Engster
2009-05-29 14:51 ` David Abrahams
2009-05-29 16:50 ` David Engster
2009-05-29 18:02 ` David Abrahams
2009-05-29 22:31 ` David Abrahams
2009-05-30 14:46 ` David Engster
2009-06-09 19:22 ` David Abrahams
2009-07-08 19:17 ` Ted Zlatanov
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=m28wkhalda.fsf@boostpro.com \
--to=dave@boostpro.com \
--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).