1 |
NAME |
2 |
rxvtc - control the rxvtd daemon |
3 |
|
4 |
SYNOPSIS |
5 |
rxvtc [same options as for rxvt] |
6 |
|
7 |
DESCRIPTION |
8 |
This manpage describes the rxvtc client program. It connects to the |
9 |
rxvtd daemon and requests a new terminal window. It takes the same |
10 |
arguments as the rxvt program. The environment will also be respected. |
11 |
Currently, it always returns immediately after contacting the daemon. |
12 |
|
13 |
OPTIONS |
14 |
All options that are valid for rxvt are valid for rxvtc, too. Please |
15 |
note that options are interpreted in the context of the daemon process. |
16 |
However, as current working directory, process environment and any file |
17 |
descriptor (e.g. for "-pty-fd") are preserved, this rarely makes a |
18 |
difference. |
19 |
|
20 |
EXIT STATUS |
21 |
If everything went well, rxvtc returns with an exit status of 0. If |
22 |
contacting the daemon fails, it exits with the exit status 2. In all |
23 |
other error cases it returns with status 1. |
24 |
|
25 |
This can be used to implement auto-starting behaviour, by checking for |
26 |
an exit status of 2, running "rxvtd -f -q" and retrying the call to |
27 |
rxvtc, like this: |
28 |
|
29 |
#!/bin/sh |
30 |
rxvtc "$@" |
31 |
if [ $? -eq 2 ]; then |
32 |
rxvtd -q -o -f |
33 |
rxvtc "$@" |
34 |
fi |
35 |
|
36 |
ENVIRONMENT |
37 |
All environment variables of the current process will be made available |
38 |
to the new instance, and will be interpreted as if rxvt were started |
39 |
directly. |
40 |
|
41 |
RXVT_SOCKET |
42 |
Both rxvtc and rxvtd use the environment variable RXVT_SOCKET to |
43 |
create a listening socket and to contact the rxvtd, respectively. If |
44 |
the variable is missing, $HOME/.rxvt-unicode-*<nodename>* is used. |
45 |
The variable must specify the absolute path of the socket to create. |
46 |
|
47 |
SEE ALSO |
48 |
rxvt(7), rxvtd(1) |
49 |
|