From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] using acid
Date: Fri, 18 Jan 2013 15:59:30 +0100 [thread overview]
Message-ID: <CAOEdRO28uBOtedKkexXsbg=gOg7zALnw3-tOMYucUMS3qxv+uA@mail.gmail.com> (raw)
Hello,
is there any document, besides the two papers by P. Winterbottom
(Acid Manual, Acid: A Debugger Built From a Language)
showing a practical use of acid?
I wonder if I could use it for watching acme during its running.
[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.]
Thanks for any comments.
Ruda
next reply other threads:[~2013-01-18 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 14:59 Rudolf Sykora [this message]
2013-01-18 17:09 ` erik quanstrom
2013-01-18 17:20 ` Jeff Sickel
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='CAOEdRO28uBOtedKkexXsbg=gOg7zALnw3-tOMYucUMS3qxv+uA@mail.gmail.com' \
--to=rudolf.sykora@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).