From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] acme automatic dump
Date: Wed, 12 Jun 2013 10:33:47 +0100 [thread overview]
Message-ID: <CAJhgaci8EN2iqggYd9y4fHcnn+13Wft_NX3id4E9Vx1ARkv1cw@mail.gmail.com> (raw)
My laptop has been a bit flaky recently
which has brought this issue to the fore for me
(nothing like a few hours' lost work to prompt
some action!)
If my computer crashes, it would be great
if I didn't lose all my unsaved work in acme.
I'm thinking of adding some way to automatically
executing a Dump on a periodic basis.
I can think of at least two approaches:
1) implement the functionality inside acme itself
(e.g. with a command-line flag)
2) implement a way of triggering a dump through
the fs interface (e.g. by adding a root-level ctl
file and allowing a "dump" message).
The second is probably less work, but is harder
to get just right (you'd probably want a way to
check if anything has changed too, to avoid
needless churn when acme's sitting idle).
Has anyone already done something like this?
Any strong thoughts on which of the above
approaches is preferable, if any?
next reply other threads:[~2013-06-12 9:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 9:33 roger peppe [this message]
2013-06-13 13:16 ` erik quanstrom
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=CAJhgaci8EN2iqggYd9y4fHcnn+13Wft_NX3id4E9Vx1ARkv1cw@mail.gmail.com \
--to=rogpeppe@gmail.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).