From: Chris Richards <cjr@netpliance.net>
Subject: Re: *'d Groups [Addendum]
Date: 21 Apr 2000 15:31:31 -0500 [thread overview]
Message-ID: <6e66tb19i4.fsf@sloth.netpliance.net> (raw)
In-Reply-To: Chris Richards's message of "21 Apr 2000 15:26:53 -0500"
Version: Gnus 5.8.2
Quitting all the way out of X-Emacs and coming back in has at least
gotten the 'g' to work. Initially most of the groups are *'d like
below but 'g' causes the group buffer to update.
Also as another side effect... my unsubscribed groups used to be
hidden in the group buffer unless I displayed all groups 'L'. Now,
regardless of the 'U' setting they are shown.
I would like to get this back to its previous behavior also.
Cheers,
cjr
--
A train stops at a train station. A bus stops at a bus station. On
my desk I have a workstation...
Chris Richards <cjr@netpliance.net> writes:
> Howdy.
>
> I had a recent X-windows meltdown which left gnus apparently in an
> unpleasant state. Upon restarting, several of my groups are in this
> format (total messages, marked messages, and unread messages
> respectively):
>
> 0 * * : nnfolder:lists.word
>
> When mail is split into that group it isn't updated. I have to
> actually enter the group summary buffer to see the messages there.
>
> After returning to the group buffer, the numbers are correct:
>
> 2 1 0 : nnfolder:lists.word
>
> If I save, quit, and restart gnus I am back to square one with the
> group marked:
>
> 0 * * : nnfolder:lists.word
>
> How can I recover from this?
>
> Cheers,
> cjr
> --
> A train stops at a train station. A bus stops at a bus station. On
> my desk I have a workstation...
next prev parent reply other threads:[~2000-04-21 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-21 20:26 *'d Groups Chris Richards
2000-04-21 20:31 ` Chris Richards [this message]
2000-04-22 11:18 ` Lars Magne Ingebrigtsen
2000-04-24 14:31 ` Chris Richards
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=6e66tb19i4.fsf@sloth.netpliance.net \
--to=cjr@netpliance.net \
/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).