9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rick Hohensee <humbubba@smarty.smart.net>
To: 9fans@cse.psu.edu
Subject: [9fans] h is for help in tp
Date: Tue, 14 Aug 2001 13:02:33 -0400	[thread overview]
Message-ID: <200108141702.NAA05037@smarty.smart.net> (raw)
In-Reply-To: <3B73F61E.F60C9811@null.net> from "Douglas A. Gwyn" at Aug 14, 2001 09:44:23 AM

I just have the command language of sam in cLIeNUX, since I don't use X. I
also call sam tp for "text processor". In view of someone whining about
the user interface, allow me to re-post my cheatsheet. In cLIeNUX tp
(sam) this comes up when you hit h. If there's further interest I'll post
the code to do that, which is trivial.


h

____________________________________________________________________________
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
					www.clienux.com


  reply	other threads:[~2001-08-14 17:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08 10:45 [9fans] ls -R rog
2001-08-08 17:08 ` [9fans] Sam question gene garbutt
2001-08-14  9:44   ` Douglas A. Gwyn
2001-08-14 17:02     ` Rick Hohensee [this message]
2001-08-16 21:07     ` Boyd Roberts
2001-08-17  8:50       ` Douglas A. Gwyn
2001-08-17 10:27         ` Re[2]: " Matt
2001-08-17 12:14         ` Boyd Roberts
2001-08-17 12:35           ` Re[2]: " Matt
2001-08-20  8:56           ` Douglas A. Gwyn
2001-08-20 11:11             ` Boyd Roberts
2001-08-20 16:25             ` Sam Ducksworth
2001-08-20 15:11               ` Boyd Roberts
2001-08-21  8:37                 ` Ozan Yigit
2001-08-21  9:31                   ` Boyd Roberts
2001-08-22  2:52                     ` Donald Brownlee
2001-08-17 10:22       ` Re[2]: " Matt

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=200108141702.NAA05037@smarty.smart.net \
    --to=humbubba@smarty.smart.net \
    --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).