From: Brian Vito <bv@tuffmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] /acme/edit commands?
Date: Sat, 21 May 2016 02:36:18 +0000 [thread overview]
Message-ID: <loom.20160521T042144-152@post.gmane.org> (raw)
In-Reply-To: <d8afcaf140d18c841717844d495e6902@9netics.com>
Skip Tavakkolian <9nut <at> 9netics.com> writes:
> all the recipes in /acme/edit/guide start with 'e' command (ee.l). 'e'
> starts by looking in /mnt/acme/index for the buffer id of "file"; it
> then operates on the corresponding buffer. so the edit commands are
> meant to operate in /mnt/acme namespace (i.e. inside acme).
>
> you can use 'sam -d' for shell scripts.
>
Got it, thanks. Unfortunately sam isn't available on Inferno, so I'll have
to make do with using acme. When I get around to it, I'll work on
extracting the logic from acme/sam and write stand-alone versions
of the /acme/edit commands. What would people generally prefer,
separate commands for a, c, d, g, i, p and x, or one command that
collectively implements the sam language?
next prev parent reply other threads:[~2016-05-21 2:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 0:32 Brian Vito
2016-05-19 1:24 ` Skip Tavakkolian
2016-05-19 4:49 ` Staven
2016-05-19 10:18 ` Skip Tavakkolian
2016-05-19 22:14 ` Brian Vito
2016-05-20 16:46 ` Skip Tavakkolian
2016-05-21 2:36 ` Brian Vito [this message]
2016-05-21 3:53 ` sl
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=loom.20160521T042144-152@post.gmane.org \
--to=bv@tuffmail.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).