From: alec@thened.net (Alec Berryman)
Subject: [sup-talk] Initial import does not preserve read/unread status
Date: Sun, 10 Aug 2008 20:13:24 -0400 [thread overview]
Message-ID: <20080811001324.GA24661@thened.net> (raw)
In-Reply-To: <20080810235352.GA20706@thened.net>
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.
next prev parent reply other threads:[~2008-08-11 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-10 23:53 Alec Berryman
2008-08-11 0:13 ` Alec Berryman [this message]
2008-08-13 3:14 ` William Morgan
2008-08-17 18:59 ` Alec Berryman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080811001324.GA24661@thened.net \
--to=alec@thened.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox