1 |
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> |
2 |
<html xmlns="http://www.w3.org/1999/xhtml"> |
3 |
<head> |
4 |
<title>rxvtc - control the rxvtd daemon</title> |
5 |
<link rev="made" href="mailto:perl-binary@plan9.de" /> |
6 |
</head> |
7 |
|
8 |
<body style="background-color: white"> |
9 |
|
10 |
<p><a name="__index__"></a></p> |
11 |
<!-- INDEX BEGIN --> |
12 |
|
13 |
<ul> |
14 |
|
15 |
<li><a href="#name">NAME</a></li> |
16 |
<li><a href="#synopsis">SYNOPSIS</a></li> |
17 |
<li><a href="#description">DESCRIPTION</a></li> |
18 |
<li><a href="#options">OPTIONS</a></li> |
19 |
<li><a href="#environment">ENVIRONMENT</a></li> |
20 |
<li><a href="#see_also">SEE ALSO</a></li> |
21 |
</ul> |
22 |
<!-- INDEX END --> |
23 |
|
24 |
<hr /> |
25 |
<p> |
26 |
</p> |
27 |
<h1><a name="name">NAME</a></h1> |
28 |
<p>rxvtc - control the rxvtd daemon</p> |
29 |
<p> |
30 |
</p> |
31 |
<hr /> |
32 |
<h1><a name="synopsis">SYNOPSIS</a></h1> |
33 |
<p><strong>rxvtc</strong> [same options as for rxvt]</p> |
34 |
<p> |
35 |
</p> |
36 |
<hr /> |
37 |
<h1><a name="description">DESCRIPTION</a></h1> |
38 |
<p>This manpage describes the <strong>rxvtc</strong> client program. It connects |
39 |
to the <strong>rxvtd</strong> daemon and requests a new terminal window. It |
40 |
takes the same arguments as the <strong>rxvt</strong> program. The environment |
41 |
will also be respected. Currently, it always returns immediately after |
42 |
contacting the daemon.</p> |
43 |
<p> |
44 |
</p> |
45 |
<hr /> |
46 |
<h1><a name="options">OPTIONS</a></h1> |
47 |
<p>All options that are valid for <strong>rxvt</strong> are valid for |
48 |
<strong>rxvtc</strong>, too. Please note that all options are currently |
49 |
interpreted in the context of the daemon process, which makes a difference |
50 |
for options that specify a file descriptor (such as <strong>-pty-fd</strong>).</p> |
51 |
<p> |
52 |
</p> |
53 |
<hr /> |
54 |
<h1><a name="environment">ENVIRONMENT</a></h1> |
55 |
<p>All environment variables of the current process will be made available |
56 |
to the new instance, and will be interpreted as if <strong>rxvt</strong> were |
57 |
started directly.</p> |
58 |
<dl> |
59 |
<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br /> |
60 |
</dt> |
61 |
<dd> |
62 |
Both rxvtc and rxvtd use the environment variable |
63 |
<em>RXVT_SOCKET</em> to create a listening socket and to contact the |
64 |
rxvtd, respectively. If the variable is missing, |
65 |
<em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used. The variable must |
66 |
specify the absolute path of the socket to create. |
67 |
</dd> |
68 |
<p></p></dl> |
69 |
<p> |
70 |
</p> |
71 |
<hr /> |
72 |
<h1><a name="see_also">SEE ALSO</a></h1> |
73 |
<p>rxvt(7), <code>rxvtd(1)</code></p> |
74 |
|
75 |
</body> |
76 |
|
77 |
</html> |