9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@9fans.net
Subject: Re: [9fans] /acme/edit commands?
Date: Fri, 20 May 2016 09:46:17 -0700	[thread overview]
Message-ID: <d8afcaf140d18c841717844d495e6902@9netics.com> (raw)
In-Reply-To: <loom.20160520T000703-526@post.gmane.org>

> I had thought the /acme/edit commands (Limbo versions are included with the
> latest Inferno distribution, which also has an Acme with Edit) allow for the
> editing of files at the command line using the Sam command language
> (without having to run Acme itself), while using Edit requires loading the files
> into Acme before operating on them. Am I wrong about either of these beliefs?
> If I am correct, I like the idea of being able to use the /acme/edit commands
> in shell scripts, just as I would use sed or other commands (rather than having
> to use Acme itself, which is more complicated), and I would be interested in
> having the /acme/edit commands available on Plan 9 / plan9port for use there
> as well.

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.




  reply	other threads:[~2016-05-20 16:46 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 [this message]
2016-05-21  2:36         ` Brian Vito
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=d8afcaf140d18c841717844d495e6902@9netics.com \
    --to=9nut@9netics.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).