| 1 |
<?xml version="1.0" encoding="UTF-8"?> |
| 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" xml:lang="en"> |
| 4 |
<head> |
| 5 |
<title>rxvtc</title> |
| 6 |
<meta name="description" content="Pod documentation for rxvtc" /> |
| 7 |
<meta name="inputfile" content="<standard input>" /> |
| 8 |
<meta name="outputfile" content="<standard output>" /> |
| 9 |
<meta name="created" content="Mon Jun 25 00:30:33 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> |
| 16 |
|
| 17 |
<ul><li><a href="#NAME">NAME</a></li> |
| 18 |
<li><a href="#SYNOPSIS">SYNOPSIS</a></li> |
| 19 |
<li><a href="#DESCRIPTION">DESCRIPTION</a></li> |
| 20 |
<li><a href="#OPTIONS">OPTIONS</a></li> |
| 21 |
<li><a href="#EXIT_STATUS">EXIT STATUS</a></li> |
| 22 |
<li><a href="#ENVIRONMENT">ENVIRONMENT</a></li> |
| 23 |
<li><a href="#SEE_ALSO">SEE ALSO</a> |
| 24 |
</li> |
| 25 |
</ul><hr /> |
| 26 |
<!-- INDEX END --> |
| 27 |
|
| 28 |
<h1 id="NAME">NAME</h1><p><a href="#TOP" class="toplink">Top</a></p> |
| 29 |
<div id="NAME_CONTENT"> |
| 30 |
<p>rxvtc - control the rxvtd daemon</p> |
| 31 |
|
| 32 |
</div> |
| 33 |
<h1 id="SYNOPSIS">SYNOPSIS</h1><p><a href="#TOP" class="toplink">Top</a></p> |
| 34 |
<div id="SYNOPSIS_CONTENT"> |
| 35 |
<p><strong>rxvtc</strong> [same options as for rxvt]</p> |
| 36 |
|
| 37 |
</div> |
| 38 |
<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p> |
| 39 |
<div id="DESCRIPTION_CONTENT"> |
| 40 |
<p>This manpage describes the <strong>rxvtc</strong> client program. It connects |
| 41 |
to the <strong>rxvtd</strong> daemon and requests a new terminal window. It |
| 42 |
takes the same arguments as the <strong>rxvt</strong> program. The environment |
| 43 |
will also be respected. Currently, it always returns immediately after |
| 44 |
contacting the daemon.</p> |
| 45 |
|
| 46 |
</div> |
| 47 |
<h1 id="OPTIONS">OPTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p> |
| 48 |
<div id="OPTIONS_CONTENT"> |
| 49 |
<p>All options that are valid for <strong>rxvt</strong> are valid for |
| 50 |
<strong>rxvtc</strong>, too. Please note that options are interpreted in the |
| 51 |
context of the daemon process. However, as current working directory, |
| 52 |
process environment and any file descriptor (e.g. for <code>-pty-fd</code>) are |
| 53 |
preserved, this rarely makes a difference.</p> |
| 54 |
|
| 55 |
</div> |
| 56 |
<h1 id="EXIT_STATUS">EXIT STATUS</h1><p><a href="#TOP" class="toplink">Top</a></p> |
| 57 |
<div id="EXIT_STATUS_CONTENT"> |
| 58 |
<p>If everything went well, rxvtc returns with an exit status of <code>0</code>. |
| 59 |
If contacting the daemon fails, it exits with the exit status <code>2</code>. In all other error |
| 60 |
cases it returns with status <code>1</code>.</p> |
| 61 |
<p>This can be used to implement auto-starting behaviour, by checking for an |
| 62 |
exit status of <code>2</code>, running <code>rxvtd -f -q</code> and retrying the call |
| 63 |
to rxvtc, like this:</p> |
| 64 |
<pre> #!/bin/sh |
| 65 |
rxvtc "$@" |
| 66 |
if [ $? -eq 2 ]; then |
| 67 |
rxvtd -q -o -f |
| 68 |
rxvtc "$@" |
| 69 |
fi |
| 70 |
|
| 71 |
</pre> |
| 72 |
|
| 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 |
| 77 |
to the new instance, and will be interpreted as if <strong>rxvt</strong> were |
| 78 |
started directly.</p> |
| 79 |
<dl> |
| 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 |
| 84 |
rxvtd, respectively. If the variable is missing, |
| 85 |
<cite>$HOME/.rxvt-unicode-<i><nodename></i></cite> is used. The variable must |
| 86 |
specify the absolute path of the socket to create.</p> |
| 87 |
</dd> |
| 88 |
</dl> |
| 89 |
|
| 90 |
</div> |
| 91 |
<h1 id="SEE_ALSO">SEE ALSO</h1><p><a href="#TOP" class="toplink">Top</a></p> |
| 92 |
<div id="SEE_ALSO_CONTENT"> |
| 93 |
<p>rxvt(7), rxvtd(1)</p> |
| 94 |
|
| 95 |
</div> |
| 96 |
</div></body> |
| 97 |
</html> |
