1 .\" Copyright (c) 1991, 1992, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)termios.4 8.4 (Berkeley) 4/19/94
33 .\" $FreeBSD: src/share/man/man4/termios.4,v 1.12.2.9 2001/12/17 11:30:12 ru Exp $
34 .\" $DragonFly: src/share/man/man4/termios.4,v 1.6 2008/04/29 09:02:45 swildner Exp $
41 .Nd general terminal line discipline
45 This describes a general terminal line discipline that is
46 supported on tty asynchronous communication ports.
47 .Ss Opening a Terminal Device File
48 When a terminal file is opened, it normally causes the process to wait
49 until a connection is established. For most hardware, the presence
50 of a connection is indicated by the assertion of the hardware
53 If the termios structure associated with the terminal file has the
55 flag set in the cflag, or if the
60 call, then the open will succeed even without
61 a connection being present.
62 In practice, applications
63 seldom open these files; they are opened by special programs, such
69 an application's standard input, output, and error files.
70 .Ss Job Control in a Nutshell
71 Every process is associated with a particular process group and session.
72 The grouping is hierarchical: every member of a particular process group is a
73 member of the same session. This structuring is used in managing groups
74 of related processes for purposes of
75 .\" .Gw "job control" ;
78 ability from the keyboard (or from program control) to simultaneously
80 a complex command (a command composed of one or more related
81 processes). The grouping into process groups allows delivering
82 of signals that stop or start the group as a whole, along with
83 arbitrating which process group has access to the single controlling
84 terminal. The grouping at a higher layer into sessions is to restrict
85 the job control related signals and system calls to within processes
86 resulting from a particular instance of a "login". Typically, a session
87 is created when a user logs in, and the login terminal is setup
88 to be the controlling terminal; all processes spawned from that
89 login shell are in the same session, and inherit the controlling
93 operating interactively (that is, reading commands from a terminal)
94 normally groups related processes together by placing them into the
95 same process group. A set of processes in the same process group
96 is collectively referred to as a "job". When the foreground process
97 group of the terminal is the same as the process group of a particular
98 job, that job is said to be in the "foreground". When the process
99 group of the terminal is different from the process group of
100 a job (but is still the controlling terminal), that job is said
101 to be in the "background". Normally the
102 shell reads a command and starts the job that implements that
103 command. If the command is to be started in the foreground (typical), it
104 sets the process group of the terminal to the process group
105 of the started job, waits for the job to complete, and then
106 sets the process group of the terminal back to its own process
107 group (it puts itself into the foreground). If the job is to
108 be started in the background (as denoted by the shell operator "&"),
109 it never changes the process group of the terminal and doesn't
110 wait for the job to complete (that is, it immediately attempts to read the next
111 command). If the job is started in the foreground, the user may
114 which generates the terminal stop signal
116 and has the effect of stopping the entire job.
117 The shell will notice that the job stopped, and will resume running after
118 placing itself in the foreground.
119 The shell also has commands for placing stopped jobs in the background,
120 and for placing stopped or background jobs into the foreground.
121 .Ss Orphaned Process Groups
122 An orphaned process group is a process group that has no process
123 whose parent is in a different process group, yet is in the same
124 session. Conceptually it means a process group that doesn't have
125 a parent that could do anything if it were to be stopped. For example,
126 the initial login shell is typically in an orphaned process group.
127 Orphaned process groups are immune to keyboard generated stop
128 signals and job control signals resulting from reads or writes to the
129 controlling terminal.
130 .Ss The Controlling Terminal
131 A terminal may belong to a process as its controlling terminal. Each
132 process of a session that has a controlling terminal has the same
133 controlling terminal. A terminal may be the controlling terminal for at
134 most one session. The controlling terminal for a session is allocated by
135 the session leader by issuing the
137 ioctl. A controlling terminal
138 is never acquired by merely opening a terminal device file.
139 When a controlling terminal becomes
140 associated with a session, its foreground process group is set to
141 the process group of the session leader.
143 The controlling terminal is inherited by a child process during a
145 function call. A process relinquishes its controlling terminal when it
146 creates a new session with the
148 function; other processes
149 remaining in the old session that had this terminal as their controlling
150 terminal continue to have it.
151 A process does not relinquish its
152 controlling terminal simply by closing all of its file descriptors
153 associated with the controlling terminal if other processes continue to
156 When a controlling process terminates, the controlling terminal is
157 disassociated from the current session, allowing it to be acquired by a
158 new session leader. Subsequent access to the terminal by other processes
159 in the earlier session will be denied, with attempts to access the
160 terminal treated as if modem disconnect had been sensed.
161 .Ss Terminal Access Control
162 If a process is in the foreground process group of its controlling
163 terminal, read operations are allowed.
164 Any attempts by a process
165 in a background process group to read from its controlling terminal
171 following special cases apply: If the reading process is ignoring or
174 signal, or if the process group of the reading
175 process is orphaned, the
182 signal is sent. The default action of the
184 signal is to stop the
185 process to which it is sent.
187 If a process is in the foreground process group of its controlling
188 terminal, write operations are allowed.
189 Attempts by a process in a background process group to write to its
190 controlling terminal will cause the process group to be sent a
192 signal unless one of the following special cases apply: If
197 is set and the process is ignoring or blocking the
199 signal, the process is allowed to write to the terminal and the
201 signal is not sent. If
203 is set, and the process group of
204 the writing process is orphaned, and the writing process is not ignoring
213 and no signal is sent.
215 Certain calls that set terminal parameters are treated in the same
216 fashion as write, except that
218 is ignored; that is, the effect is
219 identical to that of terminal writes when
222 .Ss Input Processing and Reading Data
223 A terminal device associated with a terminal device file may operate in
224 full-duplex mode, so that data may arrive even while output is occurring.
225 Each terminal device file has associated with it an input queue, into
226 which incoming data is stored by the system before being read by a
227 process. The system imposes a limit,
228 .Pf \&{ Dv MAX_INPUT Ns \&} ,
230 bytes that may be stored in the input queue. The behavior of the system
231 when this limit is exceeded depends on the setting of the
235 If this flag is set, the terminal
239 character each time a character is received
240 while the input queue is full. Otherwise, the input queue is flushed
241 upon receiving the character.
243 Two general kinds of input processing are available, determined by
244 whether the terminal device file is in canonical mode or noncanonical
247 input characters are processed according to the
251 fields. Such processing can include echoing, which
252 in general means transmitting input characters immediately back to the
253 terminal when they are received from the terminal. This is useful for
254 terminals that can operate in full-duplex mode.
256 The manner in which data is provided to a process reading from a terminal
257 device file is dependent on whether the terminal device file is in
258 canonical or noncanonical mode.
260 Another dependency is whether the
268 flag is clear, then the read request is
269 blocked until data is available or a signal has been received. If the
271 flag is set, then the read request is completed, without
272 blocking, in one of three ways:
273 .Bl -enum -offset indent
275 If there is enough data available to satisfy the entire request,
276 and the read completes successfully the number of
277 bytes read is returned.
279 If there is not enough data available to satisfy the entire
280 request, and the read completes successfully, having read as
281 much data as possible, the number of bytes read is returned.
283 If there is no data available, the read returns -1, with
289 When data is available depends on whether the input processing mode is
290 canonical or noncanonical.
291 .Ss Canonical Mode Input Processing
292 In canonical mode input processing, terminal input is processed in units
293 of lines. A line is delimited by a newline
295 character, an end-of-file
297 character, or an end-of-line
300 .Sx "Special Characters"
306 This means that a read request will
307 not return until an entire line has been typed, or a signal has been
308 received. Also, no matter how many bytes are requested in the read call,
309 at most one line is returned. It is not, however, necessary to
310 read a whole line at once; any number of bytes, even one, may be
311 requested in a read without losing information.
313 .Pf \&{ Dv MAX_CANON Ns \&}
315 number of bytes in a line.
316 The behavior of the system when this limit is
317 exceeded is the same as when the input queue limit
318 .Pf \&{ Dv MAX_INPUT Ns \&} ,
321 Erase and kill processing occur when either of two special characters,
327 .Sx "Special Characters"
328 section), is received.
329 This processing affects data in the input queue that has not yet been
330 delimited by a newline
335 character. This un-delimited
336 data makes up the current line. The
338 character deletes the last
339 character in the current line, if there is any. The
342 deletes all data in the current line, if there is any. The
346 characters have no effect if there is no data in the current line.
351 characters themselves are not placed in the input
353 .Ss Noncanonical Mode Input Processing
354 In noncanonical mode input processing, input bytes are not assembled into
355 lines, and erase and kill processing does not occur. The values of the
361 array are used to determine how to
362 process the bytes received.
365 represents the minimum number of bytes that should be received when
368 function successfully returns.
370 is a timer of 0.1 second
371 granularity that is used to time out bursty and short term data
375 .Dv \&{ Dv MAX_INPUT Ns \&} ,
377 request is undefined. The four possible values for
382 their interactions are described below.
383 .Ss "Case A: MIN > 0, TIME > 0"
386 serves as an inter-byte timer and is activated after
387 the first byte is received. Since it is an inter-byte timer, it is reset
388 after a byte is received. The interaction between
393 follows: as soon as one byte is received, the inter-byte timer is
396 bytes are received before the inter-byte timer expires
397 (remember that the timer is reset upon receipt of each byte), the read is
398 satisfied. If the timer expires before
400 bytes are received, the
401 characters received to that point are returned to the user. Note that if
403 expires at least one byte is returned because the timer would
404 not have been enabled unless a byte was received. In this case
408 > 0) the read blocks until the
413 activated by the receipt of the first byte, or a signal is received. If
414 data is in the buffer at the time of the
417 if data had been received immediately after the
419 .Ss "Case B: MIN > 0, TIME = 0"
420 In this case, since the value of
422 is zero, the timer plays no role
425 is significant. A pending read is not satisfied until
427 bytes are received (i.e., the pending read blocks until
430 are received), or a signal is received. A program that uses this case to
431 read record-based terminal
433 may block indefinitely in the read
435 .Ss "Case C: MIN = 0, TIME > 0"
440 no longer represents an inter-byte
441 timer. It now serves as a read timer that is activated as soon as the
442 read function is processed. A read is satisfied as soon as a single
443 byte is received or the read timer expires. Note that in this case if
444 the timer expires, no bytes are returned. If the timer does not
445 expire, the only way the read can be satisfied is if a byte is received.
446 In this case the read will not block indefinitely waiting for a byte; if
447 no byte is received within
449 seconds after the read is initiated,
450 the read returns a value of zero, having read no data. If data is
451 in the buffer at the time of the read, the timer is started as if
452 data had been received immediately after the read.
453 .Ss Case D: MIN = 0, TIME = 0
454 The minimum of either the number of bytes requested or the number of
455 bytes currently available is returned without waiting for more
456 bytes to be input. If no characters are available, read returns a
457 value of zero, having read no data.
458 .Ss Writing Data and Output Processing
459 When a process writes one or more bytes to a terminal device file, they
460 are processed according to the
465 implementation may provide a buffering mechanism; as such, when a call to
467 completes, all of the bytes written have been scheduled for
468 transmission to the device, but the transmission will not necessarily
470 .\" See also .Sx "6.4.2" for the effects of
473 .Ss Special Characters
474 Certain characters have special functions on input or output or both.
475 These functions are summarized as follows:
476 .Bl -tag -width indent
478 Special character on input and is recognized if the
482 section) is enabled. Generates a
484 signal which is sent to all processes in the foreground
485 process group for which the terminal is the controlling
491 discarded when processed.
493 Special character on input and is recognized if the
495 flag is enabled. Generates a
498 sent to all processes in the foreground process group
499 for which the terminal is the controlling terminal. If
503 character is discarded when
506 Special character on input and is recognized if the
508 flag is set. Erases the last character in the
510 .Sx "Canonical Mode Input Processing" .
511 It does not erase beyond
512 the start of a line, as delimited by an
522 discarded when processed.
524 Special character on input and is recognized if the
526 flag is set. Deletes the entire line, as
536 character is discarded when processed.
538 Special character on input and is recognized if the
540 flag is set. When received, all the bytes
541 waiting to be read are immediately passed to the
542 process, without waiting for a newline, and the
544 is discarded. Thus, if there are no bytes waiting (that
547 occurred at the beginning of a line), a byte
548 count of zero is returned from the
550 representing an end-of-file indication. If
555 character is discarded when processed.
557 Special character on input and is recognized if the
559 flag is set. It is the line delimiter
562 Special character on input and is recognized if the
564 flag is set. Is an additional line delimiter,
570 flag is enabled, receipt of the
574 signal to be sent to all processes in the
575 foreground process group for which the terminal is the
576 controlling terminal, and the
579 discarded when processed.
581 Special character on both input and output and is
587 control) flag is set. Can be used to temporarily
588 suspend output. It is useful with fast terminals to
589 prevent output from disappearing before it can be read.
594 character is discarded when
597 Special character on both input and output and is
603 control) flag is set. Can be used to resume output that
604 has been suspended by a
610 character is discarded when processed.
612 Special character on input and is recognized if the
614 flag is set; it is the
624 is not set, this character is translated into a
627 has the same effect as a
632 The following special characters are extensions defined by this
633 system and are not a part of
636 .Bl -tag -width indent
640 character. Same function as
643 Special character on input and is recognized if the
645 flag is set. Erases the last word in the current
646 line according to one of two algorithms. If the
648 flag is not set, first any preceding whitespace is
649 erased, and then the maximal sequence of non-whitespace
652 is set, first any preceding
653 whitespace is erased, and then the maximal sequence
654 of alphabetic/underscores or non alphabetic/underscores.
655 As a special case in this second algorithm, the first previous
656 non-whitespace character is skipped in determining
657 whether the preceding word is a sequence of
658 alphabetic/underscores. This sounds confusing but turns
659 out to be quite practical.
661 Special character on input and is recognized if the
663 flag is set. Causes the current input edit line
666 Has similar actions to the
668 character, except that
671 signal is delivered when one of the processes
672 in the foreground process group issues a
675 controlling terminal.
677 Special character on input and is recognized if the
679 flag is set. Receipt of this character causes the next
680 character to be taken literally.
682 Special character on input and is recognized if the
684 flag is set. Receipt of this character toggles the flushing
687 Special character on input and is recognized if the
689 flag is set. Receipt of this character causes a
691 signal to be sent to the foreground process group of the
692 terminal. Also, if the
695 causes the kernel to write a status message to the terminal
696 that displays the current load average, the name of the
697 command in the foreground, its process ID, the symbolic
698 wait channel, the number of user and system seconds used,
699 the percentage of cpu the process is getting, and the resident
700 set size of the process.
707 characters cannot be changed.
708 The values for all the remaining characters can be set and are
709 described later in the document under
710 Special Control Characters.
713 character functions associated with changeable special control characters
714 can be disabled individually by setting their value to
715 .Dv {_POSIX_VDISABLE} ;
717 .Sx "Special Control Characters" .
719 If two or more special characters have the same value, the function
720 performed when that character is received is undefined.
722 If a modem disconnect is detected by the terminal interface for a
723 controlling terminal, and if
730 signal is sent to the controlling
731 process associated with the terminal. Unless other arrangements have
732 been made, this causes the controlling process to terminate.
733 Any subsequent call to the
735 function returns the value zero,
736 indicating end of file. Thus, processes that read a terminal
737 file and test for end-of-file can terminate appropriately after a
741 .\" condition specified in 6.1.1.4 that applies
742 .\" when the implementation supports job control also exists, it is
743 .\" unspecified whether the
751 to the terminal device returns -1, with
755 until the device is closed.
756 .Sh General Terminal Interface
757 .Ss Closing a Terminal Device File
758 The last process to close a terminal device file causes any output
759 to be sent to the device and any input to be discarded. Then, if
761 is set in the control modes, and the communications port supports a
762 disconnect function, the terminal device performs a disconnect.
763 .Ss Parameters That Can Be Set
764 Routines that need to control certain terminal
767 do so by using the termios structure as defined in the header
769 This structure contains minimally four scalar elements of bit flags
770 and one array of special characters. The scalar flag elements are
777 The character array is named
779 and its maximum index is
784 field describe the basic
785 terminal input control, and are composed of
788 .Bl -tag -width IMAXBEL -offset indent -compact
790 /* ignore BREAK condition */
792 /* map BREAK to SIGINTR */
794 /* ignore (discard) parity errors */
796 /* mark parity and framing errors */
798 /* enable checking of parity errors */
800 /* strip 8th bit off chars */
806 /* map CR to NL (ala CRMOD) */
808 /* enable output flow control */
810 /* enable input flow control */
812 /* any char will restart after stop */
814 /* ring bell on input queue full */
817 In the context of asynchronous serial data transmission, a break
818 condition is defined as a sequence of zero-valued bits that continues for
819 more than the time to send one byte. The entire sequence of zero-valued
820 bits is interpreted as a single break condition, even if it continues for
821 a time equivalent to more than one byte. In contexts other than
822 asynchronous serial data transmission the definition of a break condition
823 is implementation defined.
827 is set, a break condition detected on input is ignored, that
828 is, not put on the input queue and therefore not read by any process. If
832 is set, the break condition flushes the
833 input and output queues and if the terminal is the controlling terminal
834 of a foreground process group, the break condition generates a
837 signal to that foreground process group. If neither
841 is set, a break condition is read as a single
852 is set, a byte with a framing or parity error (other than
859 is not set, a byte with a framing or parity
860 error (other than break) is given to the application as the
861 three-character sequence
868 flag preceding each sequence and X is the data of the character received
869 in error. To avoid ambiguity in this case, if
874 is given to the application as
882 is set, a framing or parity error (other than
883 break) is given to the application as a single character
888 is set, input parity checking is enabled. If
891 input parity checking is disabled, allowing output parity generation
892 without input parity errors. Note that whether input parity checking is
893 enabled or disabled is independent of whether parity detection is enabled
895 .Sx "Control Modes" ) .
896 If parity detection is enabled but input
897 parity checking is disabled, the hardware to which the terminal is
898 connected recognizes the parity bit, but the terminal special file
899 does not check whether this bit is set correctly or not.
903 is set, valid input bytes are first stripped to seven bits,
904 otherwise all eight bits are processed.
910 character is translated into a
916 character is ignored (not
930 is set, start/stop output control is enabled. A received
932 character suspends output and a received
938 is also set, then any character may
947 read, but merely perform flow control functions. When
958 is set, start/stop input control is enabled. The system shall
961 characters, which are intended to cause the
962 terminal device to stop transmitting data, as needed to prevent the input
963 queue from overflowing and causing the undefined behavior described in
964 .Sx "Input Processing and Reading Data" ,
965 and shall transmit one or more
967 characters, which are
968 intended to cause the terminal device to resume transmitting data, as
969 soon as the device can continue transmitting data without risk of
970 overflowing the input queue. The precise conditions under which
974 characters are transmitted are implementation defined.
978 is set and the input queue is full, subsequent input shall cause an
981 character to be transmitted to
984 The initial input control value after
986 is implementation defined.
990 field describe the basic terminal output control,
991 and are composed of the following masks:
993 .Bl -tag -width OXTABS -offset indent -compact
995 /* enable following output processing */
997 /* map NL to CR-NL (ala
1003 /* expand tabs to spaces */
1010 /* do not transmit CRs on column 0 */
1012 /* on the termianl NL performs the CR function */
1017 is set, the remaining flag masks are interpreted as follows;
1018 otherwise characters are transmitted without change.
1022 is set, newlines are translated to carriage return, linefeeds.
1026 is set, carriage returns are translated to newlines.
1030 is set, tabs are expanded to the appropriate number of
1031 spaces (assuming 8 column tab stops).
1038 are discarded on output.
1042 is set, no CR character is transmitted when at column 0 (first position).
1046 is set, the NL character is assumed to do the carriage-return function;
1047 the column pointer will be set to 0.
1051 field describe the basic
1052 terminal hardware control, and are composed of the
1055 specified are supported by all hardware.
1057 .Bl -tag -width CRTSXIFLOW -offset indent -compact
1059 /* character size mask */
1061 /* 5 bits (pseudo) */
1069 /* send 2 stop bits */
1071 /* enable receiver */
1075 /* odd parity, else even */
1077 /* hang up on last close */
1079 /* ignore modem status lines */
1083 flow control of output */
1089 /* RTS flow control of input */
1091 /* flow control output via Carrier */
1096 bits specify the byte size in bits for both transmission and
1101 and compared with the
1108 This size does not include the parity bit, if any. If
1110 is set, two stop bits are used, otherwise one stop bit. For example, at
1111 110 baud, two stop bits are normally used.
1115 is set, the receiver is enabled. Otherwise, no character is
1117 Not all hardware supports this bit. In fact, this flag
1118 is pretty silly and if it were not part of the
1121 it would be omitted.
1125 is set, parity generation and detection are enabled and a parity
1126 bit is added to each character. If parity is enabled,
1129 odd parity if set, otherwise even parity is used.
1133 is set, the modem control lines for the port are lowered
1134 when the last process with the port open closes the port or the process
1135 terminates. The modem connection is broken.
1139 is set, a connection does not depend on the state of the modem
1142 is clear, the modem status lines are
1145 Under normal circumstances, a call to the
1148 the modem connection to complete. However, if the
1156 immediately without waiting for the connection.
1161 flag is currently unused.
1165 is set then output flow control is controlled by the state
1168 If the object for which the control modes are set is not an asynchronous
1169 serial connection, some of the modes may be ignored; for example, if an
1170 attempt is made to set the baud rate on a network connection to a
1171 terminal on another host, the baud rate may or may not be set on the
1172 connection between that terminal and the machine it is directly connected
1177 field describe the control of
1178 various functions, and are composed of the following
1181 .Bl -tag -width NOKERNINFO -offset indent -compact
1183 /* visual erase for line kill */
1185 /* visually erase chars */
1187 /* enable echoing */
1195 /* visual erase mode for hardcopy */
1197 /* echo control chars as ^(Char) */
1205 /* canonicalize input lines */
1217 /* external processing */
1219 /* stop background jobs from output */
1221 /* output being flushed (state) */
1223 /* no kernel output from
1227 /* XXX retype pending input (state) */
1229 /* don't flush after interrupt */
1234 is set, input characters are echoed back to the terminal. If
1236 is not set, input characters are not echoed.
1244 character causes the terminal
1245 to erase the last character in the current line from the display, if
1246 possible. If there is no character to erase, an implementation may echo
1247 an indication that this was the case or do nothing.
1256 the current line to be discarded and the system echoes the
1269 the current line to be discarded and the system causes
1271 to erase the line from the display.
1277 are set, the system assumes
1278 that the display is a printing device and prints a
1279 backslash and the erased characters when processing
1281 characters, followed by a forward slash.
1285 is set, the system echoes control characters
1286 in a visible fashion using a caret followed by the control character.
1290 is set, the system uses an alternative algorithm
1291 for determining what constitutes a word when processing
1302 character echoes even if
1308 is set, canonical processing is enabled. This enables the
1309 erase and kill edit functions, and the assembly of input characters into
1316 .Sx "Canonical Mode Input Processing" .
1320 is not set, read requests are satisfied directly from the input
1321 queue. A read is not satisfied until at least
1324 received or the timeout value
1326 expired between bytes. The time value
1327 represents tenths of seconds. See
1328 .Sx "Noncanonical Mode Input Processing"
1333 is set, each input character is checked against the special
1339 (job control only). If an input
1340 character matches one of these control characters, the function
1341 associated with that character is performed. If
1344 checking is done. Thus these special input functions are possible only
1351 is set, implementation-defined functions are recognized
1352 from the input data. How
1361 is implementation defined.
1365 implementation-defined functions are not recognized, and the
1366 corresponding input characters are not processed as described for
1375 is set, the normal flush of the input and output queues
1388 is sent to the process group of a process that tries to write to
1389 its controlling terminal if it is not in the foreground process group for
1390 that terminal. This signal, by default, stops the members of the process
1391 group. Otherwise, the output generated by that process is output to the
1392 current output stream. Processes that are blocking or ignoring
1394 signals are excepted and allowed to produce output and the
1401 is set, the kernel does not produce a status message
1406 .Ss Special Control Characters
1407 The special control characters values are defined by the array
1409 This table lists the array index, the corresponding special character,
1410 and the system default value. For an accurate list of
1411 the system defaults, consult the header file
1412 .In sys/ttydefaults.h .
1414 .Bl -column "Index Name" "Special Character" -offset indent -compact
1415 .It Em "Index Name Special Character Default Value"
1416 .It Dv VEOF Ta EOF Ta \&^D
1417 .It Dv VEOL Ta EOL Ta _POSIX_VDISABLE
1418 .It Dv VEOL2 Ta EOL2 Ta _POSIX_VDISABLE
1419 .It Dv VERASE Ta ERASE Ta \&^? Ql \&\e177
1420 .It Dv VWERASE Ta WERASE Ta \&^W
1421 .It Dv VKILL Ta KILL Ta \&^U
1422 .It Dv VREPRINT Ta REPRINT Ta \&^R
1423 .It Dv VINTR Ta INTR Ta \&^C
1424 .It Dv VQUIT Ta QUIT Ta \&^\e\e Ql \&\e34
1425 .It Dv VSUSP Ta SUSP Ta \&^Z
1426 .It Dv VDSUSP Ta DSUSP Ta \&^Y
1427 .It Dv VSTART Ta START Ta \&^Q
1428 .It Dv VSTOP Ta STOP Ta \&^S
1429 .It Dv VLNEXT Ta LNEXT Ta \&^V
1430 .It Dv VDISCARD Ta DISCARD Ta \&^O
1431 .It Dv VMIN Ta --- Ta \&1
1432 .It Dv VTIME Ta --- Ta \&0
1433 .It Dv VSTATUS Ta STATUS Ta \&^T
1437 value of one of the changeable special control characters (see
1438 .Sx "Special Characters" )
1440 .Dv {_POSIX_VDISABLE} ,
1441 that function is disabled; that is, no input
1442 data is recognized as the disabled special character.
1446 not set, the value of
1447 .Dv {_POSIX_VDISABLE}
1448 has no special meaning for the
1456 The initial values of the flags and control characters
1460 the values in the header
1461 .In sys/ttydefaults.h .