From: dexen deVries <dexen.devries@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 08:49:01 -0800 [thread overview]
Message-ID: <2079086.GNhTW0d2yA@coil> (raw)
In-Reply-To: <CA+POUViCqK2f7TS-_5QOuNCtcUdeo5OEqRznbHu7XoN3kf5XaA@mail.gmail.com>
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
[[[↓][→]]]
next prev parent reply other threads:[~2014-01-13 16:49 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 [this message]
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
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=2079086.GNhTW0d2yA@coil \
--to=dexen.devries@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).