Re: [9fans] scripting sam

[cLIeNUX user <r@your_host.com>]

anothy@cosym.net... 
>//plan 9 has been around for nearly 10 years.  all this
>//'why can't i have my favourite toy on it?' mail is a
>//bit much.
>
>and i've been at least a casual user for almost half of
>that. how is asking about sam "why can't i have my favorite
>toy"? i was asking how to better use the tools Plan 9
>provides. yeah, you can write telnet with echo and cat; how
>exactly is that relavant to the issue at hand again? i'm
>well aware of the power of the system... which is exactly
>why i was asking how to use it, and the tools it provides,
>better, rather than sticking with sed (which can do what i
>want, but i'd need to use the hold spaces, which are ugly).
>
>much thanks to everyone who responded helpfully.
>-.




h is for help. In cLIeNUX sam. Easy hack, BTW.


____________________________________________________________________________
cLIeNUX sam/tp text processing language cheatsheet
cheatsheet markup...
  refNAME  `default'  "virtual"  /delimited/  0_or_more...  <variable>

syntax operators                (in commands, not patterns or strings)
  delimiter                     any punctuation, paired or with EOL
  next character is literal     \

text location operators         (address elements)
  linefeed (unix newline)       \n
  "empty line" at End Of File   $
  current text segment          .
  MARKed text segment           '
  scanning DIRection            - or `+'
  Line Number                   <digits>
  Character Number              #<digits>
  match scan PATtern            /regular expression, \n allowed/
  OFFset                        <DIR>LN or CN or PAT or `1'
  HALF address                  <LN or CN or PAT or MARK or `.'><OFF...>
  full ADDRess                  <HALF>,<HALF>    just  ,  is whole buffer

text inputs
  INTERactive                   accept typed text up to . alone on line
  Whole Match Backreference     &
  SUBmatch backreference        \<digit>    nth match ()-delimited in PAT
  LITeral string                /literal text and|or WMB... and|or SUB.../
  INPUT                         LIT or INTER

commands and thier PHRASE syntaxes, some multi-buffer phrases omitted
  <ADDR>a<INPUT>                _append_ INPUT after address
        b<buffer>               make buffer the current buffer
  <ADDR>c<INPUT>                _clobber_ address with INPUT
  <ADDR>d                       _delete_ addressed range of text
        e<file>                 _edit_ file, make file current buffer
        f<name>                 rename current buffer
  <ADDR>g<PAT> PHRASE           do PHRASE _if_ PAT matches in ADDR
        h                       You're soaking in it.
  <ADDR>i<INPUT>                _insert_ INPUT before address
  <ADDR>k                       mark address for reference as '
  <ADDR>m<ADDR>                 move, not copy
        n                       list buffers
  <ADDR>p                       _print_ to stdout. usual default command.
        q                       _quit_. Always works the second time.
  <ADDR>r<file>                 _read_ file into buffer after ADDR
  <ADDR>s<PAT><LIT>             use <ADDR>x<PAT>c<INPUT> instead
  <ADDR>t<ADDR>                 copy
        u                       undo. Unlimited, but one-way.
  <ADDR>v<PAT> PHRASE           do PHRASE if PAT _doesn't_ match in ADDR
  <ADDR>w<file>                 _write_ out ADDR. default is whole buffer.
  <ADDR>x<PAT> PHRASE           for each match of PAT in ADDR do PHRASE
  <ADDR>y<PAT> PHRASE           do PHRASE on text between each PAT in ADDR
............................................................................



Rick Hohensee
Forth, unix, nutmeg, tinsel