From: yard-ape@telus.net
To: plan9-gsoc@googlegroups.com, 9fans@9fans.net
Subject: [9fans] Sed label handling inconsistency
Date: Tue, 8 Jun 2010 11:06:30 -0700 [thread overview]
Message-ID: <4c0e86a6.p9p6O5x091i4Q2WY%yard-ape@telus.net> (raw)
In-Reply-To: <146c961677a8e3b29413b0c39668652f@swcp.com>
P9P sed gives me the error "Label too long" on:
% echo foo | sed 's/./&/;ta;b;:a;s//*/'
but not on:
% echo foo | sed 's/./&/
ta
b
:a
s//*/'
As though the label commands require immediate newlines.
Anyone else experience this?
next prev parent reply other threads:[~2010-06-08 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3717d8ce779c6f31d7e5c922eb34f00c@swcp.com>
2010-06-08 6:22 ` [9fans] request for testers of next beta release of tvx EBo
2010-06-08 13:10 ` ron minnich
2010-06-08 14:01 ` Skip Tavakkolian
2010-06-08 15:22 ` EBo
2010-06-08 16:39 ` Lucio De Re
2010-06-09 4:10 ` ron minnich
2010-06-09 4:37 ` Lucio De Re
2010-06-08 18:06 ` yard-ape [this message]
2010-06-08 20:29 ` [9fans] Sed label handling inconsistency erik quanstrom
2010-06-08 20:33 ` erik quanstrom
2010-06-08 22:30 ` yard-ape
2010-06-08 22:36 ` erik quanstrom
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=4c0e86a6.p9p6O5x091i4Q2WY%yard-ape@telus.net \
--to=yard-ape@telus.net \
--cc=9fans@9fans.net \
--cc=plan9-gsoc@googlegroups.com \
/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).