WISH: OnTheSpot editing, or maybe switch to miiiiiiif
WISH: just for fun, do shade and tint with XRender.
+5.9 Sat Dec 17 21:53:17 CET 2005
- fix a bug in the menu code of unknown impact, found by darix.
- clean up signal handling to be global, not per terminal
(matters only for rxvtd).
Most likely it's the empty definition for "enacs=". Just replace it
by "enacs=\E[0@" and try again.
- "bash"'s readline does not work correctly under urxvt.
+ "bash"'s readline does not work correctly under rxvt.
I need a termcap file entry.
One reason you might want this is that some distributions or
operating systems still compile some programs using the
In that case, select a font of your taste and add it to the font
list, e.g.:
- urxvt -fn basefont,font2,font3...
+ rxvt -fn basefont,font2,font3...
When rxvt-unicode sees a character, it will first look at the base
font. If the base font does not contain the character, it will go to
some editors prematurely may leave the mouse in mouse report mode.
I've heard that tcsh may use mouse reporting unless it otherwise
specified. A quick check is to see if cut/paste works when the Alt
- or Shift keys are depressed. See urxvt(7)
+ or Shift keys are depressed. See rxvt(7)
What's with this bold/blink stuff?
If no bold colour is set via "colorBD:", bold will invert text using
URxvt.color7: #e1dddd
URxvt.color15: #e1dddd
- How can I start urxvtd in a race-free way?
- Try "urxvtd -f -o", which tells urxvtd to open the display, create
- the listening socket and then fork.
+ How can I start rxvtd in a race-free way?
+ Try "rxvtd -f -o", which tells rxvtd to open the display, create the
+ listening socket and then fork.
What's with the strange Backspace/Delete key behaviour?
Assuming that the physical Backspace key corresponds to the
# use Backspace = ^H
$ stty erase ^H
- $ urxvt
+ $ rxvt
# use Backspace = ^?
$ stty erase ^?
- $ urxvt
+ $ rxvt
- Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in urxvt(7).
+ Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
For an existing rxvt-unicode:
option you can use the `keysym' resource to alter the keystrings
associated with keysyms.
- Here's an example for a URxvt session started using "urxvt -name
+ Here's an example for a URxvt session started using "rxvt -name
URxvt"
URxvt.keysym.Home: \033[1~
-embed and -pty-fd options
--enable-iso14755 (default: on)
- Enable extended ISO 14755 support (see urxvt(1), or doc/rxvt.1.txt).
+ Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt).
Basic support (section 5.1) is enabled by "--enable-frills", while
support for 5.2, 5.3 and 5.4 is enabled with this switch.
--enable-smart-resize (default: on)
Add smart growth/shrink behaviour when changing font size via hot
- keys. This should keep in a fixed position the urxvt corner which is
- closest to a corner of the screen.
+ keys. This should keep the window corner which is closest to a
+ corner of the screen in a fixed position.
--enable-pointer-blank (default: on)
Add support to have the pointer disappear when typing or inactive.
</p>
<hr />
<h1><a name="description">DESCRIPTION</a></h1>
-<p><strong>rxvt-unicode</strong>, version <strong>5.8</strong>, is a colour vt102 terminal
+<p><strong>rxvt-unicode</strong>, version <strong>5.9</strong>, is a colour vt102 terminal
emulator intended as an <em>xterm</em>(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 --
Enables ``insecure'' mode. Rxvt-unicode offers some escape sequences that
echo arbitrary strings like the icon name or the locale. This could be
abused if somebody gets 8-bit-clean access to your display, whether
-throuh a mail client displaying mail bodies unfiltered or though
-write(1). Therefore, these sequences are disabled by default. (Note
-that other terminals, including xterm, have these sequences
-enabled by default). You can enable them by setting this boolean
-resource or specifying <strong>-insecure</strong> as an option. At the moment, this
-enabled display-answer, locale, findfont, icon label and window title
-requests as well as dynamic menubar dispatch.
+through a mail client displaying mail bodies unfiltered or through
+<code>write(1)</code> or any other means. Therefore, these sequences are disabled by
+default. (Note that many other terminals, including xterm, have these
+sequences enabled by default, which doesn't make it safer, though).
+</dd>
+<dd>
+<p>You can enable them by setting this boolean resource or specifying
+<strong>-insecure</strong> as an option. At the moment, this enables display-answer,
+locale, findfont, icon label and window title requests as well as dynamic
+menubar dispatch.</p>
</dd>
<p></p>
<dt><strong><a name="item_modifier_3a_modifier"><strong>modifier:</strong> <em>modifier</em></a></strong><br />
<p>You can, however, switch fonts at runtime using escape sequences (and
therefore using the menubar), e.g.:</p>
<pre>
- printf '\e]701;%s\007' "9x15bold,xft:Kochi Gothic"</pre>
+ printf '\e]710;%s\007' "9x15bold,xft:Kochi Gothic"</pre>
<p>rxvt-unicode will automatically re-apply these fonts to the output so far.</p>
<p>
</p>
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
+.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "rxvt 1"
-.TH rxvt 1 "2005-10-25" "5.8" "RXVT-UNICODE"
+.TH rxvt 1 "2005-12-17" "5.9" "RXVT-UNICODE"
.SH "NAME"
rxvt\-unicode (ouR XVT, unicode) \- (a VT102 emulator for the X window system)
.SH "SYNOPSIS"
Enables \*(L"insecure\*(R" mode. Rxvt-unicode offers some escape sequences that
echo arbitrary strings like the icon name or the locale. This could be
abused if somebody gets 8\-bit\-clean access to your display, whether
-throuh a mail client displaying mail bodies unfiltered or though
-\&\fIwrite\fR\|(1). Therefore, these sequences are disabled by default. (Note
-that other terminals, including xterm, have these sequences
-enabled by default). You can enable them by setting this boolean
-resource or specifying \fB\-insecure\fR as an option. At the moment, this
-enabled display\-answer, locale, findfont, icon label and window title
-requests as well as dynamic menubar dispatch.
+through a mail client displaying mail bodies unfiltered or through
+\&\fIwrite\fR\|(1) or any other means. Therefore, these sequences are disabled by
+default. (Note that many other terminals, including xterm, have these
+sequences enabled by default, which doesn't make it safer, though).
+.Sp
+You can enable them by setting this boolean resource or specifying
+\&\fB\-insecure\fR as an option. At the moment, this enables display\-answer,
+locale, findfont, icon label and window title requests as well as dynamic
+menubar dispatch.
.IP "\fBmodifier:\fR \fImodifier\fR" 4
.IX Item "modifier: modifier"
Set the key to be interpreted as the Meta key to: \fBalt\fR, \fBmeta\fR,
therefore using the menubar), e.g.:
.PP
.Vb 1
-\& printf '\ee]701;%s\e007' "9x15bold,xft:Kochi Gothic"
+\& printf '\ee]710;%s\e007' "9x15bold,xft:Kochi Gothic"
.Ve
.PP
rxvt-unicode will automatically re-apply these fonts to the output so far.
rxvt [options] [-e command [ args ]]
DESCRIPTION
- rxvt-unicode, version 5.8, is a colour vt102 terminal emulator intended
+ rxvt-unicode, version 5.9, 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
Enables "insecure" mode. Rxvt-unicode offers some escape sequences
that echo arbitrary strings like the icon name or the locale. This
could be abused if somebody gets 8-bit-clean access to your display,
- whether throuh a mail client displaying mail bodies unfiltered or
- though write(1). Therefore, these sequences are disabled by default.
- (Note that other terminals, including xterm, have these sequences
- enabled by default). You can enable them by setting this boolean
- resource or specifying -insecure as an option. At the moment, this
- enabled display-answer, locale, findfont, icon label and window
- title requests as well as dynamic menubar dispatch.
+ whether through a mail client displaying mail bodies unfiltered or
+ through write(1) or any other means. Therefore, these sequences are
+ disabled by default. (Note that many other terminals, including
+ xterm, have these sequences enabled by default, which doesn't make
+ it safer, though).
+
+ You can enable them by setting this boolean resource or specifying
+ -insecure as an option. At the moment, this enables display-answer,
+ locale, findfont, icon label and window title requests as well as
+ dynamic menubar dispatch.
modifier: *modifier*
Set the key to be interpreted as the Meta key to: alt, meta, hyper,
You can, however, switch fonts at runtime using escape sequences (and
therefore using the menubar), e.g.:
- printf '\e]701;%s\007' "9x15bold,xft:Kochi Gothic"
+ printf '\e]710;%s\007' "9x15bold,xft:Kochi Gothic"
rxvt-unicode will automatically re-apply these fonts to the output so
far.
<code>enacs=\E[0@</code> and try again.
</dd>
<p></p>
-<dt><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_ur"><code>bash</code>'s readline does not work correctly under urxvt.</a></strong><br />
+<dt><strong><a name="item_bash_27s_readline_does_not_work_correctly_under_rx"><code>bash</code>'s readline does not work correctly under rxvt.</a></strong><br />
</dt>
<dt><strong><a name="item_i_need_a_termcap_file_entry_2e">I need a termcap file entry.</a></strong><br />
</dt>
</dd>
<dd>
<pre>
- urxvt -fn basefont,font2,font3...</pre>
+ rxvt -fn basefont,font2,font3...</pre>
</dd>
<dd>
<p>When rxvt-unicode sees a character, it will first look at the base
some editors prematurely may leave the mouse in mouse report mode. I've
heard that tcsh may use mouse reporting unless it otherwise specified. A
quick check is to see if cut/paste works when the Alt or Shift keys are
-depressed. See <code>urxvt(7)</code>
+depressed. See <code>rxvt(7)</code>
</dd>
<p></p>
<dt><strong><a name="item_what_27s_with_this_bold_2fblink_stuff_3f">What's with this bold/blink stuff?</a></strong><br />
URxvt.color15: #e1dddd</pre>
</dd>
<p></p>
-<dt><strong><a name="item_how_can_i_start_urxvtd_in_a_race_2dfree_way_3f">How can I start urxvtd in a race-free way?</a></strong><br />
+<dt><strong><a name="item_how_can_i_start_rxvtd_in_a_race_2dfree_way_3f">How can I start rxvtd in a race-free way?</a></strong><br />
</dt>
<dd>
-Try <code>urxvtd -f -o</code>, which tells urxvtd to open the
+Try <code>rxvtd -f -o</code>, which tells rxvtd to open the
display, create the listening socket and then fork.
</dd>
<p></p>
<pre>
# use Backspace = ^H
$ stty erase ^H
- $ urxvt</pre>
+ $ rxvt</pre>
</dd>
<dd>
<pre>
# use Backspace = ^?
$ stty erase ^?
- $ urxvt</pre>
+ $ rxvt</pre>
</dd>
<dd>
-<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code> as documented in urxvt(7).</p>
+<p>Toggle with <code>ESC [ 36 h</code> / <code>ESC [ 36 l</code> as documented in rxvt(7).</p>
</dd>
<dd>
<p>For an existing rxvt-unicode:</p>
use the `keysym' resource to alter the keystrings associated with keysyms.
</dd>
<dd>
-<p>Here's an example for a URxvt session started using <code>urxvt -name URxvt</code></p>
+<p>Here's an example for a URxvt session started using <code>rxvt -name URxvt</code></p>
</dd>
<dd>
<pre>
<dt><strong><a name="item_iso14755">--enable-iso14755 (default: on)</a></strong><br />
</dt>
<dd>
-Enable extended ISO 14755 support (see urxvt(1), or
+Enable extended ISO 14755 support (see rxvt(1), or
<em>doc/rxvt.1.txt</em>). Basic support (section 5.1) is enabled by
<code>--enable-frills</code>, while support for 5.2, 5.3 and 5.4 is enabled with
this switch.
</dt>
<dd>
Add smart growth/shrink behaviour when changing font size via hot
-keys. This should keep in a fixed position the urxvt corner which is
-closest to a corner of the screen.
+keys. This should keep the window corner which is closest to a corner of
+the screen in a fixed position.
</dd>
<p></p>
<dt><strong><a name="item_blank">--enable-pointer-blank (default: on)</a></strong><br />
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
+.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "rxvt 7"
-.TH rxvt 7 "2005-11-08" "5.8" "RXVT-UNICODE"
+.TH rxvt 7 "2005-12-17" "5.9" "RXVT-UNICODE"
.SH "NAME"
RXVT REFERENCE \- FAQ, command sequences and other background information
.SH "SYNOPSIS"
.IP "\-\-enable\-smart\-resize (default: on)" 4
.IX Item "--enable-smart-resize (default: on)"
Add smart growth/shrink behaviour when changing font size via hot
-keys. This should keep in a fixed position the @@RXVT_NAME@@ corner which is
-closest to a corner of the screen.
+keys. This should keep the window corner which is closest to a corner of
+the screen in a fixed position.
.IP "\-\-enable\-pointer\-blank (default: on)" 4
.IX Item "--enable-pointer-blank (default: on)"
Add support to have the pointer disappear when typing or inactive.
Most likely it's the empty definition for "enacs=". Just replace it
by "enacs=\E[0@" and try again.
- "bash"'s readline does not work correctly under urxvt.
+ "bash"'s readline does not work correctly under rxvt.
I need a termcap file entry.
One reason you might want this is that some distributions or
operating systems still compile some programs using the
In that case, select a font of your taste and add it to the font
list, e.g.:
- urxvt -fn basefont,font2,font3...
+ rxvt -fn basefont,font2,font3...
When rxvt-unicode sees a character, it will first look at the base
font. If the base font does not contain the character, it will go to
some editors prematurely may leave the mouse in mouse report mode.
I've heard that tcsh may use mouse reporting unless it otherwise
specified. A quick check is to see if cut/paste works when the Alt
- or Shift keys are depressed. See urxvt(7)
+ or Shift keys are depressed. See rxvt(7)
What's with this bold/blink stuff?
If no bold colour is set via "colorBD:", bold will invert text using
URxvt.color7: #e1dddd
URxvt.color15: #e1dddd
- How can I start urxvtd in a race-free way?
- Try "urxvtd -f -o", which tells urxvtd to open the display, create
- the listening socket and then fork.
+ How can I start rxvtd in a race-free way?
+ Try "rxvtd -f -o", which tells rxvtd to open the display, create the
+ listening socket and then fork.
What's with the strange Backspace/Delete key behaviour?
Assuming that the physical Backspace key corresponds to the
# use Backspace = ^H
$ stty erase ^H
- $ urxvt
+ $ rxvt
# use Backspace = ^?
$ stty erase ^?
- $ urxvt
+ $ rxvt
- Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in urxvt(7).
+ Toggle with "ESC [ 36 h" / "ESC [ 36 l" as documented in rxvt(7).
For an existing rxvt-unicode:
option you can use the `keysym' resource to alter the keystrings
associated with keysyms.
- Here's an example for a URxvt session started using "urxvt -name
+ Here's an example for a URxvt session started using "rxvt -name
URxvt"
URxvt.keysym.Home: \033[1~
-embed and -pty-fd options
--enable-iso14755 (default: on)
- Enable extended ISO 14755 support (see urxvt(1), or doc/rxvt.1.txt).
+ Enable extended ISO 14755 support (see rxvt(1), or doc/rxvt.1.txt).
Basic support (section 5.1) is enabled by "--enable-frills", while
support for 5.2, 5.3 and 5.4 is enabled with this switch.
--enable-smart-resize (default: on)
Add smart growth/shrink behaviour when changing font size via hot
- keys. This should keep in a fixed position the urxvt corner which is
- closest to a corner of the screen.
+ keys. This should keep the window corner which is closest to a
+ corner of the screen in a fixed position.
--enable-pointer-blank (default: on)
Add support to have the pointer disappear when typing or inactive.
</dt>
<dd>
Both rxvtc and rxvtd use the environment variable
-<em>RXVT_SOCKET</em> to create a listening socket and to contact
-the rxvtd, respectively. If the variable is missing,
-<em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used.
+<em>RXVT_SOCKET</em> to create a listening socket and to contact the
+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.
</dd>
<p></p></dl>
<p>
-.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14
+.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3
.\"
.\" Standard preamble:
.\" ========================================================================
.\" ========================================================================
.\"
.IX Title "rxvt 1"
-.TH rxvt 1 "2005-07-07" "5.6" "RXVT-UNICODE"
+.TH rxvt 1 "2005-12-17" "5.9" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@c \- control the @@RXVT_NAME@@d daemon
.SH "SYNOPSIS"
.IP "\fB\s-1RXVT_SOCKET\s0\fR" 4
.IX Item "RXVT_SOCKET"
Both @@RXVT_NAME@@c and @@RXVT_NAME@@d use the environment variable
-\&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact
-the @@RXVT_NAME@@d, respectively. If the variable is missing,
-\&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used.
+\&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact the
+@@RXVT_NAME@@d, respectively. If the variable is missing,
+\&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used. The variable must
+specify the absolute path of the socket to create.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
@@RXVT_NAME@@(7), @@RXVT_NAME@@d(1)
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
rxvt(7), rxvtd(1)
<dt><strong><a name="item_rxvt_socket"><strong>RXVT_SOCKET</strong></a></strong><br />
</dt>
<dd>
-Both <strong>rxvtc</strong> and <strong>rxvtd</strong> use the environment variable
-<em>RXVT_SOCKET</em> to create a listening socket and to contact
+Both <strong>rxvtc</strong> and <strong>rxvtd</strong> use the environment
+variable <em>RXVT_SOCKET</em> to create a listening socket and to contact
the rxvtd, respectively. If the variable is missing,
-<em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used.
+<em>$HOME/.rxvt-unicode-<em><nodename</em> </em>> >>> is used. The variable must
+specify the absolute path of the socket to create.
</dd>
<p></p>
<dt><strong><a name="item_display"><strong>DISPLAY</strong></a></strong><br />
.\" ========================================================================
.\"
.IX Title "rxvt 1"
-.TH rxvt 1 "2005-07-13" "5.7" "RXVT-UNICODE"
+.TH rxvt 1 "2005-12-17" "5.9" "RXVT-UNICODE"
.SH "NAME"
@@RXVT_NAME@@d \- @@RXVT_NAME@@ terminal daemon
.SH "SYNOPSIS"
.IX Header "ENVIRONMENT"
.IP "\fB\s-1RXVT_SOCKET\s0\fR" 4
.IX Item "RXVT_SOCKET"
-Both \fB@@RXVT_NAME@@c\fR and \fB@@RXVT_NAME@@d\fR use the environment variable
-\&\fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact
+Both \fB@@RXVT_NAME@@c\fR and \fB@@RXVT_NAME@@d\fR use the environment
+variable \fI\s-1RXVT_SOCKET\s0\fR to create a listening socket and to contact
the @@RXVT_NAME@@d, respectively. If the variable is missing,
-\&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used.
+\&\fI$HOME/.rxvt\-unicode\-\fI<nodename>\fI\fR is used. The variable must
+specify the absolute path of the socket to create.
.IP "\fB\s-1DISPLAY\s0\fR" 4
.IX Item "DISPLAY"
Only used when the \f(CW\*(C`\-\-opendisplay\*(C'\fR option is specified. Must contain a
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.
DISPLAY
Only used when the "--opendisplay" option is specified. Must contain
// VERSION _must_ be \d.\d+
-#define VERSION "5.8"
-#define DATE "2005-10-25"
+#define VERSION "5.9"
+#define DATE "2005-12-17"