From harvard!talcott!panda!jpn Tue May 6 20:35:55 1986 Received: by seismo.CSS.GOV; Tue, 6 May 86 20:34:33 EDT Received: from talcott by harvard.HARVARD.EDU with UUCP; Tue, 6 May 86 20:34:22 EDT From: harvard!talcott!panda!jpn Return-Path: Received: by panda.LOCAL on Tue, 6 May 86 18:38:55 edt Date: Tue, 6 May 86 18:38:55 edt Message-Id: <8605062238.AA00896@panda.LOCAL> To: talcott!seismo!rick Status: R From: Jeff Lee Subject: Georgia Tech 'se' screen editor (Part 7 of 8) Keywords: Software Tools, Yet Another Screen Editor, Both BSD and USG Newsgroups: mod.sources Approved: jpn@panda.UUCP Mod.sources: Volume 4, Issue 88 Submitted by: Jeff Lee #! /bin/sh # This is a shell archive, meaning: # 1. Remove everything above the #! /bin/sh line. # 2. Save the resulting text in a file. # 3. Execute the file with /bin/sh (not csh) to create: # Install # Makefile # README # a # abt # ah # ah_swt # arg2 # args # b # bang # bug # c # cc # ccmisc # chardel # charins # colon # com # com_swt # comdir # comdir_swt # comsyn # d # detab.c # dir # e # eh # elp # equal # f # g # h # i # j # k # l # list # ln # ln_swt # m # m_swt # motion # This archive created: Tue Apr 29 10:46:46 1986 export PATH; PATH=/bin:/usr/bin:$PATH ###### # the following added by hand since the help files were too big if test ! -d 'se_h' then echo shar: "creating directory 'se_h'" mkdir 'se_h' fi echo shar: "entering directory 'se_h'" cd se_h ###### echo shar: "extracting 'Install'" '(278 characters)' if test -f 'Install' then echo shar: "will not over-write existing file 'Install'" else cat << \SHAR_EOF > 'Install' #! /bin/sh : Install -- put se help files into their proper directory. : This program is called from the makefile. INSTALL=$1 shift umask 022 for i in $* do echo installing $i detab < $i > $INSTALL/$i done : we really should do some error checking, but what the heck. SHAR_EOF chmod +x 'Install' fi echo shar: "extracting 'Makefile'" '(936 characters)' if test -f 'Makefile' then echo shar: "will not over-write existing file 'Makefile'" else cat << \SHAR_EOF > 'Makefile' # makefile for se help scripts DOCS= README FILES= a abt ah arg2 args b bang bug c cc ccmisc chardel charins colon \ com com_swt comdir comdir_swt comsyn d dir e eh elp equal f g h i \ j k l list ln ln_swt m m_swt motion n o o- oa oc od of og oh oi ok ol \ olm om op os ot ou ov ow ox oy oz p pat pat_swt patex patex_swt q \ quote r rpt s s_swt scan scan_swt serc shell shell_swt specl t t_swt \ termchar tilde u v w x y y_swt z # destination for final version of help scripts. INSTALL=/usr/local/lib/se_h install: existsall detab Install $(INSTALL) $(FILES) existsall: $(FILES) $(DOCS) Install @echo this message indicates all the files exist, otherwise make would die. detab: detab.c cc -O -o detab detab.c clean: rm -f detab print2 clobber: clean print: prt $(DOCS) Makefile Install $(FILES) | lpr -b 'se help' touch print2 print2: $(DOCS) Makefile Install $(FILES) prt $? | lpr -b 'new se help' touch print2 SHAR_EOF fi echo shar: "extracting 'README'" '(878 characters)' if test -f 'README' then echo shar: "will not over-write existing file 'README'" else cat << \SHAR_EOF > 'README' README: This directory contains the help files for the Georgia Tech Software Tools/UNIX screen editor Se. The files with the _swt suffix contain information which is correct when the editor is in Software Tools compatibility mode. This is the default at Georgia Tech. The files without the _swt suffix either contain information which is the same for both Unix and SWT modes, or for Unix mode, which is the default at any place other than Georgia Tech. The dohelp() routine checks what mode the editor is in, and reads in the appropriate file. The files should be installed in the directory /usr/lib/se_h for se in order for se to find them. File names must be in lower case, since dohelp() maps the file name into all lower case. (On pr1mes, case is not significant in file names, so the original ratfor version did not have to do this.) Arnold Robbins Georgia Tech 2/84 SHAR_EOF fi echo shar: "extracting 'a'" '(793 characters)' if test -f 'a' then echo shar: "will not over-write existing file 'a'" else cat << \SHAR_EOF > 'a' a -- Append command default range syntax . a "a" is for appending new lines of text after a given line. If no line number is typed before the "a", text will be appended after the current line. The last line appended becomes the current line. To signal the end of the appended text, you type a "." on a line by itself. Control characters "f", "v", "l", and "k" work differently for "a" command than for "v". "a:" works as a one line append (i.e. anything following the colon is appended after the current line). To return to the command directory, type "hcomdir." See also: "hcc" (control characters) and "hc" (change). SHAR_EOF fi echo shar: "extracting 'abt'" '(599 characters)' if test -f 'abt' then echo shar: "will not over-write existing file 'abt'" else cat << \SHAR_EOF > 'abt' Abort character CTRL-F ("Funny Return") character is used to abort a "v" command before all the specified lines have been modified. Typing it causes the current line to be restored to its state of before the "v" command was begun, and causes a return to the editor's command level. Type "hv" for a description of the "v" command. Type "hrpt" for CTRL-F's meaning if in append or command mode. Type "htermchar" for info about other termination characters. SHAR_EOF fi echo shar: "extracting 'ah'" '(142 characters)' if test -f 'ah' then echo shar: "will not over-write existing file 'ah'" else cat << \SHAR_EOF > 'ah' If you're running Berkeley Unix, and you're bored Type the following command for something enjoyable: !rogue SHAR_EOF fi echo shar: "extracting 'ah_swt'" '(143 characters)' if test -f 'ah_swt' then echo shar: "will not over-write existing file 'ah_swt'" else cat << \SHAR_EOF > 'ah_swt' If you're running Berkeley Unix, and you're bored Type the following command for something enjoyable: ~rogue SHAR_EOF fi echo shar: "extracting 'arg2'" '(917 characters)' if test -f 'arg2' then echo shar: "will not over-write existing file 'arg2'" else cat << \SHAR_EOF > 'arg2' Arguments (cont) Once the terminal type is established, the remaining arg- uments are interpreted thus: if the argument begins with a "-", the rest of it is interpreted as though it appeared after the "o" in an option command. For example, an argument of "-w10" acts as a command "ow10". On the other hand, if the argument does not begin with "-", it is interpreted as a file name (path- name). The named file is read into the edit buffer, and its name becomes the remembered file name. If more than one file is named, the edit buffer will contain the contents of all the files. If an error is encountered while interpreting arguments (file not found, illegal option), the remainder will be ignored. For invoking command syntax, type "hargs". SHAR_EOF fi echo shar: "extracting 'args'" '(425 characters)' if test -f 'args' then echo shar: "will not over-write existing file 'args'" else cat << \SHAR_EOF > 'args' Argument Handling The syntax for 'se's invoking command is usually given as se {-