Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
Cc: Simon Josefsson <simon@josefsson.org>
Subject: Re: self-contained nnml
Date: Sun, 19 Aug 2001 16:21:30 +1000	[thread overview]
Message-ID: <87itfkvac5.fsf@inanna.rimspace.net> (raw)
In-Reply-To: <ilu3d6pl3p8.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Sat, 18 Aug 2001 18:42:43 +0200")

On Sat, 18 Aug 2001, Simon Josefsson wrote:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> 
>>> Todo: Port to nnfolder etc.  It should be _really_ trivial.  Any
>>> takers?
>>
>> Maybe some functions could be moved to nnmail.el, so that they are
>> easy to reuse.
> 
> Yes, that would be most of it.
> 
>> I'd say: commit it to CVS and have people whine if it doesn't work.
>> This is development software, after all.
> 
> Done.

Whine. :/

I updated my Gnus to the CVS version at:
Built at Sun Aug 19 15:53:16 EST 2001

Recompile, yada, yada, then we boot XEmacs and it starts Gnus...

...the bootstrapping of the NNML marks works just fine.

Then I note that the summary buffer is ... odd. The majority of my
groups seem to have three articles in them now, which is odd, given the
standard set is > 2000 for most of them.

So, this is odd. To continue testing, I try entering the group where I
file the output of my log monitors and such. It's only got one message
in it, which is nice.

It, of course, reports one unread out of three articles. Trying to enter
the group results in the single message being marked read but *no*
indication of a summary buffer. Ho, hum.

So, I make the last test and 'g' in the groups buffer, which restores
the system message to life. Ugh.

So, back out the changes to the day before your commit of the
stand-alone NNML stuff and it's all good again.

*sigh*

So, Simon, suggestions on how I might go about debugging this?
        Daniel

-- 
If I knew for a certainty that some man was coming to my house with the
conscious intention of doing me good, I would run for my life.
        -- Henry David Thoreau


  reply	other threads:[~2001-08-19  6:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-18 11:34 Simon Josefsson
2001-08-18 15:40 ` Kai Großjohann
2001-08-18 16:42   ` Simon Josefsson
2001-08-19  6:21     ` Daniel Pittman [this message]
2001-08-19  9:44       ` Simon Josefsson
2001-08-20  2:35         ` Problems with .newsrc.eld (aws: Re: self-contained nnml) Daniel Pittman
2001-08-20  3:18           ` Daniel Pittman
2001-08-20  9:23           ` Simon Josefsson
2001-08-21  5:07             ` Daniel Pittman
2001-08-21 16:31               ` Simon Josefsson
2001-08-21 18:13                 ` Paul Jarc
2001-08-21 20:30                   ` Simon Josefsson
2001-08-21 23:57                     ` Daniel Pittman
2001-08-21 23:56                 ` Daniel Pittman
2001-08-24 23:00 ` self-contained nnml Rob Browning
2001-08-25  0:20   ` Rob Browning
2001-08-25  0:58     ` Rob Browning
2001-08-25  2:11       ` ShengHuo ZHU
2001-08-26 18:15         ` Rob Browning
2001-08-25  9:43     ` Simon Josefsson
2001-08-26 15:29       ` Rob Browning
2001-08-26 16:32         ` Simon Josefsson
2001-08-26 18:28           ` Rob Browning

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=87itfkvac5.fsf@inanna.rimspace.net \
    --to=daniel@rimspace.net \
    --cc=simon@josefsson.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).