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 <[email protected]>wrote: > 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 maintain > > 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 > $home/acme.dump by default. > > > i.e., Dump takes one optional argument: file pathname. > > > -- > dexen deVries > > [[[↓][→]]] > > >
