9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tharaneedharan Vilwanathan <vdharani@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] acme/acid integration ...
Date: Thu, 29 Dec 2011 21:41:11 -0800	[thread overview]
Message-ID: <CAN-HoCn9uR19Y_vWArSo6=85pihyCO5H-EtUYUdfUG+JsRi3Bw@mail.gmail.com> (raw)
In-Reply-To: <24868-1325219644-887798@sneakemail.com>

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

Hi,

If I am right, this thought is presented somewhere at the end of acid (or
acme?) paper. I asked Phil about this in a meeting. I remember he said he
was not convinced about acme being acid's front end.

Someone may know more/better.

That apart, I think it is not too difficult to get the basic things
working. IMHO, acme's simplicity comes as a hinder after some point for
anything grand. I have tried acme as front end for some of my tasks. Also,
I would like to point that I love acme and I have used it aggressively.

Regards
dharani

On Thu, Dec 29, 2011 at 8:34 PM, <6o205zd02@sneakemail.com> wrote:

> I could swear I remember reading about someone writing some tools that
> made it possible to use acme as a "gui" for acid, but my searches haven't
> come up with anything concrete.  I was thinking about trying to do
> something analogous for a different debugger in P9P, and as hoping I could
> get some insights into how to begin by looking at the acme/acid work.
>
> Is my memory completely fabricated?  If not, does anyone know where I can
> find the code?
>
>    thanks,
>    Peter Canning
>
>

[-- Attachment #2: Type: text/html, Size: 1497 bytes --]

      reply	other threads:[~2011-12-30  5:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-30  4:34 6o205zd02
2011-12-30  5:41 ` Tharaneedharan Vilwanathan [this message]

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='CAN-HoCn9uR19Y_vWArSo6=85pihyCO5H-EtUYUdfUG+JsRi3Bw@mail.gmail.com' \
    --to=vdharani@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).