[9fans] Acme, dump, and $HOME

[9fans] Acme, dump, and $HOME

[Paul Lalonde]

[-- Attachment #1: Type: text/plain, Size: 634 bytes --]

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?

Paul

[-- Attachment #2: Type: text/html, Size: 735 bytes --]

Re: [9fans] Acme, dump, and $HOME

[dexen deVries]

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

[[[↓][→]]]

Re: [9fans] Acme, dump, and $HOME

[Charles Forsyth]

[-- Attachment #1: Type: text/plain, Size: 269 bytes --]

On 13 January 2014 16:42, Paul Lalonde <paul.a.lalonde@gmail.com> wrote:

> Can anyone explain to me the rationale of Dump dropping acme.dump in $HOME
> instead of $PWD?


alternatively, if started with acme -l dumpfile, why not write it back to
the same file?

[-- Attachment #2: Type: text/html, Size: 558 bytes --]

Re: [9fans] Acme, dump, and $HOME

[Paul Lalonde]

[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]

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 <dexen.devries@gmail.com>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
>
> [[[↓][→]]]
>
>
>

[-- Attachment #2: Type: text/html, Size: 2053 bytes --]

Re: [9fans] Acme, dump, and $HOME

[Paul Lalonde]

[-- Attachment #1: Type: text/plain, Size: 597 bytes --]

That seems even more magical, I think.

I've been running with Dump's $HOME lookup changed to $PWD for a few days
now with nary a glitch.
Unless someone tells me otherwise I'll start pushing for a patch :-)

Paul


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

>
> On 13 January 2014 16:42, Paul Lalonde <paul.a.lalonde@gmail.com> wrote:
>
>> Can anyone explain to me the rationale of Dump dropping acme.dump in
>> $HOME instead of $PWD?
>
>
> alternatively, if started with acme -l dumpfile, why not write it back to
> the same file?
>

[-- Attachment #2: Type: text/html, Size: 1261 bytes --]

Re: [9fans] Acme, dump, and $HOME

[Bence Fábián]

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

Because this way there is one default dump file.
Maybe it should be $home/lib/acme.dump
But when i turn on my terminal it runs acme -l $home/acme.dump
automatically. And before i turn it off i just press dump.
If I need to preserve a state for longer i can do
Dump otherfile. For me this seems the saner behaviour.

tl;dr I'm against your patch, sorry


2014/1/13 Paul Lalonde <paul.a.lalonde@gmail.com>

> That seems even more magical, I think.
>
> I've been running with Dump's $HOME lookup changed to $PWD for a few days
> now with nary a glitch.
> Unless someone tells me otherwise I'll start pushing for a patch :-)
>
> Paul
>
>
> On Mon, Jan 13, 2014 at 8:57 AM, Charles Forsyth <
> charles.forsyth@gmail.com> wrote:
>
>>
>> On 13 January 2014 16:42, Paul Lalonde <paul.a.lalonde@gmail.com> wrote:
>>
>>> Can anyone explain to me the rationale of Dump dropping acme.dump in
>>> $HOME instead of $PWD?
>>
>>
>> alternatively, if started with acme -l dumpfile, why not write it back to
>> the same file?
>>
>
>

[-- Attachment #2: Type: text/html, Size: 2105 bytes --]

Re: [9fans] Acme, dump, and $HOME

[Paul Lalonde]

[-- Attachment #1: Type: text/plain, Size: 1308 bytes --]

Your described behaviour is unaffected by the patch unless you are running
acme (automatically) from another directory.

Paul


On Mon, Jan 13, 2014 at 10:53 AM, Bence Fábián <begnoc@gmail.com> wrote:

> Because this way there is one default dump file.
> Maybe it should be $home/lib/acme.dump
> But when i turn on my terminal it runs acme -l $home/acme.dump
> automatically. And before i turn it off i just press dump.
> If I need to preserve a state for longer i can do
> Dump otherfile. For me this seems the saner behaviour.
>
> tl;dr I'm against your patch, sorry
>
>
> 2014/1/13 Paul Lalonde <paul.a.lalonde@gmail.com>
>
>> That seems even more magical, I think.
>>
>> I've been running with Dump's $HOME lookup changed to $PWD for a few days
>> now with nary a glitch.
>> Unless someone tells me otherwise I'll start pushing for a patch :-)
>>
>> Paul
>>
>>
>> On Mon, Jan 13, 2014 at 8:57 AM, Charles Forsyth <
>> charles.forsyth@gmail.com> wrote:
>>
>>>
>>> On 13 January 2014 16:42, Paul Lalonde <paul.a.lalonde@gmail.com> wrote:
>>>
>>>> Can anyone explain to me the rationale of Dump dropping acme.dump in
>>>> $HOME instead of $PWD?
>>>
>>>
>>> alternatively, if started with acme -l dumpfile, why not write it back
>>> to the same file?
>>>
>>
>>
>

[-- Attachment #2: Type: text/html, Size: 2650 bytes --]

Re: [9fans] Acme, dump, and $HOME

[Charles Forsyth]

[-- Attachment #1: Type: text/plain, Size: 367 bytes --]

On 13 January 2014 18:30, Paul Lalonde <paul.a.lalonde@gmail.com> 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.

[-- Attachment #2: Type: text/html, Size: 747 bytes --]

Re: [9fans] Acme, dump, and $HOME

[erik quanstrom]

> 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.

agree.

- erik

Re: [9fans] Acme, dump, and $HOME

[erik quanstrom]

>
> 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.

also if a snapshot is wanted, then we have a tool for that: cp(1).  :-)

- erik

Re: [9fans] Acme, dump, and $HOME

[Paul Lalonde]

[-- Attachment #1: Type: text/plain, Size: 596 bytes --]

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 <charles.forsyth@gmail.com
> wrote:

>
> On 13 January 2014 18:30, Paul Lalonde <paul.a.lalonde@gmail.com> 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.
>

[-- Attachment #2: Type: text/html, Size: 1305 bytes --]

Re: [9fans] Acme, dump, and $HOME

[Pete]

On 2014年01月13日 18:30, Paul Lalonde wrote:
> I've been running with Dump's $HOME lookup changed to $PWD for a few days
> now with nary a glitch.

I think using $PWD might give you a few problems.  I had written a
wrapper script around acme that bound ./acme.dump over $home/acme.dump,
and when ./ happens to be inside a remote filesystem, acme would get
upset if it suddenly became inaccessible due to flaky wifi or something,
and of course the time that you want a dump the most is when you can't
save your work by other means.

I've switched to just binding dumps from a directory in $home.  If you
want to do some guessing of the dump name or something, I don't suspect
that it'd take more than about 10 or 20 lines of rc to do it.

Re: [9fans] Acme, dump, and $HOME

[b.]

On 1/13/14, 11:57 AM, Charles Forsyth wrote:
>
> On 13 January 2014 16:42, Paul Lalonde <paul.a.lalonde@gmail.com
> <mailto:paul.a.lalonde@gmail.com>> wrote:
>
>     Can anyone explain to me the rationale of Dump dropping acme.dump in
>     $HOME instead of $PWD?
>
>
> alternatively, if started with acme -l dumpfile, why not write it back
> to the same file?

I had written a rather quick patch to do that very thing for p9p acme:

http://pastebin.com/raw.php?i=n7dZiQrS

I'm sure it could be done better, but here's the patch regardless.