|WRITE(1P)||POSIX Programmer's Manual||WRITE(1P)|
write user_name [terminal]
Message from sender-login-id (sending-terminal) [date]...
to user_name. When it has successfully completed the connection, the sender's terminal shall be alerted twice to indicate that what the sender is typing is being written to the recipient's terminal.
If the recipient wants to reply, this can be accomplished by typing:
write sender-login-id [sending-terminal]
upon receipt of the initial message. Whenever a line of input as delimited by an NL, EOF, or EOL special character (see the Base Definitions volume of POSIX.1‐2017, Chapter 11, General Terminal Interface) is accumulated while in canonical input mode, the accumulated data shall be written on the other user's terminal. Characters shall be processed as follows:
- Typing <alert> shall write the <alert> character to the recipient's terminal.
- Typing the erase and kill characters shall affect the sender's terminal in the manner described by the termios interface in the Base Definitions volume of POSIX.1‐2017, Chapter 11, General Terminal Interface.
- Typing the interrupt or end-of-file characters shall cause write to write an appropriate message ("EOT\n" in the POSIX locale) to the recipient's terminal and exit.
- Typing characters from LC_CTYPE classifications print or space shall cause those characters to be sent to the recipient's terminal.
- When and only when the stty iexten local mode is enabled, the existence and processing of additional special control characters and multi-byte or single-byte functions is implementation-defined.
- Typing other non-printable characters shall cause implementation-defined sequences of printable characters to be written to the recipient's terminal.
To write to a user who is logged in more than once, the terminal argument can be used to indicate which terminal to write to; otherwise, the recipient's terminal is selected in an implementation-defined manner and an informational message is written to the sender's standard output, indicating which terminal was chosen.
Permission to be a recipient of a write message can be denied or granted by use of the mesg utility. However, a user's privilege may further constrain the domain of accessibility of other users' terminals. The write utility shall fail when the user lacks appropriate privileges to perform the requested action.
- Login name of the person to whom the message shall be written. The application shall ensure that this operand is of the form returned by the who utility.
- Terminal identification in the same format provided by the who utility.
- Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of POSIX.1‐2017, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.)
- If set to a non-empty string value, override the values of all the other internationalization variables.
- Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments and input files). If the recipient's locale does not use an LC_CTYPE equivalent to the sender's, the results are undefined.
Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error and informative messages written to standard output.
- Determine the location of message catalogs for the processing of LC_MESSAGES.
- Successful completion.
- The addressed user is not logged on or the addressed user denies permission.
The following sections are informative.
The format of the terminal name is unspecified, but the descriptions of ps, talk, who, and write require that they all use or accept the same format.
The Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables, Chapter 11, General Terminal Interface
Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .
|2017||IEEE/The Open Group|