🚀 go-pugleaf

In article <Bxpxov.7Hx@chinet.chi.il.us: les@chinet.chi.il.us (Leslie Mikesell) writes:
:In article <1992Nov13.195845.26399@chpc.utexas.edu> michael@chpc.utexas.edu (Michael Lemke) writes:
:>>This could give you problems with lining up columns.
:>>An easier way is to pipe the paragraph through awk:
:>>	!} awk '{ printf "\%10s\%10s\%20s\n", $3, $2, $1}'
:>>    or  :10,14 ! awk '{ printf "\%10s\%10s\%20s\n", $3, $2, $1}'
:>Oh boy!  And this you call a screen editor?  (That was what started the 
:>thread).
:Don't forget that this is absolutely the most powerful method any editor
:can provide since it doesn't demand the author to anticipate what you
:are going to need.  You can put the input to *any* program in your
:edit buffer and filter it through the program to get the output.

I would say that the real most powerful ability in an editor is the ability
to write REAL macro programs to do things the authors never thought of.  Another
useful ability is the ability to call the editor as a subroutine, send it
commands, and get return data back. IBM's XEDIT, Univac's EDT, EIES1 +sp,
and GNU emacs are examples of what I consider to have these capabilities.

Note: I do not consider vi's :map facility to be real macros, unless one can
program in if/then/else and while/do loops in something that does not look
too much like line tranmission noise.

-- 
Kenneth Ng
AT&T vs BSDI lawsuit: The Ethnic Cleansing of the computer world.
This signature is *NOT* the intellectual property of USL.