From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) From: Jeff Sickel In-Reply-To: Date: Fri, 18 Jan 2013 11:20:41 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <150ABDE6-F5AE-4C0E-98D5-80CE3C969C12@corpus-callosum.com> References: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] using acid Topicbox-Message-UUID: 0b7a102a-ead8-11e9-9d60-3106f5b1d025 Someone made a recording of Russ' talk about acid at the 2nd IWP9, see http://mirror.cat-v.org/iwp9/2007/videos/ Acid-Trips.mov. It = unfortunately cuts out before the end. You can follow along = http://swtch.com/~rsc/talks/acid07/ That might not help answer your question, but it may give some = additional insights and techniques to get to what you're wanting. -jas On Jan 18, 2013, at 8:59 AM, Rudolf Sykora = wrote: > Hello, >=20 > is there any document, besides the two papers by P. Winterbottom > (Acid Manual, Acid: A Debugger Built =46rom a Language) > showing a practical use of acid? >=20 > I wonder if I could use it for watching acme during its running. >=20 > [I wanted to change acme so that it could understand environment > variables --- such as $home --- when doing completion after pressing > ctrl-f or ins. However, when I tried to read the source, I found = structures > with elements whose meaning is not documented. > Thus I'd like to run acme and watch and guess what they are for. > But to this end I'd like to see some examples of how to use acid. > I have never done anything like this before; I even don't know if it's = viable.] >=20 > Thanks for any comments. > Ruda >=20