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. _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
