9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: yy <yiyu.jgl@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] acme: send dot to the stdin of a more complicated command
Date: Mon,  8 Jun 2009 19:42:39 +0200	[thread overview]
Message-ID: <a81fe9be0906081042o7193daaev21135daf52bf4915@mail.gmail.com> (raw)
In-Reply-To: <a560a5d00906081030p6f8cf1f0g89206258d502df67@mail.gmail.com>

2009/6/8 Rudolf Sykora <rudolf.sykora@gmail.com>:
> The very question for me now is: why it behaves how it behaves, i.e
> why newlines (if it's them) are problematic.
>
> Ruda
>

They are the only way Edit has to separate commands. You will notice
that you cannot use something like i/A/a/W/ (or i/A/;a/W/, for
example). However, you can chord something like
i/A/
a/W/
When you chord your example, acme calls rc with: rc -c 'awk '', so it
does not work. rc is who interprets those multiple-line commands. You
could use rc functions if that makes you feel better than with plain
files, just remember to prepend the function name with a semi-colon,
to force rc to interpret the command. At least that is how I remember
it, please somebody correct me if I am wrong.


--
- yiyus || JGL .



  parent reply	other threads:[~2009-06-08 17:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08 12:48 Rudolf Sykora
2009-06-08 16:04 ` Lyndon Nerenberg
2009-06-08 16:34   ` Rudolf Sykora
2009-06-08 16:58     ` andrey mirtchovski
2009-06-08 17:30       ` Rudolf Sykora
2009-06-08 17:35         ` andrey mirtchovski
2009-06-08 17:45           ` Rudolf Sykora
2009-06-08 17:42         ` yy [this message]
2009-06-08 18:15         ` Russ Cox
2009-06-08 18:35           ` Dan Cross
2009-06-08 18:59           ` [9fans] acme: send dot to the stdin of a more complicated Skip Tavakkolian
2009-06-09  8:28           ` [9fans] acme: send dot to the stdin of a more complicated command Rudolf Sykora
2013-08-28  8:05           ` Rudolf Sykora
2013-08-28 12:13             ` dexen deVries
2013-08-28 12:53               ` Rudolf Sykora
2013-08-28 15:11               ` 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=a81fe9be0906081042o7193daaev21135daf52bf4915@mail.gmail.com \
    --to=yiyu.jgl@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).