From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 13 Jan 2014 11:36:26 -0800 Message-ID: From: Paul Lalonde To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a113687aa14bafb04efdf3195 Subject: Re: [9fans] Acme, dump, and $HOME Topicbox-Message-UUID: b2b38ee8-ead8-11e9-9d60-3106f5b1d025 --001a113687aa14bafb04efdf3195 Content-Type: text/plain; charset=ISO-8859-1 It certainly addresses my use case. I'll give it a spin when I next have 5 minutes to mess with it. Paul On Mon, Jan 13, 2014 at 11:17 AM, Charles Forsyth wrote: > > On 13 January 2014 18:30, Paul Lalonde wrote: > >> That seems even more magical, I think. >> > > The idea is that the dump file is a snapshot of a particular state, and it > made sense to me to update > the given state, instead of putting it back in the default file despite > being given an explicit state. > That seemed to me a bit contrary. > --001a113687aa14bafb04efdf3195 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
It certainly addresses my use case. =A0I'll give it a = spin when I next have 5 minutes to mess with it.

Paul


= On Mon, Jan 13, 2014 at 11:17 AM, Charles Forsyth <charles.forsyth= @gmail.com> wrote:
=

On 13 January 2014 18:30, = Paul Lalonde <paul.a.lalonde@gmail.com> wrote:
That seems even more magica= l, I think.

The idea is that t= he dump file is a snapshot of a particular state, and it made sense to me t= o update
the given state, instead of putting it back in t= he default file despite being given an explicit state.
That seemed to me a bit contrary.

--001a113687aa14bafb04efdf3195--