* [sup-talk] Initial import does not preserve read/unread status
@ 2008-08-10 23:53 Alec Berryman
2008-08-11 0:13 ` Alec Berryman
2008-08-13 3:14 ` William Morgan
0 siblings, 2 replies; 4+ messages in thread
From: Alec Berryman @ 2008-08-10 23:53 UTC (permalink / raw)
The new user guide says about sup-add:
"You can also specify --read to mark all imported messages as read; the
default is to preserve the read/unread status from the source."
When I imported a new maildir source with a mix of read and unread
messages (in the cur or new subfolder, respectively), all of the
messages were marked unread. Is the documentation wrong or is this a
bug? I hope it's a bug.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [sup-talk] Initial import does not preserve read/unread status
2008-08-10 23:53 [sup-talk] Initial import does not preserve read/unread status Alec Berryman
@ 2008-08-11 0:13 ` Alec Berryman
2008-08-13 3:14 ` William Morgan
1 sibling, 0 replies; 4+ messages in thread
From: Alec Berryman @ 2008-08-11 0:13 UTC (permalink / raw)
Alec Berryman on 2008-08-10 19:53:52 -0400:
> The new user guide says about sup-add:
>
> "You can also specify --read to mark all imported messages as read; the
> default is to preserve the read/unread status from the source."
>
> When I imported a new maildir source with a mix of read and unread
> messages (in the cur or new subfolder, respectively), all of the
> messages were marked unread. Is the documentation wrong or is this a
> bug? I hope it's a bug.
On second thought, that was a horrible bug report.
I'm using sup-0.6 from gems. I haven't done anything fancy; I just ran
'gem install sup', and it appears all my gem packages are up to date. I
configured sup by running sup-config, entering my name and address,
taking the other defaults, and then not adding any sources. I added one
source later using `sup-add maildir:/path/to/maildir'. Mutt and manual
inspection of the maildir shows most of the messages being read, but sup
shows all of them unread. The behavior does not change if I remove
~/.sup and run the same sequence of commands except for adding a
sup-sync between running sup-add and sup.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [sup-talk] Initial import does not preserve read/unread status
2008-08-10 23:53 [sup-talk] Initial import does not preserve read/unread status Alec Berryman
2008-08-11 0:13 ` Alec Berryman
@ 2008-08-13 3:14 ` William Morgan
2008-08-17 18:59 ` Alec Berryman
1 sibling, 1 reply; 4+ messages in thread
From: William Morgan @ 2008-08-13 3:14 UTC (permalink / raw)
Reformatted excerpts from Alec Berryman's message of 2008-08-10:
> When I imported a new maildir source with a mix of read and unread
> messages (in the cur or new subfolder, respectively), all of the
> messages were marked unread. Is the documentation wrong or is this a
> bug? I hope it's a bug.
Weird. Can you provide some sample filenames for read and unread
messages? (Since that's how Maildir keeps state---it might be there's
some naming variant that Sup doesn't know about.)
--
William <wmorgan-sup at masanjin.net>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [sup-talk] Initial import does not preserve read/unread status
2008-08-13 3:14 ` William Morgan
@ 2008-08-17 18:59 ` Alec Berryman
0 siblings, 0 replies; 4+ messages in thread
From: Alec Berryman @ 2008-08-17 18:59 UTC (permalink / raw)
William Morgan on 2008-08-12 20:14:09 -0700:
> Reformatted excerpts from Alec Berryman's message of 2008-08-10:
> > When I imported a new maildir source with a mix of read and unread
> > messages (in the cur or new subfolder, respectively), all of the
> > messages were marked unread. Is the documentation wrong or is this a
> > bug? I hope it's a bug.
>
> Weird. Can you provide some sample filenames for read and unread
> messages? (Since that's how Maildir keeps state---it might be there's
> some naming variant that Sup doesn't know about.)
Sure (ls -R output; maildir attached; samples from sup-talk):
sup-does-not-import-read-messages-as-read/:
cur/
new/
tmp/
sup-does-not-import-read-messages-as-read/cur:
1218394528_0.8381.barry,U=23205,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
1218397749_0.16026.barry,U=23207,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
1218405160_1.1978.barry,U=23211,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
1218413059_0.23982.barry,U=23215,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,RS
1218413717_1.26111.barry,U=23216,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
1218626652_4.3870.barry,U=23368,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
1218626652_5.3870.barry,U=23369,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe:2,S
sup-does-not-import-read-messages-as-read/new:
1218626652_2.3870.barry,U=23366,FMD5=d25c71bb54a5e1f674c1d0df91b0b4fe
sup-does-not-import-read-messages-as-read/tmp:
When I import this folder with sup, I see all messages marked as new,
but I only expect to see 1. The maildir names are generated by
offlineimap.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sup-does-not-import-read-messages-as-read.tar.bz2
Type: application/octet-stream
Size: 6635 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080817/485a2391/attachment-0001.obj>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2008-08-17 18:59 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-08-10 23:53 [sup-talk] Initial import does not preserve read/unread status Alec Berryman
2008-08-11 0:13 ` Alec Berryman
2008-08-13 3:14 ` William Morgan
2008-08-17 18:59 ` Alec Berryman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox