16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

tcsh<br />

–n Parses commands but does not execute them. This aids in debugging shell<br />

scripts.<br />

–q Accepts SIGQUIT and behaves when it is used under a debugger. Job<br />

control is disabled.<br />

–s Take command input from the standard input.<br />

–t Reads and executes a single line of input. A \ (backslash) may be used to<br />

escape the newline at the end of this line and continue onto another line.<br />

–v Sets the verbose shell variable so command input is echoed after history<br />

substitution.<br />

–x Sets the echo shell variable so commands are echoed immediately before<br />

execution.<br />

–V Sets the verbose shell variable even before executing ~/.tcshrc.<br />

–X Is to –x as –V is to –v.<br />

After processing of option arguments, if arguments remain but none of the –c, –i,<br />

–s, or –t were given, the first argument is taken as the name of a file of commands,<br />

or script, to be executed. The shell opens this file and saves its name for possible<br />

resubstitution by $0. Since many systems use shells whose shell scripts are not<br />

compatible with this shell, the tcsh shell uses such a standard shell to execute a<br />

script whose character is not a #, that is, which does not start with a comment.<br />

Remaining arguments are placed in the argv shell variable.<br />

tcsh shell editing<br />

In this topic, we first describe the <strong>Command</strong>-Line Editor. We then discuss<br />

Completion and Listing and Spelling Correction which describe two sets of<br />

functionality that are implemented as editor commands but which deserve their own<br />

treatment. Finally, the Editor <strong>Command</strong>s topic lists and describes the editor<br />

commands specific to the tcsh shell and their default bindings.<br />

tcsh shell command-line editor<br />

<strong>Command</strong>-line input can be edited using key sequences much like those used in<br />

GNU Emacs or vi. The editor is active only when the edit shell variable is set, which<br />

it is by default in interactive shells. The bindkey built-in command can display and<br />

change key bindings. Emacs-style key bindings are used by default, but bindkey<br />

can change the key bindings to vi-style bindings.<br />

The shell always binds the arrow keys to:<br />

down down-history<br />

up up-history<br />

left backward-char<br />

right forward-char<br />

unless doing so would alter another single-character binding. One can set the arrow<br />

key escape sequences to the empty string with settc to prevent these bindings.<br />

Other key bindings are, for the most part, what Emacs and vi users would expect<br />

and can easily be displayed by bindkey, so there is no need to list them here.<br />

Likewise, bindkey can list the editor commands with a short description of each.<br />

628 z/<strong>OS</strong> <strong>V1R9.0</strong> <strong>UNIX</strong> <strong>System</strong> <strong>Services</strong> <strong>Command</strong> Reference

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!