Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: corrupted score files: "..." entries
Date: Fri, 31 Jan 2003 17:09:24 +0100	[thread overview]
Message-ID: <v9u1fps3m3.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <yotlptqdmjb2.fsf@jpl.org> (Katsumi Yamaoka's message of "Sat, 01 Feb 2003 00:26:57 +0900")

On Fri, Jan 31 2003, Katsumi Yamaoka wrote:

> Please use the following one to show the values of print-length
> and print-level. :)

Thanks, I've added this.

>> But I'm afraid this isn't the relevant code (or at least not the only
>> one). With gnus-verbose is set to 10, I don't see the debug output
>> (after doing `IrS' and `V t'):

I still don't see the expected debug output after (setq print-length
10 print-level 3).  But all.SCORE still gets corrupted.  I don't know
what exactly `print-length' and `print-level' do, but it seems that
`print-length' (=10) is relevant:

,----[ all.SCORE (with some line numbers) ]
|  .  (("message-id")
|  .   ("followup")
|  .   ("from"
|  1	  ("[some string]" -1000 nil e)
|  2	  ("[some string]" -1000 nil e)
|  3	  ("[some string]" -1000 731242 s)
|  4	  ("[some string]" -1000 731232 s)
|  5	  ("[some string]" -1000 731226 s)
|  6	  ("[some string]" -1000 nil e)
|  7	  ("[some string]" -1000 nil e)
|  8	  ("[some string]" -1000 731246 s)
|  9	  ("[some string]" -1000 nil e)
| 10	  ...)
|  .   ("references"
|  1	  ("[some string]" 1000 731246 s)
|  2	  ("[some string]" nil 731243 s)
|  3	  ("[some string]" -1000 731246 s)
|  4	  ("[some string]" nil 731238 s)
|  5	  ("[some string]" nil 731237 s)
|  6	  ("[some string]" nil 731236 s)
|  7	  ("[some string]" nil 731236 s)
|  8	  ("[some string]" nil 731236 s)
|  9	  ("[some string]" nil 731233 s)
| 10	  ...)
|  .   ("subject"
|  1	  ("[some string]" -1000 731237 s)
|  2	  ("[some string]" -1000 731235 s)
|  3	  ("[some string]" -1000 731239 s)
|  4	  ("[some string]" nil nil e)
|  5	  ("[some string]" -1000 731246 s)
|  6	  ("[some string]" -1 731241 s))
|  .   (decay 731065)
|  .   (files "../hierarchical/all.SCORE"))
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/



  reply	other threads:[~2003-01-31 16:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-30 21:00 Reiner Steib
2003-01-31  4:50 ` Katsumi Yamaoka
2003-01-31 13:41   ` Reiner Steib
2003-01-31 15:26     ` Katsumi Yamaoka
2003-01-31 16:09       ` Reiner Steib [this message]
2003-02-01 16:35   ` Lars Magne Ingebrigtsen

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=v9u1fps3m3.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).