From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <2079086.GNhTW0d2yA@coil> References: <2079086.GNhTW0d2yA@coil> Date: Mon, 13 Jan 2014 10:29:00 -0800 Message-ID: From: Paul Lalonde To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7b2e4c02ea8aa704efde3f6f Subject: Re: [9fans] Acme, dump, and $HOME Topicbox-Message-UUID: b26d10bc-ead8-11e9-9d60-3106f5b1d025 --047d7b2e4c02ea8aa704efde3f6f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yes, I understand the current behaviour. I don't understand why $home was privileged this way, instead of the startup directory. So for instance, if I drop the dump filename in the top-level tag, and chord it against dump, I get the right thing - it's deposited in the directory where acme was started. I just don't understand why "acme.dump" should go to $home by default, when everything else in the editor is relative to the window directory. On Mon, Jan 13, 2014 at 8:49 AM, dexen deVries wro= te: > 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 i= n > > $HOME instead of where acme is called from. > > My use case is this: I'm working on two projects, and so want to mainta= in > > two long-term "sessions". Dump does most of what I need when I move fr= om > > 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 > $home/acme.dump by default. > > > i.e., Dump takes one optional argument: file pathname. > > > -- > dexen deVries > > [[[=E2=86=93][=E2=86=92]]] > > > --047d7b2e4c02ea8aa704efde3f6f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Yes, I understand the current behaviour. =C2=A0I don't= understand why $home was privileged this way, instead of the startup direc= tory. =C2=A0So for instance, if I drop the dump filename in the top-level t= ag, and chord it against dump, I get the right thing - it's deposited i= n the directory where acme was started. =C2=A0I just don't understand w= hy "acme.dump" should go to $home by default, when everything els= e in the editor is relative to the window directory.


On Mon, Jan 1= 3, 2014 at 8:49 AM, dexen deVries <dexen.devries@gmail.com> wrote:
On M= onday 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 m= aintain
> two long-term "sessions". =C2=A0Dump does most of what I nee= d when I move from
> one to the other, but if I don't chord in the project root directo= ry 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
$home/acme.dump by default.


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


--
dexen deVries

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



--047d7b2e4c02ea8aa704efde3f6f--