| … | |
… | |
| 17 | emulator intended as an \fIxterm\fP(1) replacement. \fBrxvtd\fP |
17 | emulator intended as an \fIxterm\fP(1) replacement. \fBrxvtd\fP |
| 18 | implements the actual program that runs runs as daemon in background and |
18 | implements the actual program that runs runs as daemon in background and |
| 19 | opens pseudo-ttys. You can run it from your X startup scripts, for |
19 | opens pseudo-ttys. You can run it from your X startup scripts, for |
| 20 | example, although it is not dependent on a working DISPLAY and, in fact, |
20 | example, although it is not dependent on a working DISPLAY and, in fact, |
| 21 | can open windows on multiple X displays. |
21 | can open windows on multiple X displays. |
|
|
22 | .PP |
|
|
23 | Both \fBrxvtd\fP and \fBrxvtc\fP use the environment variable |
|
|
24 | \fBRXVT_SOCKET\fP to create a listening socket and to contact |
|
|
25 | the \fBrxvtd\fP, respectively. If the variable is missing, |
|
|
26 | "\fB$HOME/.rxvt-\fP<nodename>" is used. |
| 22 | .PP |
27 | .PP |
| 23 | \fBrxvtc\fP is the client program of this duo. It connects to the |
28 | \fBrxvtc\fP is the client program of this duo. It connects to the |
| 24 | \fBrxvtd\fP daemon and requests a new terminal window. It |
29 | \fBrxvtd\fP daemon and requests a new terminal window. It |
| 25 | takes the same arguments as the \fBrxvt\fP program. The environment will |
30 | takes the same arguments as the \fBrxvt\fP program. The environment will |
| 26 | also be respected. Currently, it always returns immediately after contacting |
31 | also be respected. Currently, it always returns immediately after contacting |
