Deleted Added
full compact
write.1 (24110) write.1 (28794)
1.\" Copyright (c) 1989, 1993
2.\" The Regents of the University of California. All rights reserved.
3.\"
4.\" This code is derived from software contributed to Berkeley by
5.\" Jef Poskanzer and Craig Leres of the Lawrence Berkeley Laboratory.
6.\"
7.\" Redistribution and use in source and binary forms, with or without
8.\" modification, are permitted provided that the following conditions
9.\" are met:
10.\" 1. Redistributions of source code must retain the above copyright
11.\" notice, this list of conditions and the following disclaimer.
12.\" 2. Redistributions in binary form must reproduce the above copyright
13.\" notice, this list of conditions and the following disclaimer in the
14.\" documentation and/or other materials provided with the distribution.
15.\" 3. All advertising materials mentioning features or use of this software
16.\" must display the following acknowledgement:
17.\" This product includes software developed by the University of
18.\" California, Berkeley and its contributors.
19.\" 4. Neither the name of the University nor the names of its contributors
20.\" may be used to endorse or promote products derived from this software
21.\" without specific prior written permission.
22.\"
23.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
33.\" SUCH DAMAGE.
34.\"
35.\" @(#)write.1 8.1 (Berkeley) 6/6/93
1.\" Copyright (c) 1989, 1993
2.\" The Regents of the University of California. All rights reserved.
3.\"
4.\" This code is derived from software contributed to Berkeley by
5.\" Jef Poskanzer and Craig Leres of the Lawrence Berkeley Laboratory.
6.\"
7.\" Redistribution and use in source and binary forms, with or without
8.\" modification, are permitted provided that the following conditions
9.\" are met:
10.\" 1. Redistributions of source code must retain the above copyright
11.\" notice, this list of conditions and the following disclaimer.
12.\" 2. Redistributions in binary form must reproduce the above copyright
13.\" notice, this list of conditions and the following disclaimer in the
14.\" documentation and/or other materials provided with the distribution.
15.\" 3. All advertising materials mentioning features or use of this software
16.\" must display the following acknowledgement:
17.\" This product includes software developed by the University of
18.\" California, Berkeley and its contributors.
19.\" 4. Neither the name of the University nor the names of its contributors
20.\" may be used to endorse or promote products derived from this software
21.\" without specific prior written permission.
22.\"
23.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
33.\" SUCH DAMAGE.
34.\"
35.\" @(#)write.1 8.1 (Berkeley) 6/6/93
36.\" $Id: write.1,v 1.4 1997/02/22 19:57:53 peter Exp $
36.\" $Id: write.1,v 1.5 1997/03/22 17:19:32 mpp Exp $
37.\"
38.Dd June 6, 1993
39.Dt WRITE 1
40.Os
41.Sh NAME
42.Nm write
43.Nd send a message to another user
44.Sh SYNOPSIS
45.Nm write
46.Ar user
47.Op Ar ttyname
48.Sh DESCRIPTION
49.Nm Write
50allows you to communicate with other users, by copying lines from
51your terminal to theirs.
52.Pp
53When you run the
37.\"
38.Dd June 6, 1993
39.Dt WRITE 1
40.Os
41.Sh NAME
42.Nm write
43.Nd send a message to another user
44.Sh SYNOPSIS
45.Nm write
46.Ar user
47.Op Ar ttyname
48.Sh DESCRIPTION
49.Nm Write
50allows you to communicate with other users, by copying lines from
51your terminal to theirs.
52.Pp
53When you run the
54.Nm write
54.Nm
55command, the user you are writing to gets a message of the form:
56.Pp
57.Dl Message from yourname@yourhost on yourtty at hh:mm ...
58.Pp
59Any further lines you enter will be copied to the specified user's
60terminal.
61If the other user wants to reply, they must run
55command, the user you are writing to gets a message of the form:
56.Pp
57.Dl Message from yourname@yourhost on yourtty at hh:mm ...
58.Pp
59Any further lines you enter will be copied to the specified user's
60terminal.
61If the other user wants to reply, they must run
62.Nm write
62.Nm
63as well.
64.Pp
65When you are done, type an end-of-file or interrupt character.
66The other user will see the message
67.Ql EOF
68indicating that the
69conversation is over.
70.Pp
71You can prevent people (other than the super-user) from writing to you
72with the
73.Xr mesg 1
74command.
75.Pp
76If the user you want to write to is logged in on more than one terminal,
77you can specify which terminal to write to by specifying the terminal
78name as the second operand to the
63as well.
64.Pp
65When you are done, type an end-of-file or interrupt character.
66The other user will see the message
67.Ql EOF
68indicating that the
69conversation is over.
70.Pp
71You can prevent people (other than the super-user) from writing to you
72with the
73.Xr mesg 1
74command.
75.Pp
76If the user you want to write to is logged in on more than one terminal,
77you can specify which terminal to write to by specifying the terminal
78name as the second operand to the
79.Nm write
79.Nm
80command.
81Alternatively, you can let
80command.
81Alternatively, you can let
82.Nm write
82.Nm
83select one of the terminals \- it will pick the one with the shortest
84idle time.
85This is so that if the user is logged in at work and also dialed up from
86home, the message will go to the right place.
87.Pp
88The traditional protocol for writing to someone is that the string
89.Ql \-o ,
90either at the end of a line or on a line by itself, means that it's the
91other person's turn to talk.
92The string
93.Ql oo
94means that the person believes the conversation to be
95over.
96.Sh SEE ALSO
97.Xr mesg 1 ,
98.Xr talk 1 ,
99.Xr who 1
100.Sh HISTORY
101A
102.Nm
103command appeared in
104.At v1 .
83select one of the terminals \- it will pick the one with the shortest
84idle time.
85This is so that if the user is logged in at work and also dialed up from
86home, the message will go to the right place.
87.Pp
88The traditional protocol for writing to someone is that the string
89.Ql \-o ,
90either at the end of a line or on a line by itself, means that it's the
91other person's turn to talk.
92The string
93.Ql oo
94means that the person believes the conversation to be
95over.
96.Sh SEE ALSO
97.Xr mesg 1 ,
98.Xr talk 1 ,
99.Xr who 1
100.Sh HISTORY
101A
102.Nm
103command appeared in
104.At v1 .