[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Forward: [GitHub] Elmo treats IMAP4 messages flagged as both unseen and answered as seen [wanderlust/wanderlust GH-30]



At Wed, 06 Apr 2011 09:20:35 -0400,
Vitaly Mayatskikh wrote:
>
> At Fri, 25 Mar 2011 10:52:16 -0400, Dave Abrahams wrote:
>
> > From: sgrb <reply+i-703493-079d034f3628f17179246b9a8857caaa4b3e6e9e@reply.github.com>
> > To: dave+gitmirror@boostpro.com
> > Date: Fri, 25 Mar 2011 02:20:14 -0700
> > Subject: [GitHub] Elmo treats IMAP4 messages flagged as both unseen and answered as seen [wanderlust/wanderlust GH-30]
> >
> > I've found that when IMAP4 message is marked as both unseen and
> > answered, elmo forces it to be marked as seen. The following code
> > snipped is responsible for it (elmo-imap4.el:942,
> > elmo-imap4-fetch-callback-1-subr):
> >
> >     (when (and (or (memq 'important flag-list)
> >                              (memq 'answered flag-list))
> >                (memq 'unread flag-list))
> >         (setq elmo-imap4-seen-messages
> >                  (cons (elmo-message-entity-number entity)
> >                            elmo-imap4-seen-messages)))
> >
> > I suppose that this behavior is wrong. Here is an example of situation
> > when this behavior complicates usage of wanderlust: I'm reading lots of
> > corporate mail lists accessed as IMAP4 shared folders.  When someone
> > posts reply to some message in such shared folder, it becomes flagged as
> > answered and unseen until I read it (after which it becomes marked as
> > answered only). elmo automatically clears 'unread' flag in this case,
> > which makes wl-summary-down to skip this message - despite the fact that
> > I haven't read it. So I need to look for such messages manually, which
> > is very inconvinient...
> >
> > I don't know whether the behavior of IMAP4 shared folders described
> > above is common or not, but I still suggest removing of the fragment of
> > code cited above. Answered doesn't imply seen - because it could be
> > unseen by you, but answered by someone else - which is quite common in
> > case of shared folders.
>
> Looks reasonable. I'm ok to commit change, but would like to hear
> people opinion on it.

I've just pushed a commit to trunk that fixes this issue.

Best,
  -- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber.... dmjena@jabber.org
Email..... dmaus@ictsoc.de

Attachment: pgp3pYj0sqxEN.pgp
Description: PGP signature