From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <d50d7d460908070634x33c7f954r2b71110fbcfe0295@mail.gmail.com>
References: <op.ux68vceu0p3ku8@localhost>
	<C859E54C-57ED-4CA4-B3E5-0812888D843D@storytotell.org>
	<d50d7d460908070634x33c7f954r2b71110fbcfe0295@mail.gmail.com>
Date: Fri,  7 Aug 2009 15:50:10 +0200
Message-ID: <56a297000908070650k458d7044p3ed07266c36ec9dc@mail.gmail.com>
From: Noah Evans <noah.evans@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] Acme Configuration
Topicbox-Message-UUID: 3d0c4d72-ead5-11e9-9d60-3106f5b1d025

Aaron's problem is not dumping per se, it's saving his indentation and
other command line state between sessions. Unless there's something I
missed, you can only enable functions like auto-indent via the command
line(-a) or via "Indent on" in acme. The dump doesn't preserve indent
state so yes, Aaron needs a script.

Noah

On Fri, Aug 7, 2009 at 3:34 PM, Jason Catena<jason.catena@gmail.com> wrote:
> I keep many dump files around with different names, to easily suspend,
> switch, and resume acme configurations depending on what I need to
> work on. =A0This significantly reduces my context switch time, over and
> above the advantage I get from guide files keeping me from
> (mis)retyping commands.
>
> in acme: highlight and execute "Dump /home/me/dump/whatever"
> in shell: rum "acme -l /home/me/dump/whatever"
>
> Jason Catena
>
>