From: aep@exys.org (Arvid Picciani)
Subject: [sup-talk] Sup won't save state
Date: Sat, 13 Jun 2009 21:37:13 -0700 [thread overview]
Message-ID: <1244954212-sup-8783@andariel> (raw)
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
next reply other threads:[~2009-06-14 4:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 4:37 Arvid Picciani [this message]
2009-06-15 0:51 ` Arvid Picciani
2009-06-14 20:35 ` Andrei Thorp
2009-06-15 13:42 ` William Morgan
2009-06-15 13:37 ` William Morgan
2009-06-15 15:20 ` Andrei Thorp
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=1244954212-sup-8783@andariel \
--to=aep@exys.org \
/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