From: markus schnalke <meillo@marmaro.de>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Duff's rc paper: Why awk?
Date: Tue, 11 Jun 2013 17:38:56 +0200 [thread overview]
Message-ID: <1UmQeu-5gW-00@marmaro.de> (raw)
In-Reply-To: <CAOEdRO3tZkPzrxNeQVW0yxBZKFr0vxCMoY5SAPnrBGnQMjEVWQ@mail.gmail.com>
[2013-06-11 14:24] Rudolf Sykora <rudolf.sykora@gmail.com>
> > plan 9 sed reads a second line before quitting (note the "def" in the example
> > below); sed does not work.
Erik, thanks for the explanation.
However, the man page states:
q Quit. Branch to the end of the script. Do not start a new cycle.
Thus, this is a bit odd.
> Is there any good reason for this difference between plan9 and gnu behaviour?
It looks a bit like the bug described in the man page, although input is read
from the terminal, not from a pipe.
http://plan9.bell-labs.com/magic/man2html/1/sed
meillo
prev parent reply other threads:[~2013-06-11 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 13:02 markus schnalke
2013-06-07 13:18 ` erik quanstrom
2013-06-11 12:24 ` Rudolf Sykora
2013-06-11 15:38 ` markus schnalke [this message]
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=1UmQeu-5gW-00@marmaro.de \
--to=meillo@marmaro.de \
--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).