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

Comparing rxvt-unicode/doc/rxvtc.1.man.in (file contents):
Revision 1.3 by root, Thu Feb 2 00:24:14 2006 UTC vs.
Revision 1.5 by root, Sat Jul 22 05:35:16 2006 UTC

1.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14 1.\" Automatically generated by Pod::Man 2.09 (Pod::Simple 3.04)
2.\" 2.\"
3.\" Standard preamble: 3.\" Standard preamble:
4.\" ======================================================================== 4.\" ========================================================================
5.de Sh \" Subsection heading 5.de Sh \" Subsection heading
6.br 6.br
… …
126. ds Ae AE 126. ds Ae AE
127.\} 127.\}
128.rm #[ #] #H #V #F C 128.rm #[ #] #H #V #F C
129.\" ======================================================================== 129.\" ========================================================================
130.\" 130.\"
131.IX Title "rxvt 1" 131.IX Title "@@RXVT_NAME@@ 1"
132.TH rxvt 1 "2006-02-02" "7.5" "RXVT-UNICODE" 132.TH @@RXVT_NAME@@ 1 "2006-07-22" "7.8" "RXVT-UNICODE"
133.SH "NAME" 133.SH "NAME"
134@@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon 134@@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137\&\fB@@RXVT_NAME@@c\fR [same options as for @@RXVT_NAME@@] 137\&\fB@@RXVT_NAME@@c\fR [same options as for @@RXVT_NAME@@]
… …
143will also be respected. Currently, it always returns immediately after 143will also be respected. Currently, it always returns immediately after
144contacting the daemon. 144contacting the daemon.
145.SH "OPTIONS" 145.SH "OPTIONS"
146.IX Header "OPTIONS" 146.IX Header "OPTIONS"
147All options that are valid for \fB@@RXVT_NAME@@\fR are valid for 147All options that are valid for \fB@@RXVT_NAME@@\fR are valid for
148\&\fB@@RXVT_NAME@@c\fR, too. Please note that all options are currently 148\&\fB@@RXVT_NAME@@c\fR, too. Please note that options are interpreted in the
149interpreted in the context of the daemon process, which makes a difference 149context of the daemon process. However, as current working directory,
150for options that specify a file descriptor (such as \fB\-pty\-fd\fR). 150process environment and any file handles (e.g. for \f(CW\*(C`\-pty\-fd\*(C'\fR) are
151preserved, this rarely makes a difference.
151.SH "EXIT STATUS" 152.SH "EXIT STATUS"
152.IX Header "EXIT STATUS" 153.IX Header "EXIT STATUS"
153If everything went well, @@RXVT_NAME@@c returns with an exit status of \f(CW0\fR. 154If everything went well, @@RXVT_NAME@@c returns with an exit status of \f(CW0\fR.
154If contacting the daemon fails, it exits with the exit status \f(CW2\fR. In all other error 155If contacting the daemon fails, it exits with the exit status \f(CW2\fR. In all other error
155cases it returns with status \f(CW1\fR. 156cases it returns with status \f(CW1\fR.
156.PP 157.PP
157This can be used to implement auto-starting behaviour, by checking for an 158This can be used to implement auto-starting behaviour, by checking for an
158exit status of \f(CW2\fR, running \f(CW\*(C`@@RXVT_NAME@@d \-f \-q\*(C'\fR and retrying the call 159exit status of \f(CW2\fR, running \f(CW\*(C`@@RXVT_NAME@@d \-f \-q\*(C'\fR and retrying the call
159to @@RXVT_NAME@@c. 160to @@RXVT_NAME@@c, like this:
161.PP
162.Vb 6
163\& #!/bin/sh
164\& @@RXVT_NAME@@c "$@"
165\& if [ $? \-eq 2 ]; then
166\& @@RXVT_NAME@@d \-q \-o \-f
167\& @@RXVT_NAME@@c "$@"
168\& fi
169.Ve
160.SH "ENVIRONMENT" 170.SH "ENVIRONMENT"
161.IX Header "ENVIRONMENT" 171.IX Header "ENVIRONMENT"
162All environment variables of the current process will be made available 172All environment variables of the current process will be made available
163to the new instance, and will be interpreted as if \fB@@RXVT_NAME@@\fR were 173to the new instance, and will be interpreted as if \fB@@RXVT_NAME@@\fR were
164started directly. 174started directly.
165.IP "\fB\s-1RXVT_SOCKET\s0\fR" 4 175.IP "\fB\s-1RXVT_SOCKET\s0\fR" 4
166.IX Item "RXVT_SOCKET" 176.IX Item "RXVT_SOCKET"
167Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable 177Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable
168\&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact the 178\&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact the
169@@RXVT_NAME@@d, respectively. If the variable is missing, 179@@RXVT_NAME@@d, respectively. If the variable is missing,
170\&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used. The variable must 180\&\fI\f(CI$HOME\fI/.rxvt\-unicode\-\fI<nodename>\fI\fR is used. The variable must
171specify the absolute path of the socket to create. 181specify the absolute path of the socket to create.
172.SH "SEE ALSO" 182.SH "SEE ALSO"
173.IX Header "SEE ALSO" 183.IX Header "SEE ALSO"
174@@RXVT_NAME@@(7), @@RXVT_NAME@@d(1) 184@@RXVT_NAME@@(7), @@RXVT_NAME@@d(1)

Diff Legend

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