From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <775b8d190602100557n484b953ewb718217bdc5611e4@mail.gmail.com>
Date: Sat, 11 Feb 2006 00:57:48 +1100
From: Bruce Ellis <bruce.ellis@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] More 'Sam I am'
In-Reply-To: <d8a2a1d3ad5e2d6cc4afab64f0e3326c@quanstro.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <d8a2a1d3ad5e2d6cc4afab64f0e3326c@quanstro.net>
Topicbox-Message-UUID: f953c5f0-ead0-11e9-9d60-3106f5b1d025

X w
or
X/'/w

will suffice
brucee

On 2/11/06, quanstro@quanstro.net <quanstro@quanstro.net> wrote:
> i'm replying to the wrong message. but to answer the original problem,
> you /can/ script sam -d like this:
>
>        {
>                echo $script
>                echo X:'''':w
>                echo q
>        } | sam -d $filelist
>
> On 2/10/06, Aharon Robbins <arnold@skeeve.com> wrote:
> > In article <20060208212850.GK1620@augusta.math.psu.edu> you write:
> > >On Wed, Feb 08, 2006 at 10:14:53AM -0800, Lyndon Nerenberg wrote:
> > >> The problem with this is the data I want is interspersed with data t=
hat
> > >> I don't want.  And the bits I don't want are variable length
> > >> inconsistent multi-line text that is a bitch to filter out of the
> > >> rendered output stream.  It turns out that sam (against the raw HTML=
)
> > >> was the only tool that was able to do the job.  I just wish I could =
wrap
> > >> it in a shell script that I could throw at the directory containing =
all
> > >> the .html files.
> > >
>