Subject: [sup-talk] New user questions...

From: [email-masked] (Vadim Gutnik)
Date: Thu, 26 Feb 2009 09:33:30 -0800

I built sup on my ubuntu system as described on the wiki; no problems,
though I'll likely switch to the packaged
version as it becomes available.

I tried using mbox format, ran into the From: bug (I think -- out of a
couple thousand emails, maybe a dozen
forwarded messages were split from their emails; still, this isn't
tolerable. Is there a plan to make sup
recognize email breaks at least as well as mutt does?), so I'm using
mdir format, which doesn't suffer from it.

Two specific questions, though:

1) I use getmail to get my POP3SSL mail and put it into mdir format.
Usually, when getmail tells me it found
a message, I go to my running sup process and press "P" for it to pick
up the mail, and sup shows the new message.
Sometimes (maybe 5-10% of the time?) sup does not find the new message
until I quit and restart it. Known problem?
Is there anything I can do to help debug it?

2) At least once or twice I've hit "d" by habit (and mistake). Is
there a way to search for "deleted" messages? I could
just rebuild the index from scratch and reapply labels if I had to,
but ...there must be an easier way, right?

Thanks.

   Vadim

---

From: [email-masked] (William Morgan)
Date: Sun, 22 Mar 2009 10:30:30 -0700

Hi Vadim,

Better late than never, right?

Reformatted excerpts from Vadim Gutnik's message of 2009-02-26:
> Is there a plan to make sup recognize email breaks at least as well as
> mutt does?),

Yes, absolutely. This is a high-priority bug.

> Usually, when getmail tells me it found a message, I go to my running
> sup process and press "P" for it to pick up the mail, and sup shows
> the new message.  Sometimes (maybe 5-10% of the time?) sup does not
> find the new message until I quit and restart it. Known problem?

Interesting. Someone's recently reported a similar problem, also with
Maildir, but in their case the message wasn't added to the index at all.

> Is there anything I can do to help debug it?

If there's any way to reliably reproduce this so that I can see it
happening locally, of course, that's the ideal solution. Otherwise, if
you notice it happening in the wild, you can also look at the log buffer
and the poll buffer and see if there's anything obviously wrong about
what Sup reports.

> but ...there must be an easier way, right?

You can search for deleted messages by using "\" (label:deleted), or by
using L.
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (John Bent)
Date: Sun, 22 Mar 2009 11:56:34 -0600

> You can search for deleted messages by using "\" (label:deleted), or by
Also, you can hit '@' to revert to your last saved point (i.e. last time
you hit '$'), and this will undelete it as well as undoing all your
other unsaved changes.  Also, hasn't someone recently submitted an Undo
patch?

---

From: [email-masked] (William Morgan)
Date: Sun, 22 Mar 2009 12:22:50 -0700

Reformatted excerpts from John Bent's message of 2009-03-22:
> Also, you can hit '@' to revert to your last saved point (i.e. last
> time you hit '$'), and this will undelete it as well as undoing all
> your other unsaved changes.  Also, hasn't someone recently submitted
> an Undo patch?

Oh right. If you check out the "next" branch in git, you'll have undo
power too.
-- 
William <wmorgan-sup at masanjin.net>