ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvtc.1.pod
(Generate patch)

Comparing rxvt-unicode/doc/rxvtc.1.pod (file contents):
Revision 1.1 by root, Thu Jul 7 19:37:47 2005 UTC vs.
Revision 1.5 by root, Mon Aug 7 16:04:29 2006 UTC

15contacting the daemon. 15contacting the daemon.
16 16
17=head1 OPTIONS 17=head1 OPTIONS
18 18
19All options that are valid for B<@@RXVT_NAME@@> are valid for 19All options that are valid for B<@@RXVT_NAME@@> are valid for
20B<@@RXVT_NAME@@c>, too. Please note that all options are currently 20B<@@RXVT_NAME@@c>, too. Please note that options are interpreted in the
21interpreted in the context of the daemon process, which makes a difference 21context of the daemon process. However, as current working directory,
22for options that specify a file descriptor (such as B<-pty-fd>). 22process environment and any file descriptor (e.g. for C<-pty-fd>) are
23preserved, this rarely makes a difference.
24
25=head1 EXIT STATUS
26
27If everything went well, @@RXVT_NAME@@c returns with an exit status of C<0>.
28If contacting the daemon fails, it exits with the exit status C<2>. In all other error
29cases it returns with status C<1>.
30
31This can be used to implement auto-starting behaviour, by checking for an
32exit status of C<2>, running C<@@RXVT_NAME@@d -f -q> and retrying the call
33to @@RXVT_NAME@@c, like this:
34
35 #!/bin/sh
36 @@RXVT_NAME@@c "$@"
37 if [ $? -eq 2 ]; then
38 @@RXVT_NAME@@d -q -o -f
39 @@RXVT_NAME@@c "$@"
40 fi
23 41
24=head1 ENVIRONMENT 42=head1 ENVIRONMENT
25 43
26All environment variables of the current process will be made available 44All environment variables of the current process will be made available
27to the new instance, and will be interpreted as if B<@@RXVT_NAME@@> were 45to the new instance, and will be interpreted as if B<@@RXVT_NAME@@> were
30=over 4 48=over 4
31 49
32=item B<RXVT_SOCKET> 50=item B<RXVT_SOCKET>
33 51
34Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable 52Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable
35F<RXVT_SOCKET> to create a listening socket and to contact 53F<RXVT_SOCKET> to create a listening socket and to contact the
36the @@RXVT_NAME@@d, respectively. If the variable is missing, 54@@RXVT_NAME@@d, respectively. If the variable is missing,
37F<<< $HOME/.rxvt-unicode-I<< <nodename> >> >>> is used. 55F<<< $HOME/.rxvt-unicode-I<< <nodename> >> >>> is used. The variable must
56specify the absolute path of the socket to create.
38 57
39=back 58=back
40 59
41=head1 SEE ALSO 60=head1 SEE ALSO
42 61

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines