From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Sup won't save state
Date: Mon, 15 Jun 2009 06:42:04 -0700 [thread overview]
Message-ID: <1245073093-sup-5388@entry> (raw)
In-Reply-To: <1245026779-sup-3938@andariel>
Reformatted excerpts from Arvid Picciani's message of 2009-06-14:
> "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,
> 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.
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>
next prev parent reply other threads:[~2009-06-15 13:42 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
2009-06-14 20:35 ` Andrei Thorp
2009-06-15 13:42 ` William Morgan [this message]
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=1245073093-sup-5388@entry \
--to=wmorgan-sup@masanjin.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