From mboxrd@z Thu Jan  1 00:00:00 1970
From: dexen deVries <dexen.devries@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Date: Mon, 13 Jan 2014 08:49:01 -0800
Message-ID: <2079086.GNhTW0d2yA@coil>
User-Agent: KMail/4.10.5 (Linux/3.13.0-rc8-l57; KDE/4.10.5; x86_64; ; )
In-Reply-To: <CA+POUViCqK2f7TS-_5QOuNCtcUdeo5OEqRznbHu7XoN3kf5XaA@mail.gmail.com>
References: <CA+POUViCqK2f7TS-_5QOuNCtcUdeo5OEqRznbHu7XoN3kf5XaA@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
Subject: Re: [9fans] Acme, dump, and $HOME
Topicbox-Message-UUID: b258e6c8-ead8-11e9-9d60-3106f5b1d025

On Monday 13 of January 2014 08:42:22 Paul Lalonde wrote:
> Can anyone explain to me the rationale of Dump dropping acme.dump in =
$HOME
> instead of $PWD?
> I know I can pass it a different filename, but it seems odd to put it=
 in
> $HOME instead of where acme is called from.
> My use case is this: I'm working on two projects, and so want to main=
tain
> two long-term "sessions".  Dump does most of what I need when I move =
from
> one to the other, but if I don't chord in the project root directory =
to
> save the dump to, I kill my other project session.
> A one line change to looking at $PWD instead of $HOME makes acme much=
 more
> useful for my case, but am I missing an important other use?


from acme(1):

Dump Write the state of acme to the file name, if specified, or=20
$home/acme.dump by default.


i.e., Dump takes one optional argument: file pathname.


--=20
dexen deVries

[[[=E2=86=93][=E2=86=92]]]