1 |
=head1 NAME |
2 |
|
3 |
@@RXVT_NAME@@c - control the @@RXVT_NAME@@d daemon |
4 |
|
5 |
=head1 SYNOPSIS |
6 |
|
7 |
B<@@RXVT_NAME@@c> [same options as for @@RXVT_NAME@@] |
8 |
|
9 |
=head1 DESCRIPTION |
10 |
|
11 |
This manpage describes the B<@@RXVT_NAME@@c> client program. It connects |
12 |
to the B<@@RXVT_NAME@@d> daemon and requests a new terminal window. It |
13 |
takes the same arguments as the B<@@RXVT_NAME@@> program. The environment |
14 |
will also be respected. Currently, it always returns immediately after |
15 |
contacting the daemon. |
16 |
|
17 |
=head1 OPTIONS |
18 |
|
19 |
All options that are valid for B<@@RXVT_NAME@@> are valid for |
20 |
B<@@RXVT_NAME@@c>, too. Please note that all options are currently |
21 |
interpreted in the context of the daemon process, which makes a difference |
22 |
for options that specify a file descriptor (such as B<-pty-fd>). |
23 |
|
24 |
=head1 ENVIRONMENT |
25 |
|
26 |
All environment variables of the current process will be made available |
27 |
to the new instance, and will be interpreted as if B<@@RXVT_NAME@@> were |
28 |
started directly. |
29 |
|
30 |
=over 4 |
31 |
|
32 |
=item B<RXVT_SOCKET> |
33 |
|
34 |
Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable |
35 |
F<RXVT_SOCKET> to create a listening socket and to contact |
36 |
the @@RXVT_NAME@@d, respectively. If the variable is missing, |
37 |
F<<< $HOME/.rxvt-unicode-I<< <nodename> >> >>> is used. |
38 |
|
39 |
=back |
40 |
|
41 |
=head1 SEE ALSO |
42 |
|
43 |
@@RXVT_NAME@@(7), @@RXVT_NAME@@d(1) |
44 |
|