reportbug to report the bug).
+The Debian GNU/Linux package of rxvt-unicode in sarge contains large
+patches that considerably change the behaviour of rxvt-unicode. Before
+reporting a bug to the original rxvt-unicode author please download and
+install the genuine version (http://software.schmorp.de#rxvt-unicode)
+and try to reproduce the problem. If you cannot, chances are that the
+problems are specific to Debian GNU/Linux, in which case it should be
+reported via the Debian Bug Tracking System (use reportbug to report
+the bug).
For other problems that also affect the Debian package, you can and @@ -139,15 +140,22 @@ the rxvt terminfo file with the rxvt-unicode one.
bash's readline does not work correctly under rxvt.tic outputs some error when compiling the terminfo entry.enacs=. Just replace it by
+enacs=\E[0@ and try again.
+bash's readline does not work correctly under urxvt.rxvt-unicode.
+library (Fedora Core's bash is one example) and rely on a termcap entry
+for rxvt-unicode.
You could use rxvt's termcap entry with resonable results in many cases. @@ -165,22 +173,23 @@
rxvt-unicode|rxvt-unicode terminal (X Window System):\
:am:bw:eo:km:mi:ms:xn:xo:\
- :co#80:it#8:li#24:\
+ :co#80:it#8:li#24:lm#0:\
:AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
:K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
- :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\
- :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\
- :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\
- :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\
- :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
- :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\
- :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\
- :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\
- :ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\
- :ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\
- :nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\
- :st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\
- :up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
+ :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\
+ :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\
+ :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\
+ :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\
+ :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
+ :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
+ :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
+ :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\
+ :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\
+ :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\
+ :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\
+ :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
+ :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\
+ :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
:vs=\E[?25h:
- rxvt -fn basefont,font2,font3...+ urxvt -fn basefont,font2,font3...
When rxvt-unicode sees a character, it will first look at the base @@ -372,6 +381,18 @@ box data is correct.
+ #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)+
However, __STDC_ISO_10646__ is the only sane way to support
-multi-language apps in an OS, as using a locale-dependent (and
-non-standardized) representation of wchar_t makes it impossible to
-convert between wchar_t (as used by X11 and your applications) and any
-other encoding without implementing OS-specific-wrappers for each and
-every locale. There simply are no APIs to convert wchar_t into anything
-except the current locale encoding.
However, that means rxvt-unicode only works in POSIX, ISO-8859-1 and
+UTF-8 locales under FreeBSD (which all use Unicode as wchar_t.
__STDC_ISO_10646__ is the only sane way to support multi-language
+apps in an OS, as using a locale-dependent (and non-standardized)
+representation of wchar_t makes it impossible to convert between
+wchar_t (as used by X11 and your applications) and any other encoding
+without implementing OS-specific-wrappers for each and every locale. There
+simply are no APIs to convert wchar_t into anything except the current
+locale encoding.
Some applications (such as the formidable mlterm) work around this @@ -460,6 +485,29 @@ complete replacements for them :)
wcwidth and a compile problem.
+-multiwindow or
+-rootless mode instead, which will result in similar look&feel as the
+old libW11 emulation.
+At the time of this writing, cygwin didn't seem to support any multi-byte
+encodings (you might try LC_CTYPE=C-UTF-8), so you are likely limited
+to 8-bit encodings.
So the only workaround is not to kill your Input Method Servers.
+Also, many people (me included) like large windows and even larger
-scrollback buffers: Without --enable-unicode3, rxvt-unicode will use
+scrollback buffers: Without --enable-unicode3, rxvt-unicode will use
6 bytes per screen cell. For a 160x?? window this amounts to almost a
kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
-use 10 Megabytes of memory. With --enable-unicode3 it gets worse, as
+use 10 Megabytes of memory. With --enable-unicode3 it gets worse, as
rxvt-unicode then uses 8 bytes per screen cell.
:antialiasing=false), which saves lots of
+antialiasing (by appending :antialias=false), which saves lots of
memory and also speeds up rendering considerably.
rxvt(7)
+depressed. See urxvt(7)
To ensure rxvtd is listening on it's socket, you can use the -following method to wait for the startup message before continuing:
-
- { rxvtd & } | read
+Try urxvtd -f -o, which tells urxvtd to open the
+display, create the listening socket and then fork.
# use Backspace = ^H
$ stty erase ^H
- $ rxvt
+ $ urxvt
# use Backspace = ^?
$ stty erase ^?
- $ rxvt
+ $ urxvt
Toggle with ESC [ 36 h / ESC [ 36 l as documented in rxvt(7).
Toggle with ESC [ 36 h / ESC [ 36 l as documented in urxvt(7).
For an existing rxvt-unicode:
@@ -817,7 +870,7 @@ use the `keysym' resource to alter the keystrings associated with keysyms.Here's an example for a URxvt session started using rxvt -name URxvt
Here's an example for a URxvt session started using urxvt -name URxvt
@@ -1697,19 +1750,21 @@Ps = 18 Change colour of bold characters to Pt Ps = 19 Change colour of underlined characters to Pt - Ps = 20 Change default background to Pt + Ps = 39 Change default foreground colour to Pt rxvt compile-time option Ps = 39 Change default foreground colour to Pt. - Ps = 46 Change Log File to Pt unimplemented + Ps = 49 Change default background colour to Pt rxvt compile-time option Ps = 49 Change default background colour to Pt. Ps = 50 Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n - Ps = 55 Log all scrollback buffer and all of screen to Pt - Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (rxvt extension) + Ps = 703 Menubar command Pt rxvt compile-time option (rxvt-unicode extension) + Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills). Ps = 703 Menubar command Pt (Compile menubar). - Ps = 704 Change colour of italic characters to Pt + Ps = 705 Change background pixmap tint colour to Pt Ps = 705 Change background pixmap tint colour to Pt (Compile transparency). - Ps = 710 Set normal fontset to Pt. Same as Ps = 50. - Ps = 711 Set bold fontset to Pt. Similar to Ps = 50. - Ps = 712 Set italic fontset to Pt. Similar to Ps = 50. + Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50. + Ps = 711 Set bold fontset to Pt. Similar to Ps = 50 (Compile styles). + Ps = 712 Set italic fontset to Pt. Similar to Ps = 50 (Compile styles). + Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles). + Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). @@ -1765,9 +1820,12 @@
+ B<%n> rxvt name (as per the B<-name> command-line option) + B<%v> rxvt version + B<%%> literal B<%> character
General hint: if you get compile errors, then likely your configuration -hasn't been tested well. Either try with --enable-everything or use the -./reconf script as a base for experiments. ./reconf is used by myself, -so it should generally be a working config. Of course, you should always -report when a combination doesn't work, so it can be fixed. Marc Lehmann -<rxvt@schmorp.de>.
+hasn't been tested well. Either try with--enable-everything or use
+the ./reconf script as a base for experiments. ./reconf is used by
+myself, so it should generally be a working config. Of course, you should
+always report when a combination doesn't work, so it can be fixed. Marc
+Lehmann <rxvt@schmorp.de>.
+All
You can specify this and then disable options you do not like by
+following this with the appropriate --disable-... arguments,
+or you can start with a minimal configuration by specifying
+--disable-everything and than adding just the --enable-... arguments
+you want.
eu, vn
+are always compiled in, which includes most 8-bit character sets). These
+codeset tables are used for driving X11 core fonts, they are not required
+for Xft fonts, although having them compiled in lets rxvt-unicode choose
+replacement fonts more intelligently. Compiling them in will make your
+binary bigger (all of together cost about 700kB), but it doesn't increase
+memory usage unless you use a font requiring one of these encodings.
| all | all available codeset groups |
| jp_ext | rarely used but big japanese encodings |
| kr | korean encodings |
Without --enable-unicode3, the number of additional precomposed -characters is rather limited (2048, if this is full, rxvt will use the +
Without --enable-unicode3, the number of additional precomposed characters +is rather limited (2048, if this is full, rxvt-unicode will use the private use area, extending the number of combinations to 8448). With ---enable-unicode3, no practical limit exists. This will also enable -storage of characters >65535.
+--enable-unicode3, no practical limit exists. +This option will also enable storage (but not display) of characters +beyond plane 0 (>65535) when --enable-unicode3 was not specified.
The combining table also contains entries for arabic presentation forms, -but these are not currently used. Bug me if you want these to be used.
+but these are not currently used. Bug me if you want these to be used (and +tell me how these are to be used...).--enable-transparency).
--enable-transparency).
memset() function and other
@@ -2734,10 +2801,10 @@
A non-exhaustive list of features enabled by --enable-frills (possibly
+
A non-exhaustive list of features enabled by --enable-frills (possibly
in combination with other switches) is:
MWM-hints + EWMH-hints (pid, utf8 names) and protocols (ping) seperate underline colour settable border widths and borderless switch settable extra linespacing - extra window properties (e.g. UTF-8 window names and PID) iso-14755-2 and -3, and visual feedback backindex and forwardindex escape sequence - window op and locale change escape sequences + window op and some xterm/OSC escape sequences tripleclickwords settable insecure mode - keysym remapping support+ keysym remapping support + cursor blinking and underline cursor + -embed and -pty-fd options
--enable-frills, while support for 5.2, 5.3 and 5.4 is enabled with
+--enable-frills, while support for 5.2, 5.3 and 5.4 is enabled with
this switch.
urxvt, resulting
+Set the basename for the installed binaries, resulting
in urxvt, urxvtd etc.). Specify --with-name=rxvt to replace with
rxvt.
rxvt-unicode)
+Change the environmental variable for the terminal to NAME.