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.4 by root, Mon Jul 17 19:20:29 2006 UTC vs.
Revision 1.5 by root, Sat Jul 22 05:35:16 2006 UTC

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

Diff Legend

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