"#rxvt-unicode" has some rxvt-unicode enthusiasts that might be
interested in learning about new and exciting problems (but not FAQs :).
+ I use Gentoo, and I have a problem...
+ There are three big problems with Gentoo Linux: first of all, most if
+ not all Gentoo systems are completely broken (missing or mismatched
+ header files, broken compiler etc. are just the tip of the iceberg);
+ secondly, the Gentoo maintainer thinks it is a good idea to add broken
+ patches to the code; and lastly, it should be called Gentoo GNU/Linux.
+
+ For these reasons, it is impossible to support rxvt-unicode on Gentoo.
+ Problems appearing on Gentoo systems will usually simply be ignored
+ unless they can be reproduced on non-Gentoo systems.
+
Does it support tabs, can I have a tabbed rxvt-unicode?
Beginning with version 7.3, there is a perl extension that implements a
simple tabbed terminal. It is installed by default, so any of these
In this case either do not specify a preeditStyle or specify more than
one pre-edit style, such as OverTheSpot,Root,None.
+ If it still doesn't work, then maybe your input method doesn't support
+ compose sequences - to fall back to the built-in one, make sure you
+ don't specify an input method via "-im" or "XMODIFIERS".
+
I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755
Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on
international keyboards) or simply use ISO 14755 support to your
The selection stuff mainly makes the selection perl-error-message aware
and tells it to convert perl error messages into vi-commands to load the
- relevant file and go tot he error line number.
+ relevant file and go to the error line number.
URxvt.scrollstyle: plain
URxvt.secondaryScroll: true
bold and normal fonts.
Please note that I used the "urxvt" instance name and not the "URxvt"
- class name. Thats because I use different configs for different
+ class name. That is because I use different configs for different
purposes, for example, my IRC window is started with "-name IRC", and
uses these defaults:
IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007
IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007
- "Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes.
+ "Alt-Ctrl-1" and "Alt-Ctrl-2" switch between two different font sizes.
"suxuseuro" allows me to keep an eye (and actually read) stuff while
keeping a very small window. If somebody pastes something complicated
(e.g. japanese), I temporarily switch to a larger font.
arises).
The correct solution for this problem is to install the terminfo, this
- can be done like this (with ncurses' infocmp and works as user and
- admin):
+ can be done by simply installing rxvt-unicode on the remote system as
+ well (in case you have a nice package manager ready), or you can install
+ the terminfo database manually like this (with ncurses infocmp. works as
+ user and root):
REMOTE=remotesystem.domain
infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti"
- ... or by installing rxvt-unicode normally on the remote system,
-
One some systems you might need to set $TERMINFO to the full path of
$HOME/.terminfo for this to work.
If you don't plan to use rxvt (quite common...) you could also replace
the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt".
+ nano fails with "Error opening terminal: rxvt-unicode"
+ This exceptionally confusing and useless error message is printed by
+ nano when it can't find the terminfo database. Nothing is wrong with
+ your terminal, read the previous answer for a solution.
+
"tic" outputs some error when compiling the terminfo entry.
Most likely it's the empty definition for "enacs=". Just replace it by
"enacs=\E[0@" and try again.
infocmp -C rxvt-unicode
- Or you could use this termcap entry, generated by the command above:
-
- rxvt-unicode|rxvt-unicode terminal (X Window System):\
- :am:bw:eo:km:mi:ms:xn:xo:\
- :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=\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:
+ Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap,
+ generated by the command above.
Why does "ls" no longer have coloured output?
The "ls" in the GNU coreutils unfortunately doesn't use terminfo to
should be enabled, as important functionality (menus, selection, likely
more in the future) depends on it.
- You should not overwrite the "perl-ext-common" snd "perl-ext" resources
+ You should not overwrite the "perl-ext-common" and "perl-ext" resources
system-wide (except maybe with "defaults"). This will result in useful
behaviour. If your distribution aims at low memory, add an empty
"perl-ext-common" resource to the app-defaults file. This will keep the
wchar_t. This is, of course, completely fine with respect to standards.
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.
+ "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)
http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c
+ I want 256 colors
+ Are you sure you need 256 colors? 88 colors should be enough for most
+ purposes. If you really need more, there is an unsupported patch for it
+ in the doc directory, but please do not ask for it to be applied.
+