WISH: look into XAddConnectionWatch, does anybody need that?
DUMB: support tex fonts
+8.6 Fri Nov 23 14:10:57 CET 2007
- upgrade libev to disable kqueue on anything but netbsd as it
seems to be broken everywhere else w.r.t. ptys.
- allow for spurious event notifications, as at least epoll and
<meta name="description" content="Pod documentation for rxvt-unicode (ouR XVT, unicode)" />
<meta name="inputfile" content="<standard input>" />
<meta name="outputfile" content="<standard output>" />
- <meta name="created" content="Mon Nov 19 13:01:50 2007" />
+ <meta name="created" content="Fri Nov 23 12:34:59 2007" />
<meta name="generator" content="Pod::Xhtml 1.57" />
<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
<body>
</div>
<h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p>
<div id="DESCRIPTION_CONTENT">
-<p><strong>rxvt-unicode</strong>, version <strong>8.4</strong>, is a colour vt102 terminal
+<p><strong>rxvt-unicode</strong>, version <strong>8.6</strong>, is a colour vt102 terminal
emulator intended as an <i>xterm</i>(1) replacement for users who do not
require features such as Tektronix 4014 emulation and toolkit-style
configurability. As a result, <strong>rxvt-unicode</strong> uses much less swap space --
will not immediately destroy its window when the program executed within
it exits. Instead, it will wait till it is being killed or closed by the
user; resource <strong>hold</strong>.</p>
+ </dd>
+ <dt><strong>-xrm</strong> <i>string</i></dt>
+ <dd>
+ <p>Works like the X Toolkit option of the same name, by adding the <i>string</i>
+as if it were specified in a resource file. Resource values specified this
+way take precedence over all other resource specifications.</p>
+ <p>Note that you need to use the <i>same</i> syntax as in the .Xdefaults file,
+e.g. <code>*.background: black</code>. Also note that all rxvt-specific
+options can be specified as long-options on the commandline, so use
+of <strong>-xrm</strong> is mostly limited to cases where you want to specify other
+resources (e.g. for input methods) or for compatibility with other
+programs.</p>
</dd>
<dt><strong>-keysym.</strong><i>sym</i> <i>string</i></dt>
<dd>
3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults
4. SCREEN_RESOURCES for the current screen
5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename>
+ 6. resources specified via -xrm on the commandline
</pre>
<p>Note that when reading X resources, <strong>rxvt</strong> recognizes two class
.\" ========================================================================
.\"
.IX Title "@@RXVT_NAME@@ 1"
-.TH @@RXVT_NAME@@ 1 "2007-11-19" "8.4" "RXVT-UNICODE"
+.TH @@RXVT_NAME@@ 1 "2007-11-23" "8.6" "RXVT-UNICODE"
.SH "NAME"
rxvt\-unicode (ouR XVT, unicode) \- (a VT102 emulator for the X window system)
.SH "SYNOPSIS"
will not immediately destroy its window when the program executed within
it exits. Instead, it will wait till it is being killed or closed by the
user; resource \fBhold\fR.
+.IP "\fB\-xrm\fR \fIstring\fR" 4
+.IX Item "-xrm string"
+Works like the X Toolkit option of the same name, by adding the \fIstring\fR
+as if it were specified in a resource file. Resource values specified this
+way take precedence over all other resource specifications.
+.Sp
+Note that you need to use the \fIsame\fR syntax as in the .Xdefaults file,
+e.g. \f(CW\*(C`*.background: black\*(C'\fR. Also note that all @@RXVT_NAME@@\-specific
+options can be specified as long-options on the commandline, so use
+of \fB\-xrm\fR is mostly limited to cases where you want to specify other
+resources (e.g. for input methods) or for compatibility with other
+programs.
.IP "\fB\-keysym.\fR\fIsym\fR \fIstring\fR" 4
.IX Item "-keysym.sym string"
Remap a key symbol. See resource \fBkeysym\fR.
starts. @@RXVT_NAME@@ will consult the following files/resources in order,
with later settings overwriting earlier ones:
.PP
-.Vb 5
+.Vb 6
\& 1. system-wide app-defaults file, either locale-dependent OR global
\& 2. app-defaults file in $XAPPLRESDIR
\& 3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults
\& 4. SCREEN_RESOURCES for the current screen
\& 5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename>
+\& 6. resources specified via -xrm on the commandline
.Ve
.PP
Note that when reading X resources, \fB@@RXVT_NAME@@\fR recognizes two class
rxvt [options] [-e command [ args ]]
DESCRIPTION
- rxvt-unicode, version 8.4, is a colour vt102 terminal emulator intended
+ rxvt-unicode, version 8.6, is a colour vt102 terminal emulator intended
as an *xterm*(1) replacement for users who do not require features such
as Tektronix 4014 emulation and toolkit-style configurability. As a
result, rxvt-unicode uses much less swap space -- a significant
it exits. Instead, it will wait till it is being killed or closed by
the user; resource hold.
+ -xrm *string*
+ Works like the X Toolkit option of the same name, by adding the
+ *string* as if it were specified in a resource file. Resource values
+ specified this way take precedence over all other resource
+ specifications.
+
+ Note that you need to use the *same* syntax as in the .Xdefaults
+ file, e.g. "*.background: black". Also note that all rxvt-specific
+ options can be specified as long-options on the commandline, so use
+ of -xrm is mostly limited to cases where you want to specify other
+ resources (e.g. for input methods) or for compatibility with other
+ programs.
+
-keysym.*sym* *string*
Remap a key symbol. See resource keysym.
3. RESOURCE_MANAGER property on root-window OR $HOME/.Xdefaults
4. SCREEN_RESOURCES for the current screen
5. $XENVIRONMENT file OR $HOME/.Xdefaults-<nodename>
+ 6. resources specified via -xrm on the commandline
Note that when reading X resources, rxvt recognizes two class names:
Rxvt and URxvt. The class name Rxvt allows resources common to both rxvt
// VERSION _must_ be \d.\d+
-#define VERSION "8.5"
-#define DATE "2007-11-21"
+#define VERSION "8.6"
+#define DATE "2007-11-23"
projects / dana / urxvt.git / commitdiff