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.6 by root, Mon Aug 7 16:17:30 2006 UTC vs.
Revision 1.7 by root, Sun Jun 24 22:12:18 2007 UTC

1<?xml version="1.0" ?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!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.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
3<html xmlns="http://www.w3.org/1999/xhtml"> 3<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
4<head> 4<head>
5<title>rxvtc - control the rxvtd daemon</title> 5 <title>rxvtc</title>
6<meta http-equiv="content-type" content="text/html; charset=utf-8" /> 6 <meta name="description" content="Pod documentation for rxvtc" />
7<link rev="made" href="mailto:perl-binary@plan9.de" /> 7 <meta name="inputfile" content="&lt;standard input&gt;" />
8</head> 8 <meta name="outputfile" content="&lt;standard output&gt;" />
9 <meta name="created" content="Mon Jun 25 00:11:17 2007" />
10 <meta name="generator" content="Pod::Xhtml 1.57" />
11<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
12<body>
13<div class="pod">
14<!-- INDEX START -->
15<h3 id="TOP">Index</h3>
9 16
10<body style="background-color: white">
11
12<p><a name="__index__"></a></p>
13<!-- INDEX BEGIN -->
14
15<ul>
16
17 <li><a href="#name">NAME</a></li> 17<ul><li><a href="#NAME">NAME</a></li>
18 <li><a href="#synopsis">SYNOPSIS</a></li> 18<li><a href="#SYNOPSIS">SYNOPSIS</a></li>
19 <li><a href="#description">DESCRIPTION</a></li> 19<li><a href="#DESCRIPTION">DESCRIPTION</a></li>
20 <li><a href="#options">OPTIONS</a></li> 20<li><a href="#OPTIONS">OPTIONS</a></li>
21 <li><a href="#exit_status">EXIT STATUS</a></li> 21<li><a href="#EXIT_STATUS">EXIT STATUS</a></li>
22 <li><a href="#environment">ENVIRONMENT</a></li> 22<li><a href="#ENVIRONMENT">ENVIRONMENT</a></li>
23 <li><a href="#see_also">SEE ALSO</a></li> 23<li><a href="#SEE_ALSO">SEE ALSO</a>
24</ul> 24</li>
25</ul><hr />
25<!-- INDEX END --> 26<!-- INDEX END -->
26 27
27<hr /> 28<h1 id="NAME">NAME</h1><p><a href="#TOP" class="toplink">Top</a></p>
28<p> 29<div id="NAME_CONTENT">
29</p>
30<h1><a name="name">NAME</a></h1>
31<p>rxvtc - control the rxvtd daemon</p> 30<p>rxvtc - control the rxvtd daemon</p>
32<p> 31
33</p> 32</div>
34<hr /> 33<h1 id="SYNOPSIS">SYNOPSIS</h1><p><a href="#TOP" class="toplink">Top</a></p>
35<h1><a name="synopsis">SYNOPSIS</a></h1> 34<div id="SYNOPSIS_CONTENT">
36<p><strong>rxvtc</strong> [same options as for rxvt]</p> 35<p><strong>rxvtc</strong> [same options as for rxvt]</p>
37<p> 36
38</p> 37</div>
39<hr /> 38<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p>
40<h1><a name="description">DESCRIPTION</a></h1> 39<div id="DESCRIPTION_CONTENT">
41<p>This manpage describes the <strong>rxvtc</strong> client program. It connects 40<p>This manpage describes the <strong>rxvtc</strong> client program. It connects
42to the <strong>rxvtd</strong> daemon and requests a new terminal window. It 41to the <strong>rxvtd</strong> daemon and requests a new terminal window. It
43takes the same arguments as the <strong>rxvt</strong> program. The environment 42takes the same arguments as the <strong>rxvt</strong> program. The environment
44will also be respected. Currently, it always returns immediately after 43will also be respected. Currently, it always returns immediately after
45contacting the daemon.</p> 44contacting the daemon.</p>
46<p> 45
47</p> 46</div>
48<hr /> 47<h1 id="OPTIONS">OPTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
49<h1><a name="options">OPTIONS</a></h1> 48<div id="OPTIONS_CONTENT">
50<p>All options that are valid for <strong>rxvt</strong> are valid for 49<p>All options that are valid for <strong>rxvt</strong> are valid for
51<strong>rxvtc</strong>, too. Please note that options are interpreted in the 50<strong>rxvtc</strong>, too. Please note that options are interpreted in the
52context of the daemon process. However, as current working directory, 51context of the daemon process. However, as current working directory,
53process environment and any file descriptor (e.g. for <code>-pty-fd</code>) are 52process environment and any file descriptor (e.g. for <code>-pty-fd</code>) are
54preserved, this rarely makes a difference.</p> 53preserved, this rarely makes a difference.</p>
55<p> 54
56</p> 55</div>
57<hr /> 56<h1 id="EXIT_STATUS">EXIT STATUS</h1><p><a href="#TOP" class="toplink">Top</a></p>
58<h1><a name="exit_status">EXIT STATUS</a></h1> 57<div id="EXIT_STATUS_CONTENT">
59<p>If everything went well, rxvtc returns with an exit status of <code>0</code>. 58<p>If everything went well, rxvtc returns with an exit status of <code>0</code>.
60If 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
61cases it returns with status <code>1</code>.</p> 60cases it returns with status <code>1</code>.</p>
62<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
63exit status of <code>2</code>, running <code>rxvtd -f -q</code> and retrying the call 62exit status of <code>2</code>, running <code>rxvtd -f -q</code> and retrying the call
64to rxvtc, like this:</p> 63to rxvtc, like this:</p>
65<pre>
66 #!/bin/sh 64<pre> #!/bin/sh
67 rxvtc &quot;$@&quot; 65 rxvtc &quot;$@&quot;
68 if [ $? -eq 2 ]; then 66 if [ $? -eq 2 ]; then
69 rxvtd -q -o -f 67 rxvtd -q -o -f
70 rxvtc &quot;$@&quot; 68 rxvtc &quot;$@&quot;
71 fi</pre> 69 fi
72<p> 70
73</p> 71</pre>
74<hr /> 72
75<h1><a name="environment">ENVIRONMENT</a></h1> 73</div>
74<h1 id="ENVIRONMENT">ENVIRONMENT</h1><p><a href="#TOP" class="toplink">Top</a></p>
75<div id="ENVIRONMENT_CONTENT">
76<p>All environment variables of the current process will be made available 76<p>All environment variables of the current process will be made available
77to the new instance, and will be interpreted as if <strong>rxvt</strong> were 77to the new instance, and will be interpreted as if <strong>rxvt</strong> were
78started directly.</p> 78started directly.</p>
79<dl> 79<dl>
80<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong> 80 <dt><strong>RXVT_SOCKET</strong></dt>
81 <dd>
82 <p>Both rxvtc and rxvtd use the environment variable
83<cite>RXVT_SOCKET</cite> to create a listening socket and to contact the
84rxvtd, respectively. If the variable is missing,
85<cite>$HOME/.rxvt-unicode-<i>&lt;nodename&gt;</i></cite> is used. The variable must
86specify the absolute path of the socket to create.</p>
87 </dd>
88</dl>
81 89
82<dd> 90</div>
83<p>Both rxvtc and rxvtd use the environment variable 91<h1 id="SEE_ALSO">SEE ALSO</h1><p><a href="#TOP" class="toplink">Top</a></p>
84<em>RXVT_SOCKET</em> to create a listening socket and to contact the 92<div id="SEE_ALSO_CONTENT">
85rxvtd, respectively. If the variable is missing,
86<em>$HOME/.rxvt-unicode-<em>&lt;nodename</em> </em>&gt; &gt;&gt;&gt; is used. The variable must
87specify the absolute path of the socket to create.</p>
88</dd>
89</li>
90</dl>
91<p>
92</p>
93<hr />
94<h1><a name="see_also">SEE ALSO</a></h1>
95<p>rxvt(7), <code>rxvtd(1)</code></p> 93<p>rxvt(7), rxvtd(1)</p>
96 94
97</body> 95</div>
98 96</div></body>
99</html> 97</html>

Diff Legend

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