9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "James A. Robinson" <jimr@highwire.stanford.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] 9p write event to Acme?
Date: Wed, 28 Aug 2013 23:47:46 -0700	[thread overview]
Message-ID: <CAPd04b4=m72f_s8BVuAtjFsXVWOgu-LftuNMZdfzqCZJhH4PfA@mail.gmail.com> (raw)

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

[argh, I posted this to the google group though I know that it won't show
up...]

Folks,

I'm interested in writing some Acme commands to simulate
execution of certain built-in commands.  For example, I would
like to be able to simulate the user 2-1 chording on an Edit
command in the tag.

Is my understanding correct if I am thinking that this would
consist of a single event

c0: M
c1: x
flag ^= 8
nb: 4
nr: 4
text: Edit
arg: ...

where ... represents the argument passed to Edit?
Or would this consist of two events, with text set
to Edit and then to the command to pass in?

It's not clear to me if I also have muck with q0, q1,
oq0, oq1 or loc.  I was guessing that only people
reading an event would be interested in those.

I looked around to see if I could find examples of
programs sending events to acme via 9p, but I haven't
managed to find them.  I see several examples of
scripts calling something named winwriteevent, and
the man page for that sounds promising, but I don't
see it as part of plan9port, and I was guessing that
people might use 9p write to acme/$winid/event
instead, or write Go/C program using the acme api
libraries that Russ provided?

Jim

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

             reply	other threads:[~2013-08-29  6:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29  6:47 James A. Robinson [this message]
2013-08-30 12:41 ` James A. Robinson

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='CAPd04b4=m72f_s8BVuAtjFsXVWOgu-LftuNMZdfzqCZJhH4PfA@mail.gmail.com' \
    --to=jimr@highwire.stanford.edu \
    --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).