From 86bf6c65c13d0db10cfe00abbf8b697c22d2de91 Mon Sep 17 00:00:00 2001 From: root Date: Thu, 2 Feb 2006 00:24:14 +0000 Subject: [PATCH] *** empty log message *** --- Changes | 6 ++---- doc/rxvtc.1.html | 11 +++++++++++ doc/rxvtc.1.man.in | 13 +++++++++++-- doc/rxvtc.1.txt | 9 +++++++++ 4 files changed, 33 insertions(+), 6 deletions(-) diff --git a/Changes b/Changes index 88ff742e..95f48f0a 100644 --- a/Changes +++ b/Changes @@ -13,15 +13,13 @@ WISH: anyevent mouse notification / manage MotionMask better. 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 diff --git a/doc/rxvtc.1.html b/doc/rxvtc.1.html index ad824066..8b14a70b 100644 --- a/doc/rxvtc.1.html +++ b/doc/rxvtc.1.html @@ -16,6 +16,7 @@
  • SYNOPSIS
  • DESCRIPTION
  • OPTIONS
    • +
  • EXIT STATUS
  • ENVIRONMENT
  • SEE ALSO
    • @@ -51,6 +52,16 @@ 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 diff --git a/doc/rxvtc.1.man.in b/doc/rxvtc.1.man.in index 574f4c8b..18eb947a 100644 --- a/doc/rxvtc.1.man.in +++ b/doc/rxvtc.1.man.in @@ -1,4 +1,4 @@ -.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3 +.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14 .\" .\" Standard preamble: .\" ======================================================================== @@ -129,7 +129,7 @@ .\" ======================================================================== .\" .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" @@ -148,6 +148,15 @@ All options that are valid for \fB@@RXVT_NAME@@\fR are valid for \&\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 diff --git a/doc/rxvtc.1.txt b/doc/rxvtc.1.txt index 7207178e..87198790 100644 --- a/doc/rxvtc.1.txt +++ b/doc/rxvtc.1.txt @@ -16,6 +16,15 @@ OPTIONS 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 -- 2.34.1