From: "James A. Robinson" <jim.robinson@gmail.com>
To: "9fans@9fans.net" <9fans@9fans.net>
Subject: [9fans] Edit X// and with a pipe in plan9port?
Date: Wed, 28 Jun 2017 17:14:56 +0000 [thread overview]
Message-ID: <CAPd04b64L2US9nMhr6RsxY75sR7_D2S48ESeY=EMBDf6azn=Pw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
So let's say I have an Edit line
Edit ,x,(^//.+\n)+(const|func|type|var) , x,^(// [^ \t].*\n|//\n)+,|sed
's:^//::'|fmt|sed 's:^://:'
that I can use in a tag to reformat comments in a body. I noticed that
while it's possible to run an Edit with an X from a separate body if I use
Acme's sam commands:
Edit X/.go$/ ,x,(^//.+\n)+(const|func|type|var) , x,^(// [^
\t].*\n|//\n)+,p
an attempt to run the pipe command via an X:
Edit X/.go$/ ,x,(^//.+\n)+(const|func|type|var) , x,^(// [^
\t].*\n|//\n)+,|sed 's:^//::'|fmt|sed 's:^://:'
will crash acme:
$ /usr/local/plan9/bin/acme
/usr/local/plan9/bin/acme: qunlock pc=0x7fbc98900002 owner=0 self=108727000
oops
Abort trap: 6
Anyone ever look into this?
Jim
[-- Attachment #2: Type: text/html, Size: 1143 bytes --]
reply other threads:[~2017-06-28 17:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAPd04b64L2US9nMhr6RsxY75sR7_D2S48ESeY=EMBDf6azn=Pw@mail.gmail.com' \
--to=jim.robinson@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).