… | |
… | |
58 | <dl> |
58 | <dl> |
59 | <dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br /> |
59 | <dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br /> |
60 | </dt> |
60 | </dt> |
61 | <dd> |
61 | <dd> |
62 | Both rxvtc and rxvtd use the environment variable |
62 | Both rxvtc and rxvtd use the environment variable |
63 | <em>RXVT_SOCKET</em> to create a listening socket and to contact |
63 | <em>RXVT_SOCKET</em> to create a listening socket and to contact the |
64 | the rxvtd, respectively. If the variable is missing, |
64 | rxvtd, respectively. If the variable is missing, |
65 | <em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used. |
65 | <em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used. The variable must |
|
|
66 | specify the absolute path of the socket to create. |
66 | </dd> |
67 | </dd> |
67 | <p></p></dl> |
68 | <p></p></dl> |
68 | <p> |
69 | <p> |
69 | </p> |
70 | </p> |
70 | <hr /> |
71 | <hr /> |