From: Paul Lalonde <paul.a.lalonde@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme, dump, and $HOME
Date: Mon, 13 Jan 2014 11:01:07 -0800 [thread overview]
Message-ID: <CA+POUVjt+0cgdrK8-JwPks5_ACprEJ8GbHsZ8fHDQAqG4kZ8eA@mail.gmail.com> (raw)
In-Reply-To: <CAOCRf5UPzXWv=8uWQ8ChAu_1pS6XPDxB8F8n-v8ooz02CVJLNA@mail.gmail.com>
[-- 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 --]
next prev parent reply other threads:[~2014-01-13 19:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 16:42 Paul Lalonde
2014-01-13 16:49 ` dexen deVries
2014-01-13 18:29 ` Paul Lalonde
2014-01-13 16:57 ` Charles Forsyth
2014-01-13 18:30 ` Paul Lalonde
2014-01-13 18:53 ` Bence Fábián
2014-01-13 19:01 ` Paul Lalonde [this message]
2014-01-13 19:17 ` Charles Forsyth
2014-01-13 19:18 ` erik quanstrom
2014-01-13 19:19 ` erik quanstrom
2014-01-13 19:36 ` Paul Lalonde
2014-01-13 21:39 ` Pete
2014-01-16 5:39 ` b.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+POUVjt+0cgdrK8-JwPks5_ACprEJ8GbHsZ8fHDQAqG4kZ8eA@mail.gmail.com \
--to=paul.a.lalonde@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).