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