Lines Matching refs:built

251 .IR built-ins ,
254 The reasons that some commands are built-in are presented later.
256 between a command that is built-in and one that
259 all commands that are built-in follow command line conventions.
314 built-in.
358 Aliases can be used to redefine built-in commands so that
364 using the built-in \f5test\fP command.
433 A built-in command named \f5hist\fP
783 The built-in command \f5bg\fP
785 while the built-in command \f5fg\fP
795 There is a built-in command \f5jobs\fP
817 A built-in version of \f5kill\fP
865 built-in can be given with argument
1045 The output of built-in commands and traces have values quoted so that they
1216 as arguments to the \f5set\fP built-in,
1243 built-in command of \f5ksh\fP
1253 built-in of \f5ksh\fP removes
1367 built-in.
2178 The Bourne shell has a built-in command \f5read\fP
2185 is not a built-in command and incurs considerable overhead to use.)
2191 built-in cannot read a single line that ends in
2195 built-in has a
2241 Because the prompt is associated with the \f5read\fP built-in,
2242 the built-in command line editors will be able to re-output
2272 The \f5ksh\fP built-in, \f5print\fP,
2318 Special characters in the output of most \f5ksh\fP built-in commands
2355 The \f5getopts\fP built-in command can be used
2357 with the way \f5ksh\fP does for its own built-in commands.
2359 The \f5getopts\fP built-in allows users to specify options
2389 standard output connected to the shell.  The built-in command \f5print\fP
2394 the built-in command \f5read\fP
2441 that are created as part of user defined built-ins.
2454 built-in command.
2460 built-in can be used to cause the function to return to
2521 built-in command are local to the function that they are declared in.
2566 Except for special built-ins,
2567 function names take precedence over built-in names and names
2571 you can use the \f5command\fP built-in command.
2669 and more built-ins
2677 the language but are \fIspecial\fP built-ins.
2678 Special built-ins are built-ins that are considered a
2696 Other commands are built-in because they perform side effects
2700 are examples of such built-ins.
2701 These built-ins are semantically equivalent to commands that
2702 are not built-in except that they don't take a path search
2705 A third reason to have a command built-in is so that
2713 The final reason for having a command be a built-in is
2716 faster to initiate a command that is built-in than
2732 Special built-ins.
2736 Commands that are built-in that are not associated with a pathname
2745 with a built-in command, the built-in command is executed.
2761 The first argument of the \f5command\fP built-in, described earlier,
2763 In all other ways, \f5command\fP behaves like a built-in
2766 a special built-in, the special properties of this built-in
2772 You can get a complete list of the special built-in commands
2775 the current built-ins and the pathname that they are associated with.
2776 A built-in can be bound to another pathname by giving
2777 the pathname for the built-in.  The basename of this path must
2778 be the name of an existing built-in for this to succeed.
2779 Specifying the name of the built-in without a pathname causes
2780 this built-in to be found before a path search.
2781 A built-in can be deleted  with the \fB\-d\fP option.
2783 On systems with run time loading of libraries, built-in commands
2785 Each command that is to be built-in must be written as a
2787 \fIname\fP is the name of the built-in that is to be added.
2790 the exit status for this built-in.
2794 The built-in command,
2801 It reports on reserved words, aliases, built-ins, and
2809 for built-ins that use numerical values in the Bourne shell.
2813 \f5umask\fP built-in command
2819 The \f5trap\fP and \f5kill\fP built-in commands
3134 On systems with dynamic libraries, it is possible to add built-in
3135 commands at run time  with the built-in command \f5builtin\fP 
3171 The time to execute a built-in command or a function is one or two
3213 built-ins without changing the semantics at all.
3216 programs as shell built-in commands.
3217 Implementations on other systems can add built-in commands
3219 The procedure for writing built-in commands that can be loaded
3223 .IR "Guidelines for writing \f5ksh-93\fP built-in commands,"