ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvtc.1.html
(Generate patch)

Comparing rxvt-unicode/doc/rxvtc.1.html (file contents):
Revision 1.3 by root, Thu Feb 2 00:24:14 2006 UTC vs.
Revision 1.4 by root, Mon Jul 17 19:20:29 2006 UTC

1<?xml version="1.0" ?>
1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> 2<!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<html xmlns="http://www.w3.org/1999/xhtml">
3<head> 4<head>
4<title>rxvtc - control the rxvtd daemon</title> 5<title>urxvtc - control the urxvtd daemon</title>
6<meta http-equiv="content-type" content="text/html; charset=utf-8" />
5<link rev="made" href="mailto:perl-binary@plan9.de" /> 7<link rev="made" href="mailto:perl-binary@plan9.de" />
6</head> 8</head>
7 9
8<body style="background-color: white"> 10<body style="background-color: white">
9 11
… …
24 26
25<hr /> 27<hr />
26<p> 28<p>
27</p> 29</p>
28<h1><a name="name">NAME</a></h1> 30<h1><a name="name">NAME</a></h1>
29<p>rxvtc - control the rxvtd daemon</p> 31<p>urxvtc - control the urxvtd daemon</p>
30<p> 32<p>
31</p> 33</p>
32<hr /> 34<hr />
33<h1><a name="synopsis">SYNOPSIS</a></h1> 35<h1><a name="synopsis">SYNOPSIS</a></h1>
34<p><strong>rxvtc</strong> [same options as for rxvt]</p> 36<p><strong>urxvtc</strong> [same options as for urxvt]</p>
35<p> 37<p>
36</p> 38</p>
37<hr /> 39<hr />
38<h1><a name="description">DESCRIPTION</a></h1> 40<h1><a name="description">DESCRIPTION</a></h1>
39<p>This manpage describes the <strong>rxvtc</strong> client program. It connects 41<p>This manpage describes the <strong>urxvtc</strong> client program. It connects
40to the <strong>rxvtd</strong> daemon and requests a new terminal window. It 42to the <strong>urxvtd</strong> daemon and requests a new terminal window. It
41takes the same arguments as the <strong>rxvt</strong> program. The environment 43takes the same arguments as the <strong>urxvt</strong> program. The environment
42will also be respected. Currently, it always returns immediately after 44will also be respected. Currently, it always returns immediately after
43contacting the daemon.</p> 45contacting the daemon.</p>
44<p> 46<p>
45</p> 47</p>
46<hr /> 48<hr />
47<h1><a name="options">OPTIONS</a></h1> 49<h1><a name="options">OPTIONS</a></h1>
48<p>All options that are valid for <strong>rxvt</strong> are valid for 50<p>All options that are valid for <strong>urxvt</strong> are valid for
49<strong>rxvtc</strong>, too. Please note that all options are currently 51<strong>urxvtc</strong>, too. Please note that all options are currently
50interpreted in the context of the daemon process, which makes a difference 52interpreted in the context of the daemon process, which makes a difference
51for options that specify a file descriptor (such as <strong>-pty-fd</strong>).</p> 53for options that specify a file descriptor (such as <strong>-pty-fd</strong>).</p>
52<p> 54<p>
53</p> 55</p>
54<hr /> 56<hr />
55<h1><a name="exit_status">EXIT STATUS</a></h1> 57<h1><a name="exit_status">EXIT STATUS</a></h1>
56<p>If everything went well, rxvtc returns with an exit status of <code>0</code>. 58<p>If everything went well, urxvtc returns with an exit status of <code>0</code>.
57If contacting the daemon fails, it exits with the exit status <code>2</code>. In all other error 59If contacting the daemon fails, it exits with the exit status <code>2</code>. In all other error
58cases it returns with status <code>1</code>.</p> 60cases it returns with status <code>1</code>.</p>
59<p>This can be used to implement auto-starting behaviour, by checking for an 61<p>This can be used to implement auto-starting behaviour, by checking for an
60exit status of <code>2</code>, running <code>rxvtd -f -q</code> and retrying the call 62exit status of <code>2</code>, running <code>urxvtd -f -q</code> and retrying the call
61to rxvtc.</p> 63to urxvtc.</p>
62<p> 64<p>
63</p> 65</p>
64<hr /> 66<hr />
65<h1><a name="environment">ENVIRONMENT</a></h1> 67<h1><a name="environment">ENVIRONMENT</a></h1>
66<p>All environment variables of the current process will be made available 68<p>All environment variables of the current process will be made available
67to the new instance, and will be interpreted as if <strong>rxvt</strong> were 69to the new instance, and will be interpreted as if <strong>urxvt</strong> were
68started directly.</p> 70started directly.</p>
69<dl> 71<dl>
70<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br /> 72<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong>
71</dt> 73
72<dd> 74<dd>
73Both rxvtc and rxvtd use the environment variable 75<p>Both urxvtc and urxvtd use the environment variable
74<em>RXVT_SOCKET</em> to create a listening socket and to contact the 76<em>RXVT_SOCKET</em> to create a listening socket and to contact the
75rxvtd, respectively. If the variable is missing, 77urxvtd, respectively. If the variable is missing,
76<em>$HOME/.rxvt-unicode-<em>&lt;nodename</em> </em>&gt; &gt;&gt;&gt; is used. The variable must 78<em>$HOME/.rxvt-unicode-<em>&lt;nodename</em> </em>&gt; &gt;&gt;&gt; is used. The variable must
77specify the absolute path of the socket to create. 79specify the absolute path of the socket to create.</p>
78</dd> 80</dd>
79<p></p></dl> 81</li>
82</dl>
80<p> 83<p>
81</p> 84</p>
82<hr /> 85<hr />
83<h1><a name="see_also">SEE ALSO</a></h1> 86<h1><a name="see_also">SEE ALSO</a></h1>
84<p>rxvt(7), <code>rxvtd(1)</code></p> 87<p>urxvt(7), <code>urxvtd(1)</code></p>
85 88
86</body> 89</body>
87 90
88</html> 91</html>

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines