WISH: http://www120.pair.com/mccarthy/nextstep/intro.htmld/Workspace.html is the correct nextstep scrollbar look.
DUMB: support tex fonts
+ - fix urxvtc.1.pod: it actually claimed -pty-fd would not work. But
+ it does! :->
+
7.8 Mon Jul 17 21:00:46 CEST 2006
- INCOMPATIBLE CHANGE: this version will always read ~/.Xdefaults,
earlier versions only read it if display-resources (usually from
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
-<title>urxvtc - control the urxvtd daemon</title>
+<title>rxvtc - control the rxvtd daemon</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:perl-binary@plan9.de" />
</head>
<p>
</p>
<h1><a name="name">NAME</a></h1>
-<p>urxvtc - control the urxvtd daemon</p>
+<p>rxvtc - control the rxvtd daemon</p>
<p>
</p>
<hr />
<h1><a name="synopsis">SYNOPSIS</a></h1>
-<p><strong>urxvtc</strong> [same options as for urxvt]</p>
+<p><strong>rxvtc</strong> [same options as for rxvt]</p>
<p>
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
-<p>This manpage describes the <strong>urxvtc</strong> client program. It connects
-to the <strong>urxvtd</strong> daemon and requests a new terminal window. It
-takes the same arguments as the <strong>urxvt</strong> program. The environment
+<p>This manpage describes the <strong>rxvtc</strong> client program. It connects
+to the <strong>rxvtd</strong> daemon and requests a new terminal window. It
+takes the same arguments as the <strong>rxvt</strong> program. The environment
will also be respected. Currently, it always returns immediately after
contacting the daemon.</p>
<p>
</p>
<hr />
<h1><a name="options">OPTIONS</a></h1>
-<p>All options that are valid for <strong>urxvt</strong> are valid for
-<strong>urxvtc</strong>, 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 <strong>-pty-fd</strong>).</p>
+<p>All options that are valid for <strong>rxvt</strong> are valid for
+<strong>rxvtc</strong>, too. Please note that options are interpreted in the
+context of the daemon process. However, as current working directory,
+process environment and any file handles (e.g. for <code>-pty-fd</code>) are
+preserved, this rarely makes a difference.</p>
<p>
</p>
<hr />
<h1><a name="exit_status">EXIT STATUS</a></h1>
-<p>If everything went well, urxvtc returns with an exit status of <code>0</code>.
+<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>urxvtd -f -q</code> and retrying the call
-to urxvtc.</p>
+exit status of <code>2</code>, running <code>rxvtd -f -q</code> and retrying the call
+to rxvtc, like this:</p>
+<pre>
+ #!/bin/sh
+ rxvtc "$@"
+ if [ $? -eq 2 ]; then
+ rxvtd -q -o -f
+ rxvtc "$@"
+ fi</pre>
<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>urxvt</strong> were
+to the new instance, and will be interpreted as if <strong>rxvt</strong> were
started directly.</p>
<dl>
<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong>
<dd>
-<p>Both urxvtc and urxvtd use the environment variable
+<p>Both rxvtc and rxvtd use the environment variable
<em>RXVT_SOCKET</em> to create a listening socket and to contact the
-urxvtd, respectively. If the variable is missing,
+rxvtd, respectively. If the variable is missing,
<em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used. The variable must
specify the absolute path of the socket to create.</p>
</dd>
</p>
<hr />
<h1><a name="see_also">SEE ALSO</a></h1>
-<p>urxvt(7), <code>urxvtd(1)</code></p>
+<p>rxvt(7), <code>rxvtd(1)</code></p>
</body>
.\" ========================================================================
.\"
.IX Title "@@RXVT_NAME@@ 1"
-.TH @@RXVT_NAME@@ 1 "2006-07-17" "7.8" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 1 "2006-07-22" "7.8" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon
.SH "SYNOPSIS"
.SH "OPTIONS"
.IX Header "OPTIONS"
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).
+\&\fB@@RXVT_NAME@@c\fR, too. Please note that options are interpreted in the
+context of the daemon process. However, as current working directory,
+process environment and any file handles (e.g. for \f(CW\*(C`\-pty\-fd\*(C'\fR) are
+preserved, this rarely makes a difference.
.SH "EXIT STATUS"
.IX Header "EXIT STATUS"
If everything went well, @@RXVT_NAME@@c returns with an exit status of \f(CW0\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.
+to @@RXVT_NAME@@c, like this:
+.PP
+.Vb 6
+\& #!/bin/sh
+\& @@RXVT_NAME@@c "$@"
+\& if [ $? \-eq 2 ]; then
+\& @@RXVT_NAME@@d \-q \-o \-f
+\& @@RXVT_NAME@@c "$@"
+\& fi
+.Ve
.SH "ENVIRONMENT"
.IX Header "ENVIRONMENT"
All environment variables of the current process will be made available
=head1 OPTIONS
All options that are valid for B<@@RXVT_NAME@@> are valid for
-B<@@RXVT_NAME@@c>, 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 B<-pty-fd>).
+B<@@RXVT_NAME@@c>, too. Please note that options are interpreted in the
+context of the daemon process. However, as current working directory,
+process environment and any file handles (e.g. for C<-pty-fd>) are
+preserved, this rarely makes a difference.
=head1 EXIT STATUS
This can be used to implement auto-starting behaviour, by checking for an
exit status of C<2>, running C<@@RXVT_NAME@@d -f -q> and retrying the call
-to @@RXVT_NAME@@c.
+to @@RXVT_NAME@@c, like this:
+
+ #!/bin/sh
+ @@RXVT_NAME@@c "$@"
+ if [ $? -eq 2 ]; then
+ @@RXVT_NAME@@d -q -o -f
+ @@RXVT_NAME@@c "$@"
+ fi
=head1 ENVIRONMENT
NAME
- urxvtc - control the urxvtd daemon
+ rxvtc - control the rxvtd daemon
SYNOPSIS
- urxvtc [same options as for urxvt]
+ rxvtc [same options as for rxvt]
DESCRIPTION
- This manpage describes the urxvtc client program. It connects to the
- urxvtd daemon and requests a new terminal window. It takes the same
- arguments as the urxvt program. The environment will also be respected.
+ This manpage describes the rxvtc client program. It connects to the
+ rxvtd daemon and requests a new terminal window. It takes the same
+ arguments as the rxvt program. The environment will also be respected.
Currently, it always returns immediately after contacting the daemon.
OPTIONS
- All options that are valid for urxvt are valid for urxvtc, 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 -pty-fd).
+ All options that are valid for rxvt are valid for rxvtc, too. Please
+ note that options are interpreted in the context of the daemon process.
+ However, as current working directory, process environment and any file
+ handles (e.g. for "-pty-fd") are preserved, this rarely makes a
+ difference.
EXIT STATUS
- If everything went well, urxvtc returns with an exit status of 0. If
+ 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 "urxvtd -f -q" and retrying the call to
- urxvtc.
+ an exit status of 2, running "rxvtd -f -q" and retrying the call to
+ rxvtc, like this:
+
+ #!/bin/sh
+ rxvtc "$@"
+ if [ $? -eq 2 ]; then
+ rxvtd -q -o -f
+ rxvtc "$@"
+ fi
ENVIRONMENT
All environment variables of the current process will be made available
- to the new instance, and will be interpreted as if urxvt were started
+ to the new instance, and will be interpreted as if rxvt were started
directly.
RXVT_SOCKET
- Both urxvtc and urxvtd use the environment variable RXVT_SOCKET to
- create a listening socket and to contact the urxvtd, respectively.
- If the variable is missing, $HOME/.rxvt-unicode-*<nodename>* is
- used. The variable must specify the absolute path of the socket to
- create.
+ Both rxvtc and rxvtd use the environment variable RXVT_SOCKET to
+ create a listening socket and to contact the rxvtd, respectively. If
+ the variable is missing, $HOME/.rxvt-unicode-*<nodename>* is used.
+ The variable must specify the absolute path of the socket to create.
SEE ALSO
- urxvt(7), urxvtd(1)
+ rxvt(7), rxvtd(1)
projects / dana / urxvt.git / commitdiff