Subject: [sup-talk] Sup won't save state

From: [email-masked] (Arvid Picciani)
Date: Sat, 13 Jun 2009 21:37:13 -0700

Hi,
I'm trying out sup and I totally like the concept so far, unfortunately it
doesn't work correctly for me.

1) It doesn't save its state.  The next time I open it up, read messages
are new again.

2) when pressing c, to compose a new message, it asks for a Subject.
Later in vim I see the Subject field contains random characters instead.

3) Most input "dialogs" (?) can't be killed.  Pressing ESC does nothing.
The only to chancel such an operation is to kill sup.

4) It behaves very odd when two clients are using the same imap account.
Yes, the docs state that, but not how to work around that when you
_have_  to use two clients. Currently I'm trying to use offlineimap,
unfortunately that's broken.

Thank you,
Arvid

---

From: [email-masked] (Arvid Picciani)
Date: Sun, 14 Jun 2009 17:51:18 -0700

Sorry,  still takes a little to get used to sup.  I have no clue what
was on and off list, but I assume this was off,  so I'm going to repost
it:

> $ in inbox mode to save, or at intervals. does clean shutdown not do
> this automatically?

"clean shutdown" is one of the reasons I went away from Gui crap.
It almost never works for me.
I don't even know how to shut down a Linux computer "cleanly" other then
by clicking some button on some Gui menu, which I don't have,
so most Gui programs just crash and leave me next time with some
ridiculous "recovery assistant".
Sup does exactly that and it's highly annoying. It doesn't even work.
Why the hell are you trying to kill a non existent sup instance?
Maybe I should just alias sup="rm .sup/lock;sup"

End of rant.

So how do I configure sup to save automatically?

PS:  the encrypt/reply to menu on the reply view is pretty cool :)

---

From: [email-masked] (Andrei Thorp)
Date: Sun, 14 Jun 2009 13:35:57 -0700

Yeah, sorry, I replied to person accidentally while on handheld.
Thanks for forwarding.

Anyway, yeah, wish saving in sup was better. Don't really know
anything better than sup-sync.

-AT

---

From: [email-masked] (William Morgan)
Date: Mon, 15 Jun 2009 06:37:15 -0700

Reformatted excerpts from Arvid Picciani's message of 2009-06-13:
> 1) It doesn't save its state.  The next time I open it up, read
> messages are new again.

How are you quitting Sup?

> Later in vim I see the Subject field contains random characters

Strange. Are they related in any way? Can you give an example?

> 3) Most input "dialogs" (?) can't be killed.  Pressing ESC does
> nothing.  The only to chancel such an operation is to kill sup.

Ctrl-g.

> 4) It behaves very odd when two clients are using the same imap
> account.  Yes, the docs state that, but not how to work around that
> when you _have_  to use two clients.

If you change the IMAP folder via another client, you'll have to run
sup-sync --changed on that source before running Sup. Sup should detect
this and tell you. What "odd" behavior are you seeing?
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (William Morgan)
Date: Mon, 15 Jun 2009 06:42:04 -0700

> "clean shutdown" is one of the reasons I went away from Gui crap.

Clean shutdown has nothing to do with GUI vs not GUI.

> I don't even know how to shut down a Linux computer "cleanly" other
> then by clicking some button on some Gui menu, which I don't have,

It's hard to guess what you're doing here, but it sounds like you're
pressing ctrl-c to kill Sup and then pressing y at the "die ungracefully
now?" prompt. You may want to read the new user guide:
http://sup.rubyforge.org/NewUserGuide.txt.
-- 
William <wmorgan-sup at masanjin.net>

---

From: [email-masked] (Andrei Thorp)
Date: Mon, 15 Jun 2009 11:20:58 -0400

> Strange. Are they related in any way? Can you give an example?

When this happened to me, they were absolutely unrelated, looked like
trying to vim a bit of a binary file...

But went away randomly a few days later.

-AT