From: Peter Davis <pd@world.std.com>
Subject: Re: HELP! HELP! HELP!
Date: Sat, 05 Apr 2003 18:26:23 GMT [thread overview]
Message-ID: <Xns9354886D5972Cpeterdavismediaonene@216.148.227.77> (raw)
In-Reply-To: <84brzknbzu.fsf@lucy.is.informatik.uni-duisburg.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1882 bytes --]
kai.grossjohann@gmx.net (Kai Großjohann) wrote in
news:84brzknbzu.fsf@lucy.is.informatik.uni-duisburg.de:
> Peter Davis <pd@world.std.com> writes:
>
>> Well, I *thought* that was it. However, I'm now seeing some very
>> weird behavior. Specifically:
>>
>> 1) I fetch new mail. This appears to work normally, and all the
>> appropriate groups have unread message counts in the *Group*
>> buffer.
>
>
>> 2) I enter a group, and the number of messages in the *Summary* buffer
>> doesn't match the message count. For example, the new message
>> count said 5 new messages, but only 1 is displayed in the summary
>> buffer (and no, it's not a collapsed thread).
>
> Given that these counts are (bad) estimates anyway, I'm not surprised.
>
> Does C-u RET show all articles as it is supposed to do?
>
>> 3) I hit 'n' on that message, and another message gets added to the
>> *Summary* buffer. Continuing to type 'n' continues to add messages
>> to the *Summary*.
>
> Hm. There was a variable for auto-extending groups like this. Hm.
> I can't find that variable, though. Anyone?
>
>> 4) At some point, 'n' stops adding messages, and starts simply jumping
>> the cursor around among the various displayed articles. However
>> ... the display in the *Article* buffer *doesn't* match the line in
>> the *Summary* buffer, and I can't get them to match.
>
> `g' should do the right thing. But I've also seen `n' jumping around.
Thanks again, Kai. I'll try this again, re-creating the Active file from
scratch. It's entirely possible that the old one didn't quite match the
folder structure anymore.
Thanks!
-pd
--
--------
Peter Davis
Funny stuff at http://world.std.com/~pd
Resources for children's writers & illustrators:
http://world.std.com/~pd/cwrl.html
next prev parent reply other threads:[~2003-04-05 18:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <r88uos3a.fsf@bitstream.com>
2003-03-27 11:01 ` Turning MH folders into nnml groups Kai Großjohann
[not found] ` <1y0s1nux.fsf@bitstream.com>
[not found] ` <8465q3es7a.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <87u1dmd42z.fsf@wassern.consult-meyers.com>
[not found] ` <f6e2d38e.0304021034.224f2d8d@posting.google.com>
2003-04-03 15:55 ` HELP! (Was: Re: Turning MH folders into nnml groups) Peter Davis
[not found] ` <84pto2mo36.fsf@lucy.is.informatik.uni-duisburg.de>
2003-04-04 15:05 ` HELP! Peter Davis
2003-04-04 15:46 ` HELP! Kai Großjohann
[not found] ` <znn6dxgd.fsf_-_@bitstream.com>
[not found] ` <84cwiwqvn2.fsf@lucy.is.informatik.uni-duisburg.de>
[not found] ` <Xns93539813463DDpdavispageflexinccom@199.103.147.5>
[not found] ` <Xns93539BEB6884Fpdavispageflexinccom@199.103.147.5>
[not found] ` <smsykk93.fsf@bitstream.com>
[not found] ` <84brzknbzu.fsf@lucy.is.informatik.uni-duisburg.de>
2003-04-05 18:26 ` Peter Davis [this message]
[not found] ` <87fzp0zo3p.fsf@wassern.consult-meyers.com>
[not found] ` <adf6gvdd.fsf@bitstream.com>
2003-04-05 13:58 ` Turning MH folders into nnml groups A. L. Meyers
2003-04-05 19:33 ` Peter Davis
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=Xns9354886D5972Cpeterdavismediaonene@216.148.227.77 \
--to=pd@world.std.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).