From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Jumbled group buffer
Date: Fri, 20 Jul 2001 15:05:58 -0700 [thread overview]
Message-ID: <2nlmlj8ddl.fsf@piglet.jia.vnet> (raw)
In-Reply-To: <m14rs78nhk.fsf@reader.newsguy.com> (Harry Putnam's message of "20 Jul 2001 12:40:19 -0700")
Harry Putnam <reader@newsguy.com> writes:
> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
>
>> Harry Putnam <reader@newsguy.com> writes:
>>
>> > I've been noticing lately with my recent (2wks) cvs, something I don't
>> > rembember being like this before. I use tic and dormant a lot so in
>> > my group buffer I'll see an `*' at the left of groups with something
>> > ticked or dormant. Now my group buffer looks jumbled due to a on char
>> > indent on the groups with the asterisk.
>> >
>> > I don't remember it looking like that before. Or is this something
>> > I've inadvertantly activated.
>> >
>> > * 18: nnml:seawolf
>> > 5: nnml:secd
>> > * 0: nnml:slrn
>> > 12: nnml:time
>> > * 0: nnml:system
>> > 146: nndir:/mnt/pack/Mail/texi
>> > 37: nndir:/mnt/pack/Mail/texi2
>> > * 0: nnml:ucsb
>> > * 0: nnvirtual:ptw+
>> > 0: nnml:cron
>> > 122: nnml:cron_fetchall
>> > 1: nnml:cron_misc
>> >
>> >
>> > Seem like it used to appear with all nnml lined up at the first n
>> > regardless of Asterisk.
>>
>> It works for me. What is your gnus-group-line-format?
>
> I don't think I've changed this for quite a long time.
> But memory isn't all that reliable.
>
> (setq gnus-group-line-format"%M%S%p%P%5y: %(%g%)%l\n")
I don't get the clue. Maybe `M-x gnus-compile RET' helps a little.
ShengHuo
next prev parent reply other threads:[~2001-07-20 22:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 22:20 Harry Putnam
2001-07-20 17:59 ` ShengHuo ZHU
2001-07-20 19:40 ` Harry Putnam
2001-07-20 22:05 ` ShengHuo ZHU [this message]
2001-07-21 19:25 ` Harry Putnam
2001-07-21 21:52 ` Kai Großjohann
2001-07-24 6:04 ` ShengHuo ZHU
2001-07-24 6:45 ` Harry Putnam
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=2nlmlj8ddl.fsf@piglet.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).