Qedit aims to
provide everything an MPE or HP-UX programmer could need to write COBOL,
PowerHouse, or other programs, and to prepare documentation. Therefore, Qedit
has Line mode for batch editing and full-screen mode for interactive editing.
On HP terminals, Qedit's full-screen mode is called Visual mode. On VT
terminals, Qedit’s full-screen mode is called Screen mode. See “Getting a Quick Start with VT Full-Screen Editing” on page 27.
|
This feature does
not work on the hpterm terminal emulator at the moment.
|
As
of HP-UX 11.0, HP has dropped support for block-mode terminals. For this
reason, full-screen editing as implemented on HP3000 computers only works on
HP-UX versions earlier than 11.0. On HP-UX 11.0 or later, full-screen
editing
is available in Screen
mode
(Set Visual Screen On) on VT-type terminals or in Visual Blockemulation
emulation (Set
Visual Blockemulation On) on HP-type terminals.
|
As its name
implies, Blockemulation emulates block-mode operations by reading each line one
by one instead of reading the whole screen in a single operation. Depending on
the type of connection, this process might take a few seconds as the cursor
moves down the screen.
Qedit's Visual
mode is a powerful but friendly full-screen editor designed specifically for
programmers. It gives you full access to the editing capabilities of your
terminal in block-mode, with low system overhead. You can move, copy, mark and
delete blocks of text with Visual's cut-and-paste functions, and page backward
and forward through your file with function keys. To use Visual mode, you must
have an HP terminal or an HP terminal emulator (e.g., Reflection from WRQ).
In Visual mode,
you have access to all Line mode commands (including UDCs, command files,
compiling, linking and running programs, shell scripts, and string searching
and changing). Qedit's search and replace functions aim to be simple, fast and
powerful (e.g., ignore embedded words, etc.). The Undo command allows you to
cancel any previous edits to your file, working back to the state at which you
started. Using the optional Open and Shut feature, you can switch between files
instantly.
Visual mode is a
good introduction to the HP operating systems for users who don't work on HP
computers all day. Those who may particularly benefit are novice users, or
users who run Qedit only to update a report skeleton once a week. These
occasional users no longer have to memorize editing commands. Visual mode
provides a familiar environment where novices can make changes to the entire
screen, just as they do on PC editors. You can even configure some electronic
mail packages (HPDesk, elm), to put your users directly into Visual mode when
they edit a message.
After you have invoked Qedit, and Texted or
Opened a file, you switch from Line mode to Visual mode by typing VI or
pressing F1. If you don't have a file open, Qedit opens a scratch file and, if
empty, fills it with a screenful of blank lines.
VI [ linenum | "string" ] or press F1
(Default: linenum
= *)
Whereas in Line mode you type in command and
text lines ending each with a Return, in Visual you edit a full screen of text
in block-mode using the terminal keyboard. Since your terminal is off-line from
the computer, you can use its cursor and editing keys. You edit by moving the
cursor around the screen, inserting and deleting lines and characters. Press
Enter to save your changes. To move through the file, you have the convenience
of eight function keys, such as F6 Forward
One Page.
Visual mode in
Reflection for Windows, showing cut-and-paste indicators
You copy, move,
hold, and delete blocks of text easily by placing "cut-and-paste"
indicators at the start of the line. You may type Line mode commands at the
home line ===>
and execute them via the Enter or the F7 key. Combining the
cut-and-paste functions with the Open and Shut commands, you can also copy and
move text quickly between different Qedit files. Use the ZZ cut-and-paste
indicator with any command to mark text easily.
The Set Visual
command controls how Visual mode operates and allows great latitude in
configuring Visual to your own liking. For example, you can choose to have
automatic update; decide where the current line or cursor appears; and select
how many lines will carry over when you page up or down.
When you are done,
exit Visual mode using F8, then Keep or Shut your file. Press F8 again to leave
Qedit.
===>
Okay 1691.75
WFILE.DOC.TACCT
"verify"(u) Move Ready
*
procedure abc;
+1 begin
+2 integer def;
// ....+....10...+....20...+...
The screen starts with the home Line, followed by the status Line, several text Lines, and ends with the template Line. Columns 3 and 4 of text
lines sometimes contain special characters and are called the indicator columns.
You type commands, search for strings and for
line numbers after the ===>
on the home line.
These are executed
when the F7 or Enter key is pressed.
The home line is
also used by Qedit to print error messages. You must clear the error message by
pressing the F7 or Enter key before you can type another command in the home
line.
The second line shows the status, the current
line number (i.e., that of the * line), the name of the file you are editing,
the current string with its window, and any pending cut-and-paste task.
Okay 1691.75
WFILE.DOC.TACCT
"verify"(u) Move Ready
If you have Texted
a file into Qeditscr, the status line shows the name of the Text file, which is
also your default Keep file.
By default you see the * (current) line and
19 lines after it. Each line is prefixed by the relative line number, and two
columns for special indicators.
*
procedure abc;
+1 begin
+2 integer def;
Use Set Vis Above
and Set Vis Below to adjust the number of lines shown above and below the
current line.
The last line has // and a column template.
The // signals end-of-screen to Qedit and must not be erased.
// ....+....10...+....20...+...
Visual uses more than 76 columns for text on
Reflection, Qcterm, a 2393/97, 2626, or 700/9x terminals.
Qedit leaves
columns 3 and 4 of the text lines for you to enter cut-and-paste operators
(i.e., MM, CC, HH, etc.). Also, Qedit may print one of two special indicators
in these columns:
|
!
|
line extends
beyond the visible right margin
|
|
?
|
line contains
control characters, shown as dots
|
An ! means the line extends beyond the right
terminal margin. To shift the screen image left, type Set Left 55 at the Visual
home line and press F7.
A ? means the line contains nonprinting
characters such as Nulls, Escapes, Bells, Tabs or possibly Roman-8 extended
characters. Qedit replaces these characters with dots (.) in Visual mode, and
does not allow you to make changes. These ? lines are not updated when you
press Enter.
To edit Bells, Escape sequences, Tabs,
ShiftOuts and ShiftIns in Visual, use Set Vis Bell, Set Vis Esc, Set Vis Tab,
Set Vis SO and Set Vis SI. All these specify substitute characters to be shown
instead of dots. To edit other control codes, use Modify or Change from the
===> line. If you turn Set Editinput Extend Off, Qedit regards Roman-8
characters as nonprinting noise and show them as dots.
In Visual mode, the keyboard gives you the
power to move around the screen, edit text, and control the flow of Qedit.
You move around the screen using the cursor
keys and others:
|
Cursor Left
|
Move one space to
left
|
|
Backspace
|
Move one space to
left
|
|
Cursor Right
|
Move one space to
right
|
|
Cursor Up
|
Move one space up
|
|
Cursor Down
|
Move one space
down
|
|
Return
|
Down to next line,
back to column 5
|
|
Home Up
|
Move to ===>
line
|
|
Shift-Home
|
Move to bottom of
screen
|
|
Tab
|
Move to next right
Set TAB column
|
|
Shift-Tab
|
Move to next left
Set TAB column
|
|
Prev Page
|
Only moves around
terminal memory
|
|
Next Page
|
Only moves around
terminal memory
|
You revise the screen image using these keys:
|
Space bar
|
Move cursor right
and erase character
|
|
any char
|
Overwrite cursor
and move it right
|
|
Del Char
|
Remove character
at current cursor
|
|
Ins Char
|
Enable
"insert"; use again to disable
|
|
Ins Line
|
Insert blank line
above current line
|
|
Del Line
|
Delete line at
current cursor
|
|
Clear Line
|
Erase to the end
of the line
|
|
Clear Display
|
Avoid! Recovery: Home Up,*,F7
|
To save the changes you have made on the screen,
|
Enter
|
Send screen image
to Qedit, update file
|
To return from
Visual mode to Line mode:
Some other keys:
|
Select
|
Useless in Qedit
|
|
Stop
|
Do not use in
Visual
|
|
Break
|
Disabled in Visual
|
|
Reset
|
Use if screen
locks up, press Enter
|
|
Esc
|
First key of
Escape sequences
|
|
Del
|
Does not delete
anything!
|
If you are using a PC with Reflection for
DOS, you need to map the PC keys into the HP keys.
Note that the PC
keyboard has two keys labeled Enter, which are used differently in Qedit. The
Enter key above the Right Shift key is called the Return key in this manual,
and is used to execute commands in Line mode. In Visual mode, this key moves
the cursor down by one line. The other Enter key (on the numeric keypad) is
called the Enter key, and is used to update the screen in Visual mode.
Here are the
default Reflection keystrokes for common functions:
|
Terminal
Keyboard
|
Reflection Key
Sequence
|
|
Enter
|
Enter on the
numeric keypad. If that doesn't work, try the "+" on the numeric
keypad, or try Shift-F10
|
|
Home Up
|
Control-Home
|
|
Shift-Home
|
Control-End
|
|
Ins Line
|
Alt-I
|
|
Del Line
|
Alt-D
|
|
Clear Line
|
Alt-K
|
|
Clear Display
|
Alt-J (avoid in
Visual!)
|
|
User keys
|
F9
|
|
System keys
|
F10 (then F7 for
help)
|
|
Additional
Functions
|
Reflection Key
Sequence
|
|
Begin Line (Column
1)
|
Home
|
|
End Line
|
End
|
|
Help about
Reflection
|
Alt-H
|
|
Exit
|
Alt-X
|
AdvanceLink is similar (Alt-H is help, Alt-I
is Insert Line, Alt-D is Delete Line), but Clear Line is Alt-L, and Enter is
Alt-F3. Other terminal emulators have their own keystrokes for common
functions. See your emulator's manual for details.
Much of the
convenience of Visual mode is due to the power built into the eight user
function keys: F1 through F8.
|
F1
|
Update and go to
next page
|
|
F2
|
Roll Up Screen n lines, as per Set Vis Roll
|
|
F3
|
Findup (search
back for current string)
|
|
F4
|
Find (search ahead
for current string)
|
|
F5
|
Backward One Page
|
|
F6
|
Forward One Page
|
|
F7
|
Execute command
typed in ===> line
|
|
F8
|
Exit from Visual
back to Line mode
|
F1: Update and Go to Next Page
Qedit reads the current page and updates the
file, then displays the next page. The F1
key combines the Enter key and F6 (Forward) in a single key. However, F1
does not execute any command typed in the home line as the Enter key would.
F2: Roll Up Screen
Qedit clears the screen and displays a new
one that is rolled up n lines
(default: 6), where n is controlled
by Set Vis Roll.
F3: Findup - Previous String
Qedit searches backward in the file, starting
from the * line, until it finds a line that contains the current string. Qedit
clears the screen and displays a new page, with * positioned at the line that
contains the found string. Visual also displays the target string on the Status
line.
Before you can use
F3, you must establish the string for which to search. Type the string in
quotes prefixed by a circumflex (^"string")
at the ===>
on the home line and press F7, to do the first Findup.
F4: Find - Next String
Qedit searches forward in the file, starting
from the * line, until it finds a line that contains the current string. Qedit
clears the screen and displays a new page, with * positioned at the line that
contains the found string. Visual also shows the target string on the Status
line.
Before you can use
F4, you must enter the target string. Type the string in quotes ("string") at the ===> on the home line and
press F7, to do the first Find.
F5: Backward One Page
Qedit clears the screen and displays the
previous page. By default, the top line of the original screen becomes the
bottom line of the new screen. Use Set Vis Carry to change the number of lines
carried over to the new screen.
F6: Forward One Page
Qedit clears the screen and displays the next
page. By default, the bottom line of the original screen becomes the top line
of the new screen. Use Set Vis Carry to change the number of lines carried over
to the new screen.
F7: Execute a Command
Use the F7 key to execute commands. The
current screen is not updated, unless you have Set Vis Update On. Type whatever
command you want to execute after the ===>.
This includes "strings" to find, Qedit Line mode commands such as
Open or Justify, shell commands, calculator commands (=5/6), and special Visual
commands (e.g., * for Refresh, ? for Help). Then press F7. Qedit reads only the
home line and executes the function. To first save your screen changes and then
execute, use Enter instead of F7.
See the section
"Home Line Commands" for complete details.
F8: Exit from Visual
To return from Visual mode to Line mode, use
the F8 key. Press F8 again once you are in Line mode to exit Qedit and return
to HP-UX. If for some reason F8 fails to exit from Visual, type / at the ===> and
press F7 or the Enter key. This should get you back to Line mode.
Line
Number. Move to a specific line (e.g., to line 45).
===>45 F7
> and <. Move ahead or back a
page. Use with a number to move several pages (e.g., ahead 3 pages).
===>>3 F7
+ and -. Move forward or backward any
number of lines (e.g., back 200 lines). If you do not specify a number, the
default is the number of lines configured by Set Vis Roll.
===>-200 F7
~ The Tilde Key. Return to the
"most recent" screen. If you jump from line 1500 to line 451, ~ sends
you back to 1500. This is handy if you jump briefly to another part of your
file to check something then want to get back to your original location.
The tilde is also
available from line-mode but it has to be enabled by removing it from the list
of string delimiters. In order to do this, you could do the following:
/V
stringd
Set
STRINGDelimiters "|\~{}[]_@?!#>%&:'"
/S
stringd "|\{}[]_@?!#>%&:'"
Notice that tilde
has been removed from the delimiter list entered on the Set command.
===>~ F7
FIRST and LAST. Move to start or end of
file.
===>first F7
Scrollup
Character. This character can be entered
in the cut-and-paste columns to scroll up in the file. A single character
scrolls the number of lines defined by Set Visual Roll. If the character is
entered more than once, Qedit scrolls up that many times the number of Roll lines. For example, enter 4 minus signs anywhere to scroll
4 X Roll lines. The default scrollup character is a minus sign. It can be
changed to something else with Set Visual Scrollup.
It is never necessary to remember line
numbers in full-screen mode. Visual allows you to mark, hold, move, copy,
replicate, or delete a block of text, all visually. This is called
"cut-and-paste" and is done by putting special indicators in the two
blank columns at the left of each text line before you press the Enter key. For
example, DD indicates a block of text to be deleted.
Order Is Not Important (But One at a Time).
You can enter the indicators in any order and on different screens, but
10,000 is the maximum number of lines you can cut. When you have defined a
complete cut-and-paste task, Qedit completes the task and removes the
indicators. You can only perform one cut-and-paste task at a time.
|
Single Line
|
Block of Text
|
Function
|
|
M
|
MM
|
Move line or block
of text
|
|
C
|
CC
|
Copy line or block
of text
|
|
D
|
DD
|
Delete line or
block of text
|
|
H
|
HH
|
Hold a line or
block of text
|
|
|
HJ
|
Append block of
text to Hold file
|
|
|
JJ
|
Justify a block of
text
|
|
Z
|
ZZ
|
Mark a line or
block of text
|
|
A
|
Insert text
"after" this line (or use F for "following")
|
|
B
|
Insert text
"before" this line (or P for "preceding")
|
|
AH
|
Insert Hold file
after this line (or use FH)
|
|
BH
|
Insert Hold file
before this line (or use PH)
|
|
A0
|
Insert Hold0 file
after this line (or F0)
|
|
B0
|
Insert Hold0 file
before this line (or P0)
|
|
R
|
A line to be
replicated after itself
|
|
Rn
|
A line or block to
be replicated n times (max. 9).
(See "Copying a Block of Text" below.)
|
Display Enhanced. When
the cut-and-paste task is partly defined, Qedit highlights the indicated lines
and adds a warning to the status line.
You can cancel a pending cut-and-paste task
(if you have not pressed the final Enter) by entering a period (.) in the ===> line
and pressing F7.
===>. F7
Paste
One Copy at a Time. Suppose you want to copy a section of text from one
place in your file to another. Here is one way to do it. First, locate the
screen containing the start of the block that you want to copy, using a string
search via the home line. Move the cursor down to the first line you want to
copy, then press Cursor Left twice and type "CC" in the blank columns
provided. Press Enter and you should see that line highlighted in inverse
video.
Second, find the
end of the text section and mark the last line with another "CC".
After you press Enter, you should see the entire block highlighted.
Third, go to the screen
where you want to insert a copy of the text. Move the cursor down to the line before the desired insertion point,
Cursor Left once and type "A" (for after). Press Enter and the block
should appear.
Paste Multiple Copies at
Once.
When working with a block of text, you can
use the same cut-and-paste codes to mark the beginning and the end of the block
(i.e., HH on the first line of the block and HH again on the last line). The
only exception to this is the block replication code.
In this case, you
would use RR to mark the beginning of the block and Rn to mark the end of the block, where n represents the number of times you want that block replicated.
For example, to have the same block replicated five times, you would enter R5.
The new blocks are inserted immediately after the last line of the copied
block.
The original lines
marked for replication are written to the Hold0 file.
Using Visual mode's cut-and-paste functions,
you can copy and move blocks of text between
files.
You can only edit
one file at a time in Qedit, but you can switch quickly between different Qedit
files by Opening and Shutting them.
/o
file1
Open
file1 List * = 20
/o
file2 {implicitly shuts file1}
Shut
file1
Open
file2 List * = 48
/o
* {open the last file
that was shut}
Shut
file2
Open
file1 List * = 20
/o
* {open the second file
again}
Shut
file1
Open
file2 List * = 48
Note: The * shortcut
refers to the last Qedit file that was shut.
Now, to copy a
block of text from file1 to file2, use HH twice (just as you would
use CC) to hold the block in file1.
Then, open file2, and use AH or BH to
paste in the text from the Hold file. To move a block from file1 to file2, use the
DD function to delete the block of text from the first file. The deleted block
is stored in a temporary Hold file called Hold0 (Hold-zero). Now immediately
open file2 and use A0 or B0 to paste
in the text from Hold0.
Single line
|
V
|
a single line to
be diVided
|
|
G
|
a single line to
be glued
|
|
GJ
|
a single line to
be glued with a space inserted
|
Block of text
|
VV
|
begin or end of
the block to be diVided
|
|
GG
|
begin or end of
the block to be glued
|
To divide a line, use the V (diVide)
cut-and-paste function in column 3 or 4, then insert the special field
separator ("~") at each division point in the line. The default field
separator is tilde ("~" ), but you can override this with Set Vis
Field. If no "~" is found in the line, a blank line is added after
the line.
What about
dividing all the lines in a range? Use VV to mark the start and the end of the
line range, then place the field separators in the first line of the range.
Every line of the range is divided at the specified field columns. If no
"~" is found, a blank line is added after each line.
When marking
several division points, insert them into the first line of the block from right to left. As you insert them, they
shift the following text to the right one space each. Otherwise, if you insert
them from left to right, it is difficult to select the proper division point
for subsequent fields.
To Glue the next line to the current line,
use a G in column 3 or 4. To Glue two lines with a space inserted at the joint,
use GJ in columns 3 and 4.
To glue
"pairs" of lines within a block, use GG to mark the start and end of
the block.
By default, G and GG append text after the
last nonblank character in a line, but it is also possible to glue text to
specific columnar fields. You do this by inserting a field separator at the
start of each field (mark the first line only). The default field separator is
the tilde ("~"), but you may override this with Set Vis Field. If you
specify three fields, G glues the next three lines to the first line. GG glues
the next three lines to the first line, and then go on to the next group of four
lines. If the precise column number where each field starts is important to
you, insert the field separators from right to left, since each one that is
inserted shifts the column numbers that follow off by one more.
The XX indicators are used to mark
lines that you do not want displayed in full-screen mode. Once marked, the
block of text is replaced with a single line.
--- Excluded Area --- 10/34.5
This line shows the line numbers which are currently
excluded. An excluded area setting is saved in the workfile so it's preserved
across Open/Shut commands. To reset the excluded area and see the original
lines again, type .xx on the Homeline and press
Enter or F7.
The excluded area can also be defined using Set
Visual XX. The current excluded area is displayed on the Verify
Visual output.
Restrictions
The Excluded Area line must not be
removed, altered or used in any way. This also means that you can not enter any
indicators in the cut-and-paste area. If you wish to paste lines before or
after the excluded area, you should use the appropriate cut-and-paste
indicators on the line that immediate precedes or follows the Excluded Area line.
An excluded area can not be included in any other block
operation such as ZZ, CC, MM or other XX.
If any of these rules are broken, Qedit displays an
appropriate error message.
Justification in text alignment is available
in full-screen mode. To justify a block of text, simply mark the first and last
lines in the block with the JJ indicator. If Qedit uses any justify default
settings, they are defined by the Set Justify command. If there are no default
settings, Qedit assumes the text should be justified within the current display
width.
The justified
lines are written to the Hold0 file. A single J indicator is not valid.
When the insertion
point is on the current screen, Qedit renumbers the screen if needed (and if
Set Vis Renum is ON).
When entering a
lot of new text, it is tiresome to keep pressing Ins Line for each new line. To
insert a block of 10 blank lines quickly, press Ins Line to create one blank
line, Cursor Left twice, type R9, and press Enter. This reproduces nine copies
of the blank line immediately after it (as well as updating the paragraph you
just finished typing). Repeat as needed.
Visual has both an
implicit and an explicit Hold file.
The
Implicit Hold0 File. Any block processed by the CC, MM, JJ, RR, or DD
indicators is also written to a disc file called Hold0 (Hold-zero). This allows
you to copy the lines back into your workfile using A0 or B0 (add from Hold0, After or Before the line on which you place the indicator).
The
Explicit Hold File. The HH indicator writes a block to the Hold file
without moving or modifying it. Use H for a single line. To copy the line(s)
back into your workfile, use AH or BH. You may need a Hold file when creating a
file that you want to compile, or when using the Use command. You must use HH
(instead of CC) for copying text from one file to another.
When HH is used to mark the beginning and end
of a block, it copies the block of text to the explicit Hold file. With the HH
indicator, the current contents of the Hold file are erased and replaced with
the marked lines.
If you want to
append a block of text to the Hold file, you can use the HJ indicator. HH or HJ
can be used to mark the first line. However, HJ must be used to mark the last
line. You cannot hold-append a single line of text, which means you can append
only two or more lines. With the HJ indicator, the current contents of the Hold
file are preserved and the block of text is appended to it.
The ZZ indicators mark a group of lines that
you want Qedit to remember. Use Z to mark a single line. Note: "Z"
for a single line is valid only in Visual mode; in Line mode, use
"ZZ" to mark a single line. See the ZZ command in the "Qedit
Commands" chapter for further information. Once marked, the lines are
displayed at half-bright intensity and you can refer to them in any home line
command by using ZZ where the line numbers are expected. This is especially
useful when listing lines to the printer, changing or appending strings, and
formatting text:
===>
list $lp zz F7
===>
change "bob"Robert" zz F7
===>
verify zz F7 {check current ZZ
range}
===>
zz off F7 {cancel ZZ
range}
If you want to copy text into your current
workfile from another file that is not a Qedit file, you cannot use the methods
described above. You cannot Open the second file if it is not in Qedit format.
Instead, use the List command to find the portion of text that you want to add
from it (without Shutting the first file). Then, use the Add command to paste
in the text.
===>list
xxx
===>add
* = xxx 10.7/22.9
All Qedit commands are supported in Visual
mode. To do a command, such as Listf or ls, press the Home Up key to reach the
home line, then type your command after the ===> and press F7 or Enter. To
execute a command, such as Change, on a subset of the file, first use the ZZ
cut-and-paste indicators to mark the subset and then use ZZ in the command.
After most ===>
commands, Qedit prompts you for more commands ("Next command
[Visual]"). Type in more commands, or return to your Visual screen above,
by pressing the Enter or Return key.
Qedit accepts each
command, executes it and goes back to the "Next command" prompt.
There are a few exceptions to this process. By default, when you enter an Open
command, Qedit assumes you want to edit the file immediately and switches into
full-screen mode automatically. If you wish to disable this feature, enter Set
Visual Editonopen Off.
If the tilde has
been removed from the list of string delimiters (see Set
Stringdelimiters)
and you enter a tilde "~" at the "Next command" prompt,
Qedit uses the current line number associated with the tilde, makes it the
current line and goes back into Visual immediately.
To search for a string, simply type it in
quotes at the ===> line and press F7 or Enter.
===>"string" F7
Qedit will find
the next line containing that string,
display the page around it, and show the target string in the Status line. To
find the next occurrence of the same string, press F4.
To find the previous occurrence of a string, prefix
the string with a circumflex.
===>^"string"
F7
To find the next previous
occurrence, press F3.
You may delimit strings with any of the
following characters:
|
~
|
Tilde
|
|
|
|
Vertical line,
Up-line
|
|
"
|
Quotation mark
|
|
'
|
Apostrophe, Single
quote
|
|
:
|
Colon
|
|
%
|
Percent sign
|
|
\
|
Reverse slant,
Backslash
|
You may use single quotes (') if you do not
have Set Decimal On. Note that, with this syntax, Qedit permits a few less
characters in Visual mode than it does in Line mode because Visual mode uses
these characters for other purposes. For example, the question mark is used to
get quick help about Visual mode, instead of as a string delimiter. If you
insist on using other delimiters, you should use the Find command on the ===> line.
===>F
:string: F7
You can change
strings on the screen by entering a Change command on the ===> line.
===>c
"niether"neither" */*+19 F7
To get help, press
Home Up, type ? and press F7 or Enter.
===>? F7
The ? command
gives a one-screen summary of Visual mode. For complete on-line help on Qedit,
including Visual, type HELP in the ===>
line and press F7 or Enter.
===>help F7
For help on a
specific command, type HELP [command name].
See the Help command in the "Qedit Commands" chapter. To get out of
help, press F8.
To format a screen
paragraph, mark the paragraph with ZZ cut-and-paste indicators, then use a
Justify command that includes a ZZ. For example:
===>justify both margin 68 zz
F7
If every paragraph
ends with a blank line, you can Justify a paragraph by using the relative line
number on the screen. Justify will start at that point and continue until it
finds a blank line:
===>justify both margin 68 *+2
F7
For more
information on Justify, see the Justify command in the "Qedit
Commands" chapter.
After you have made some changes to your
screen in Visual mode and updated the file by pressing Enter, you may decide
you don't want those changes after all. You can use the Undo command to cancel
these changes.
All of the changes
you make on the screen before pressing Enter, are treated by Qedit as one
"undo-able" command, except for cut-and-paste operations. Qedit
always executes a cut-and-paste last after updating the file with any other
changes, no matter what order the changes were made in. This means that you can
choose to undo just the cut-and-paste operation, or undo it and all of the
other changes. You can continue undoing your previous changes until the file is
back to its original state.
If you make changes to the screen, then
decide not to keep them before you
press Enter to update your screen, how do you get your original text back? You refresh the screen by typing a * on the
home line, then pressing F7, F1 or Enter (or any function key with Set Vis
Update On). Use the Undo command if you press Enter and then decide that you
don't want to keep your changes.
If you insert so
many new lines that you push the column template line right off the bottom of
your screen, don't worry -- it's not really gone. Qedit won't update your
screen without the template line, however. Press Next Page (Pg Dn) to pull up
the next screen of display memory. You have a problem only if you inserted so
many lines that you pushed the template line right out of display memory, and
even then you can still recover your changes. See the Errors in Visual section of Appendix E, regarding qscreen.
Screen Refresh is particularly
useful if you've pressed Clear Display by accident.
===>* F7
When using Set Vis
Update On to automatically update the screen, use *> F7 or *< F7 to move
ahead or back one page, without updating the current page.
You may enter any
Line mode Qedit command in the ===>
line, including Opening another file, and calculator commands (=). The
ZZ cut-and-paste indicator can be used to mark a group of lines for use in any
Qedit Line mode command.
===>list
$char zz F7
When editing a file with short records (e.g.,
Set Lang Text, Set Len 20), the right margin of terminal display memory is set
to match the record length. This means that when typing home line commands you
wrap the status line at the same width as the records (very inconvenient if the
record length is 3 bytes!). You can, however, cursor past the right margin to
type a longer command. Therefore, Qedit expands the right margin when you use F7
to execute the home line command, making it possible to execute a long command
even when the data length is short. Qedit cannot expand the right margin if you
press Enter (and may cut short your command).
If your function
keys do not work for some reason, you may not be able to use F8 to exit from
Visual. Instead, press Home Up, type / and press Enter. This updates your
current screen and returns you to Line mode.
===>/ F7
To run Qedit for
HP-UX, type this command:
/opt/robelle/bin/qedit
Qedit.
Copyright Robelle Solutions Technology Inc. 1977-2001.
(Version
5.8) Type ? for help.
qux/
Qedit prints its
version number and prompts with "qux/". You type commands, ending
each with Return. For example, to edit a file enter a Text command:
To save your
edits, use the Keep command.
When you start
Qedit, you are initially in Line mode (you type command and text lines, ending
each with the Return key). Qedit has two full-screen modes: Visual mode for HP
terminals and Screen mode for VT terminals.
Full-screen
editing as implemented on HP3000 computers only works on HP-UX versions earlier
than 11.0. On HP-UX 11.0 or later, full-screen editing
is available in Screen
mode
(Set Visual Screen On) on VT-type terminals or in Visual Blockemulation
emulation (Set Visual Blockemulation On) on HP-type terminals.
As its name
implies, Blockemulation emulates block-mode operations by reading each line one
by one instead of reading the whole screen in a single operation. Depending on
the type of connection, this process might take a few seconds as the cursor
moves down the screen.
On HP terminals,
Qedit's full-screen mode is called Visual mode. The function keys give you
eight quick functions: F1 = Visual, F2 = Roll up, F3 = Findup, F4 = Find, F5 =
Browse backward one page, F6 = Browse forward, F7 = Listredo, and F8 = Exit.
Press the F1 key
or use the Visual command to switch to full-screen mode, where you can edit a
full screen of text with the terminal keys. The Enter key passes the revised
screen back to Qedit, and the F7 key executes any Line command that you type on
the home line. If you have an HP terminal or emulator, you will want to export
RCRTMODEL so that you can use advanced screen features. See "Variables
that Drive Qedit."
To return from
Visual mode to Line mode, press the F8 key. To save your changes to the Text
file, use the Keep command. To get out of Qedit, type Exit or press F8 again.
If you forget to
Keep your changes, Qedit asks if you want to "Discard your changes?"
or stay in Qedit to save them.
Screen mode
differs from Visual mode by doing edits to a line right away, instead of
waiting for a screenful of changes. Use PF1 for Help, PF3/PF4 to browse back
and forth in the file. You can enter new text right away (there is no concept
of command mode vs insert mode like there is in vi). Perform edit operations
with control-key sequences. To exit Screen mode, press ^E.
Qedit's primary scratch file is called
"Qeditscr." By default, this file is created in
/var/tmp (/usr/tmp is the default on older
versions of HP-UX) or the path name specified in the TMPDIR environment variable. The scratchfile name is qscr.xxxxxxxxx where
"xxxxxxxxx" is a random string generated by the HP-UX tempnam routine.
If you want to move scratch files to a
different directory, you can set the TMPDIR environment variable.
TMPDIR=/home/user1/tmp
export
TMPDIR
Keep in mind that Qedit works with absolute filenames and
these names can not have more than 240 characters. Whenever you use the default
options for Opening or Texting a file, your work will be in the Qeditscr
scratch file.
What if you want
to edit two or more files and copy lines between them? You could Text the first
file, Hold the selected lines, Keep your changes, then Text the second file and
insert the lines. However, if you are doing numerous edits, the constant Text
and Keep operations are inconvenient.
It is faster to
Text each file into an extra scratch file
of its own. Then use the "Open ?" or the "Open *-n" command to switch quickly
between them. By default, Text always copies the file into the Qeditscr scratch
file. However, Qedit can supply up to eight extra scratch files. To Text a file
called abcd into an extra scratch file, type:
When you Exit,
Qedit checks whether you have any unsaved edits in any of your scratch files.
If there are some unsaved edits, Qedit prompts you to "Discard?" them
or to stay in Qedit to save them with the Keep command.
Sometimes you start editing a new document
and have nothing to Text to create the extra scratch file. In this case, use
the New command without parameters.
Qedit creates a
new extra scratch file and assigns it a sequential number (1,2,3...). If you
use an Open ? command, you would see "Extra Scratch file #2" in the
list of files. If you do a Keep or Set Keep Name command, you would see the
Keep file as the Text name in Open ?.
When you log on to
HP-UX, a program is run called the shell. The shell program interprets
commands, executes them, and controls command execution. Making configuration
changes requires that you know which shell you are using and what files are
automatically executed.
The Bourne and Korn shells execute the file
/etc/profile when you log on to HP-UX. They then look for a file in your home
directory called .profile. If it exists, it is executed. If you use SAM to add
new users, the file /etc/d.profile is automatically copied to the home group of
the new user. If you want to make global changes to the commands executed at
login time, you should change two files:
/etc/profile {always
executed at login}
/etc/d.profile {default
.profile for new users}
The C shell executes the file /etc/csh.login
when you log on to HP-UX. It then looks for the file .login in your home
directory. If it exists, it is executed. Next, the C shell executes the file
.cshrc in your home directory (also executed any time you invoke a new copy of
/bin/csh). If you use SAM to add new users, the files /etc/d.login and
/etc/d.cshrc are automatically copied to the home group of the new user. If you
want to make global changes to the commands executed at login time, you should
change these files:
/etc/csh.login {always
executed at login}
/etc/d.login {default
.login for new users}
/etc/d.cshrc {default
.cshrc for new users}
You can invoke Qedit with the command:
If you want to be
able to just type
to invoke
Qedit/UX, you must either add /opt/robelle/bin to your PATH or copy
/opt/robelle/bin/qedit to a directory that is currently on your PATH. Similarly,
the man pages for Qedit are found in /opt/robelle/man/man1/qedit.1. To make the
man pages available to everyone, you can either add /opt/robelle/man to your
MANPATH or you can copy the man pages to a directory that is currently on your
MANPATH.
See the discussion
above about the files automatically executed by the Bourne and Korn shells. The
easiest way to change the two PATHs for all users on your HP-UX machine is to
log on as root and add these two lines to the file /etc/profile after any
existing PATH or MANPATH statements:
PATH=$PATH:/opt/robelle/bin
MANPATH=$MANPATH:/opt/robelle/man
Remember to delete
any PATH or MANPATH settings in /etc/d.profile, so that new users do not
override your changes. You also have to warn existing Bourne and Korn shell
users to change the .profile file in their home directories.
See the discussion
above about the files automatically executed by the C shell. The easiest way to
change the two PATHs for all users on your HP-UX machine is to log on as root
and add these two lines to the file /etc/csh.login after any existing path or
MANPATH statements:
set
path=($path /opt/robelle/bin)
setenv
MANPATH "$MANPATH":/opt/robelle/man
Remember to delete
any path or MANPATH settings in both /etc/d.login and /etc/d.cshrc, so that new
users do not override your changes. You also have to warn existing C shell
users to change their .login and .cshrc files in their home directories.
Most HP-UX users have Control-D configured as
the end-of-file character and Control-C as the interrupt character. If you use
Robelle-style modify, you must reassign Control-D to a different control
character. If you are a former MPE user, you may wish to assign Control-Y as
your interrupt character. A standard shell configuration file (.profile for
Bourne and Korn shells and .login for the C shell) usually contains a line
like:
stty
erase "^H" kill "^U" intr "^C" eof "^D"
swtch "^Z"
To change both the
end-of-file and interrupt character, you should change the "intr" and
"eof" control keys as follows:
stty
erase "^H" kill "^U" intr "^Y" eof "^E"
swtch "^Z"
Note that the
end-of-file signal is required by many programs. Many introductory books on
UNIX assume that Control-D generates an end-of-file. You have to remember to
now use Control-E (at least Control-E is easy to remember since end-of-file
starts with the letter "E").
When you run Qedit, it automatically
"uses" two configuration files if they exist: /opt/robelle/qeditmgr and .qeditmgr in your home
directory. The system manager usually creates /opt/robelle/qeditmgr
and puts Qedit commands in it to set Qedit options. To check the options for your
site, List this file.
If you want a
personal Qeditmgr file, create the file .qeditmgr
in your home directory. This file is in addition to the global Qeditmgr file
which is always executed first.
Qedit treats the Qeditmgr file exactly like a
usefile, so Qeditmgr can include any
Qedit commands. The Set commands let you configure Qedit so it has the ideal
defaults for your shop (e.g., Set Lang Cobol ...). Here is a typical Qeditmgr
file:
{These
are default qedit values for all users:}
set
lang cobolx all on
set
x date list off {mark
changed lines with date}
set
check on {verify
delete/format of >5 lines}
set
list page on {lp
listings interpret $page}
z=list
*/last {define
z command}
For details on Set
commands, refer to the "Qedit Commands" chapter.
If one set of
defaults is not appropriate for everyone on your system, it is possible to set
up personal Qeditmgr files in each user's home directory. See the chapter
"Running Qedit on HP-UX" for details.
You normally run Qedit as an on-line session.
You type Qedit commands on your terminal and Qedit prints responses on your
terminal. If you redirect stdin or stdlist, Qedit assumes that it is in batch.
Qedit in batch is
almost identical to Qedit on-line, except for answering questions. When Qedit
asks a question in batch, no one is there to answer it. Therefore, Qedit does not expect an answer from stdin.
Qedit assumes that you want your batch task to complete, so it always selects
the option that will complete the command successfully. This is normally a
"YES" answer, as in "yes, clear the file" or "yes,
upshift the line". Qedit prints the question on stdlist, as well as the
answer that it has selected for you.
When Qedit encounters an error in batch, no
one is there to correct it. Therefore, Qedit normally aborts. However, you can
use Set Autocont On to override this abort, instructing Qedit to keep
processing after errors in batch.
You can invoke
Qedit/UX with options, or an initial file name to edit, or both (or neither).
The syntax for invoking Qedit/UX is:
See below for suggestions
on setting the EDITOR environment variable so that Qedit is automatically
invoked as your editor from other tools like elm.
You can specify commands to be executed using
the -c option before the file name. The -c is followed by commands to be
executed. There must be no space between the -c and the command list.
If those commands
contain a space, they must be enclosed in single or double quotes; otherwise,
the quotes are optional. When both -c and a file name occur, the –c commands
are executed after the file is accessed for editing. Here are some examples:
qedit
-cvisual myfile
qedit
-c"visual" myfile
qedit
-c'set vis ab 3 bel 12;visual' myfile
qedit
-c"text abc;use fixit;k,y;e"
Sometimes you want to invoke Qedit for a
specific purpose, such as writing a message in elm. You are using Qedit as a
dedicated tool for a specific purpose. In these cases, specify -s and a file
name. You can only edit that file and it will be saved on exit. You will not be
allowed to edit any other files.
qedit
-cvisual -s myfile
/exit
Save
your changes (yes/no)?
Some users find that they Exit from Qedit
inadvertently by pressing F8 too many times. To require user approval on Exit,
use the -v option.
qedit
-v
/e
Okay
to exit [no]:
/
Qedit needs to purge your random-named
scratch files when it terminates. But you may not have saved your editing work
yet. In that case, Qedit asks you "Discard changes?" and will not
Exit/Purge unless you answer Yes:
qedit
myfile
/visual
/exit
Discard
your changes [no]:
/
This section
describes features of Qedit/UX that interact with the HP-UX environment.
HP-UX utilities that invoke an external
editor use the variable EDITOR to determine which editor and run-time options
are invoked. The electronic mail tool elm is an example of a utility that uses
an external editor to write all messages.
If you want to use
Qedit as your standard editor, you need to set the EDITOR variable. We
recommend using the -s option for application use. If you wish to immediately
go into Visual mode, you should specify -cvisual as part of the variable
string. The following example sets the EDITOR variable to invoke Qedit and put
you into Visual mode:
Bourne and Korn
shells:
$EDITOR="qedit
-s -cvisual";export EDITOR
C Shell:
%setenv
EDITOR "qedit -s -cvisual"
When Qedit needs a
disposable scratch file (e.g., for Text or Add), it creates a Qedit format file
in /var/tmp by default (/usr/tmp is
the default on older versions of HP-UX) or the path name specified in the TMPDIR environment variable. The scratchfile name is qscr.xxxxxxxxx where
"xxxxxxxxx" is a random string generated by the HP-UX tempnam routine.
Keep in mind that Qedit works with absolute filenames and
these names can not have more than 240 characters.
Because all HP-UX
files are permanent, Qedit must purge this scratch file when you exit Qedit. If
you have made any changes, Qedit asks whether you want to discard the changes
that you have made.
Qedit has two Hold files: Hold and Hold0. The
first one is created using the Hold command or with HH/HJ in Visual mode.
Lines are written
to the Hold0 file every time you move or copy with the Add command (MM, CC, and
DD in Visual mode) or justify (JJ) or replicate (RR) lines in full-screen mode.
By default, these Hold files are created in /var/tmp (/usr/tmp is the default on older versions of HP-UX) or
the path name specified in the TMPDIR environment variable. The
Hold files are called qholdxxxxxxxxx (explicit Hold) and qholdxxxxxxxxx.0 (implicit hold file) where "xxxxxxxxx" is a
random string generated by the HP-UX tempnam routine.
If you want to have these files in a different location,
you can set the TMPDIR environment variable to
the new path name.
TMPDIR=/home/user1/tmp
export
TMPDIR
Keep in mind that Qedit works with absolute filenames and
these names can not have more than 240 characters. So that you don't have to
remember these names, you can refer to these files as Hold or Hold0 in Qedit
commands. For example,
/hold
50/60 {save
lines in the Hold file}
/open
report.cob {switch
files}
/aq
last=hold {lines
copied from the Hold file}
The value of TMPDIR can be a relative or absolute path.
Internally, Qedit always uses the absolute path. It converts the relative path
if needed.
You cannot use
Qedit to look at files in your current directory called hold or hold0, unless
you qualify them with the directory or a relative path name, as in ./hold.
The Hold files are removed when you exit Qedit.
You can execute shell commands by typing them
at anywhere you can type a Qedit command. If Qedit determines that it is not
one of its own commands, it assumes it's a shell command and tries to execute
it as such. If the shell command matches an existing Qedit command, you must
precede it by a colon (:) or an exclamation mark (!). Shell commands are
executed by your default shell (the one configured in /etc/passwd for your user
name).
If you want to
enforce the use of the colon or exclamation mark prefix, you can enter Set
Limits Colonreq ON.
Shell commands are
executed by a child copy of your shell. Child shells cannot change environment
variables in the parent's environment. To change the value of an environment
variable, you must first exit Qedit.
If you use the POSIX or Korn shell, you have
access to a shell command history function. By default, the shell saves the
last 128 commands you have entered. The default name is .sh_history and is
located in your home directory. If you want to use a different file name,
change the HISTFILE environment variable. If you want to change the number of
commands saved, change the value of the HISTSIZE variable.
Normally, you
recall commands from the history stack by using the fc command. This command
calls up the default shell editor that works like the vi editor. You can
instruct the shell to use Qedit/UX as your command line editor instead.
The first step,
which is probably the most important one, is setting the FCEDIT variable. This
variable specifies which editor you want to use to modify the commands. The default
editor is /bin/ed. To change the editor, use
FCEDIT='qedit
"-c m ;k,yes;e"'
export
FCEDIT
The export command
is not mandatory, but it is good practice to include this command in case you
start up another shell process. Also note that the quotes are very important.
You begin with single quotes and enclose the Qedit/UX commands in double
quotes.
In the next step,
you can use the fc command to recall commands. It has a fairly simple set of
arguments. You can also create your own set of commands using aliases.
A typical set of
commands would include:
alias
listredo="fc -l"
alias
redo=fc
alias
xeq="fc -e -"
NOTE: You cannot
use "do" because it is a shell-reserved keyword. The xeq command is
used instead.
The listredo
command simply lists the most recent commands in the history stack. Its default
(no argument) setting lists the last 16 commands.
When you use one
line number as the argument, listredo lists all the commands from the specified
line on. When you enter a few characters as the argument, the list starts with
the last command that has these characters.
listredo
100 {list
all commands starting with number 100}
listredo
c@ {list
all commands starting with a "c"}
With two line
numbers, listredo lists all commands between these two lines.
listredo
100 105 {list
commands 100 to 105}
The redo command
recalls one or more commands and allows you to modify them before executing
them. It uses similar syntax to listredo. If you do not specify an argument,
redo recalls the last command you have entered. If you specify a command
number, it recalls that particular entry. If you enter a string, it recalls the
most recent command starting with that string. If you enter 2 numbers, it
recalls all the commands between these 2 numbers and allows you to modify them,
one by one.
The xeq command
recalls one or more commands and executes them immediately. It works the same
as the redo command. The only difference is that you are not able to modify the
commands.
The default Qedit/UX tab stops are every 8
characters. You can override this using Set Tabs Stop n (every 2 to 15 characters). If you Exit from Qedit with the tabs
set to anything other than Set Tabs Stop 8, Qedit resets your terminal to the
default tab stops.
When you Text or
List a file with tab characters in it, Qedit/UX does not expand them to spaces.
If you want to edit lines containing explicit tab characters, see Set Vis Tab.
If you want to expand tabs into spaces when Texting a file, use the Expandtabs
option:
Some file names are hardcoded into Qedit.
This section describes these file names for Qedit/UX.
This is an optional file that is designed to
contain configuration commands. You cannot change this file name. Even if you
move Qedit/UX to a different directory, Qedit/UX still looks for
/opt/robelle/qeditmgr as the default configuration file.
In addition to the system wide
/opt/robelle/qeditmgr, each user can have a personal (optional) configuration
file. When you invoke Qedit/UX, it reads commands from the file .qeditmgr in
your home directory.
This is the name
of the Qedit/UX help file. You can override this name, using Set Filename Help:
/set
filename help /usr/local/help/qedit
Qedit has a Line mode and two full-screen
modes: Visual mode and Screen mode. Visual mode is designed for HP terminals
such as the 700/92, PCs running an emulator such as Reflection, or
"hpterm" running on a UNIX workstation or X-terminal. If you are
using another brand of CRT or a generic terminal emulator (ANSI, VT100), Visual
mode will not work. Screen mode is designed for VT terminals, such as VT100 and
VT220. Other terminal types may also work with Screen mode.
By default, Qedit
assumes that you have an HP-compatible terminal. However, you can direct Qedit
to identify your HP terminal by exporting the variable RCRTMODEL with value 2.
Or you can export three variables that define the version of your terminal (see
Variables that Drive Qedit).
Qedit has a number of environment variables
that allow you to configure and direct the execution of Qedit. These variables
identify the type of HP terminal you have, the default function keys, the
default settings for the terminal G and H straps, and other options.
When you run
Qedit, it must identify the type of terminal that you are using and determine
what function-key labels to display. Qedit does status requests to detect the
model number and the current width of display memory. This information is used
to enhance the functioning of Qzmodify, Visual, Help and List. Qedit locks the
keyboard during terminal identification and discards any user input that
manages to get through. However, if you have Reflection typeahead enabled,
Qedit cannot lock the keyboard; be careful not to type during terminal
identification in this case.
Qedit sets three variables to remember your
terminal state: RCRTMODEL, RPCVERSION and RCRTWIDTH. If you run Qedit and these
variables are already set, Qedit does not need to do the status requests of
your terminal. To reset these variables and force Qedit to re-identify the
terminal, use the Set Visual Stop command. You can set a fourth variable,
RCRTSTRAPSGH, to request nondefault handshaking in Line mode. The fifth
variable, RLABELDEFAULT, is described under "Function Key Label
You must set and export environment variables
before you invoke Qedit. The syntax for setting environment variables depends
on which shell you are using.
Bourne (sh) and
Korn (ksh) shells:
In some versions
of the POSIX shell, you might have to split the previous command in two:
$RCRTMODEL=2
$export
RCRTMODEL
C shell (csh):
Remember to always
type the variable name in uppercase letters. The Bourne and Korn shells do not
allow spaces before the "=". To check your environment variables use:
Bourne (sh) and
Korn (ksh) Shells:
C Shell (csh):
If you use either an HP terminal (e.g., 239x and 700/9x series) or a terminal emulator such as Reflection, you can get
Qedit to identify the terminal type automatically by setting an environment
variable. If you use a VT terminal, you should either not set the variable at
all or set it to zero.
If you set the
environment variable RCRTMODEL to 2 and export it before running Qedit, Qedit
can identify your terminal, Reflection emulator or Qcterm emulator
automatically. This includes the terminal ID number such as 70092 or 2392 and
the Reflection or Qcterm version number such as 430. For Reflection, Qcterm and
700/9x terminals, Qedit also
determines how many columns of display memory you have set originally. On a PC
with Reflection, Qedit detects whether your combination of VGA adaptor and
Reflection version is likely to switch into 132-column mode whenever more than
80 columns of display memory are requested.
|
Qcterm
version 2.0 or higher is required to use Qedit's Blockemulation mode.
|
Qcterm
emulates a 700/92 terminal but can display 200 columns as well as 80 or 132
columns normally available on a 700/92 terminal.
|
export
RCRTMODEL=2 {sh/ksh}
/opt/robelle/bin/qedit
Qedit/UX.
Copyright Robelle Solutions Technology Inc. 1977-2000.
qux/verify
visual {e.g.,
Crt=7009,Col=132}
Qedit takes
advantage of any features that it finds, such as widening display memory,
enabling wordwrap if you have done Set Vis Wordwrap On, enabling
Limited-Immediates in block-mode, resetting display memory to the width it had
at startup, etc.
Instead of setting
RCRTMODEL to 2, you can set it to the actual terminal ID number, such as 2392.
RCRTMODEL can have any of these values:
|
Value
|
Terminal
|
|
0
|
Assume that you
are using a 2392-style HP terminal
|
|
1
|
Not using an HP
terminal, don't check it
|
|
2
|
Interrogate the
terminal to identify it
|
|
1234
|
This terminal or
emulator is not fully-compatible with an HP terminal
|
|
2392,etc.
|
This is a newer HP
terminal with labels
|
|
2393/2397
|
This terminal can
have up to 160 columns of display
|
|
7009
|
A 700/9x terminal
with 132-column ability
|
You would also set
the RPCVERSION and RCRTWIDTH variables to describe the rest of your terminal's
attribute. When you use rcrtmodel=2,
you don't set RPCVERSION or RCRTWIDTH. Qedit does not update your environment
variables with the identity that it finds since a child process cannot change
the parent's environment on HP-UX.
Type 1234 Terminal or Emulator
Set the RCRTMODEL
to 1234 if the terminal or emulator you are using does not support all the
standard HP terminal features. For example, you should use this setting with
hpterm. hpterm is a UNIX terminal emulator running under
the X window system. It's a basic 2392 emulator. hpterm will not identify
itself to Qedit, nor let Qedit change the display width by Escape sequence
(although you can configure the display width manually).
You need an
X-windows server. A Unix/Linux workstation usually have this, or you can
download and install one of the existing X-window systems available for
Microsoft Windows such as X-win32 from Starnet Communications (www.starnet.com)
or Winaxe from LabF.com.
If you are not
already familiar with hpterm, you should be able to start hpterm with:
/usr/bin/X11/hpterm
-display 192.168.0.1:0.0 -ls
where 192.168.0.1
is your PC's IP address. The "-ls" argument requests that
/etc/profile and .profile be executed so your environment is set as if you used
login.
When RCRTMODEL is
set to 1234 before you run Qedit, Qedit functions in the following way:
1.
It accepts hpterm as an hp terminal that is capable of
more than 80 columns of display memory and of doing full-screen mode.
At the moment, hpterm cannot support the line-mode Visual strategy for
HP-UX 11 (Blockemulation).
Qedit actually accepts any hp terminal emulator
without question, so this option may be useful with other emulators.
2.
If you set RCRTWIDTH
to some value between 81 and 256, Qedit accepts it as the manually set display
width.
3.
If you do not set RCRTWIDTH, Qedit attempts to sense
the current display width of hpterm and sets the jcw itself. The maximum width
is 256 columns. Qedit can support up to
999 columns but, in these instances, the width has to be entered using the
RCRTWIDTH variable or the Set Term Columns
command.
4.
Qedit sets the option that eliminates changes to
display width: Set
MarginFixed On.
This
option also ensures that the right margin is always set at the right edge of
the display width. Normally the right margin is set at the last valid column of
the file, which might be less than the display width. You can use this option
with other emulators if you wish to stop Qedit from changing the display width.
Please
read the section on Set
Visual Marginfixed
to learn about its advantages and disadvantages.
5.
The only way to change the display width with hpterm is
manually. If you use the Set Term
Columns command to specify a new width, Qedit prints the following message and
waits for you to change the width manually:
Please
change display width and press Enter:
Qedit
does not verify that you have done this correctly, so if you make a mistake, do
another Set Term Columns command to fix the width.
6.
Set Visual
Stop
normally resets all the jcws to their default state, forcing Qedit to
re-identify the terminal. However, for hpterm, the RCRTMODEL and RCRTWIDTH jcws
are not reset, since the terminal cannot
be identified automatically. If you wish to stop using 1234
mode, you must reset RCRTMODEL to 0 manually.
7.
Set Visual
Widen
should normally be set to 76 or 80 (default) with hpterm. Otherwise you will
not be able to use the extra columns beyond 80.
RPCVERSION contains information about the
terminal emulator e.g. Reflection or Qcterm. If you are not using a terminal
emulator, you can set RPCVERSION to 1. If you omit it or set it to 0, but you
do set RCRTMODEL to 2, Qedit attempts to identify which (if any) version of the
emulator you are using.
If you are using
Reflection, the version number has a direct impact on Qedit's behavior in
full-screen mode. Qcterm's version currently does not have any impact. If you
always use the same version and emulator, set RPCVERSION to the value determined
by this chart:
wXyyy,
where
w=0
for display width can be expanded
1
for display width cannot be expanded
2
for 132-column VGA in DOS Reflection
X=0
for DOS Reflection
1
for Macintosh Reflection
2
for Windows Reflection
5
for Qcterm
yyy=version number (420 = 4.20)
For example, R1
for DOS version 4.30 with a 132-column VGA adaptor would be 20430.
You cannot do the
:Reflect command if Xyyy equals 150 or 200. This same value is shown in Verify
Visual as {Reflect=420}; if it says "Col=80 max", this PC emulator was unable to
make display memory wider.
Most HP terminals have 80 columns of display
memory. However, 700/9x terminals can switch into 132-column mode and
Reflection emulators can have as many columns of scrollable display memory as
you wish. If you do not set RCRTWIDTH, Qcterm emulates a 700/92 terminal but
can display 200 columns as well as 80 or 132 columns normally available on a
700/92 terminal.
Qedit will query
the terminal to see how wide display memory is at startup. Qedit must determine
the width of display memory in order to properly fold listings of lines that
will overflow that width, and to reset the width after it has been changed.
To change the Line
mode display width while within Qedit, do Set Term Columns.
You can set the RLABELDEFAULT variable to
specify what function key labels appear upon entry into Qedit.
|
Value
|
labels
|
|
0
|
don't care
|
|
1
|
terminal lacks
labels
|
|
2
|
show user keys
|
|
3
|
show modes keys
|
|
4
|
no keys -- blank
|
|
5
|
F1 to F8 labels
|
|
6
|
Qedit's labels
|
If you wish to use
Qedit's function keys in Line mode, set the RLABELDEFAULT variable to 6 before
running Qedit. You must have the G and H straps set to "yes" for the
function keys to work.
The G and H straps of the HP terminal control
datacomm handshaking. If you pull up your Terminal Config screen, it should
look something like this:
InhHndShk(G)
YES Inh DC2(H) YES
Since these are
"inhibit" straps, YES actually means "no, don't do the
handshake." G and H control whether
the terminal waits for a DC1 and/or DC2 prompt character from the computer
before sending input (such as on terminal status requests, or upon pressing
Enter in block-mode). If the straps are configured incorrectly, the symptom is
a hung terminal (i.e., the terminal is waiting for a prompt that is never going
to come, or the terminal sent the data before the computer was ready because it
didn't wait for the prompt).
To override the G
and H strap settings of your CRT, use the RCRTSTRAPSGH variable. The default
value for Qedit/UX is 3, which means no handshake (G=YES, H=YES, inhibit both).
A value of 0 means use handshaking and may be necessary if you "shl"
to an MPE system and use terminal-based typeahead. Unfortunately, a 0 value
makes function keys lock up in Line mode Qedit/UX.
The valid values
for the RTSTRAPSGH variable are as follows:
|
Value
|
G
|
H
|
comment
|
|
0
|
no
|
no
|
(handshaking
active)
|
|
1
|
no
|
yes
|
|
|
2
|
yes
|
no
|
|
|
3
|
yes
|
yes
|
(default for
HP-UX)
|
If the QEDITMGRTRACE variable is set to a
nonzero value, Qedit prints tracing messages for the Qeditmgr configuration
files. The trace includes the name of each Qeditmgr file that Qedit attempted
to open, each command executed from the file, and command line arguments used
to invoke Qedit.
Qedit updates a variable, QEDCURWFILE, with
the name of your current or last workfile. This gives you the ability to
reference the current workfile easily from within a shell script without having
to pass it in as a parameter.
When the Qedit for Windows client establishes
a new connection, it transmits information about the passwords included in the
request. Qedit updates two variables with the information: QEDSTOREDPWD and QEDPROMPTEDPWD. The first
variable indicates which passwords are stored with the connection. The second
variable indicates which passwords are prompted for.
Values for these
variables only have one character: the letter U
representing the user password. Since there is only one password, the letter
can only appear in one. The other variable in this case is not created at all.
For example, if the password is stored with the connection, QEDSTOREPWD will have a value of
U and QEDPROMPTEDPWD will not exist at
all.
This gives you the
ability to reference these variables from within a shell script.
Qedit looks for the files it needs in the
/robelle directory. Normally, Qedit is installed in /opt/robelle. For example,
the Qedit server expects to find its log files in a subdirectory called
log/qedit. It would expect to find the error log file in
/opt/robelle/log/qedit/error.log
which is the
default full path name of the error log. If you install Qedit in a directory
other than /opt/robelle, Qedit should be able to determine the new location and
adjust the path for its support files (e.g., online help for host-based Qedit,
log files for the server).
If Qedit is unable
to correctly determine its current location, it is going to revert back to
/opt/robelle.
If you wish to use
a specific path explicitly, you need to set the ROBELLE environment variable to
the new directory. For example,
ROBELLE=/usr/apps/robelle
export
ROBELLE
There are two
limitations to the path name: the full path name of the file must be no more
than 240 characters, and the path name to the /robelle directory must be no
more than 219 characters. A slash mark (/) is optional at the end of your
ROBELLE environment variable. To set up the log files in the new directory, you
have to manually create the "log" or "help" subdirectory in
the alternate search path.
So, in order to
determine the location of support files, Qedit goes through the following:
·
Uses the ROBELLE variable, if it exists.
·
If the ROBELLE variable does not exist, Qedit
tries to identify the location it is running from and, if successful,
determines the location based on that information.
If the information
from the previous steps is not available, Qedit assumes the files are in the
/opt/robelle directory.
Qcat is a filter program similar to cat and
zcat. Qcat reads a set of Qedit files and prints the lines on standard output.
Type man qcat for more
information.
qcat
QeditFile > TextFile
We have tried to make the MPE and HP-UX
versions of Qedit as compatible as possible. This section describes how
Qedit/UX is different from Qedit/MPE.
Qedit/UX uses
three forms of workfiles: original, Jumbo, and Wide-Jumbo. The Wide-Jumbo
format is new and is used for most files on which you use the Text command. On
HP-UX, the original format is unable to save some information about your file (due
to technical differences in how the Qedit workfiles are stored on MPE versus
HP-UX). Once you shut an original file, the following is lost:
·
The name of the file from which you texted.
·
The current line number.
·
The ability to immediately reopen the file and
"Undo" changes.
·
The settings for Set Left and Set Right.
For these reasons,
Wide-Jumbo workfiles will be the standard in Qedit/UX.
Qedit/UX does not
allow substitution of the current file name into shell scripts and commands,
because the asterisk (*) is an important substitution character in HP-UX. For
example,
cannot compile
your current file. Instead, it compiles all files in your current directory.
The following
features do not work in Qedit/UX:
·
Beginfile/Endfile commands.
·
Hints are not available.
·
Verify to a line printer.
·
Any MPE-style command such as :Pause, :Run, etc.
·
Proc command, except for Up and Down.
·
I/O redirection of Qedit commands.
·
Spell and Words commands.
·
Out= option of the Listredo command.
·
User Defined Commands and command files.
·
The QEDITCOUNT variable
Qedit operates in Line mode or Visual mode,
depending upon the type of terminal. The same commands are used in both modes.
In Line mode, you do everything with commands. In Visual mode, you do most
editing with built-in functions of your terminal, but use commands for some
things. Line mode commands work in Visual mode, and Visual mode function keys
work in Line mode.
Here we describe
the Qedit commands in alphabetic order. For each command, we show both the
longest and the shortest name that Qedit can recognize, as in Add [A].
Highlighted terms (e.g., linenum) and
jargon words (e.g., "workfile") are defined in the "Glossary".
The Visual
command
is described only briefly in this section: see the chapter "Getting A
Quick Start with Full-Screen Editing" for full details.
Here are general
guidelines that apply to using the Qedit commands.
Each Qedit command has a name such as List
that you can abbreviate to any leading subset. Thus, L means List. Some
commands require more than one letter: GARbage, DEStroy, RENumber, SHut,
VIsual. You may append option letters to the command: Q, T, or J. Q means
"quiet", T means "template", and J means various things,
depending on the command.
list
all {fully spelled out}
l
@ {maximal abbreviation}
lq {list quietly}
listqt {list quietly, with template}
lqjt {list quiet, jumping, with template}
list
$ {most recent external file name}
s
dec on {Set Decimal command}
sh {Shut command}
You can enter the commands in uppercase or
lowercase. Shell commands such as ls and cd can only be in lowercase. These
commands are identical:
LIST
ALL {uppercase}
list
all {lowercase}
You can enter several commands on a single
line, if you separate them with semicolons. The maximum command line is 256
characters, and \ is not supported for continuation. If you want to have an
HP-UX command or a calculator command in the stack, you should enclose it in
parentheses. This prevents Qedit from passing the rest of the line as
parameters. For example,
List
5;!find . -name testfile -exec cat {} ;
{fails}
List
5;(!find . -name testfile -exec cat {} ;)
{works}
If the syntax
requires semicolons and parentheses, you have to put the problematic command in
a shell script and use it in the command list instead.
Any error causes
Qedit to flush the remaining commands in the line.
list
505;add *-1 {list line 505; add just
before it}
shut;who
When combining
Qedit commands, be certain to use the same quote character in all the commands.
Wrong:
/c7/7"DISPLAY";c\.\\
Right:
/c7/7"DISPLAY";c".""
You may annotate Qedit commands by putting
comment text in curly braces at the end of the line:
keep
sample,yes {update disc file}
Such comments are
recognized at the "/" prompt, in usefiles, as well as Visual's home
line and Next? prompt and List's More? prompt.
You can stop most Line mode functions by
pressing the Control-Y key. For example, to stop an inadvertent List ALL, use
Control-Y. To stop the Add, Modify, or Replace commands, use either Control-Y
or two slashes (//).
Some commands have no alphabetic name. In
Line mode, pressing only Return means display the next line and a backslash (\)
means display the previous line, $ means enable Memory Lock and $- means
disable Memory Lock. In either mode, ? means Help, any line number means go to
that line, a string means display the next line with that string, and
"^" means search backwards for a string:
|
55
|
find and display
line 55 or higher
|
|
FIRST
|
find and display
first line
|
|
;;;;
|
display the next 5
lines
|
|
\
|
display the
previous line
|
|
-5
|
move current line
back 5 lines
|
|
"string"
|
display next line
with string
|
|
^"string"
|
display previous
line with string
|
|
$
|
turn on memory
lock at this line
|
|
$-
|
turn off memory
lock
|
Qedit accepts the eight user function keys of
HP terminals as one-keystroke abbreviations for useful functions:
|
F1
|
Go into Visual;
Update/Getnext if in Visual
|
|
F2
|
Roll the screen up
6 lines; browse
|
|
F3
|
Findup (find
previous line with current string)
|
|
F4
|
Find (find next
line with current string)
|
|
F5
|
Browse Backward
One Page
|
|
F6
|
Browse Forward One
Page
|
|
F7
|
Listredo (line) or
execute ===>
line (Visual)
|
|
F8
|
Exit from Qedit or
Exit from Visual to Line mode
|
^1 through ^8 are
another way of invoking the user function keys in Line mode.
Qedit accepts most HP-UX commands and
scripts. If the shell command matches an existing Qedit command, you must
precede it with a colon (:) or an exclamation (!). See Running Qedit on HP-UX for more details.
Any command that begins with an equal sign
(=) is treated as a calculator expression. This feature can be used to compute
temporary values and do conversions from one number base to another.
Adds lines into the workfile. There are five
varieties of Add that cover all the ways you can add lines into a Qedit
workfile:
|
NEW
|
Add new lines to
your workfile from Stdin.
|
|
STRING
|
Add a new line
from the command prompt.
|
|
COPY
|
Copy lines from
one place to another.
|
|
MOVE
|
Move lines from
one place to another.
|
|
FILE
|
Bring lines in
from an external file.
|
Add some new lines from the terminal
keyboard. Insert them at a given line number or after it.
ADD [ linenum ]
(Q=no linenums, J=justified, T=template)
(Default: linenum
= *)
The linenum parameter specifies where to add
new lines and also determines the increment between new lines. If linenum is 9.1, lines will be
incremented by 0.1; if 9.01, then 0.01. If linenum
already exists, Qedit increments it and begins adding after the existing
line. If linenum is 0, Qedit adds new
lines before the first existing line in the file. If you don't say which linenum, Add inserts the lines after the
current position (*). (See Miscellaneous Points below.)
Examples
/add
5 {add new lines after line
5}
5.1
line a {Qedit prompts with line
number}
5.2
line b {you enter line of text
and Return}
5.3
// {you enter // or
Control-Y to stop}
/aq {add after * line; no prompt}
This
is new text
// {end the Add command}
Temporary Workfile
If you do not have a named workfile Open when you Add, Qedit
automatically builds a temporary workfile for you. This file has a random file
name and is created in /var/tmp
by default. If you want to have temporary files in a different directory, enter
the new path name in the TMPDIR environment variable.
TMPDIR=/home/user1/tmp
export
TMPDIR
Keep in mind that Qedit works with
absolute filenames and these names can not have more than 240 characters.
If you make any changes to the file (e.g., by adding lines),
Qedit will ask if you want to save your changes when you exit.
Using the Tab Key
By default, Qedit defines tabs every 8 columns
across the line (every 10 for Qedit/MPE). You can override these default tab
stops using Set Tabs Stop n (every 2
to 15 characters) or Set Tabs 5 10 22 28 ... for completely custom tab stops.
When you press the tab key as you Add lines, Qedit correctly inserts spaces in
your lines and skip to the correct column on your screen (assuming you are
using an HP terminal).
Overflowing Lines or Line
Numbers
The Add command continues prompting until you
press Control-Y, or you type "//" at the end of a line, or you run
out of line numbers. When you exhaust the line numbers possible between two
lines, Qedit prints "Error: Already". You can continue by doing a
range Renumber on the area where you wish to add more lines. Thus, if your last
line added was 4.999, use Renum 4/5 to spread out the lines between 4 and 5.
You can configure Qedit to automatically
renumber part of the file so that you do not have to renumber it manually. See
the Set Visual Renum option.
Line Wraparound
If you enter a line that is too long, Qedit
divides it into several lines. Set Wraparound ON divides lines on
"word" boundaries only. Any words that will not fit on the current
line are moved to the next line. If only a small number of words are moved to
the next line, Qedit prompts you to complete the line. To end the Add when this
happens, press Return before typing "//". If you are editing FORTRAN
source code, Qedit generates a valid continuation line for you.
Automatically Indenting
Lines
AJ for justified is a special option to
indent new lines. The linenum you
specify must be an existing line. You enter new lines beneath it. Qedit will
then indent the new lines by exactly the same number of spaces as the existing
line. You can shift the indentation left by typing {'s at the start of a line,
or shift it right with }'s. To redefine the { and } characters, use Set Zip.
Modifying a Line During
Add
When you know you made a typo, and prefer to
fix it now instead of going on, the auto-modify character will help you. Enter
the command Set Zip []@{}#, or better yet, put it in your Qeditmgr
configuration file. The # character (or other special character of your choice)
is called the auto-modify character. It allows you to modify the line you are
currently entering. Type "#" at the end of the line, and Qedit
redisplays the line for you to modify. When you are done with the Modify, you
press Return to continue adding new lines.
Miscellaneous Points to
Note
If you have Set Left/Right margins, the new
lines added will have spaces to the left and right of the margins. That is, the
line you enter will be left-justified within the current margins of the
workfile.
The maximum default increment between new
lines is 1.0 (or 0.1 for standard COBOL files). You can change this default
with Set Increment.
You can ask Qedit to remove nonprinting
characters from your input lines using Set Editinput Data ON. If you do not
wish to allow the extended Roman-8 characters, use Set Editinput Data ON Extend
OFF.
Add one new line, with the text coming from a
string in the command itself. This is handy when you need some literal text
within a User Command or Use file, but don't want to create a temporary file to
hold it.
ADD linenum string
(Q=no linenums, J=justified, T=template)
(Default: linenum
= *)
The linenum parameter specifies where to
insert the new line containing the string.
Examples
/add
5 "new line"
5.1
new line
/add
10.01 "change datasetdata setall"
10.01
change datasetdata setall
Add lines by copying duplicates of existing
lines.
ADD linenum = rangelist
(Q=no display)
(Defaults: none)
The linenum parameter tells Qedit where to
insert the copied lines. The number of decimal places in linenum tells Qedit how finely to number the new lines:
/add
50 = 1/9 {new lines will be
50.1, 50.2, 50.3...}
/add
50.10=1/9 {new lines will be
50.10, 50.11, 50.12...}
The rangelist parameter tells Qedit which
lines to copy:
/add
50.1 = 1/9 10/15 {'1/9 10/15' is the rangelist}
Examples
/list
4/8 {how lines look before
the copy command}
4
aaaaaaaa
5
bbbbbbbb
6
cccccccc
7
dddddddd
8
eeeeeeee
/add
5 = 7/8 {copy lines 7 and 8
after line 5}
5.1
dddddddd
5.2
eeeeeeee
2
lines COPIED
/list
4/8 {how lines look after
the copy command}
4
aaaaaaaa
5
bbbbbbbb
5.1
dddddddd
5.2
eeeeeeee
6
cccccccc
7
dddddddd
8
eeeeeeee
/aq
5 = 5 {duplicate line 5
after itself}
Notes
Add prints each
new line, unless you use AQ. When you copy lines, the rangelist must not include the linenum
(e.g., /Add 5 = 4/6 is rejected because it would be an infinite loop).
Qedit prints "Error: Already". The lines copied are not deleted from
the original location. You now have two copies of the lines (and a copy in the
Hold0 file, see Add-Move).
If you have Set Left/Right margins, Qedit
prints only the portion of each line within the margins. However, it will
actually copy the entire line, including the portion outside of the current
margins.
Move some lines from one place in the file to
another, deleting them from the original position.
ADD linenum < rangelist
(Q=no display)
(Defaults: none)
The linenum tells Qedit where to move the
lines. The number of decimal places in linenum
determines the line number increment. For example, "/add
5.10<100/200" creates lines 5.10, 5.11, 5.12, etc.
The rangelist tells Qedit which lines to
move. Add deletes the original lines after moving them. You still only have one
copy of each line.
Examples
/list
4/7 {how lines look before the
move}
4
aaaaaaaa
5
bbbbbbbb
6
dddddddd
7
cccccccc
/add
5 < 7 {move line 7 after line
5}
5.1 cccccccc
1
line MOVED
/list
4/7 {how lines look after the
move}
4
aaaaaaaa
5
bbbbbbbb
5.1
cccccccc
6
dddddddd
Notes
Control-Y during a
move stops the move, but it also changes the move into a copy. The lines being
moved in the current range are not deleted.
Add-Move ignores Set LEFT/RIGHT margins; it
moves entire lines. However, it only prints the portion of the line within the
current margins.
When you copy or move lines using Add= or
Add<, Qedit first puts the lines into a "Hold" file called Hold0.
It then counts the lines. If you do not have sufficient line numbers to insert
the new lines, Qedit stops and prints "Error: Already". Use Renum to
renumber the range of line numbers and then copy the lines from the Hold0 file.
See also the Hold command.
/list
hold0
/add
55=hold0 {add from Hold file}
Add lines to the workfile from an external
file.
ADD linenum = filename [,UNN]
[ rangelist ]
(Q=no display)
(Default: entire file)
The linenum tells Qedit where to begin
adding the lines from the external file.
The filename tells Qedit which file to copy
from. It can be any type of disc file. If any of the lines are too long, they
will be truncated with a warning. Use filename,UNN
when you are adding from a data file with numeric characters in the last eight
columns which are not really sequence numbers.
The rangelist tells Qedit how much of the
file to copy. The default is to copy the entire file. If the external file does
not have sequence numbers, Qedit assumes that the file is numbered from 1 by
the current Set Increment. When you specify a rangelist, Add leaves a copy of
the lines from the external file in the Hold0 file, as well as in your
workfile.
Examples
/add
500.01 = abc {copy in the file ABC
after 500.01}
500.001 abc line-1 {prints each line copied from file}
500.002 abc line-2 {prints new line numbers too}
/aq
5 = xyz 5/10 {copy in lines 5/10 of the file XYZ}
/l
template "$page"(up) {list page breaks in a file}
1
$PAGE "xx" {select
the template you want}
24
$PAGE "yy"
37
$PAGE "zz"
/add
5=template 24/36 {copy the lines
between $pages}
/shut
/dev/src/test.c {establishing
"previous" file}
/new
cust {open another file}
/a
1 = $ 50/60 {$ stands for
/dev/src/test.c}
Notes
Add prints each
line as it copies it, unless you use AQ. If Qedit finds invalid sequence
numbers in a file, it begins assigning "logical" sequence numbers
using the last valid sequence number and the current Set Increment.
If you have Set Left/Right margins, Qedit
inserts blanks before the left margin in each line. That is, the lines from the
external file are left-justified within the current margins of the workfile.
Appends a string to the end of each line in
the rangelist.
APPEND "string" [ rangelist ]
(Q=no display)
(Default: rangelist
= *)
Append allows you
to add a semi-colon (or any other string of characters) to the end of a line
(/AP ";" 5/10). Append prints each line that it changes. If the
resulting line would be too long, Append goes into Modify on that line.
Examples
/list
25
25 to the end of the line
/append
"!"
25
to the end of the line!
/ap ")" 1/4
1
(redo function)
2
(modify function)
3
(append function)
4
(list function)
Starts "browsing" the current file
by displaying one page "backward". You stay in "browse"
mode until you enter any command (see List, jumping option).
BACKWARD
(F5 key does the same)
In Line mode,
Backward and Forward (or F5/F6) throw you into List-Jumping's browse-mode.
Qedit displays a screen of text, where the screen size is either 23 lines or
what you specify with Set List LJ, then waits for you by asking
"More?". Press Return to see the next screen. Typing a line number
moves you to the screen starting at that line, pressing F2-F6 does the
appropriate action, and F8 or "//" or Control-Y or typing any command
gets you out of browse-mode. At the "More" prompt, the *
"current" line is the last line displayed.
Repeat any combination of the previous 1,000
command lines, with or without editing.
BEFORE
[
start [ / stop ] ]
[
string ]
[
ALL | @ ]
(Default: redo previous line)
(BQ=redo without change)
(BJ=listredo)
The Before command
allows you to modify the commands before it executes them. If you don't need to
change them, use BQ or :Do. Commands are numbered sequentially, starting with 1
for the first command entered and, by default, the last 1,000 commands are
accessible. This numbering sequence applies only to the temporary redo stack,
because this stack is discarded when you exit Qedit. The numbering sequence in
a persistent redo stack, which is accessible across Qedit invocations,
continues between invocations. Use the :Listredo or BJ command to display the
previous commands. You can redo a single command, a range of commands, or the
most recent command whose name matches a string.
The Before command
uses Qedit-style Control characters for modifying the commands. The default
mode is to replace characters. To delete use Control-D, and to insert use
Control-B. If you prefer HP-style modify (D, R, I, and U), use the :Redo
command instead of Before, or do Set Modify HP.
Examples
/ls
/users/obb
{"bob" is not spelled right}
/users/obb
not found
/Before {redo most recent
command}
ls
/users/obb {last command
is printed}
bob {you enter changes to it}
ls
/users/bob {the edited
command is shown}
{you press
Return}
/listredo
-10/ {show last 10
commands}
/before
5 {redo 5th command
in stack}
/bef
8/10 {redo 8th
through 10th}
/b
ls {redo last ls
command}
/b
@temp {redo last
containing "temp"}
/before
–2 {redo command
before previous}
/before
-5/-2 {redo by relative
lines}
Notes
HP-UX reacts to certain control characters which might
conflict with the Qzmodify codes. For example, control-D sends an end-of-file
signal to HP-UX but is also the delete character in Qzmodify. You should use
the HP-UX stty program to change the
default end-of-file signal. Please see the section "Control
Characters and stty" on page 48 for
more details.
If you wish to
change any characters within the line, the modify operators are the regular
Control Codes used in Qedit:
Any printing
characters replace the ones above.
Control-D plus
spaces deletes columns above.
Control-B puts you
into "insert before" mode.
Control-A starts
appending characters at the end of line.
Control-A,
Control-D, plus spaces, deletes from the end.
Control-T ends
Insert Mode, allowing movement to a new column.
Control-G recovers
the original line.
Control-O
specifies "overwrite" mode (needed for spaces).
Change current working directory.
CD [directory]
(Default: $home directory)
You can switch
directories using the cd command. The cd command affects your Qedit processes
and any processes that you create. When you exit Qedit, you will be in the same
directory that you were in when you invoked Qedit.
Examples
cd
/usr/local/bin
cd {return to home}
cd
$HOME {return to home}
cd
~ {return to home}
cd
$SAVEDIR {Error!!!}
The last example
shows a limitation of cd inside Qedit. You can't refer to a directory name that
is saved in a variable, because Qedit simulates the cd command, instead of
passing it to your shell program for execution. Qedit does not simulate the
shell command processing such as variable substitution. (The three special
cases for "home" are hardcoded into Qedit's cd.)
In addition, a few things still do not work
well when doing shell commands in Qedit. If you launch a command in the
background using "&", the jobs command will not show the status
of it. If you set an environment variable, it will not be set for Qedit. Both
of these problems are caused by the fact that shell commands are executed by a
child process which is unable to change the status of Qedit.
Changes one string or column range to another
string in some or all of your lines. There are two basic varieties of Change:
|
STRINGS
|
replace one string
with another
|
|
COLUMNS
|
replace a column
range with a string
|
Replaces one string of characters by another
string, the two strings being separated by a single quote character.
CHANGE "string1"string2" [ rangelist ]
(Q=no display, J=verify, T=CobX Tag)
(Default: rangelist
= *)
The string1 tells Change what string of
characters to find. The default for string1
is the last string used, and you specify this default via the null string
(e.g., change
""xxx"). The null string recalls the last string and the
window used with it. If the target string1
occurs more than once in a line, Qedit changes every occurrence.
The string2 tells Change what characters to
substitute. In this format of the Change command, only three quote characters
are used to define the two strings, not four as you would normally expect.
Another oddity is that string2 does
not become the current string. This is so that you can do another Change or
Find command using "" as the target (i.e., the last string), finding
and fixing multiple occurrences of the same string (e.g., find "nad"; CH
""and"; F; CH ""and"; ...). The third
difference of string2 is that a null
string for this parameter actually means "null". change "very"" 100 means
remove "very" from line 100.
The rangelist tells Change what lines to
search for string1. The default rangelist is the current line only.
If string2 is shorter than string1 (e.g., change "Robert"Bob"),
Qedit shortens the line by shifting the rest of the line left. If string2 is longer (e.g., change "Bob"Robert"),
Qedit lengthens the line by shifting characters right. If string2 is so much longer that the line would be too long, Qedit
sends you into the Modify command to fix the line by hand.
Change prints each
line that it updates, unless you use CQ.
Examples
/list
55 {display line with
mistake}
55
select lines contaning both of two
/change
"contan"contain" {change string in current line}
55
select lines containing both of two
/change
"sub"subindex" all
{make a global change}
10
subindex = subindex + 1
11
table(subindex) = 0
213
if subindexway = 0 {oops-bad
change!}
/cj
"cust"Customer" 200/300
{change with user approval}
225
Display Customer {shown for
approval}
Change
okay (Y,N,or Modify) [No]: yes
/list
9 {display line to review}
9
The test results were very exciting.
/c
"very"" {remove
word, change to null string}
9
The test results were exciting.
/find
"wiith" {search forward for
line with error}
99
the string is combined wiith the second string
/c
""with" {change
"wiith" to "with"}
99
the string is combined with the second string
Using Alternates to Quote
You may select your own quote character if
you find " too much work because it is a shifted key. Among the
alternatives are \ : and ' (apostrophe). See the "Glossary"
for more on strings and other alternates to quotes.
/c
:wiith:with:
/c
\wiith\with\
Approving Each Changed
Line
Use CJ to give yourself approval over each
change before it is updated. With CJ, Qedit displays the line as it would be
and asks you for a Yes, No, or Modify answer. Use CJ when you have trouble
working out the precise strings to change.
Searching for Two Strings
at Once
Because the rangelist can contain a search string, you can actually select
lines containing both of two strings:
/c
"xxx"filename" all
{"xxx" becomes "filename" in ALL}
/c
"xxx"filename" "rename" {line must contain "rename" too}
Including a Window
The form of Change command just described
requires only three quotes per command, but does not allow all options. You
cannot specify a special window - you
will always use the default Set Window value. To do a Change with a special
window, you must specify four quote characters, two for each string:
CHANGE "string1" (window)
"string2" [ rangelist ]
Each string is
delimited by two quote characters and the two strings must be separated by a space
or a comma. Between the two strings you may insert a window such as (SMART) or (20/30) or (UPSHIFT).
Changing Within a Column Range
If you insert a column window, Qedit changes
only the columns within the window.
Columns outside the window are
untouched:
/change "CUSTREC" (10/39)
"CUSTOMER-RECORD"
In this example,
"CUSTREC" is expanded to "CUSTOMER-RECORD", but the data at
column 40 and beyond is not moved. In addition, the Change must not cause the
rest of the window to overflow.
Changing Uppercase and
Lowercase
If you specify an upshift window, Qedit
ignores the case of letters when matching the target string. It will match
words that are spelled with caps or without:
/change "JONES" (upshift)
"Fitz-Jones" all
In this example,
Change selects lines containing "JONES", "Jones", or even
"joneS".
Avoiding Changes to
Embedded Words
If you specify a Smart window, Qedit rejects
those matches in which the target string is actually in the middle of another
word:
/change "FRANK" (smart)
"Frank" all
This example
selects "FRANK", but reject "FRANKLYN." You can combine
Smart and Upshift.
Patterns and Windows
In other commands the window can specify a pattern to
match. In the Change command patterns are not allowed, because Change cannot
perform pattern changes. However, a string specified in the rangelist portion
of the Change command may be a pattern. For example:
/change
"CUSTREC" "CUST-REC" "@01@PIC@" (pattern)
{change custrec to cust-rec in
all lines that}
{ also contain "01" and
"PIC" in that order}
CobX Tags
Cobol tags are short strings stored in
columns 73 to 80 of CobX source files. The Cobol tag value is defined using the
Set X command. Once enabled, updated lines and added lines are automatically
updated with the tag. They can also be modified manually with custom tag values.
In its regular
form, the Change command affects only the text area in columns 7 to 72. If you
wish to make changes to Cobol tags, use the T
suffix. You can think of it as the Tag
option. This option operates only on the tag area itself, columns 73 to
80.
/change "CUST" "SUPP" all
{change cust to supp in all
lines. }
{ cust must be between columns
7 and 72. }
/changeT "CUST" "SUPP"
all
{change cust to supp in all
lines. }
{ cust must be between columns
73 and 80. }
To to this, the Tag option temporarily changes
the margins to (73/80).
Qedit displays a warning every time this option is used. Because the margin
values have changed, explicit column range in a Window can only be between 73
and 80.
/changeT "CUST" (50/60)
"SUPP" all
Warning: ChangeT: editing the Cobol tag area only
(73-80).
Error: Window
/changeT
"CUST" (73/80) "SUPP" all
Warning: ChangeT: editing the Cobol tag area only
(73-80).
10
SUPP0102
1 line
changed
Because the
margins have been changed, Qedit displays text in the tag area only except when
the Justify option is used. In this case, Qedit prompts for confirmation before
making the change. It would be hard to determine if a line needs to be changed
based only on the tag value. So, when the Justify option is used, Qedit
displays the complete line. The user has the option to accept the changes,
reject the changes or manually modify the line. If the user chooses to modify
the line, only the tag is displayed.
Replace some columns in some lines with a new
string of characters. Use Change to insert columns, shift text left, or shift
text right.
CHANGE column [/column] [(window)] "string" [rangelist]
(Q=no display, J=verify)
(Default: rangelist
= *)
Change replaces
the target column range with the string in the lines of the rangelist. You can use this to insert a
string at a specified column. You can also use it to replace, expand, or
contract specified columns.
If you specify a
single column instead of a range,
Qedit inserts the string before that
column and shifts the rest of the line to the right. You can create new columns
by inserting blanks in front of a position (e.g., change 5 " ").
If you specify a range of columns, Qedit
replaces that column range with the string.
The string may be the same length as
the column range, longer, or shorter. If the string is shorter than the column
range deleted, the rest of the line shifts left. If longer, the rest of the
line shifts right. You can remove columns entirely by changing them to a null
string (e.g., change
5/7 "").
Examples
/change
5"|"all {draw vertical
line of "|"s in file}
/cq
1/2 "" 10/15 {shift lines
10/15 left 2 spaces}
/cq
1 " " 10/15 {shift lines 10/15 right 3 spaces}
/cq
1(1/8)" " all {shift columns
1/8 right 1 space}
{don't change text beyond
column 8}
/change
12/12 :: {delete column 12 in the
current line}
Notes
See the discussion
of windows under "Changing
Strings". Those notes also apply to column changes.
The first column
number is usually 1, except for standard COBOL source files, where it is 7 (seven).
The last column number depends on the current values for Set Language, Set
Length, and Set Right.
Change prints each
line modified, unless you use CQ. CJ asks you to verify each change.
Shut the current work file and remove it from
the recently accessed file list.
CLose
(Default: none)
The Shut command
is the normal way to close a workfile. When you Shut a file (or Open another
one), Qedit remembers the name of the current workfile in a list of recently
accessed files. This allows you to reopen the file using open ?. However, the list is of
limited size. If you are not coming back to edit the current file again, use
the Close command instead of Shut. This keeps other file names from falling off
the bottom of the list.
Examples
/open
abc
/open
def
/close {close "def" and forget it}
/open
* {current file is now
"abc"}
Copies one or more columns to a
different location on the same line.
COLCOPY source [ /source2 ] destination1 [ /destination2 ]
[ rangelist ]
(Q=no display,
J=verify, T=CobX Tag)
(Default: rangelist
= *)
Colcopy copies text in columns specified by source1 and source2 to the destination columns specified by destination1 and destination2 in the lines of rangelist.
Even though Colcopy can modify multiple lines using a rangelist, it really operates on one line at a time. You can not
copy columns from one line to another.
Source and destination columns always represent the
original location. All changes are based on that assumption.
If source1 only
is specified, Qedit copies just that column (length of 1). If destination1 only is specified, the
source columns are inserted at that location. If you wish to replace a single
column, enter a destination range where destination1
and Destination2 are the same e.g. Colcopy 1 10/10.
/list
1
1
abcdefghijklmnopqrstuvwxyz
/colcopy
1 10 { insert column 1 at column
10 }
1
abcdefghiajklmnopqrstuvwxyz
1
line changed
/colcopy
1/5 10 { insert columns 1/5 at
column 10 }
1
abcdefghiabcdejklmnopqrstuvwxyz
1
line changed
If destination1
and destination2 are specified, text
in these columns is replaced by the source text. If the source text is narrower
or wider, the line is shortened or expanded as needed.
/colcopy
1 10/15 { copy column 1 to columns
10/15 }
1
abcdefghiapqrstuvwxyz
1
line changed
/colcopy
1/5 10/11 { copy columns 1/5 to 10/11.
Line expands. }
1
abcdefghiabcdelmnopqrstuvwxyz
1
line changed
/colcopy
1/5 10/20 { copy columns 1/5 to 10/20.
Line shortens. }
1
abcdefghiabcdeuvwxyz
1
line changed
Trailing Spaces
Trailing spaces on the line are not
significant. This means that a line can expand until a non-space character
reaches the current right margin (Set Right).
However, trailing spaces from the source text are significant and are copied in the operation. If the line can not be expanded further,
Qedit displays a warning message and allows the user to modify it.
/list
2
2
abcd efghiabcdeuvwxyz
/colcopy
1/8 20 { insert columns 1/8 at 20
}
1
abcd efghiabcdeabcd uvwxyz
1
line changed
/Set
right 30
/colcopy
1/5 30 { insert columns 1/5 at 30 }
Warning:
Source columns could not be inserted. Please modify. (Warning 2)
1
abcd efghiabcdeabcd uvwxyz
1
line modified
Overlapping Columns
When source and destination columns do not
overlap, the results are straightforward. If source and destination columns
overlap partially or completely, the results might not be as expected. Keep in
mind that:
·
source and destination columns are always based
on the original line
·
the destination columns are removed
·
the source columns are put in their place
Approving Each
Changed Line
Use COLJ to give yourself approval over
each change before it is updated. With
COLJ, Qedit displays the line as it would be and asks you for a Yes, No, or
Modify answer.
CobX Tags
Cobol tags are
short strings stored in columns 73 to 80 of CobX source files. The Cobol tag
value is defined using the Set X command. Once enabled, updated lines and added lines are
automatically updated with the tag. They can also be modified manually with
custom tag values.
In its regular form, the Colcopy command affects only the
text area in columns 7 to 72. If you wish to make changes to Cobol tags, use
the T suffix. You can think of it as
the Tag option. This option operates
only on the tag area itself, columns 73 to 80.
/ColT 73/74 79/80 all {
copies content of columns 73 and 74 }
{
into columns 79/80 }
/ColT 73/74 75 all {
inserts content of columns 73 and 74
}
{
in column 75. Columns 76-80 are shifted. }
To to this, the Tag option temporarily changes
the margins to (73/80). Qedit displays a warning
every time this option is used. Because the margin values have changed,
explicit column range in the source and destination columns can only be between
73 and 80.
/ColT 23/24 79/80 all
Warning: ColcopyT:
editing the Cobol tag area only (73-80).
Error: The
Sourcestart column (23) is not between 73 and 80
/ColT 73/74 79/80 10
Warning: ColcopyT:
editing the Cobol tag area only (73-80).
10 ME0307ME
1 line changed
Because the margins have been changed, Qedit displays text
in the tag area only except when the Justify option is used. In this case,
Qedit prompts for confirmation before making the change. It would be hard to
determine if a line needs to be changed based only on the tag value. So, when
the Justify option is used, Qedit displays the complete line. The user has the
option to accept the changes, reject the changes or manually modify the line.
If the user chooses to modify the line, only the tag is displayed.
Moves one or more columns to a
different location on the same line.
COLMOVE source [ /source2 ] destination1 [ /destination2 ]
[ rangelist ]
(Q=no display,
J=verify, T=CobX Tag)
(Default: rangelist
= *)
Colmove moves text in columns specified by source1 and source2 to the destination columns specified by destination1 and destination2 in the lines of rangelist.
The source columns are removed from their original location. Even though Colmove can modify multiple lines
using a rangelist, it really operates
on one line at a time.
You can not move columns from one line to another. Source
and destination columns always represent the original location. All changes are
based on that assumption.
If source1 only
is specified, Qedit moves just that column (length of 1). If destination1 only is specified, the
source columns are inserted at that location.
If you wish to replace a single column, enter a destination range where destination1 and Destination2 are the same e.g. Colcopy 1 10/10. A move means the original columns are removed and the
line is shifted left. Then the source text is inserted at the destination.
/list
1
1
abcdefghijklmnopqrstuvwxyz
/colmove
1 10 { move column 1 to column
10 }
1
bcdefghiajklmnopqrstuvwxyz
1
line changed
/colmove
1/5 10 { move columns 1/5 to
column 10 }
1 fghiabcdejklmnopqrstuvwxyz
1
line changed
If destination1
and destination2 are specified, text
in these columns is replaced by the source text. If the source text is narrower
or wider, the line is shortened or expanded as needed.
/colmove
1 10/15 { move column 1 to columns 10/15 }
1
bcdefghiapqrstuvwxyz
1
line changed
/colmove
1/5 10/11 { move columns 1/5 to 10/11 }
1
fghiabcdelmnopqrstuvwxyz
1
line changed
/colmove
1/5 10/20 { move columns 1/5 to 10/20 }
1
fghiabcdeuvwxyz
1
line changed
Trailing Spaces
Trailing spaces on
the line are not significant. This means that a line can expand until a
non-space character reaches the current
right margin (Set Right). However, trailing spaces from the source text are
significant and are moved in the operation.
/list
2
2
abcd efghiabcdeuvwxyz
/colmove
1/8 20 { move columns 1/8 to 20 }
1
efghiabcdeabcd uvwxyz
1
line changed
Overlapping
Columns
When source and
destination columns do not overlap, the results are straightforward. If source
and destination columns overlap partially or completely, the results might not
be as expected. Keep in mind that:
·
source and destination columns are always based
on the original line
·
the source columns are removed
·
the destination columns are removed
·
the source columns are put in their place
Here is an example:
/list
1
1
abcdefghijklmnopqrstuvwxyz
/colm
6/20 15
1
abcdefghijklmnopqrstuvwxyz
1
line changed
Apparently, nothing has changed but, in fact, something did
happen to the line. Qedit removed the source columns
"fghijklmnopqrst" and tried to insert the original text where column
15 used to be. Column 15 was part of the area that has been removed so Qedit
inserts the text where it should have been i.e. between "e" and
"u". So, it's putting the original text back where it was.
Moving Passed the
Right Margin
Destination columns
can exceed the current right margin. In this case, Qedit assumes the columns
should be moved to the end of the line. Effectively, the source columns are
inserted in the rightmost columns of the line. The destination columns do not
have to be a precise value. They just need to be larger than the current right
margin. If the right margin is currently set at 80, the following commands
yield the same results.
/v
right
Set
Right 50
/lt2
....+....10...+....20...+....30...+....40...+....5
2 abcdefghijklmnopqrstuvwxyz
/colm
1/5 51
2
fghijklmnopqrstuvwxyz abcde
1
line changed
/colm
1/5 88/90
2
fghijklmnopqrstuvwxyz abcde
1
line changed
Approving Each
Changed Line
Use COLMJ to give yourself approval
over each change before it is updated.
With COLMJ, Qedit displays the line as it would be and asks you for a
Yes, No, or Modify answer.
CobX Tags
Cobol tags are
short strings stored in columns 73 to 80 of CobX source files. The Cobol tag
value is defined using the Set X command. Once enabled, updated lines and added lines are
automatically updated with the tag. They can also be modified manually with
custom tag values.
In its regular form, the Colmove command affects only the
text area in columns 7 to 72.If you wish to make changes to Cobol tags, use the
T suffix. You can think of it as the Tag option. This option operates only on the tag area itself,
columns 73 to 80.
/ColmT 73/74 79/80 all {
copies content of columns 73 and 74 }
{
into columns 79/80 }
/ColmT 73/74 75 all {
inserts content of columns 73 and 74
}
{
in column 75. Columns 76-80 are shifted. }
To to this, the Tag option temporarily changes
the margins to (73/80). Qedit displays a warning
every time this option is used. Because the margin values have changed,
explicit column range in the source and destination columns can only be between
73 and 80.
/ColmoveT 23/24 79/80 all
Warning: ColcopyT:
editing the Cobol tag area only (73-80).
Error: The
Sourcestart column (23) is not between 73 and 80
/ColmoveT 73/74 79/80 10
Warning: ColcopyT:
editing the Cobol tag area only (73-80).
10 ME0307ME
1 line changed
Because the margins have been changed, Qedit displays text
in the tag area only except when the Justify option is used. In this case,
Qedit prompts for confirmation before making the change. It would be hard to
determine if a line needs to be changed based only on the tag value. So, when
the Justify option is used, Qedit displays the complete line. The user has the
option to accept the changes, reject the changes or manually modify the line.
If the user chooses to modify the line, only the tag is displayed.
Deletes lines from the workfile.
DELETE [ rangelist ]
(Q=no display, J=verify)
(Default: rangelist
= *)
Delete prints each
line in rangelist, with an underline
character after the line number, as it deletes them, unless you use DQ.
Notes
If you do Delete All, you must answer
"Y" to a verifying question before the lines will be deleted. This
also applies if you Set Check Delete is ON and you delete more than 5 lines.
If you delete the wrong lines, you can cancel
the Delete by striking Control-Y. However, you must use Control-Y before you
press Return on the next command line. Qedit responds by printing
"Undeleted" or "Canceled". Once you have typed in the next
command line and press Return, your chance to recover using Control-Y is gone
and the previous Delete command is final. You can still undo the deletion using
Undo.
Delete All resets
the Set Keep Name (default for Keep command) so that a later Keep command will not wipe out the wrong file
by mistake.
Confirm Each Deletion
Use DJ to give yourself approval over each
delete before it is carried out. With
DJ, Qedit displays the line (even if the Quiet option is used) and asks you for
a Yes, No, or Stop answer.
Answer No or Return to keep the line.
Answer Yes to delete the current line.
Unlike the basic Delete operation where lines are removed with the next
command, lines confirmed in DJ are deleted immediately. They can be recovered
with an Undo
command.
Answer Stop if you wish to stop the
delete process. When you use Stop, lines that have been deleted are not
recovered automatically. Use Undo to recover them.
Examples
/delete
5/6 {remove lines 5 and 6 from
file}
5
_this is line 5
6
_and this is line 6!
/dq
2 10/49 {delete lines 2 and
10/49}
/delete
"."(1/1) {delete lines
with "." in column 1}
{Implied rangelist is
ALL}
/del "."(1/1 nomatch) {delete lines
without "."}
/d
"~"(pattern) {delete all
blank lines}
/dj
3/66
3
this is line 3
Delete it (Y,N or Stop) [No]:
4
this is line 4
Delete it (Y,N or Stop) [No]:Y
5
this is line 5
Delete it (Y,N or Stop) [No]:n
6
this is line 6
Delete it
(Y,N or Stop) [No]:S
1
line Deleted!
Purges the current workfile, or a named HP-UX
file, after first verifying with the user.
DESTROY [ filename ]
(Default: current workfile)
The filename parameter can be the name of
any file that you have write access to, "$" to refer to the
"last" file name mentioned in another command, or "*" to
refer to either the current workfile or, if none is currently open, the one just
Shut.
Examples
/destroy
/dev/src/test.c
/dev/src/test.c
# of lines=162
Purge
file [no]? Oui {that's French for
"yes"}
/open
ctemp
/des
*
ctemp
Qedit file, # of lines=15
Purge
file [no]? {Return key means
"no"}
File
NOT purged
/list
datapg2 {check contents of
file}
/destroy
$ {...then purge it}
Divides a line into two or more lines at
specified columns. Divide can turn a field-oriented record into a series of
lines with one field per line. It can also append a blank line after every line
in a file. See also VV in Visual. For the opposite of Divide, see the Glue
command.
DIVIDE [ ( columnlist ) ] [ rangelist ]
(Default: columnlist
= ], rangelist = *)
The columnlist parameter is one or more
valid column numbers in ascending order such as (10 20 30), or it may be a (])
for "after end-of-line" (i.e., append a blank line). All characters
from the specified column to end-of-line are moved to a new line after the
original line.
The rangelist parameter specifies one or
more lines in the file. Each line is split into two or more lines according to
the column parameter. The default rangelist
is the current line.
The default columnlist is "]", except when
the Divide command has no parameters or only a "string" rangelist. Then the current line is
split at the "current column". When Divide has no parameters, the
current column is "]". Following a successful string match, the
current column is the first column of the string position in the line(s).
Examples
/find
"abc";divide {move
"abc..." to a new line}
/list
*+2;divide {move ahead 2 lines, add
a blank line}
/divide
(20) all {split every line at
column 20}
/divide
(20 40) @ {split every line at
columns 20 and 40}
/divide
(10 20 30) {split current line at 3
places}
/divide
(]) */*+10 {add blank line after
lines */*+10}
/divide
(20)"Qedit" {split all
"Qedit" lines at column 20}
/divide
"Qedit" {split all
"Qedit" lines at "Qedit"}
/divide
(])"Qedit" {add blank line
to all "Qedit" lines}
Notes
After a Divide
command, the current line is the last line divided. To not print the lines, use
DivideQ.
Divide works
within the current Left and Right margins. That is, characters to the right or
left of the current margins are not moved.
When working with
COBOLX files, the Divide command does not consider the tag (columns 73 to 80)
as part of the data. This means that the current tag data is not moved to the
new split line. It also means that you cannot divide a line past column 73.
The :Do command repeats (without changes) any
of the previous 1,000 commands.
DO [ start [ / stop ] ]
[
string ]
[
ALL | @ ]
(Default: repeat the previous command)
Commands are
numbered sequentially from 1 as entered and the last 1,000 of them are
retained. Use the :Listredo command to display the previous commands. You can
repeat a single command (do 5),
a range of commands (do
5/10) or the most recent command whose name matches a string (do list). If you want to modify
the commands before executing them, use :Redo or Before.
Examples
/listredo {or /bj or ,, }
/do {do previous command again}
/do
39 {do command line 39 again}
/do
5/8 {do command lines 5 to 8
again}
/do
list {do most recent List
command}
/do
ls {do last starting with
"ls"}
/do
ls job {do last "ls job"
command}
/do
@job {do last containing
"job"}
/do
-2 {do command before
previous}
/do
-7/-5 {do by relative line
number}
/do
5/ {do command lines 5 to
"last"}
Notes
To stop a :Do All,
use Control-Y.
Exit from Qedit and return to the operating
system.
EXIT [string]
The current
workfile is closed and Qedit terminates. The F8 user key is the same as Exit.
To close the
current workfile without exiting, use Shut.
When you Exit,
Qedit checks whether you have any unsaved edits in any of your scratch files.
If so, you are prompted to Discard? them,
or stay in Qedit to save them.
Examples
/opt/robelle/bin/qedit
/open
qedit.doc {open file to work
on}
/modify
2482.5/ {do some editing...}
.
.
.
/exit {ready to quit for the
day!}
Notes
To avoid
accidental Exit as a result of pressing F8 one time too many, you can run Qedit
with the –v option. This forces user approval of Exit.
The string parameter is only allowed when
Qedit is running as a server.
The string is a message sent to the Qedit for Windows
client. The client receives the exit notification, displays the message and
disconnects immediately. If no string is specified, a default message is
displayed.
Finds the next line in the workfile that
contains a string. Use Findup if you want to search for the previous line. Find
always finds a single line that matches a string. Use the List command if you
want to find many lines that match a string.
FIND [string] [linenum]
FIND [string range] [linenum]
(Q=no display)
(Default: string
= recent; linenum = *+1)
Find defaults string to be "same as last
string" and linenum to be
"starting from the next line". This saves having to repeatedly type
the string and linenum. Once you have defined your string and starting position, just enter "F" to find the
next line.
Find does not
start searching at the beginning of your file. Find will start searching for
the string at the line after the current
line, unless you specify a linenum to
start the search. If you want to search from the beginning of your file, use
Find string FIRST.
The F4 user key
does the same function as Find with no parameters.
Examples
/find
"exit" first {find first
line with "exit"}
45
this command will cause an exit from the
(28)^
/f {find next line with
"exit"}
90
after you exit from a module, the program
(11)^
/f {continue finding
lines...}
...
/f {...until you reach end of
file}
Warning:
No Line {prints error and
rewinds}
Error:
End of File
/f {next Find wraps around!}
Warning:
Rewind to FIRST
45 this command will cause an
exit from the
(28)^
/fq"$page"(1/5);m {find next $page and modify it}
/fq;c""exit" {find next string and change it}
/fq;c""" {find next string and remove it}
/f
"start"/"end" [
{find string range and set ZZ}
Lines
5/11 saved in ZZ
Notes
The Q option lets
you find the line without printing it. Use FQ if you intend to Modify the line
after you find it.
Find prints an
error when the search reaches the LAST line without locating the string. Then,
if you enter another Find without a line number, the search starts from the
FIRST line in the file, after printing a warning.
To find/see all
occurrences of a string in a file, use the List command.
When a string
range is used and a corresponding block is found, the start and end line
numbers are stored in the ZZ marker.
Finds the previous line in the workfile that
contains a string. Findup can be shortened to ^. Use Find if you want to search
for the next line.
FINDUP
[string] [linenum]
(Q=no display)
(Default: string
= recent; linenum = *-1)
Findup defaults string to be "same as last
string" and linenum to be
"starting from the previous line". This saves having to repeatedly
type the string and linenum. Once you have defined your string and starting position, all you
need to enter is "^" or "FINDU" to find the next string.
The F3 user key
does the same function as Findup without parameters.
Examples
/findup
"exit" last {find last line
with "exit"}
90
after you exit from a module, the program
(11)^
/findup find previous line with
"exit"
45
this command will cause an exit from the
(28)^
/^ {continue finding lines...}
...
/^ {...until you reach start
of file}
Warning:
No Line {prints error and rewinds}
Error:
Beginning of File
/findup {next Findup wraps around!}
Warning:
Rewind to LAST
90
after you exit from a module, the program
(11)^
/findupq;mod {find string and modify it}
/findupq;c""exit" {find string and change it}
/findupq;c""" {find string and remove it}
Notes
Refer to the notes
under the Find command.
Displays
information about a self-describing file created by programs such as Suprtool.
These programs store information about the record layout such as field names,
data types, length.
FORM [ $LP | $LPA | $LPB ] [ filename ]
(Default: filename
= current Text file)
If filename is
omitted and a workfile is currently active, Qedit uses the name of the Text
file (see Verify Keep). An external
filename can be specified. In this case, the name must be the name of the data
file.
If the file is not self-describing, Qedit displays the
following message:
Error: File is not
self-describing.
Self-describing files on Hp-UX have 2 components: the data
file and the data description file. The name of the data description file is
the name of the data file followed by the .sd extension. For example,
/home/user1/mydata.dat { data }
/home/user1/mydata.dat.sd { data description }
The Form output looks like this:
Self-describing information for /home/user1/mydata.dat
File: /home/user1/mydata.dat (SD Version B.00.00) Has linefeeds
Entry: Offset
CHAR-FIELD X5 1
<<Sort# 1 >>
INT-FIELD I1 6
DBL-FIELD I2 8
PACKED-FIELD P12
12
PACKED*-FIELD P12 18
QUAD-FIELD I4 24
ID-FIELD I1 32
LOGICAL-FIELD K1 34
DBLLOG-FIELD K2 36
ZONED-FIELD Z5
40
Entry Length:
80 Blocking: 1
LP Listing
$lp, $lpa and $lpb
send output to a device associated with an environment variable of the same
name. For example, to print to the device called Laser with the $lpa option,
you must set the |4LPA| environment variable to Laser, as in |2export
lpa=laser|. If the LP environment variable is not set, Qedit will attempt to
send the output to the default system printer.
But if the LPA or LPB environment variables are not set with a valid
device name, an error will occur.
Starts "browsing" the current file
by displaying the next page "forward". You stay in "browse"
mode until you enter any command (see List, jumping option).
FORWARD
(F6 key does the same)
In Line mode,
Backward and Forward (or F5/F6) throw you into List-Jumping's Browse mode.
Qedit displays a screen of text, where the screen size is either 23 lines or
what you specify with Set List LJ, then waits for you by asking
"More?". Press Return to see the next screen, typing a line number
moves you to the screen starting at that line, pressing F2-F6 does the
appropriate action, and F8 or "//" or Control-Y or typing any command
gets you out of browse mode. At the "More" prompt, the *
"current" line is the last line displayed.
Finds and recovers wasted space in the current
workfile.
GARBAGE
(Q = no summary)
If you keep adding lines to a workfile and
editing them, eventually you will get an "Error: Full" message in
Line mode or "File nearly full!" in Visual mode, and be unable to add
more lines. One method of continuing at this point is to use the Garbage
command.
/garbage
/gar {minimal command name}
Garbage combines
partially full blocks to squeeze out free blocks, but it also searches the
workfile for any blocks that have been "lost" (i.e., are no longer on
the "free list" or the "text list"). It does not make your
file any smaller, it just allows you to continue editing by finding usable
space within the file.
Garbage prints a
summary of how much space it recovered and how much is available in the file.
The summary report can be suppressed using GarbageQ.
5 blocks squeezed out, 2 found, 55 used,
10 on free list, 9 for expansion.
In this example,
Garbage reports that 5 blocks were retrieved via squeezing, 2 lost blocks were
found, 55 blocks are currently used to hold text, 10 empty blocks are held on a
"deleted-block" list (the free list), and 9 blocks are available if
the EOF is expanded toward the LIMIT.
Joins a line with one or more following
lines, either concatenated or at specified tab positions. Use Glue to turn a
list of fields into a single record-oriented line. See also GG in Visual mode.
For the opposite of Glue, see the Divide command.
GLUE [ ( columnlist ) ] [ rangelist ]
(Defaults: columnlist = ], rangelist =
*/*+n)
The columnlist is a list of ascending column
numbers in parentheses such as (10 20 30), or ( ] ) for "after the
end-of-line", which is the default.
The rangelist specifies which lines to
combine. The default rangelist is the
current line plus n. When you specify
a range of lines, Glue joins the lines in "pairs".
Examples
/glue {joins *+1 to *}
/gluej {joins *+1 to * with space
between}
/glue;glue {join *+1 and *+2 to *}
/glue
(10) all {joins lines in
"pairs" at column 10}
/glue
(10 20 30) {joins 4 lines into 1
record}
/glue
"string" {glue
"string" lines to lines that follow}
Notes
If there are not
enough lines at the end of a rangelist to
fill in each column of the list, Glue does
not go beyond the rangelist. If
there is not enough room to move all of the characters into the line, as many
characters as will fit are moved, the following line is not deleted, and Qedit
prints an "overflow" warning.
After a Glue
command, the current line is the line last spliced together. To suppress
printing of the spliced lines, use GlueQ.
If you don't
specify a list of column fields, Glue removes leading spaces from the following
lines before moving them. To insert a single space between them, use GlueJ
instead. If you do specify columnar fields, Glue treats spaces as valid data
and moves them intact. If you specify more than one field, some nonblank data
may be overwritten if the columns are too close together or the lines to be
glued are too long. You can always use Undo to cancel a Glue command.
If Left or Right
margins have been Set, only the text within the margins is copied and the
following lines are not deleted.
When editing
COBOLX files, the tag area (columns 73 to 80) is not considered part of the
data. This means that the tag string on the next line is not moved to the new
line. It also means you cannot glue to columns past 73.
Gives instructions on the use of Qedit.
Everything in the Qedit User Manual is
also in the Help command. "?" means the same as Help.
HELP [ command [ ,keyword ] ]
[
TERMS [ ,word] ]
[
INTRO ]
[
NEWS ]
(Default: browse through the entire help
file)
(Q = Quick Reference Guide "Quick
Help")
The parameters
have the following meaning:
command explains
command; lists subsidiary keywords to
select.
command,keyword finds keyword under command.
command,@
prints everything about the command.
TERMS [,word]
explains word (see "Glossary").
INTRO explains how to apply Qedit to typical
problems.
NEWS shows any new features in Qedit.
Examples
/h
text {explain the Text command and show
sub-keywords}
/h text,@ {tell all about Text. Comma is required}
Quick Help - HQ
HQ looks for entries under the keyword Quick
in the helpfile. Quick contains the text from the Qedit Quick Reference Guide, offering the experienced user a review of
command syntax.
/hq
visual {full-screen options}
/hq
shortcuts {quick list of
shortcuts}
Notes
The help file must
be on the system for the Help command to work. If the file is missing, Qedit
still works fine, but you cannot get any on-line help. The default file name is
/opt/robelle/help/qedit. Within the Help command, use "+" to see what
levels exist "beneath" you and "?" for "help on
Help". The help file is organized into levels: to go back to the previous
level, press Return instead of entering a keyword. Press F8 to exit the QHELP
subsystem completely and return to Qedit. Use the Prev Page (or Page Up) key on
your terminal to review help already printed.
Lets you explicitly write lines to the Hold
file.
HOLD [ filename ] [ rangelist ]
(Default: hold current line)
(Q=hold without display)
(J=append, without erasing)
You can refer to the current contents of the
Hold file by the actual file name, "hold", in any of the commands
that access external files (Add-File, List, Use).
Examples
/hold 50/60
{erase Hold, hold lines}
/holdj
100/198 {append more lines to Hold}
/ho
"direct" {hold lines with
string}
/open
abc.src
/add 33=hold {adds held lines to abc.src}
/holdq
/etc/profile
/list
hold
Implicit
Hold
When using the Add
command to move or copy lines within a file, Qedit overwrites a file named
Hold0 with a copy of the lines. It counts the lines and tries to select a line
number increment that will accommodate the number of lines being added to your
workfile. So, if the command fails or if you wish to copy the same lines again,
you can refer to the Hold0 file. Adding from an external file also holds the
lines if you specify a rangelist for the file, and if the file is not the Hold
file itself.
/add 55=hold0
/list
hold0 {the Hold file is
temporary}
Notes
By default, the Hold files are created in /var/tmp (/usr/tmp is the default on older versions of HP-UX). If
you want to keep your Hold files in a different location, you can enter the new
path name in the TMPDIR environment variable.
TMPDIR=/home/user1/tmp
export
TMPDIR
The file name
starts with "qhold" and ends with a random string of characters. The
Hold0 file ends with ".0". Keep in mind that Qedit works with
absolute filenames and these names can not have more than 240 characters.
Every time you use "hold" or
"hold0" by themselves as a file name in any command, Qedit replaces
the word with the fully-qualified file name of the appropriate Hold file.
translates to
/Add 1=/var/tmp/qholdDAAa05429.0
With Justify, you can do text formatting:
center lines, right-justify lines, left-justify lines, and fill text into
margins.
JUSTIFY [option] [keyword ...] [rangelist]
(Q=no display)
(Default option:
Null or Set Justify)
When the Justify
command is processing the range of lines you specified, if you decide not to
continue, press Control-Y to stop the formatting.
Options Specify Which
Function
|
Justify Right
|
right-justify each
line
|
|
Justify Center
|
center each line
|
|
Justify Centre
|
Canadian spelling!
|
|
Justify Left
|
remove leading
spaces
|
|
Justify Format
|
fill lines, ragged
right margin
|
|
Justify Both
|
fill lines,
straight right margin
|
|
Justify Null
|
default - no
changes - safety
|
Keyword Parameters of
Justify
|
MARGIN column
|
right edge,
relative to left
|
|
TWO [ ON|OFF ]
|
maintain 2 spaces
after . ? and !
|
|
INDENT spaces
|
indentation for
list of points
|
|
WITHINDENT
|
activate
configured indentation
|
|
STOP "chars"
|
break
justification when found
|
|
START "chars"
|
start new
paragraph
|
You may shorten
options and keywords to the leading letters.
Rangelist Specifies Which
Lines
For the Format and Both options, the rangelist specifies some lines to
format. Warning: if you type a single line number (e.g., just both 5),
Qedit begins formatting lines from that line number to the end of the
paragraph. Qedit sees blank lines as end-of-paragraph markers, so if you justify format all you end up
with smooth and even chunks of text, set off by blank lines. This is one of the
few places in Qedit where a single line number implies a range of lines.
For the Left,
Right and Center options, a single line rangelist
means a single line. But, you can specify a "string" rangelist to center or justify only
lines containing a string. Specifying a "string" rangelist with the
Format or Both options is equivalent to specifying a single line number i.e.
formatting starts with the line which has the string and continues to the end
of the paragraph.
Verification Before
Formatting
If Set Check Justify is ON, Justify Format
and Both require user verification before formatting more than 5 lines. This
should eliminate inadvertent formatting of entire source programs!
You can also use
the Undo command to undo the effects of the Justify command.
Left and Right Edges for
Justify
Justify works within borders called the left
and right edge. The left edge is usually column 1, or column seven 7 in
standard COBOL. The right edge is usually the highest column number allowed in
the file (e.g., 80 for JOB files). However, if you use Set Left and Set Right
to create margins for your file, Justify operates within those limits. Set Left
will be the left edge and Set Right will be the right edge. You can also use
the Margin keyword to establish the right edge for Justify, but remember that
this edge is relative to any Set Left value.
Examples
/justify
center 5/6 {center lines 5 through 6}
/j
right 5/6 {right-justify lines
5 through 6}
/j
left 5/6 {left-justify lines 5
through 6}
/j
format 5/50 {format lines 5/50
into margins}
/j
f 5/6 {splice lines 5 and 6
into one line}
/j
both 5 {format a paragraph,
even right edge,}
{ from line 5 to the next blank line}
Right Justifying Lines
Justify Right shifts each line of rangelist to the right until the last
nonblank character is at the right edge. For example:
/justify right margin 50 rangelist
Input lines:
Robelle
Solutions Technology Inc.
Tools for HP3000
Output lines:
Robelle Solutions Technology
Inc.
Tools for
HP3000
Centering Lines
Justify Center adjusts each rangelist line so that it is centered between the left edge and the
right edge. For example:
/justify center margin 50 rangelist
Input lines:
Robelle
Solutions Technology Inc.
Tools for HP3000
Output lines:
Robelle Solutions Technology Inc.
Tools for HP3000
Left Justifying Lines
Justify Left removes leading spaces from each
rangelist line, until the left-most
nonblank character is at the left edge. This will left-justify the lines. Use
for this option to recover from an inadvertent Center or Right option. For
example:
Input lines:
Robelle Solutions Technology
Inc.
Tools for HP3000
Output lines:
Robelle
Solutions Technology Inc.
Tools
for HP3000
Filling Words into Tidy
Paragraphs
Justify Format adjusts the processed lines so
that the words fill the space between the left edge and the right edge, but
allows the right edge to be ragged:
/justify format margin 50 rangelist
Input lines:
The
Format keyword performs a
function
which is equivalent to .ad l
(left-justify)
in nroff and troff.
Uneven
lines are converted into lines
of
about the same length.
Output lines:
The
Format keyword performs a function which
is
equivalent to .ad l (left-justify) in
nroff
and troff. Uneven lines are converted
into
lines of about the same length.
Making Both Edges Even
Justify Both is similar to Justify Format,
except that both the left and right edges of the text are even. This is
accomplished by inserting blanks between words. For example:
/justify both margin 50 rangelist
Input lines:
The
Both keyword performs a
function
which is equivalent to .ad b
(adjust
both) in nroff and troff. Uneven
lines
are converted into lines
of
exactly the same length.
Output lines:
The
Both keyword performs a
function which is
equivalent to
.ad b (adjust both) in nroff and
troff. Uneven lines are converted into lines
of
exactly
the same length.
Null Option
Justify Null is
included as an option to serve as a default. If Both were the default option,
most of your file would be quickly formatted if you accidentally typed "J
5" instead of "LJ 5".
Configuring the Justify
Command
The five options (Right, Center, Left, Format,
and Both) and the four keywords (Margin, Two, Indent, and Withindent),
configure the Justify command. The hierarchy of configuration values is as
follows:
Startup default (the "default
default")
overridden by
SET Justify (the configured default)
overridden by
Keywords in Justify command
You set your own defaults for the Justify option and keyword values using Set Justify. Once you find the setting you
like, you may want to put them in your Qeditmgr configuration file so you won't
have to do the Set Justify command every time you run Qedit. For example:
/set justify
null margin 50 two on
causes
/justify both 5
to be interpreted
as
/justify both
margin 50 two on 5
but you can
override your own defaults, as in
/justify both
margin 60 10/20
which merges with
your Set Justify values to produce
/justify both
margin 60 two on 10/20
Configuring the Right Edge
The Margin keyword specifies the right-most
column for processed lines. This column is needed for the Right, Center, Format
and Both options. The value you specify is relative to any Set Left margin that
is effective at the time of the Justify command.
Determining the Left Edge
For the Both and Format options, the left
margin is determined by looking at the first and second lines of each
"paragraph". If the first and second line are indented, the entire
paragraph will be indented. Of course, this indentation is relative to any Set
Left.
/justify
both margin 50 linenum
Input lines:
The Both keyword performs a
function which is equivalent to
.ad
b (adjust both) in nroff and troff.
Uneven
lines are converted into lines
of
exactly the same length.
Output lines:
The Both keyword performs a function which
is
equivalent to .ad b (adjust both)
in nroff
and
troff. Uneven lines are converted into
lines of exactly the same length.
Two Spaces at End of
Sentence
Normally, when Qedit adjusts text with Format
and Both, it inserts one space between each symbol, regardless of the number of
spaces between symbols in the input text. If the Two keyword is ON, Justify
maintains two blanks after the end of a sentence (i.e., after a . ? or !, or
one of those three followed by a quote mark or a right parenthesis and a
space). The default for this keyword is OFF.
Justify does not
insert two spaces if the input only contains one; it merely maintains two
spaces if they are there already (this means you don't have to worry about
getting two spaces in a name like Calvin C. Cook).
/justify
format two on margin 70 99.5/
Formatting a List of
Points
The Indent keyword is a special capability
for handling lists of numbered points (1., 2., 3., ...). It assumes that your
text is indented and that the numbers for each point appear to the left of that
indentation. The Indent parameter specifies the number of spaces at the start
of each line that will not contain text to format. Justify leaves anything to
the left of this border "as is". In fact, the existence of text to
the left of the border acts as an "end-of-point" indicator,
eliminating the need for a blank line between points to stop the justification.
Indent is relative to any Set Left.
The end of each
point in a list is effectively an end of paragraph. Here is a sample of what
happens when you attempt to format a list of points without the Indent keyword:
/justify both margin 50 rangelist
Input lines:
1. Text which occurs in
a list of points should also
be formatted into even lines.
2. Any
text to the left of column 5
causes a
"justification break".
Output lines:
1. Text which occurs in a list of points
should
also
be formatted into even lines. 2. Any
text
to the left
of column 5
causes a
"justification break".
All of the points
have been run together into a single point. You can avoid this result by
inserting a blank line at each point, or by doing Justify on each point
individually, or by using the Indent keyword:
/justify both margin 50 indent 4 rangelist
Input lines:
1. Text which occurs in
a list of points should also
be formatted into even lines.
2. Any
text to the left of column 5
causes a
"justification break".
Output lines:
1. Text which occurs in a list of points
should
also be formatted into even lines.
2.
Any text to
the left of column 5 causes a
"justification break".
Activating Indentation
Withindent activates an Indent value that you
have previously configured with Set Justify Indent. Withindent allows you to
settle on a single indentation for all "lists of points" without
having to respecify that value on every Justify command. You merely specify
Withindent when you format a list of points:
/set
justify indent 4 {configure potential
indentation}
/justify
format 5 {this is not a list of
points}
/just
f with 9 {this is a list of points}
Justification Breaks and Formatting
Commands
Justify has options to define characters that
start and/or stop justification when found in column one. These options make it
much easier to justify text in files which contain embedded commands and
special characters for a format program (e.g., Prose, TDP, etc.). The specific
characters are defined using the Start and Stop options:
/set
justify stop ".+" start "` "
This command says
that any line with "." or "+" in column one stops text
justification and that line is not changed. Any line with "`" or
" " (space) in column one ends justification of the previous
paragraph and signals a new paragraph (i.e., that line is formatted as part of
the next paragraph).
It's important to
note that a "string" rangelist has precedence over Start and Stop
characters. In other words, the latter options are ignored.
Here is an example
which justifies some text from a Robelle document that consists of both text
and embedded Prose formatting directives. Note that lines beginning with
"." and "+" are not altered, and the line beginning with
"`" properly appears as a new paragraph.
/justify
start "` " stop ".+" margin 50 format all
Input lines:
.for([
T S:40 // l55 / "-" pn:1 "-" /]
+ [ S
T:40 // l55 / "-" pn:1
"-" /])
.par(f` p5 s1 u3).com Define ` as Start of Paragraph
.ent
`|1Welcome to Compare|
.beginkey
compare
Welcome to version 2.2 of Compare -- a
file
comparison program for text files.
`Compare answers the question,
"How
different are these two text files?"
Compare will tell you whether lines
have
been added, or whether a block of
lines
is now different.
Output lines:
.for([
T S:40 // l55 / "-" pn:1 "-" /]
+ [ S
T:40 // l55 / "-" pn:1
"-" /])
.par(f` p5 s1 u3).com Define ` as Start of Paragraph
.ent
`|1Welcome to Compare|
.beginkey
compare
Welcome to version 2.2 of Compare -- a
file
comparison
program for text files.
`Compare answers the question, "How
different are
these
two text files?" Compare will tell you
whether
lines have been added, or whether a block
of
lines is now different.
Creates a standard disc file and writes the
workfile into it. Keep is the reverse of Text, which copies a standard disc
file into a workfile that you can edit. Use Text when you need to duplicate a
file.
KEEP [filename][,options] [ rangelist
]
(Q=no linenums)
(Defaults: rangelist=ALL, filename=last)
Keep Options
Qedit allows
several options on the Keep command. Note that the comma preceding the option
name is mandatory, and that spaces are not allowed before the comma or the
option name.
|
Keep filename,UNN
|
unnumbered (same
as KQ)
|
|
Keep filename,YES
|
go ahead and purge
old file
|
|
Keep filename,NO
|
never purge an old
file
|
|
Keep filename,XEQ
|
assign xeq access
|
|
Keep filename,IFDIRTY
|
only if changes
made
|
|
Keep filename,LF
|
insert Newline
delimiters
|
|
Keep filename,NOLF
|
Do not insert Newline
delimiters
|
Keep creates a new
disc file named filename. You can
combine several options on the same Keep command. The default filename is the name of the last Text or
full Keep (i.e., it does not count if you use a rangelist or have reduced the margins with Set Left or Set Right).
If filename already exists, Qedit
will ask you to verify that it is okay to purge it unless you specify the ,YES
or ,NO option.
Sometimes the file
will have sequence numbers in each line (this is called numbered), but you can
omit the sequence numbers with KQ, or by specifying the ,UNN option.
Keep transfers rangelist lines from the workfile to filename. The default rangelist is ALL. Warning: Qedit writes
only the data within the current left and right margins, so reset the margins
first if you want the entire line (e.g., Set Left; Set Right).
Examples
/text
/src/report.cob {make a copy}
Scratch
file
/find
"FUNCTION-CODE"
14
05 FUNCTION-CODE PIC X8.
/change
"X8"X10"
14
05 FUNCTION-CODE PIC X10.
/keep
/src/new.cob {create a new
file}
... {do some more changes}
/keep {save again with same
name...}
/src/new.cob
# of records = 127
Purge
existing file [No]? yes {you must
authorize purge!}
/s
left 1;s right 50 {define margins
as first 50 columns}
/kq
/data/nov99 {unnumbered with
50-byte records}
/k
notes,UNN,YES {unnumbered,
purge old file}
/keep
,yes {keep to last
text, purging old}
Absolute File Name
When you are using CD, you may find yourself
doing the following: Text file xxx, change to another directory to add from
some other files, then Keep to update your original file. Keep defaults to the
"absolute" name (e.g., /user/dev/lib/src/xxx). This means you can
change to other directories after a Text, but still easily Keep the file back
under its original name. In the past, Keep would default to the
"relative" name of the Text file (e.g., xxx), saving the file in your
current working directory.
Keep Only When Changes
Were Made
Keep,Ifdirty only does the Keep operation if
the workfile has been modified since the last Text or Keep. This can be useful
in scripts that do Changes: by not Keeping files where no string changes
occurred, you reduce the number of files that appear on the partial backup. To
see whether your workfile is clean or dirty, do Verify Open.
File Modification
Timestamp
When you use the Text command on a file,
Qedit stores the file's modification timestamp in the workfile. If you try to
Keep the file, Qedit compares the stored timestamp with the file's current
timestamp. If they are different, it means the original file has changed since
you first opened it. Qedit will alert you to the difference by displaying a
message similar to the following:
Warning:
Original file has been modified since the initial
Text or last Keep
The file timestamp
can change for a number of reasons. Here are few examples:
·
Someone else might have been working on that
same file with Qedit and saved their changes before you did.
·
The file could have been restored.
·
Maybe you used the file to test a program which
modified the file in some way.
Because the
timestamp message is just a warning, Qedit continues its processing. It then
asks for Keep confirmation. If you answer "Yes", the file will be
purged and you might lose someone else's changes. Qedit will also store the new
modification timestamp.
If you answer
"No", you should compare the contents of the file with your workfile
and decide if it is safe to Keep your changes. This is one way to compare the
files:
·
Keep the workfile under a different name
·
Use our Compare bonus program to display the
differences between the original file and the new version you just created
·
Look at the report and separate the lines that
you changed from the ones you did not touch
·
If needed, apply changes to your copy so you are
not missing anything important
By default,
timestamp checking on Keep is enabled. If you want to change this setting, use
the Set Keep Checktimestamp command.
If you want to
erase the saved timestamp, you can use the Set Keep Name command.
Newline Delimiters
Normally, lines in
a UNIX file are terminated by a NewLine character. Even the last line of the
file has to be terminated. For cases in which the last NewLine character is
missing, Qedit is still able to read all the lines. However, if the file is
saved back, Qedit adds a NewLine terminator. This makes the new file a little
different than the original, even if you have not made any changes to it.
By default, Qedit
inserts a Newline delimiter after each line. If you do not want Newline terminators, use the NOLF
option. The only Newline characters written to the file are the ones included
in the data. Using the Length option on the Text
command disables the
LF
Keep feature (Set
Keep LF Off).
If you wish to override this, you can use the LF option.
Notes
When you Text a
file and Keep it again, Qedit attempts to duplicate the original file. The form
of the Keep file depends upon the current language and Set options, especially
Set Keep. To see what the Keep file will look like, use Verify Keep.
Keep will retain the security of your
existing file (i.e., the file's ACL) if you answer Yes to the "Purge
old?" question.
Prints lines of
the current workfile or an external file either on your screen or to a printer
device.
LIST [$option...] [ rangelist ]
(Default: rangelist
= *)
LIST [$option...] filename[,UNN]
[ rangelist ]
(Default: rangelist
= ALL)
(Q=no linenums, T=template, J=jumping)
If you do not specify a filename, List displays lines of the current workfile. If you do
specify a filename, List displays
lines from that file without Shutting your current workfile. You can refer to
the "previous" file by a shorthand method, a "$".
If you specify a single line number as a
rangelist and that line does not exist in the current file, Qedit's action
depends on the Set List Nearest setting. If the option is Off, the default,
Qedit displays a No Line warning. If the option is On, Qedit displays the
nearest line. For example, if lines 100 to 120 are missing from a file, here is
what would happen:
/List
100
Warning:
No Line
/Set
List Nearest On
/List
100
121
This is line #121.
If you are trying
to do something similar on an external file, Qedit does not display anything.
Specify filename,UNN when listing a data file
which has numeric characters in the last 8 column positions and they are not
valid sequence numbers.
When you list
lines of your current workfile, Qedit shows only the columns within the current
left and right margins, and the default rangelist
is the current line (e.g., List = List *). When you List an external filename, margins are ignored and the
default rangelist is ALL.
Examples
/list
5 {display line 5 only}
/listq
5/ {List-Quiet from 5 to Last}
/list
"customer" {all lines
containing "customer"}
/list
-5/+5 {display current vicinity}
/l
report.cob {display entire source
file}
/l
report.cob ]-10/ {print last 11 lines of
file}
/l
$ "$page"(1/5)
{"$page" in column 1 of previous file}
/set
left 55;set right 132 {set margins in
wide file}
/listt
all {show template above
columns}
/list
"bob" (upshift)
{"bob","BOB","Bob",etc.}
/list
"@UPD@MAST@" (pat) {strings
UPD and MAST both in line}
{pattern matching}
$-Options
You can configure permanent options for the List command using Set List; you can also
select temporary options within a
specific List command. The temporary options are preceded by a dollar sign.
LIST [ $option ... ] [ filename[,UNN]
] [ rangelist ]
The temporary
$-options come after the command name and before the external filename and rangelist.
Here are the
$-options accepted in the List command:
|
[$DEVice device ]
|
The $device option
sends output to a specified device. The device must be a valid printer name
or class. The following command sends lines 1 through 30 in the current file
to the device printer:
/list $device printer
1/30
|
|
[$lp | $lpa | $lpb
| $record ]
|
$lp, $lpa and $lpb send output to a device
associated with an environment variable of the same name. For example, to
print to the device called Laser with the $lpa option, you must set the LPA
environment variable to Laser, as in export
lpa=laser. If the LP environment variable is not set, Qedit will
attempt to send the output to the default system printer. But if the LPA or LPB environment variables
are not set with a valid device name, an error will occur. $Record sends
output to LPCRT=stdlist via Record mode.
|
|
[$HEX | $OCTAL |
$DECIMAL]
|
Numeric dump
|
|
$CHAR
|
Remove garbage; combines with Hex/Octal/Dec
|
|
$PCL code
|
LaserJet fonts and
orientation
|
|
$DUPLEX
|
Double-sided printing on certain LaserJets
|
|
$EVEN | $ODD
|
Outputs even or odd number of pages
|
|
[$COLUMNS (range,
...)]
|
Lists only certain columns
The $columns option allows you to list only the contents of certain columns.
You can specify up to four column ranges. The ranges have to be enclosed in
parentheses and can be separated by commas or spaces.
A range must have a start column and, optionally, an end column. If only a
start column is specified, the end column is assumed to be the same. In this
case, Qedit lists only one column. For example
/List $columns (5) {lists only the
contents of column 5}
/List $columns (5/10) {lists the contents of columns 5 to 10}
/List $columns (5 20/30) {lists column 5 and 20 to 30}
Column numbers must be valid for the Language of the file. For most files,
the first column is 1. For COBOL-type files, the first column is 7. Column
numbers must also be within the current left and right margins. The column
numbers do not have to be entered in a particular order. For example, the
column numbers in the first range can be greater than the column numbers in
the second range. The text appears in range order (i.e., range1, range2,
range3 and range4). The same column can be included in multiple column
ranges. The total number of columns listed cannot exceed the absolute line
length maximum (8,172 characters).
Although a template Listing is allowed with $columns, the output might not be
very helpful. For example,
/LT $column (15/20)
+....2
1 O
2 pp
3 QQQ
4 rrrr
List $include is supported with $columns, but included files are treated as
if they are the same type as the main file. For example, if you include a
COBOL file within a Data file, the COBOL file will start at column one.
You can specify a rangelist (e.g., a search string with $columns). Qedit
first searches for the string, which can appear anywhere on the line, then
applies the $columns specification.
|
|
$DOUBLE
|
Double space the
listing (or $DBL)
|
|
$SHIFT
|
Shift the listing
four spaces to the right
|
|
[$RIGHTBY spaces]
|
Shift the listing to the right by the
number of spaces
The $rightby option works like the $shift option. It allows you to shift the
printed output to the right. The $shift option shifts the output by four
spaces. The $rightby option allows you to specify the number of spaces by
which the output is shifted. This number can be between 1 and 30.
/List $shift LP {shifts output by
four spaces}
/List $rightby 4 LP {also shifts output by four spaces}
/List $rightby 20 LP {shifts output by 20 spaces}
|
|
$INCLUDE
|
List/search
$include files as well
|
|
$USE
|
List/search
usefiles as well
|
|
$PAGE [ ON|OFF ]
|
Override Set List
Page option
|
|
$LINES count
|
Override Set List
Lines (per page)
|
|
$LENGTH characters
|
Specify the
maximum line length
|
Here is an example
that uses three of the $-options:
/list $lpa $double $shift all
This command would list all of the current
file to the LPA with double spacing, and the listing would be shifted four
spaces to the right. To send the output of the List command to the device
called Laser, an environment variable must be set to a valid printer name
before running Qedit (export
LPA=laser).
When listing an
external file, the $-options must come before the file name:
/list
$hex $char filename {hex-char dump of
file}
Include Files
Normally, Qedit only searches the current
file for a string. If you specify the $include keyword, however, Qedit will
also search the $include files for the string.
/list
$include "global_variable"
The lines that specify Include files must
begin with either "$", "#", "!", or
".". In SPL programs, an exclamation point indicates that the rest of
the line should be treated as a comment. So, if a line starts with an
exclamation point followed by the word Include, Qedit also assumes this to be a
comment and not an actual Include statement.
The $include
command must be spelled out in full, and it can be indented from the prefix
character ($, #, etc.).
The prefix
character can be in any column as long as it is preceded by spaces only. Even
though Qedit allows prefix indentation, other programs such as compilers might
require prefixes to be in specific columns e.g. column 1.
So, as far as
Qedit is concerned, the following examples are valid Include source lines:
$include
'globals.source'
$include constant.srcinc
$
include headers
#include
<strings.h>
#include
"parser/bnf.c"
! include somefile
.include chapter1.book
You cannot combine
the $use and $include options.
Listing C Include Files
Qedit/UX assumes that any include statement
such as
#include
<stdio.h>
is a C include
file. If the file name starts with a letter, it is qualified with /usr/include/. This is where the
standard C include files are located. C file names that start with
"../h" are ignored because they indicate Include files for rebuilding
the HP-UX kernel.
Usefiles
The $use option is very similar to the
$include option. If you specify the $use keyword, Qedit will also search any
usefiles for a string. Usefiles are commonly used in PowerHouse source code,
Qedit and Suprtool command files, and jobs streams that run Qedit and Suprtool.
The lines that
contain the "use" directive must have the word "use" as the
first word in the line. Leading blanks are allowed. Everything after the word
"use" is assumed to be a file name.
You cannot combine
the $use and $include options.
$Device Option
The List command
now has an option to specify the HP-UX print device. For example:
list
$device printer 1/10
The above command
prints lines 1 through 10 of the current file to the printer name or class
called Printer. The name specified after the $device keyword must be a valid
printer name or class. If both the $device and $lp keywords are used, the
$device takes precedence.
Configuring Printers
By using environment variables before running
Qedit, you can define LP, LPA and LPB in your .profile as three different
printers on your system.
$LP;export
LP
$LPA=serialp;export
LPA
$LPB=shipping;export
LPB
Merging Options
The $-options in
the List command are merged with the Set List options, except that Set List
Record ON applies only to the file LP, not LPA and LPB. The $-options can be
combined wherever they make sense; they can be used with Jumping, Quiet and
Template, and can work on the current workfile or an external file. $-Options
may be shortened (e.g., $h = $hex).
Interrupting a Listing
Press the Control-S key to "pause"
the listing for review. Then, press Control-Q to resume the listing. On newer
HP terminals, the Stop key pauses a listing until you press Stop again. To stop
the List command, press the Control-Y key.
Listing External Files
With the List
command, you can look at any file on a system to which you have read access
security.
Qedit studies the
file and determines whether it has sequence numbers or not. If you ask for a rangelist of lines, Qedit implicitly
numbers a file without numbers. It starts at line 1.0 and adds the current Set
Increment value. If the file has sequence numbers, Qedit uses them, unless it
finds illegal numbers or numbers out of sequence. It
then prints the following message:
Error: line number out of sequence (001200) - renumbering
the rest
The string in parentheses is the incorrect line number. You
should make sure it contains numeric digits only and that it is greater than
the number on the previous line. To check this information, you should text the
file using the Unnumbered option.
After reporting the information, Qedit then assigns
new numbers to the lines, starting with the last valid number and adding the
current increment.
Qedit uses this shorthand character to refer
to the most recent external file name: "$". For example,
/list
report.cob "$page"(1/5)
/list
$ 500/600
Template Listing
The LT command prints a column-number
template before the first line of the listing.
/lqt 5
....+....10...+....20...+....30...+....40...+....50..
training of Qedit users is so easy that you
will
Remember that the
first column number in a standard COBOL source file is column 7, not column 1.
For a COBFREE file, the first column is 1. In addition, if you have done Set
Left and Set Right to define margins for your file, the template starts with
the Left margin column and ends with the Right margin column.
/set
left 20;set right 41
/lqt
5
20...+....30...+....40
it
users is so easy th
Browsing or
"List-Jumping"
When you add "J" to
"List" it means list-jumping. This lists the lines specified, but
stops every 23 lines (this pause is handy at 19.2K baud). Browse quickly
throughout a file, viewing as much or as little of each section as you like.
The default rangelist for ListJ is
*/Last, and ListJ linenum means start
jumping at linenum. You can go into
Browse mode quickly from Line mode by using the function keys. Press F6 to
start browsing at the current line, press F5 to browse starting back a page,
and press F2 to roll the screen forward a few lines before starting to browse.
At the end of each
screen, ListJ prompts you for "what to do next?" and waits for your
reply. If the user presses Return or F6, or types "yes", Qedit
displays the next screen. If the user presses F8 or Control-Y, or types
"no", Qedit stops the listing. If the user types a line number, a
string, or a relative line count (e.g., -50, +5), or presses F2, F3, F4, or F5,
Qedit moves to a new location within the file. When you enter any command,
Qedit stops the listing, returns to Command mode, and executes the command.
When you are on an HP terminal, ListJ enhances and erases the line with the
"what to do next?" prompt.
You can combine
ListJ with the $include option to browse through the specified files as well as
their $include files. You can combine with ListJ with "Q" to display
the lines without sequence numbers. Also, you can combine "ListJ"
with "T" to print a column template at the top of each screen. In
fact, you can combine all three options into "ListJQT" to List-Jump
without line numbers, but with a column template.
The screensize
can be changed from 23 lines to another number with Set List LJ nn (where nn is some number of lines from 5 to 100). If you put the command
Set List QJ On in your Qeditmgr file, you can avoid seeing sequence numbers
when you browse.
When List-Jumping
reaches the last line of your file, it prints "End! Are you DONE?
[yes]" and waits for your answer. "Yes" ends the listing, and
"No" starts listing again from the beginning. Set List Endstop On
disables this question; List-Jumping just prints the last line of the file and
ends the LJ command.
Controlling Printer
Listings
When you specify "$lp" (or
"$lpa" or "$lpb") in a List command, Qedit looks for an LP
environment variable, retrieves the value, and uses this as the device name.
The lines that would have been printed on the terminal are written to the
printer file instead. At the end of the command, Qedit closes the file, which
releases it for printing.
The default Qedit
listing to the printer is a raw dump of your lines, with or without line
numbers. It has no page breaks, no headings, no title, and no page numbers.
However, you can override this default with the Set List command.
Listing to Attached
Printer
To list to a printer that is attached to your
terminal, use List $record. If you want all listings to $lp to go to the
attached printer, do Set List Record On and then List $lp. Qedit will use
Record mode on your terminal or PC to print on the attached printer. This
option opens a file named LPCRT instead of LP. If you are listing to an
attached printer from a terminal, your terminal may remain locked after the
printout is completed. This generally happens when you have handshaking
enabled. (G-H straps set to No). You can do a soft reset to unlock your
terminal.
If handshaking is
disabled (G-H straps set to Yes), the List command works and returns control to
the terminal, but two "S" characters are printed on the terminal.
There is currently no known workaround to these problems.
If you have a LaserJet connected to your PC
and are using Reflection, you will want to Set Printer-Passthru-Conv No in Reflection.
Otherwise you will find that some characters are printing oddly, such as the
square block printing as a plus-minus sign. If you are using Reflection for
Windows, the above option may be called "Disable Printer Translation"
or "Use Host Character Set." As well, you have to select "Bypass
Windows Printing" and disable "Auto Form Feed."
You can combine this option with other
listing options such as $PCL or $duplex. You cannot interrupt Record mode with
Control-Y, but you can do a soft Reset. This unlocks the keyboard and causes
the rest of the output to appear on the screen. You can then stop it with
Control-Y.
LP Listings with Headings
To have Qedit do a page break every 60 lines
and put a heading with a page number on each page, do List $page On $lp (or
$record, $lpa, $lpb). To configure "paging" as the default, do Set
List Page On. Two lines at the top of each page are used as a heading. The
first line contains the page number, the file name (or the last Text file name
in the case of Qeditscr), and the time of the listing, and the second line is
blank.
In this mode, Qedit also looks for $title,
$page, #pragma page, and #pragma title commands in your file and uses them to
create page breaks. The optional string parameter of these commands replaces
the date and time in the page heading (e.g., $page "Monthly Staff
Review"). A $page or $title command without a string clears the title area
of the heading.
To vary the number of lines per page, do List
$lines nn, or use Set List Lines nn for a permanent override, where nn is a value between 1 and 256.
(Assumes Set List Page On.).
/set list page on lines 59
To print the
heading only on the first page, use $lines 0. This
causes continuous printing with no page ejects.
/list
$lp $lines 0 all {ignores $page too}
To perform continuous printing with no automatic page
ejects but skip to a new page on $Page directives, use $lines 999.
/list $lp $lines 999 all
{skips to a new page on $page only}
To drop the file name from the page heading,
do Set List Name Off. (Assumes Set List Page On.)
/set
list page on name off
To drop the page numbers from each page, do
Set List Num Off. (Assumes Set List Page On.)
/set
list page on name off num off
To drop the title from the heading, do Set
List Title Off. (Assumes Set List Page On.)
/set
list page on title off
To drop the
two-line heading from each page while still doing page breaks, use Set List to
disable the three components of the heading:
/set
list page on name off num off title off
Getting an Even or Odd Number of Pages
There are times when the number of printed
pages is important. For example, you could have a printer that is always loaded
with pre-printed forms that come in pairs (e.g., Page 1 of 2 and Page 2 of 2)
or the paper is folded in certain ways so that a report is easier to tear up
and insert into a binder. In both examples, sending a report with an odd number
of pages would cause the next output to be on a wrong page.
To prevent this
from happening, you can now use the $even or $odd options on the List command
and ask Qedit to "round up" the number of pages. The $even option
ensures that the output has an even number of pages. Similarly, the $odd option
ensures there is an odd number of pages by sending an extra page eject sequence
before closing the output file.
These even and odd
options are mutually exclusive (i.e., they cannot be both enabled at the same
time). If you try use them both on the same command, Qedit uses the last one in
the sequence. For example, you can type
/List
$even $odd $lpa myfile
Qedit does not see
this as an error and uses the $odd option, ignoring $even.
These options only
make sense if you are sending the list to a printer, either attached or
spooled. They have no effect when listing the file to the screen. For this
reason, you have to specify a destination printer using $lp, $lpa, $lpb,
$record or $device.
You can also use one
of these options as the default by using the Set List command. Specifying a
$-option on the List command overrides the Set value. There is currently no way
to completely ignore the Set options. If you want both options to be disabled,
you have to issue
/Set
List Even Off Odd Off
prior to the List command.
Double-Spaced Listings
When listing to LP, you can force the result
to be double spaced with List $double. This feature can be combined with most
of the other features of List, including LT, LQ, and Set List Page On. To make
all printer listings double spaced, do Set List Dbl On. LQ on a CCTL file
disables the Double option because the CCTL codes in the file control the
spacing on the listing.
LaserJet Listings
Qedit has two special options for HP
LaserJets: $duplex and $PCL. Duplex means double-sided printing, and PCL means
Printer Command Language, which is used to select fonts, spacing, and
orientation.
$Duplex
for Two-Sided Printing. Some LaserJets can print on both sides of the
paper; use List $duplex to enable this option.
PCL =
Printer Command Language. All LaserJets have several sizes of character
fonts and can print in either landscape or portrait orientation. To help you
take advantage of these features, Qedit has a number of PCL codes that can do
all the work for you. PCL stands for Printer Command Language, which is the HP
standard for printers. To specify a LaserJet option for a single listing, use
List $PCL; to configure all listings, use Set List PCL. To disable the special
PCL option, use PCL 0. Get a quick on-line listing of the PCL options with
Changing Fonts and
Orientation
Landscape-Tiny: PCL 1. To list to the
LaserJet in the tiny font that prints across the paper sideways (i.e., 16.67
pitch, landscape), use PCL 1.
/list
$device printer $pcl 1 all
Landscape-Regular: PCL 2. To list with
the regular Courier font in landscape orientation, use PCL 2.
The Standard: PCL 3. The normal default
for LaserJet output is portrait orientation (across the narrow side) with the
Courier font. However, once you insert a font cartridge into your LaserJet, it
may select one of the cartridge fonts as the default instead of Courier. PCL 3
allows you to select the standard Courier font, even if another font cartridge
is installed.
Portrait-Tiny: PCL 4. Some LaserJets
provide the tiny "Line printer" font in portrait orientation as well
as landscape orientation. PCL 4 selects this option.
A4
Special: PCL 5. To print 80 columns, instead of 77, across A4 paper using
the standard Courier typeface, try PCL 5. This tightens the spacing between
characters.
Legal-Landscape-Tiny: PCL 6. To print
tiny letters in landscape orientation on legal-size paper, use PCL 6.
You can combine
PCL 1, 2, 3, 4, 5, and 6 with Page On and Off, with Lines 0, with LQ, with
$DBL, with $record, and with $duplex.
Two-Column Listings
If your LaserJet supports "Line
printer" font in landscape orientation, you can print listings across the
page with two columns of text side by side.
/list $lp
$pcl 10 all {two-column listing
format}
/lq
$rec $pcl 10 1/200
If you have a
legal-size paper tray, you can use PCL 11 to print two wide columns of 110
characters each on a single piece of paper.
A4-Size Paper
Most of the PCL options, with the exception
of PCL 5, were designed and tested with North American letter-size paper. PCL 5
is especially for A4 paper; it reduces the horizontal spacing between
characters so that 80 columns of Courier output can fit on a single line. In
addition, if you add 2000 to a PCL code, Qedit adjusts the number of rows and
columns for that option to match A4 paper. For example, to print two-up
landscape on A4 paper, use PCL 2010 instead of PCL 10.
In general,
selecting A4 paper gives you more space along the long dimension of the paper
and less space along the short dimension. If you are happy with the way
letter-size rows and columns work on A4 paper, simply do not add 2000 to the
PCL code.
Summary of Qedit PCL Codes
|
PCL
|
L/P
|
Font
|
A4 Rows
|
A4 Columns
|
Letter Rows
|
Letter Columns
|
Notes
|
|
1
|
L
|
lp
|
58
|
188
|
60
|
175
|
|
|
2
|
L
|
courier
|
43
|
110
|
45
|
100
|
|
|
3
|
P
|
courier
|
64
|
77
|
60
|
80
|
"standard"
|
|
4
|
P
|
lp
|
85
|
128
|
80
|
132
|
|
|
5
|
P
|
courier
|
64
|
80
|
60
|
80
|
A4-squeeze
|
|
6
|
L
|
lp
|
60
|
223
|
60
|
223
|
legal-size*
|
|
10
|
L
|
lp
|
58
|
95
|
60
|
87
|
two columns
|
|
11
|
L
|
lp
|
60
|
110
|
60
|
110
|
2-up legal*
|
L/P mean landscape
or portrait orientation.
* Note: PCL 6 and
11 were designed to print on North American legal-size paper and will select
that size. However, you can see what happens with A4 paper by using 2006 and
2011. Some people have found this useful.
Roman-8 vs. ASCII
The PCL option requests a Roman-8 character
set, but some combination font cartridges only supply the ASCII character set
(half as many characters means twice as many fonts in a single cartridge). If
you ask for landscape Line printer and get landscape Courier instead, your Line
printer font probably has the ASCII character set instead of the Roman-8
character set. To request an ASCII font, add 1,000 to the PCL code. For
example, if you have a Super Cartridge (55 fonts in one!), use PCL 1001, 1004,
1006, 1010 and 1011. To select both ASCII and A4 paper, add 3000.
Folding Wide Lines
Qedit/UX might have difficulty handling files
without Newline delimiters at the end of each line or files with lines longer
than 8,172 characters. To be able to access these files, you can use the $length
option to specify the maximum number of
characters you want on each line.
The :Listredo command displays any of the
previous 1,000 commands.
LISTREDO [ start [ / stop ] ] [;ABS]
[;OUT=file]
[
string ] [;REL]
[
ALL | @ ] [;UNN]
(Default: display previous 20 commands)
(BJ, F7 and ,, are short for Listredo)
Commands are
numbered sequentially from 1 as entered and the last 1,000 are retained. You
can display a single command, a range of commands, all 1,000, or all the
commands whose name matches the string. You can print the commands with
ABSolute line numbers (the default), RELative line numbers (-5/-4), or
UNNumbered. The OUT option is not available for Qedit/UX. If you want to redo
any of these commands, see :Do, :Redo, and Before.
Examples
/listredo
5
/listredo
5/10
/listredo
help {print all Help commands}
/bj {historical shorthand!}
/listredo
-10 {print last ten commands}
/listredo
ALL {print entire redo stack}
/listredo
rm {print all rm commands}
/listredo
rm xx {print all "rm
xx" commands}
/listredo
@rm {print all with "rm"
anywhere}
/listredo
@;rel {print all, relative
numbers}
Notes
The :Listredo
command can be abbreviated to ",," or BJ, or can be invoked by the F7
function key. Using F7 to invoke Listredo only works in Line mode, not Visual
mode. You cannot use ";" to combine commands on the same line.
Displays the complete Undo change log of
commands that modified text, starting with the most recent and working
backward.
LISTUNDO
Listundo shows the complete Undo change log,
including each command, the number of lines updated, deleted, added, or
renumbered by that command, and the text lines. Text for deleted lines is
preceded by an underscore ("_") as in the Delete command, and the
"before" value of lines that were updated has a Greater Than
">".
Commands are
printed in reverse order, with the most recent command first. This is the
command that would undone by the next Undo command. To stop the Listundo
report, use Control-Y.
Examples
Display contents of a directory.
LS names
(Default: current
directory)
Qedit has a
command called Lsort. Due to Qedit's shorthand command parsing, ls would be
interpreted as Lsort. The Lsort command is retained for compatibility with the
MPE version of Qedit, but Qedit/UX accepts ls to mean the HP-UX ls command.
Examples
/ls {current directory}
/ls
-a {show hidden files also}
Sorts a range of
lines.
LSORT range [
KEYS keylist ]
LSORT string range [
KEYS keylist ]
(Q=no display)
(Default: by entire
line)
The simplest Lsort command just specifies a range of lines
to be sorted and no other parameters. This means to use the entire line as the
key and sort the lines into ascending order, printing them once sorted.
To stop Lsort from printing the sorted lines, use LsortQ.
The Lsort command can be abbreviated to "lso", "lsq"
(quiet), "lst" (template) and "lsj" (justify).
"ls" followed by a space executes the HP-UX shell command. "ls"
followed by any other character is executed as a possible shell command.
Parameters
To sort by some other key fields in the lines (from one to
four are supported) or to sort the lines in Descending Order, you need to
specify the KEYS keylist parameters.
The keylist consists of one to four
keys separated by spaces or commas, with a key consisting of either a column
range or a starting column and length:
column , length [DESC]
column / column [DESC]
Ascending Order is assumed by default, but you may specify
DESC to sort this key in Descending Order.
Examples
/lsort all
{sort entire file}
/lsortq all
{sort without printing}
/lsort 10/33
{sort some lines only}
/lsort 30/last keys 10,5 {col 10 through 14}
/lsort zz keys 10/20 {col 10 through 20}
/lsort 20/last keys 1,10 20,5,desc {two keys}
Merges an external file into the current
workfile by line number. Use Merge to apply source-code
"changes-files" containing new and revised text, that are distributed
by some application vendors.
MERGE filename [ (rangelist) ]
(Q=no display, J=Justified)
(Default: rangelist:
ALL)
MergeQ suppresses
printing of the merged lines.
The optional rangelist specifies a subset of the
external file to merge into the current file.
Examples
/text
master.src {start with the master file}
/merge
changes {update changed lines, add
new}
Notes
To make your own
"merge file", create a file that contains edits to be applied to your
current workfile. Mark the lines of text that will replace existing lines in
your workfile, with the corresponding line numbers. Give new line numbers to
any completely new lines of text to be added to your workfile. $Edit Void
removes the line number specified in the command and, optionally, lines up to
and including a Void= line number. Warning:
the Void= parameter cannot accept
a decimal point so, for example, you must enter Qedit line 60.1 as 60100. To
delete from line 55 to 60.1, you would use the following:
Justified
The default is to
replace existing lines with the corresponding line from the external file. The
Justified option appends the corresponding line from the external file. Text is
appended immediately after the last non-blank character if Set
Work Trailingspaces is disabled. If Trailingspaces is enabled, text is
appended immediately after the last significant trailing space. If the
resulting merged line is too long for the current length, the merged line is
truncated. Let's say the current workfile contains:
and the external file contains:
A MergeJ would result in:
If the maximum length was 5, the resulting file would be:
/mergej myfile
1 11111
Warning: Result line
will be too long. Truncating merged
text.
2 22222
Warning: Result line
will be too long. Truncating merged
text.
3 33333
Warning: Result line
will be too long. Truncating merged
text.
3 lines merged
/l all
1 abc11
2 def22
3 ghj33
Editing characters within lines using either
Control codes (default Set Mod Robelle), D-I-R-U edits (Set Mod HP), or Control
codes with visible feedback (Set Mod Qzmod).
MODIFY rangelist
(Q=no linenum, T=template)
(Default: rangelist
= *)
By default, Modify
displays the first line and puts the cursor under the first column. You enter
an "edit-line" to specify a changes. You use spaces to move the
cursor under the word you want to change, then type new characters to replace
those in the columns above. For example:
/modify 5
5
Over 2000 computers use Suprtool.
{prints line}
750 {you edit it}
5
Over 2750 computers use Suprtool.
{prints new line}
<Return> {end Modify}
Each time you
press Return, Modify applies your changes to the line and prints the new
result. This cycle continues until you enter only a Return (no more edits).
You use nonprinting
Control codes for editing, such as Control-D to delete. For visual feedback, do
Set Mod Qzmod, which puts your cursor right on top of the line and responds to
each Control code by revising the image on the screen (i.e., Control-D actually
makes the character disappear from the screen). If you would prefer to use
MPE-style edits (D-I-R-U) instead of Control Codes, do Set Mod HP to
reconfigure Modify.
To force the line
number onto a separate line, use Set Mod Prompt OFF.
Examples
/modify
5/ {modify from line 5 until ^Y
or end}
/find
"corelate";m {find spelling error and modify line}
/mod
"q_flag" {modify all lines
with "q_flag"}
Getting into Modify Mode
There are other commands that invoke Modify
mode in Qedit:
·
Change, when a line overflows or you use CJ.
·
Add, when you use the auto modify character from Set Zip.
·
Before, so that you can revise and redo a
previous command.
·
Redo, also enables you to revise and redo a
previous command.
Edit Functions of Modify
Here are the edit
functions of Modify and their Control codes, which may be changed with the Set
Modify command.
|
Function
|
Key
|
Purpose
|
|
Overwrite
|
Control-O
|
Replace characters
(default).
|
|
Delete
|
Control-D
|
Delete characters.
|
|
Before
|
Control-B
|
Insert characters
before a column.
|
|
Append
|
Control-A
|
Add characters to
end of the line.
|
|
Divide
|
Control-V
|
Divide line in two
at this column.
|
|
Goof
|
Control-G
|
Restart Modify
with original line.
|
|
Terminate
|
Control-T
|
End this edit so
you can do another.
|
|
Lengthen
|
Control-L
|
Same as Append (Control-A).
|
|
Insert
|
Control-^
|
Same as Before
(Control-B).
|
HP-UX reacts to certain control characters which might
conflict with the Qzmodify codes. For example, control-D sends an end-of-file
signal to HP-UX but is also the delete character in Qzmodify. You should use
the HP-UX stty program to change the
default end-of-file signal. Please see the section "Control
Characters and stty" on page 48 for
more details.
You create Control codes by holding down the
Control key while pressing the other key. Most Control codes are invisible and
do not move the cursor. In the user manual, the symbol (^) as a prefix stands
for the Control key (^-D for Control-D).
Some functions
combine two of the Control codes: pressing ^-T then ^-V in the first column of
a line splices two lines together
(and deletes the second line if it's emptied). Actions not restricted to column
1 may be performed at any point on the line.
|
Function
|
Key
|
Col.
|
Purpose
|
|
Splice
|
^T ^V
|
1
|
Fills current line
from next line.
|
|
Insert Line
|
^A ^V
|
1
|
Adds a blank line before current one.
|
|
Insert Line
|
^A ^V
|
|
Adds a blank line after current line.
|
|
Delete Last
|
^A ^D
|
|
Spaces remove
characters at end of line.
|
|
Replace End
|
^A ^O
|
|
Replaces from end
of line (overwrites).
|
|
Delete Line
|
^T ^D
|
1
|
Deletes current
line.
|
Overwriting Characters
To overwrite
characters in a line, type the new characters underneath the ones to be
replaced. There is no need to type a control character; "overwrite"
is the default edit function. Once you are in Overwrite mode, you can also use
the Space bar to erase the columns that you move through. If you have not yet
typed any characters, the Space bar just moves your column position to the
right one place. You can get into Overwrite mode at any time while in modify by
pressing Control-O. Terminate overwrite mode and go into space- transparency
mode by typing Control-T.
Start Over Editing a Line
To correct a Modify mistake, enter the Goof
control code (Control-G) and press Return. Qedit restores the line to its
original contents and restarts the Modify cycle. Control-G does not undo Splits
and Splices.
Doing Several Edits in One
Line
You can do more
than one edit operation in one edit-line if each edit is clearly separated from
the preceding and following ones. When the edits are at different ends of the
line, you must Terminate the first function so that you can move the cursor
right to the next column. The Terminate control code (Control-T) provides this
capability.
The following
illustrates where to place your control codes (^ stands for the Control key),
even though they will not appear on your screen. The first example capitalizes
the "r" in "return", then replaces "in error"
with "by mistake", which requires inserting the letters
"ke." The second example inserts the word "Goof" and a
space at the start of the line, and deletes the last two words at the end of
the sentence, adding a final period.
/m 13
13 a
return. If you do this in error,
{displays line}
R by mistake {^codes are: }
<spaces>
R<^T, spaces> by mista<^B>ke<Return>
13 a
Return. If you do this by mistake,
{redisplays}
/m+1
14
control code restores the line for you. {displays line}
Goof . {^codes are: }
<^B>Goof
<^T, spaces> .<^D, Return>
14
Goof control code restores the line.
{redisplays}
Deleting Characters
To delete characters from the line, starting
with the current column position, enter the Delete control code (Control-D).
Then space to the right the number of columns to be deleted. Any remaining
characters in the line are left-shifted to fill in the deleted columns.
In all cases, the
columns deleted are those immediately above the cursor, regardless of what
other functions have been performed previously on the same line. The Delete
function is stopped by the first nonblank character, either Return, a printing
character to switch back into Overwrite function, or another control code.
HP-UX reacts to certain control characters which might
conflict with the modify codes. For example, control-D sends an end-of-file
signal to HP-UX but is also the delete character in modify. You should use the
HP-UX stty program to change the
default end-of-file signal. Please see the section "Control
Characters and stty" on page 48 for
more details.
Erasing the Line
To erase from the
current column to the end of the line, enter the Delete control code, followed
by a Return. If you do this by mistake, the Goof control code restores the line
for you.
Inserting Characters
To insert characters in the line before the
current column position, enter the Before control code (Control-B). Then type
the characters to be inserted. The existing characters starting in the insert
column are right-shifted to make room for the new characters.
On the operator's
console of Seried 800 compputers, the Control-B character puts the terminal
into "maintenance" mode. In these cases, use Control-^ instead. If
you do press Control-B on the console accidentally, type "CO" on a
Series 800 or 900.
Adding Characters to the
End of a Line
To add characters to the end of the line
after the last nonblank character in the line, enter the Append control code
(Control-A). Then type the characters to be added. This function is independent
of the current column position.
Dividing a Line into Two
Lines
The Divide control code (Control-V) splits
the current line into two lines at the current column position. If a line
number is available, Qedit moves all characters from the current column to the
end of the line to a new line that is added after the current line. The Goof
function recalls the original contents of the line, but does not delete the new
line (neither does Control-Y). See also Divide command.
Splicing Two Lines
Together
To splice two lines together, you must be on
the first column of the first line you wish to splice. Type Control-T, then
Control-V, and quick as a wink, all the characters from the second line are
appended to the end of your current one. Qedit moves only as many characters as
will fit. If all the characters are moved, the second line, now empty, is
deleted. See also the Glue command.
Editing Lines with More
Than 80 Columns
To modify long
lines (i.e., more than 80 columns), use Set Left and Set Right to define a
slice through the lines.
/set left 55
/mqt
* {quiet, with template}
+....60...+....70...+....80...+....90...+....100..+....
ubsequent
Sales Follow-up - Completion Ratio Report
Or use Set Modify
Qzmodify, it handles long lines without the need to set margins.
Qzmodify: WYSIWYG
You may want to try Set Modify Qzmodify to
replace the normal Qedit modify with a "visual" modify (What You See
Is What You Get). Qzmodify uses the same Control codes, plus many extensions,
but Qzmodify does single-character reads. This allows it to respond immediately
and visually to each keystroke, but means that the performance is unacceptable
over NS, packet-switching LANs, and the DTC. Once in Qzmodify, type Control-Q
for a list of commands.
How to Edit in Qzmodify
In Qzmodify,
"what you see is what you get". The cursor rests on the same line as
the text you are editing. If you press any printable key (ASCII code 32 or
greater), that key either replaces the character the cursor was on, or (if
Insert mode is on) inserts the key before that character, moving the rest of
line to the right by one character.
When you initially
enter Qzmodify you are in Transparent mode--here, a blank simply causes the
cursor to move one space to the right. Pressing any other printable character
immediately terminates Transparent mode and puts you in Overwrite mode, so the
character replaces the one the cursor is on. The three basic modes are:
|
Mode
|
To enter
|
To exit
|
|
transparent
|
^T
|
any printable
char, ^B, ^O, or ^X
|
|
overwrite
|
^O
|
^T, ^B, or ^X
|
|
insert
|
^B or ^^
|
^T, ^O, or ^X
|
Qzmodify will not
allow you to create a line longer than a maximum specified by the calling
program, nor can you accidentally "lose" characters off the right
edge when using Insert mode ... Qzmodify beeps when you try to do something
illegal. To edit Roman-8 characters, use Set Editinput Extend ON.
Editing Commands
Qzmodify has an extensive set of commands,
all of which are invoked via control characters. In this documentation, the
symbol ^ means that the following character is a control character (e.g., ^G is
control-G). Control characters may be entered as lowercase or uppercase letters
(i.e: ^g and ^G are identical).
HP-UX reacts to certain control characters which might
conflict with the Qzmodify codes. For example, control-D sends an end-of-file
signal to HP-UX but is also the delete character in Qzmodify. You should use
the HP-UX stty program to change the
default end-of-file signal. Please see the section "Control
Characters and stty" on page 48 for
more details.
|
Char Mnemonic
|
Description
|
|
^A append
|
Go to end-of-line.
Moves the cursor to just after the last character on the line. If the line is
already at the maximum length, the cursor is placed at the last character.
|
|
^B before
|
Turn on Insert
mode. Turns off Overwrite mode. If you enter a character while in Insert
mode, it will be put Before the character the cursor is on, and the rest of
the line will move one to the right.
|
|
^^ before
|
Control up-arrow...synonym
of ^B. Use ^^ instead of ^B if you are on a system console!
|
|
^C case
|
Change case of
current character. If the current character is a lowercase letter, it will be
changed to an uppercase letter and vice versa.
|
|
^D delete
|
Delete character.
Pressing ^D will cause the character under the cursor to be deleted, and the
rest of the line to be moved one space to the left.
|
|
^L^D delete end
|
If the cursor is
just past the last character in the line, (i.e., you just did a ^L or ^A),
then the ^D will delete the last character of the line.
|
|
^E erase
|
Erase to end of
line. This will erase all of the text from the cursor to the end of the line.
|
|
^F<c> find
|
Find next
occurrence of character <c>. The cursor will be moved to the next
occurrence of the character <c> to the right of the cursor. If
<c> is not found, you will hear a beep.
|
|
^F<n><c>
|
Find nth
occurrence of <c> where 1<=n<=8.
|
|
^G goof
|
Undo all current
modifications. Restores the line of text to its original form. Note: ^V, ^K,
^T^D, and ^T^V cannot be undone.
|
|
^H backspace
|
Move back one
character (nondestructive).
|
|
^I tab
|
Skip ahead to the
next tab stop.
|
|
^J justify
|
Deletes blanks
from the cursor to the first nonblank (does not delete that character).
|
|
^K add
|
Requests Qedit to
add a line after the current line. The current line will then be redisplayed
for editing and you will get to edit the new line.
|
|
^L lengthen
|
Go to
end-of-line...synonym of ^A. Use ^L instead of ^A if you are on a Type Ahead
Engine (TAE).
|
|
^M return
|
Marks the end of
editing a line. Returns the modified line to Qedit. Note that ^M is the same
as Return.
|
|
^O overwrite
|
Initiates
Overwrite mode and turns off Insert mode (^B). In Overwrite mode, if you
enter a character, it will replace the one on the screen.
|
|
^P<#><dir>
|
Moves up or down
some number of lines of text. For example, ^P3- moves back three lines.
|
|
^Q query
|
Displays list of
Qzmodify functions.
|
|
^S<c> scan
|
Find previous
occurrence of <c>. The cursor will be moved to the first occurrence of
<c> to the left of the current cursor position. If <c> is not
found, you will hear a beep.
|
|
^S<n><c>
|
Find nth
occurrence of <c> where 1<=n<=8.
|
|
^T Transparent
|
Terminates Insert
mode and Overwrite mode. After ^T, if you type blanks, the cursor simply
moves right one space without affecting the text. Transparent mode is always
turned off automatically whenever a nonblank printable character is entered,
then Overwrite mode is turned on.
|
|
^T^D delete
|
If done at column
one, this deletes the entire line.
|
|
^T^V splice
|
If done at column
one, this will join the next line to the end of the current line and display
the spliced line for editing. If not a column one, then is the same as ^V.
|
|
^U jUmpback
|
Move back to the
previous tab stop. This is the opposite to ^I. As an aid to remembering them,
^I is the same as pressing the tab key, and ^U is just to the left of ^I on
the keyboard.
|
|
^V split
|
Split the current
line (at the cursor) into two lines and modify both of them. Note that ^Y
restores the text if you decide not to make the change, but you have to
manually remove the second split-off line.
|
|
^X eXamine
|
Examine
(redisplay) the current line.
|
|
^Y abort
|
Terminates modify without changing the current line.
|
|
^W Wordproc
|
Shifts into
"word-processor" mode. In word-processor mode, the next control
character is used to select a function. The functions are:
|
|
^W^C
|
Compress multiple
blank spaces to single blank spaces.
|
|
^W^D
|
Delete Word.
Deletes from the cursor to the next blank, and then any following blanks up
to (but not including) the next nonblank.
|
|
^W^H
|
Toggles a flag
that remembers if you have an HP 110 (or an HP 2640). The flag is needed
because the HP 110 knows only a subset of the "standard" HP 26xx
escape sequences, and some of them incorrectly!
|
|
^W^L
|
Draws a ruled
"line"; similar to the ListT command.
|
|
^W^N
|
Toggles Numbered
mode. A line-number prefix will be displayed in front of a line of text only
if both of the following are true:- line numbers have been requested (either
via a Modify command from Qedit or via ^W^N);- the line number was passed to
Qzmodify by Qedit (i.e., you did an Modify command, not an ModifyQ command)
|
|
^W<c>^D
|
Delete all
characters from the cursor up to, but not including, character <c>.
Note: <c> must be a printable ASCII character (character code > 31).
If the cursor is currently on the same <c>, it is deleted immediately
before looking for the first <c>. If <c> is not found, nothing is
deleted.
|
|
^W^P<c>
|
Put the character
into the text. This is useful when you want to put a control character into
the text. All nonprintable characters will be displayed as periods (.), so
they will take up one space on the line.
|
|
^W^S^D
|
Downshift all
letters from the cursor to end-of-line.
|
|
^W^S^U
|
Upshift all
letters from the cursor to end-of-line.
|
|
^W^S^T
|
Reverse the case
(e.g., "a" becomes "A" and "A" becomes
"a") of all letters from the cursor to end-of-line.
|
|
^W^T
|
Toggles the Type
Ahead Engine (if you have one) through three states: disabled, enabled,
ignored.
|
|
^W^V
|
Prints the version
ID of Qzmodify.
|
|
^W?
|
Display the ASCII
character code for the character that the cursor is on.
|
|
^W$<hh>
|
Replace the
character at the current column position with the ASCII character whose
hexadecimal value is <hh>.
|
Symbols Used in Qzmodify
Command List
<c> is any
single character. Qzmodify will search for this character. If <c> is ^W,
the search will be for the next word (words are anything delimited by blanks)
instead of for a single character.
<#> is zero
or more digits. For example, ^P12+ would mean move forward 12 lines. ^P3- would
move back three lines.
<n> is one
of: ^A, ^B, ..., ^H and is interpreted as the number 1, 2, ..., 8 respectively.
<dir> is a
"-" to move "back", or a "+" to move
"forward".
<hh> is any
pair of hexadecimal digits.
Note: When
modifying a line longer than 79 characters, some commands (e.g.: ^D, ^B, ^E)
will not update any line of the screen display other than the one you are on.
Whenever you want to see an accurate display of your text line, press ^X to
refresh the display. This limitation could be fixed, but only at the cost of
slowing down response time while editing these longer lines.
Note: You cannot
use the special keys on an HP terminal (e.g.: cursor keys, insert char, delete
char, clear) because they are designed to either send no characters to the
computer when they are pressed or two characters ... and both of these choices
cause difficult problems unless you are on an HP e3000 with a Type Ahead
Engine. Thus, these keys should not be used. If you use them by accident, a ^X
will refresh the display of the line you are editing.
Qzmodify with a Type Ahead
Engine
The Type Ahead Engine (TAE) from Telamon can
be in one of three states from the Qzmodify viewpoint: disabled, enabled, or
ignored. Each is defined below.
Ignored. Qzmodify will not do anything
to either encourage the use, or discourage the use, of the TAE. This is usually
the initial state (see below).
Enabled. Qzmodify will place the TAE in
single-character mode at entry, and restore it to Line mode at exit. This means
that the HP3000 won't lose typed ahead input anymore, and that the special keys
(e.g., cursor keys) will work nicely.
Disabled. Qzmodify will disable
typeahead (by sending ^A^V to the TAE) at entry, and enable it at exit. In this
mode, the TAE is effectively taken out of the "circuit".
With Qedit, you
configure TAE-treatment as part of the Set Modify Qzmodify command:
Set
Mod Qzmodify {ignore the TAE}
Set
Mod Qzmod TAEOFF {TAE exists, disable it}
Set
Mod Qzmod TAE {TAE exists, enable it}
When the TAE is
present and enabled, you can use these extra commands:
|
^W^T
|
Toggles the Type
Ahead Engine through three states: disabled, enabled, ignored.
|
|
leftarrow
|
The HP26xx
left-arrow key will move the cursor 1 space to the left.
|
|
rightarrow
|
The HP26xx
right-arrow key will move the cursor 1 space to the right.
|
|
up arrow
|
Move up to the
prior line of text, leaving cursor in the same column. The terminal screen is
scrolled DOWN, so the line you were just editing is moved down 1.
|
|
down arrow
|
Move down to the
next line of text, leaving cursor in the same column. The terminal screen is
scrolled UP, so the line you were just editing is moved up 1.
|
|
delete char
|
Deletes the
character under the cursor (like ^D).
|
|
insert char
|
Turns on Insert
mode (like ^B).
|
|
insert line
|
Asks Qedit to add
a new line after the current line.
|
|
delete line
|
Asks Qedit to
delete the current line.
|
|
^leftarrow
|
Moves cursor LEFT
to the blank just after the nearest "word" on the left of the
cursor. Valid only if a Type Ahead Engine is present and enabled. Only
available on HP264x terminals.
|
|
^rightarrow
|
Moves cursor RIGHT
until it reaches the start of the next "word" (will not move past
current end of text.) Valid only if a Type Ahead Engine is present and
enabled. Only available on HP264x terminals.
|
Hpmodify: No Control
Characters
Set Modify Hpmodify replaces Qedit's standard
Modify in all places with MPE-style editing (D for delete, I for insert, R for
replace, U for undo, > for append, >D for delete at end, >R for
replace at end, and D> for clear). We suggest Hpmodify when using Qedit over
finicky datacomm networks, since it does not require any Control codes.
Hpmodify Keys - Reference
|
Directive
|
Effect
|
|
i
|
INSERT. If text
follows the i, this text is inserted in the current line, starting at the
position of the i.
|
|
r
|
REPLACE. If text
follows the r, this text replaces the same number of characters in the
current line, beginning at the position of the r.
|
|
d
|
DELETE. Deletes a
character from the current line for each d specified in the edit line. Note
that "d d" does not specify a range as it does in MPE V but simply
deletes one character above each d. Multiple d's may be followed by an Insert
or Replace operation.
|
|
d>
|
DELETE. Deletes to
the end of the current line from the position specified by d>. May be
followed by an Insert or Replace operation.
|
|
>
|
APPEND. If text follows the >, this text
is appended to the end of the current line. If a > without text is
positioned beyond the end of the current line, then a simple replacement is
performed instead.
|
|
>d
|
DELETE. Deletes
from the end of the current line, right-to-left. Multiple d's and Insert and
Replace strings may be specified after > .
|
|
>r
|
REPLACE. Replaces
characters at the end of the command line. The last (rightmost) character of
the replacement string is at the end of the line.
|
|
c
|
CHANGE. Changes all occurrences of one
string to another in the current line starting at the c. The search string
and replace string must be properly delimited. A proper delimiter is a
nonalphabetic character (such as ' " or /) The substitution is specified
as cdelim search-string delim [replace-string [delim]]. Omitting the replace-string
causes occurrences of search-string
to be deleted, with no substitution.
|
|
u
|
UNDO. A single u in column one cancels the
most recent edit of the current line. Using the Undo command twice in a row
cancels all edits for the current line and re-establishes the original,
unedited line. If u is placed anywhere other than column one of the current
line, then a simple replacement is performed. Undo makes sense only if you
have a line on which you have performed some editing that can be
"undone."
|
|
other
|
Simple replacement.
Any other character (not i, r, d, d>, >, >d, >r, c, or u) will be
put into the current line at the position above where it is placed, replacing
any existing character. Simple replacement also occurs for the editing
characters i, r, c, or > if they are not followed by text; or if >
appears at or beyond the current end of line.
|
Hpmodify Examples
|
Edit
|
Action
|
|
u
|
First occurrence
undoes the previous edits. The u must be in column one.
|
|
u
|
Second occurrence
undoes all edits on the current line. The u must be in column one.
|
|
rxyz
|
Replaces the
current text with xyz starting at the position of r.
|
|
xyz
|
Replaces the
current text with xyz starting at the position of x.
|
|
ixyz
|
Inserts xyz into
the current line, starting at the position of the i.
|
|
ddd
|
Deletes three
characters, one above each d.
|
|
d xyz
|
Deletes a single
character above the d, skips one space, then replaces the current text with
xyz starting at the position of x.
|
|
ddixy
|
Deletes two
characters, then inserts xyz in the current line starting at the position of
the i.
|
|
d d
|
Deletes one
character above the first d, skips two spaces and deletes a second character
above the second d. It does not delete a range of characters, making it
unlike the MPE V version of Redo.
|
|
d d>xyz
|
Deletes a single
character above the first d, skips two spaces and deletes to the end of the
line beginning at the second d, and then places xyz at the end of line.
|
|
>xyz
|
Appends xyz to the
end of the current line.
|
|
>ddxyz
|
Deletes the last
two characters from the end of the current line and then places xyz at the
end of the line.
|
|
>rxyz
|
Replaces the last
three characters in the current line with xyz.
|
|
>ixyz
|
Appends xyz to the
end of the line. In this case, the i command is superfluous, because >
accomplishes the same result. Using >xyz would be sufficient.
|
|
c/ab/def
|
Changes all
occurrences of ab to def, starting at c.
|
|
c"ab"
|
Deletes all
occurrences of "ab" starting at c.
|
|
cxyz
|
Replace the
current text with cxyz, starting at c. Because delimiters have not been
specified (as they were in the previous two examples), this is a simple
replacement with the four characters.
|
Creates a new, empty Qedit workfile and opens
it. This can be either an unnamed extra scratch file or a named workfile. The
advantages of a workfile are that you can instantly Open and Shut it, and that
it compresses your data. You can use Text to make a copy of a Qedit file when
you wish to protect the work you have done.
NEW filename [,language [ (size) ]
NEW
(Default: extra scratch, 3200 lines)
Qedit shuts the
current file and builds filename,
which it then opens for editing. If you leave out filename, Qedit creates a new extra scratch file and assigns it a
number (1,2,3..) so that you can recognize it in Verify Open and Open ?. Up to
eight extra scratch files are allowed (see also the TextJ command). You cannot
Exit without discarding or saving any edits you have done in an extra scratch
file.
The language defaults to the current Set
Lang value, but can be overridden.
If you want to force creating a Wide-Jumbo
format, you should set the Length to a value larger than 1,000 before issuing
the New command.
/Set
Length 2500
/New
newwork
These commands
create a new permanent workfile called Newwork. If you want to create a new
scratch file, enter the New command by itself.
The optional size is ignored by Qedit/UX. The maximum number of lines in a
Qedit/UX workfile is 99,999,999.
Examples
/new {create an extra scratch
file}
/new
memos {create an empty
file named Memos}
/set
lang job {define file as
80-column records}
/add
/new
frankie {build frankie}
/aq
1=johnny {memos was shut automatically}
Building Workfiles with Text
You can also create new workfiles while doing
a Text command.
/t
frankie=johnny {build Frankie
file ...}
{and copy Johnny
into it}
Instantly opens or reopens a Qedit file for
editing or browsing, as opposed to the Text command which creates a copy of a
file for editing.
OPEN filename[,BROWSE|DEFER|NODEFER]
*
*-n
?
(Default: edit
primary scratch file)
Qedit shuts the
current workfile and opens filename.
The filename must exist (see New and
Text) and must be a Qedit workfile or scratch file. You cannot Open a Keep file
- you must first Text it into a scratch file.
Open filename,Browse
opens a workfile for browsing in Qedit. You can use the List command, including
List-Jumping, Hold, Visual mode HH and ZZ, and any other functions of Qedit
which do not modify the file.
Open-Browse protects you from making unplanned changes to a file.
If you try to Keep
the file with its original name i.e. you enter a Keep without a filename, you
will get an error.
/Open
workfile,browse
/Verify
Keep
Set
Keep Name txtfile
/K
File
opened with Browse, please specify a Keep file name
You can still
force a Keep by specifying an explicit filename as in:
/Open
workfile,browse
/Keep
txtfile
TXTFILE.DATA.ACCT,OLD
80B FA # of records=16
Purge existing file [no]? y
Open filename,Defer opens the workfile
without write access, but acquires write access later if you attempt to modify
the file. Set Open Defer On makes Defer the default and Open filename,Nodefer overrides that command.
It is important to
remember that certain workfile attributes and settings are normally saved when
the file is opened with write access. Some of these settings are the ZZ marker,
the current line marker (*), and a new default Keep name modified with Set Keep
Name. If you open a workfile in Browse mode, these settings are not updated
unless the file is re-opened with write access.
To reopen the file
most recently accessed, do open *;
for the file before that do open
*-1, then open
*-2, and so. To select from a list of recently accessed files, do open ?.
Examples
/open
mail {want to edit Mail}
/c "stop"start" @
/open
* {reopen previous file}
/list all
/open
? {select a recent file}
/visual
/open
*-1 {select file before
last}
/list "function"
/open
*-2 {select file before
that}
/hold 400/500
/open {edit scratch file}
Notes
Since you must
Open a file before editing, any command that requires an Open file creates a
scratch file if none is Open.
If you attempt to
Open a file which is not a Qedit workfile, you see a message similar to the
following:
/open qpart2
Error: Cannot open a non-Qedit file. Use Text command.
You need to Text
this file, not Open it.
The Open Stack
Qedit maintains an Open-Stack of the ten most
recently Opened files. One of these is always reserved for the primary scratch
file. You can have up to eight extra scratch files (see TextJ and New), which
take priority over named workfiles in the Open-Stack. To reopen one of these
files, do an open ?
command. Open ? prints the list and prompts for a relative file number,
starting with zero for the most recent (same as Open *).
Open
*-n allows you to open one of
the recently accessed files directly. Open
*-2 opens the third file in the list, since zero is the first.
When you open any
file it moves to the top of the list and the other files are pushed down one
position. The Close command shuts the current workfile and removes it from the
list of recently accessed files. This is useful to stop desired file names from
dropping off the bottom of the list. If the file is a scratch file, you are
prompted to Discard Changes.
Set Open Defer On
If you use Set Open Defer On, the Open
command does not acquire write access to a workfile until you make a change to
it. The workfile is opened with read access by default, unless Qedit knows you
are going to be writing to it (as when Text or Add force an Open). If you only
browse through the file, the Last-Mod date does not change. This includes
full-screen mode viewing. However, if you make any changes to the file or use
Set Left/Right/Length /Lang, Qedit reopens the workfile with write access.
It is important to
remember that certain workfile attributes and settings are normally saved when
the file is opened with write access. Some of these settings are the ZZ marker,
the current line marker (*), and a new default Keep name modified with Set Keep
Name. If you explicitly open a workfile in Browse mode or use Set Open Defer
On, these settings are not updated permanently unless the file is re-opened
with write access.
You can override
the current Set Open Defer value by doing Open filename,Defer or Open filename,Nodefer.
There are a few
error conditions that may occur if you attempt to modify a file because now someone
else can edit the file while you have it open. For example, you cannot obtain
write access if someone else already has write access to the file. In Visual
mode, you may see the error "Unable to reopen file with write access.
Concurrent usage/backup?".
If "Error: File open by another Qedit Process"
appears when you try to open a file, it means that someone else is editing the
file.
If you are working
in Visual mode, someone can delete the lines you want to edit after Qedit has displayed
them on your screen. If this happens, Qedit does not update your screen and
displays this error message: "File has changed since page last displayed.
Another user?"
Crash Recovery
Qedit ensures the validity of workfiles after
a system crash or program termination. It checks to see whether the file was
properly closed the last time. If the file was in the midst of Renumber, Qedit
completes the renumber. If the file was in the middle of a Text, Qedit clears
the file so you can do the Text over again. In all other cases, Qedit prints a
RECOVERY warning and searches through the file to eliminate any duplicate
lines. After a RECOVERY, examine the area of lines that you were last editing.
A few lines may be missing or out-of-date, but that is all.
File Modification
Timestamp
When you use the Text or Keep commands on a
file, Qedit stores the file's modification timestamp in the workfile. If you
Shut the workfile to do something else, the next time you Open it, Qedit will
compare the stored value with the file's current timestamp. If they are
different, it means that the original file has changed either since you last
worked on it or since the last time you saved your changes. Qedit will alert
you to the difference by displaying a message similar to the following:
Warning: Original file has been modified since
the
initial Text or last Keep !
The file timestamp
can change for a number of reasons. Here are few examples:
·
Someone else might have been working on that
same file with Qedit and saved their changes before you did.
·
The file could have been restored.
·
Maybe you used the file to test a program which
modified the file in some way.
Because the
timestamp message is just a warning, Qedit continues its processing. However,
if you want to be sure you are not missing important data, you should compare
the contents of the file with your workfile and decide if it is safe to
continue editing your copy.
This is one way to
compare the files:
·
Use Verify Keep and write down the default Keep
name
·
Keep the workfile under a different name
·
Use our Compare bonus program to display the
differences between the original file and the new version you just created
·
Look at the report and separate the lines that you
changed from the ones you did not touch
·
If needed, apply changes to your copy so that
you do not miss anything important
It is important to
remember that certain Qedit commands will shut and open workfiles on your
behalf. The timestamp warning might appear when you do not expect it.
By default,
timestamp checking on Open is disabled. If you want to change this setting, you
can use the Set Open Checktimestamp command.
Calls internal procedures to downshift and
upshift lines.
PROC [ DOWN | UP ] [ rangelist
]
(Defaults: previous proc)
For DOWN and UP,
the default rangelist is the current
line (*); PQ shifts quietly (i.e., without printing the lines); and PJ shifts
with user verification (i.e., PJ prints each shifted line and asks you to
approve it).
Built-In PROCs to Shift Up
or Down
The Up and Down
Procedures put Roman-8 characters into uppercase or lowercase if Set Editinput
Extend is On. Otherwise, they only operate on A-Z and a-z.
The first time
that you use Down or Up after running Qedit, they ask you to configure them.
There are 4 options: 1 means to shift every alpha character in the lines, 2
means to skip over characters enclosed in double quotes ("), 3 means to
skip over characters enclosed in single quotes ('), and 4 means to skip over
characters enclosed in either double quotes or single quotes. If Down (or Up)
finds a line with unmatched quotes, it prints a warning and stops (unless the lines
are part of a COBOL program, in which case unmatched quotes are okay).
/open
qedit.doc {open document file}
/list
415.1 {display a line}
415.1 You will need to Purge the
old file.
/proc
down 415.1 {try it lowercase}
Set
Shift DOWN? 1(@) 2(") 3(') 4("
or ') [0]:2
415.1 you will need to purge the
old file.
/proc
up 415.1 {try it uppercase}
Set
Shift UP? 1(@) 2(") 3(') 4("
or ') [0]:2
415.1
YOU WILL NEED TO PURGE THE OLD FILE.
/proc
down {lowercase is better}
/proc
410/415 {downshift some more
lines}
/pq
420/1002 {many more! quietly}
/pj
up 1003 {upshift with
approval}
1003
>GET D-LINE (Okay?) yes
If you always
configure the shifting routines to the same option (e.g., skip strings with
double quotes), you can use Set Shift to define the configuration:
Prints a message on $stdlist.
Q [ "string"
]
(Default: print a blank line)
The string of up to 80 characters is printed
on $stdlist.
Use the Q command
to print prompts from usefiles. This works especially well when you use a file
quietly.
Enables you to modify and repeat any of the
previous 1,000 command lines.
REDO [ start [ / stop ] ]
[
string ]
[
ALL | @ ]
