| 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="#exit_status">EXIT STATUS</a></li> |
| 20 |
<li><a href="#environment">ENVIRONMENT</a></li> |
| 21 |
<li><a href="#see_also">SEE ALSO</a></li> |
| 22 |
</ul> |
| 23 |
<!-- INDEX END --> |
| 24 |
|
| 25 |
<hr /> |
| 26 |
<p> |
| 27 |
</p> |
| 28 |
<h1><a name="name">NAME</a></h1> |
| 29 |
<p>rxvtc - control the rxvtd daemon</p> |
| 30 |
<p> |
| 31 |
</p> |
| 32 |
<hr /> |
| 33 |
<h1><a name="synopsis">SYNOPSIS</a></h1> |
| 34 |
<p><strong>rxvtc</strong> [same options as for rxvt]</p> |
| 35 |
<p> |
| 36 |
</p> |
| 37 |
<hr /> |
| 38 |
<h1><a name="description">DESCRIPTION</a></h1> |
| 39 |
<p>This manpage describes the <strong>rxvtc</strong> client program. It connects |
| 40 |
to the <strong>rxvtd</strong> daemon and requests a new terminal window. It |
| 41 |
takes the same arguments as the <strong>rxvt</strong> program. The environment |
| 42 |
will also be respected. Currently, it always returns immediately after |
| 43 |
contacting the daemon.</p> |
| 44 |
<p> |
| 45 |
</p> |
| 46 |
<hr /> |
| 47 |
<h1><a name="options">OPTIONS</a></h1> |
| 48 |
<p>All options that are valid for <strong>rxvt</strong> are valid for |
| 49 |
<strong>rxvtc</strong>, too. Please note that all options are currently |
| 50 |
interpreted in the context of the daemon process, which makes a difference |
| 51 |
for options that specify a file descriptor (such as <strong>-pty-fd</strong>).</p> |
| 52 |
<p> |
| 53 |
</p> |
| 54 |
<hr /> |
| 55 |
<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>. |
| 57 |
If contacting the daemon fails, it exits with the exit status <code>2</code>. In all other error |
| 58 |
cases it returns with status <code>1</code>.</p> |
| 59 |
<p>This can be used to implement auto-starting behaviour, by checking for an |
| 60 |
exit status of <code>2</code>, running <code>rxvtd -f -q</code> and retrying the call |
| 61 |
to rxvtc.</p> |
| 62 |
<p> |
| 63 |
</p> |
| 64 |
<hr /> |
| 65 |
<h1><a name="environment">ENVIRONMENT</a></h1> |
| 66 |
<p>All environment variables of the current process will be made available |
| 67 |
to the new instance, and will be interpreted as if <strong>rxvt</strong> were |
| 68 |
started directly.</p> |
| 69 |
<dl> |
| 70 |
<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br /> |
| 71 |
</dt> |
| 72 |
<dd> |
| 73 |
Both rxvtc and rxvtd use the environment variable |
| 74 |
<em>RXVT_SOCKET</em> to create a listening socket and to contact the |
| 75 |
rxvtd, respectively. If the variable is missing, |
| 76 |
<em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used. The variable must |
| 77 |
specify the absolute path of the socket to create. |
| 78 |
</dd> |
| 79 |
<p></p></dl> |
| 80 |
<p> |
| 81 |
</p> |
| 82 |
<hr /> |
| 83 |
<h1><a name="see_also">SEE ALSO</a></h1> |
| 84 |
<p>rxvt(7), <code>rxvtd(1)</code></p> |
| 85 |
|
| 86 |
</body> |
| 87 |
|
| 88 |
</html> |
