9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] sam: ?changes not in sequence
Date: Tue,  7 Feb 2006 16:07:01 -0800	[thread overview]
Message-ID: <7359f0490602071607i3952ccdej9294dc1992ed6708@mail.gmail.com> (raw)
In-Reply-To: <43E934CD.8090002@orthanc.ca>

delete the space after the x.  it's a feature, not a bug, that
x without a delimeter means 'break into lines'.  thus
  x /pat/
and
  x/pat/
mean very different things.

-rob

On 2/7/06, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
> Given an input stream containing:
>
>          <td>Creating XML-RPC client...</td>
>        <td align="right">0.0001</td>
>              <td>Creating XML-RPC client...</td>
>        <td align="right">0.0001</td>
>              <td>Creating XML-RPC client...</td>
>        <td align="right">0.0001</td>
>              <td>Creating XML-RPC client...</td>
>        <td align="right">0.0001</td>
>              <td>Creating XML-RPC client...</td>
>        <td align="right">0.0001</td>
>
> Should not the sam command:
>
>         , x /^.*Creating.+\n/ d
>
> delete lines 1,3,5,7 and 9?  Or have I lost my mind (again).  Instead of
> deleting the lines, sam spits out the "?changes not in sequence" error.
>
> n.b.  This is Plan 9 from User Space sam (on FreeBSD 6.almost1).
>
> --lyndon
>


  reply	other threads:[~2006-02-08  0:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08  0:01 Lyndon Nerenberg
2006-02-08  0:07 ` Rob Pike [this message]
2006-02-08  0:20   ` Lyndon Nerenberg
2006-02-08  0:08 ` Russ Cox

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=7359f0490602071607i3952ccdej9294dc1992ed6708@mail.gmail.com \
    --to=robpike@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).