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.2 by root, Mon Nov 28 19:36:28 2005 UTC vs.
Revision 1.3 by root, Wed Feb 1 18:07:18 2006 UTC

… …
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 all options are currently
21interpreted in the context of the daemon process, which makes a difference 21interpreted in the context of the daemon process, which makes a difference
22for options that specify a file descriptor (such as B<-pty-fd>). 22for options that specify a file descriptor (such as B<-pty-fd>).
23 23
24=head1 EXIT STATUS
25
26If everything went well, @@RXVT_NAME@@c returns with an exit status of C<0>.
27If contacting the daemon fails, it exits with the exit status C<2>. In all other error
28cases it returns with status C<1>.
29
30This can be used to implement auto-starting behaviour, by checking for an
31exit status of C<2>, running C<@@RXVT_NAME@@d -f -q> and retrying the call
32to @@RXVT_NAME@@c.
33
24=head1 ENVIRONMENT 34=head1 ENVIRONMENT
25 35
26All environment variables of the current process will be made available 36All environment variables of the current process will be made available
27to the new instance, and will be interpreted as if B<@@RXVT_NAME@@> were 37to the new instance, and will be interpreted as if B<@@RXVT_NAME@@> were
28started directly. 38started directly.

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines