----- Original Message -----
From: Yuri Arapov <yuri.arapov@xxxxxxxxxx>
To: <sylpheed@xxxxxxxxxx>
Sent: Friday, March 28, 2003 11:39 AM
Subject: [sylpheed:19490] Re: .sylpheed_mark update frequency


> On Fri, 28 Mar 2003 00:54:57 +0100
> Plamen <plamen@xxxxxxxxxx> wrote:
>
> [...]
>
> > #########################################################
> > # Program to execute when left mousebutton is pressed   #
> > #########################################################
> > #Execute xiterm -T elm -e elm &
> > #Execute startmailer &
> > Execute cp /dev/null ~/Mail/.asmail && /usr/bin/sylpheed && cp /dev/null
> > ~/Mail/.asmail &
> >
> > > INSERTED comment
> >  This is most recent line in this file. Before I'll run MUA, I _clear_
> > this file, i.e. I'll delete all messages from it and it sets number of
> > new messages to 0. I can do such thing every time I read a message if
> > MUA allows it (in fact, I do not need it so I don't think how to set it
> > in sylpheed). This cleaning is repeated after MUA finishs its run. Note,
> > that asmail is "docked" in wharf as icon and the right way how to run
> > MUA is to click to asmail's icon.
> > > END of comment
>
> Well, here it is.  You consider that mail is read when you launch MUA. I
> want the status of every single message to be changed when I really read
> it.

When I launch MUA, I can see this statistic in MUA :-)

>
> Sylpheed does update its internal structures on every mark/unmark event.
> And periodically updates mark/unmark status on the disk (via
> .sylpheed_mark).
>

Yes, udpates _internal_ structures. There is no standard how to tell such
informations to other programs. This is why I didn't think about it yet. But
if you need it, try make a patch.

Plamen