From: Dan Christensen <jdc@jhu.edu>
Cc: ding@gnus.org
Subject: Re: strange behaviour when `B c'ing an empty article
Date: Thu, 07 Oct 1999 01:07:52 -0400 [thread overview]
Message-ID: <87so3n4v2v.fsf@chow.mat.jhu.edu> (raw)
In-Reply-To: Shenghuo ZHU's message of "06 Oct 1999 23:20:37 -0400"
Shenghuo ZHU <zsh@cs.rochester.edu> writes:
> Now, another patch make more things work. (Committed)
Getting closer. :-) I copied the articles to groups test8 and
test9 (with `B c') and have attached the files below.
Here are various things that seem odd:
o The number of lines in the non-empty article got changed from 3
to 1 when the move is done. What is the correct way to count
lines in an article?
o The number of lines in the empty article is calculated as 1
(both before and after the move). Is this correct?
o The Xref lines are different for the two articles. One is
self-referential, and the other points back to my Inbox.
I think the latter is correct, right?
o On the short article, if display the full headers by
hitting `t', everything looks ok except that I get two
headers combined on one line:
X-Gnus-Article-Number: 1 Thu Oct 7 00:55:51 1999From: Dan Christensen <jdc@chow.mat.jhu.edu>
Mbox format sure is awkward...
Here is test8:
---------------
From jdc@chow.mat.jhu.edu Wed Oct 06 16:28:32 1999
Received: from jdc by scratchy with local (Exim 2.05 #1 (Debian))
id 11Yxfr-0006FN-00; Wed, 6 Oct 1999 16:28:31 -0400
To: jdc@scratchy
Subject: test of orphan scoring
From: Dan Christensen <jdc@chow.mat.jhu.edu>
Date: 06 Oct 1999 16:28:31 -0400
X-Gnus-Mail-Source: file:/var/mail/jdc
Message-ID: <874sg48c9c.fsf@chow.mat.jhu.edu>
User-Agent: Gnus/5.07009701 (Pterodactyl Gnus v0.97.1) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 1
Xref: scratchy Inbox:10385
X-Gnus-Article-Number: 1 Thu Oct 7 00:55:51 1999
------------------
and test9:
------------------
From jdc@chow.mat.jhu.edu Wed Oct 06 16:29:27 1999
Received: from jdc by scratchy with local (Exim 2.05 #1 (Debian))
id 11Yxgl-0006Fd-00; Wed, 6 Oct 1999 16:29:27 -0400
To: jdc@scratchy
Subject: Re: test of orphan scoring
References: <874sg48c9c.fsf@chow.mat.jhu.edu>
From: Dan Christensen <jdc@chow.mat.jhu.edu>
Date: 06 Oct 1999 16:29:26 -0400
In-Reply-To: Dan Christensen's message of "06 Oct 1999 16:28:31 -0400"
X-Gnus-Mail-Source: file:/var/mail/jdc
Message-ID: <87puys6xnd.fsf@chow.mat.jhu.edu>
User-Agent: Gnus/5.07009701 (Pterodactyl Gnus v0.97.1) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Xref: scratchy test9:1
Lines: 1
X-Gnus-Article-Number: 1 Thu Oct 7 00:58:24 1999
this is the followup to jdc
------------------
Thanks a lot for looking into this...
Dan
--
Dan Christensen
jdc@math.jhu.edu
next prev parent reply other threads:[~1999-10-07 5:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-06 20:57 Dan Christensen
1999-10-06 23:24 ` Shenghuo ZHU
1999-10-07 0:26 ` Dan Christensen
1999-10-07 3:20 ` Shenghuo ZHU
1999-10-07 5:07 ` Dan Christensen [this message]
1999-10-07 5:51 ` Shenghuo ZHU
1999-10-07 15:37 ` Dan Christensen
1999-10-07 21:15 ` Shenghuo ZHU
1999-10-07 21:44 ` Dan Christensen
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=87so3n4v2v.fsf@chow.mat.jhu.edu \
--to=jdc@jhu.edu \
--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).