From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Thu, 13 Jun 2013 09:16:51 -0400 To: 9fans@9fans.net Message-ID: <1ee7ead923ea1a151a681f9a746032f1@kw.quanstro.net> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] acme automatic dump Topicbox-Message-UUID: 65c97c96-ead8-11e9-9d60-3106f5b1d025 > 1) implement the functionality inside acme itself > (e.g. with a command-line flag) >=20 > 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). >=20 > 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). if acme simply set a bit on dump "cleansincedump" and cleared that bit on any edit, then a conditional dump if not clean would prevent any churn, and seems like it could be pretty straightforward. it would also solve one of my pet peeves=E2=80=94having to confirm quitting acme right after a dump because there are "changed files". - erik