WISH: http://www120.pair.com/mccarthy/nextstep/intro.htmld/Workspace.html is the correct nextstep look.
DUMB: support tex fonts
-THINK: struct passwd *userinfo; /* defined in pwd.h + if ((userinfo = getpwuid(getuid())) != NULL) + shell = strdup(userinfo->pw_shell); /* retrieve current shell */
-
TODO: xim "how to" faq entry
- changed interpretation of [alpha] colour prefix.
- +option now really sets the option to default, instead of using the
resource value.
- - options that require an agrument now _really_ require an argument.
- - use exit status 2 in urxvtc when urxvtd couldn't be contacted.
+ - options that require an argument now really _require_ an argument.
+ - return exit status 2 in urxvtc when urxvtd couldn't be contacted.
- the linux yield hack is back, now using usleep, and enabled only on
__linux__.
- further round trip eliminations in the !XFT case by remembering
<li><a href="#synopsis">SYNOPSIS</a></li>
<li><a href="#description">DESCRIPTION</a></li>
<li><a href="#options">OPTIONS</a></li>
+ <li><a href="#exit_status">EXIT STATUS</a></li>
<li><a href="#environment">ENVIRONMENT</a></li>
<li><a href="#see_also">SEE ALSO</a></li>
</ul>
<p>
</p>
<hr />
+<h1><a name="exit_status">EXIT STATUS</a></h1>
+<p>If everything went well, rxvtc returns with an exit status of <code>0</code>.
+If contacting the daemon fails, it exits with the exit status <code>2</code>. In all other error
+cases it returns with status <code>1</code>.</p>
+<p>This can be used to implement auto-starting behaviour, by checking for an
+exit status of <code>2</code>, running <code>rxvtd -f -q</code> and retrying the call
+to rxvtc.</p>
+<p>
+</p>
+<hr />
<h1><a name="environment">ENVIRONMENT</a></h1>
<p>All environment variables of the current process will be made available
to the new instance, and will be interpreted as if <strong>rxvt</strong> were
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3
+.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "rxvt 1"
-.TH rxvt 1 "2005-12-17" "5.9" "RXVT-UNICODE"
+.TH rxvt 1 "2006-02-02" "7.5" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon
.SH "SYNOPSIS"
\&\fB@@RXVT_NAME@@c\fR, too. Please note that all options are currently
interpreted in the context of the daemon process, which makes a difference
for options that specify a file descriptor (such as \fB\-pty\-fd\fR).
+.SH "EXIT STATUS"
+.IX Header "EXIT STATUS"
+If everything went well, @@RXVT_NAME@@c returns with an exit status of \f(CW0\fR.
+If contacting the daemon fails, it exits with the exit status \f(CW2\fR. In all other error
+cases it returns with status \f(CW1\fR.
+.PP
+This can be used to implement auto-starting behaviour, by checking for an
+exit status of \f(CW2\fR, running \f(CW\*(C`@@RXVT_NAME@@d \-f \-q\*(C'\fR and retrying the call
+to @@RXVT_NAME@@c.
.SH "ENVIRONMENT"
.IX Header "ENVIRONMENT"
All environment variables of the current process will be made available
daemon process, which makes a difference for options that specify a file
descriptor (such as -pty-fd).
+EXIT STATUS
+ If everything went well, rxvtc returns with an exit status of 0. If
+ contacting the daemon fails, it exits with the exit status 2. In all
+ other error cases it returns with status 1.
+
+ This can be used to implement auto-starting behaviour, by checking for
+ an exit status of 2, running "rxvtd -f -q" and retrying the call to
+ rxvtc.
+
ENVIRONMENT
All environment variables of the current process will be made available
to the new instance, and will be interpreted as if rxvt were started