From exmh-workers-admin@redhat.com  Mon Jul 22 19:48:38 2002
Return-Path: <exmh-workers-admin@spamassassin.taint.org>
Delivered-To: yyyy@localhost.netnoteinc.com
Received: from localhost (localhost [127.0.0.1])
	by phobos.labs.netnoteinc.com (Postfix) with ESMTP id DAE9D440D6
	for <jm@localhost>; Mon, 22 Jul 2002 14:48:14 -0400 (EDT)
Received: from dogma.slashnull.org [212.17.35.15]
	by localhost with IMAP (fetchmail-5.9.0)
	for jm@localhost (single-drop); Mon, 22 Jul 2002 19:48:14 +0100 (IST)
Received: from listman.spamassassin.taint.org (listman.spamassassin.taint.org [66.187.233.211]) by
    dogma.slashnull.org (8.11.6/8.11.6) with ESMTP id g6MIGt411887 for
    <jm-exmh@jmason.org>; Mon, 22 Jul 2002 19:16:55 +0100
Received: from listman.spamassassin.taint.org (localhost.localdomain [127.0.0.1]) by
    listman.redhat.com (Postfix) with ESMTP id 5A8023F380; Mon, 22 Jul 2002
    14:16:02 -0400 (EDT)
Delivered-To: exmh-workers@listman.spamassassin.taint.org
Received: from int-mx1.corp.spamassassin.taint.org (int-mx1.corp.spamassassin.taint.org
    [172.16.52.254]) by listman.redhat.com (Postfix) with ESMTP id 1D8E93F301
    for <exmh-workers@listman.redhat.com>; Mon, 22 Jul 2002 14:15:24 -0400
    (EDT)
Received: (from mail@localhost) by int-mx1.corp.spamassassin.taint.org (8.11.6/8.11.6)
    id g6MIFO004770 for exmh-workers@listman.redhat.com; Mon, 22 Jul 2002
    14:15:24 -0400
Received: from mx1.spamassassin.taint.org (mx1.spamassassin.taint.org [172.16.48.31]) by
    int-mx1.corp.redhat.com (8.11.6/8.11.6) with SMTP id g6MIFOR04766 for
    <exmh-workers@redhat.com>; Mon, 22 Jul 2002 14:15:24 -0400
Received: from tippex.localdomain (h189n1fls22o974.telia.com
    [213.64.79.189]) by mx1.redhat.com (8.11.6/8.11.6) with SMTP id
    g6MI3rs07283 for <exmh-workers@redhat.com>; Mon, 22 Jul 2002 14:03:53
    -0400
Received: by tippex.localdomain (Postfix, from userid 500) id 9D292470D;
    Mon, 22 Jul 2002 20:15:16 +0200 (CEST)
Received: from tippex.localdomain (localhost [127.0.0.1]) by
    tippex.localdomain (Postfix) with ESMTP id 88301470C; Mon, 22 Jul 2002
    20:15:16 +0200 (CEST)
X-Mailer: exmh version 2.5_20020719 01/15/2001 with nmh-1.0.4
To: Chris Garrigues <cwg-dated-1027791513.94b180@DeepEddy.Com>
Cc: exmh-workers@spamassassin.taint.org
Subject: Re: Another bug
In-Reply-To: Message from Chris Garrigues
    <cwg-dated-1027791513.94b180@DeepEddy.Com> of
    "Mon, 22 Jul 2002 12:38:32 CDT."
    <1027359513.3184.TMDA@deepeddy.vircio.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
From: Anders Eriksson <aeriksson@fastmail.fm>
Message-Id: <20020722181516.9D292470D@tippex.localdomain>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by int-mx1.corp.spamassassin.taint.org
    id g6MIFOR04766
X-Loop: exmh-workers@spamassassin.taint.org
Sender: exmh-workers-admin@spamassassin.taint.org
Errors-To: exmh-workers-admin@spamassassin.taint.org
X-Beenthere: exmh-workers@spamassassin.taint.org
X-Mailman-Version: 2.0.1
Precedence: bulk
List-Help: <mailto:exmh-workers-request@spamassassin.taint.org?subject=help>
List-Post: <mailto:exmh-workers@spamassassin.taint.org>
List-Subscribe: <https://listman.spamassassin.taint.org/mailman/listinfo/exmh-workers>,
    <mailto:exmh-workers-request@redhat.com?subject=subscribe>
List-Id: Discussion list for EXMH developers <exmh-workers.spamassassin.taint.org>
List-Unsubscribe: <https://listman.spamassassin.taint.org/mailman/listinfo/exmh-workers>,
    <mailto:exmh-workers-request@redhat.com?subject=unsubscribe>
List-Archive: <https://listman.spamassassin.taint.org/mailman/private/exmh-workers/>
Date: Mon, 22 Jul 2002 20:15:11 +0200


Chris said:
> 
> I can tell you what the 'clear' and 'del' arguments mean:
> 
> Mh_SequenceUpdate lists/l-k clear cur {} public
> 	This means to clear the 'cur' sequence for lists/l-k
> 
> Mh_SequenceUpdate lists/l-k del unseen 5400 public
> 	This means to delete message 5400 from the 'unseen' sequence for lists/l-k
> 
> Can you explain more what you were actually doing as this occurred?  This 
> doesn't appear to be background processing.  Is there significance to message 
> 5400?  Is it the one that isn't displaying?
> 
> Chris

After sending the report I started fiddling with the Ftoc_RescanLine 
stuff and I havn't seen it since. I can't really tell if it was my 
hacking that removed it, or if it was some transitional magic 
happening since this was the first invocation of that version of 
exmh. I've backed out my stuff now, and'll let you know if it happens 
again.


On another thing with the Ftoc_RescanLine stuff. This routine is 
called at times still unclar to me. An inspection of the routine 
suggests that it is used in the transition of a message to/form 
"current" state to re-paint the ftoc line. However, checking the 
msg.tcl code (MSgChange) we find:

    if {$msgid != {}} {
        # Allow null msgid from Msg_ShowWhat, which supplies line 
instead
        if {$msgid < 0}  return
    } else {
        # line null too, try using first in folder
        if {[string length $line] == 0} { set line 1 }
        set msgid [Ftoc_MsgNumber [Ftoc_FindMsg $msgid $line]]
    }
    Ftoc_ClearCurrent
    Mh_SetCur $exmh(folder) $msgid
    Ftoc_ShowSequences $exmh(folder)

The Ftoc_ClearCurrent calls Ftoc_RescanLIne to clear the '+' sign 
_before_ the on-disk transition is made. I hacked this stuff and more 
or less changed the order. It works, but fails on some folder changes.

My feeling of this is that we really do not want to have a 
Ftoc_ClearCurrent, but rather just a RescanLine and the caller had 
better know the line or msgid. That routine shoud just put in the '+' 
if the line/msg in question happened to be the cur msg. Thoughts?


/Anders










_______________________________________________
Exmh-workers mailing list
Exmh-workers@redhat.com
https://listman.redhat.com/mailman/listinfo/exmh-workers