From: aep@exys.org (Arvid Picciani)
Subject: [sup-talk] Sup won't save state
Date: Sun, 14 Jun 2009 17:51:18 -0700 [thread overview]
Message-ID: <1245026779-sup-3938@andariel> (raw)
In-Reply-To: <1244954212-sup-8783@andariel>
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 :)
next prev parent reply other threads:[~2009-06-15 0:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 4:37 Arvid Picciani
2009-06-15 0:51 ` Arvid Picciani [this message]
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=1245026779-sup-3938@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