1 .\" Copyright (c) 1983, 1990 The Regents of the University of California.
2 .\" 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 .\" from: @(#)talk.1 6.6 (Berkeley) 4/22/91
33 .\" $Id: talk.1,v 1.15 2000/07/30 23:57:02 dholland Exp $
37 .Os "Linux NetKit (0.17)"
40 .Nd talk to another user
47 is a visual communication program which copies lines from your
48 terminal to that of another user.
51 .Bl -tag -width ttyname
53 If you wish to talk to someone on your own machine, then
55 is just the person's login name. If you wish to talk to a user on
61 If you wish to talk to a user who is logged in more than once, the
63 argument may be used to indicate the appropriate terminal
74 contacts the talk daemon on the other user's machine, which sends the
76 .Bd -literal -offset indent -compact
77 Message from TalkDaemon@his_machine...
78 talk: connection requested by your_name@your_machine.
79 talk: respond with: talk your_name@your_machine
82 to that user. At this point, he then replies by typing
84 .Dl talk \ your_name@your_machine
86 It doesn't matter from which machine the recipient replies, as
87 long as his login name is the same. Once communication is established,
88 the two parties may type simultaneously; their output will appear
89 in separate windows. Typing control-L (^L)
91 will cause the screen to
92 be reprinted. The erase, kill line, and word erase characters
93 (normally ^H, ^U, and ^W respectively)
94 will behave normally. To exit, just type the interrupt character
97 then moves the cursor to the bottom of the screen and restores the
98 terminal to its previous state.
100 As of netkit-ntalk 0.15
102 supports scrollback; use esc-p and esc-n to scroll your window, and
103 ctrl-p and ctrl-n to scroll the other window. These keys are now
104 opposite from the way they were in 0.16; while this will probably be
105 confusing at first, the rationale is that the key combinations with
106 escape are harder to type and should therefore be used to scroll one's
107 own screen, since one needs to do that much less often.
109 If you do not want to receive talk requests, you may block them using the
111 command. By default, talk requests are normally not blocked.
112 Certain commands, in particular
117 may block messages temporarily in order to
118 prevent messy output.
121 .Bl -tag -width /var/run/utmp -compact
123 to find the recipient's machine
125 to find the recipient's tty
134 The protocol used to communicate with the talk daemon is braindead.
140 uses a different and even more braindead protocol that is completely
141 incompatible. Some vendor Unixes (particularly those from Sun) have
142 been found to use this old protocol.
146 may have trouble running on machines with more than one IP address,
147 such as machines with dynamic SLIP or PPP connections. This problem is
148 fixed as of netkit-ntalk 0.11, but may affect people you are trying to