"=20

make | pre

find_name=3D"grep 'NAME=3D' ./makefile | cut -c 6- "
cmd=3D `eval $find_name | awk '{print "./"$0}'`
$cmd

echo "
"
>
> make | pre
>
> find_name=3D"grep 'NAME=3D' ./makefile | cut -c 6- "
> cmd=3D `eval $find_name | awk '{print "./"$0}'`
> $cmd
>
> echo "
" 
> 
> make | pre
> 
> find_name="grep 'NAME=' ./makefile | cut -c 6- "
> cmd= `eval $find_name | awk '{print "./"$0}'`
> $cmd
> 
> echo "
 tags, since these
explicitly *prevent* output from appearing in real time. 

If that works, then you may notice that you're losing the formatting
advantage of using . You can work around this, and keep the ,
by appending 
 tags to each line as it appears, but to do that you're
probably going to need to pipe your output through something else.

For example, what I do (since Ruby is what I happen to use) is wrap the
call to my script in a Ruby script which redirects stdout to pass thru
my own class. Here are some relevant excerpts:

require "#{ENV["TM_SUPPORT_PATH"]}/lib/web_preview.rb"
require "#{ENV["TM_SUPPORT_PATH"]}/lib/escape.rb"

    def write(s)
      s = htmlize(s, :no_newline_after_br => true)
      @old_stdout.print s
    end

So, what happens is as output occurs it is passed to me, because I am
substituting myself for stdout. (Heh heh.) Meanwhile the real stdout has
been saved as @old_stdout. So my write() is called (because I appear to
be stdout), I fix up the output with a 
 using TextMate's built-in
htmlize(), and then pass the line on out to the real stdout, thus
causing it to appear in TextMate's output window, in real time.

So you might be able to set up a pipe that does something similar. There
are buffering issues, of course, which are too elaborate to discuss
here... :)

m.

-- 
matt neuburg, phd = matt(a)tidbits.com 
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
http://www.tidbits.com/matt/default.html#applescriptthings

--===============7030549441600651957==--