| 1 | FREQUENTLY ASKED QUESTIONS |
1 | RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS |
| 2 | Meta, Features & Commandline Issues |
2 | Meta, Features & Commandline Issues |
| 3 | My question isn't answered here, can I ask a human? |
3 | My question isn't answered here, can I ask a human? |
| 4 | Before sending me mail, you could go to IRC: "irc.freenode.net", channel |
4 | Before sending me mail, you could go to IRC: "irc.libera.chat", channel |
| 5 | "#rxvt-unicode" has some rxvt-unicode enthusiasts that might be |
5 | "#rxvt-unicode" has some rxvt-unicode enthusiasts that might be |
| 6 | interested in learning about new and exciting problems (but not FAQs :). |
6 | interested in learning about new and exciting problems (but not FAQs :). |
|
|
7 | |
|
|
8 | I use Gentoo, and I have a problem... |
|
|
9 | There are two big problems with Gentoo Linux: first, most if not all |
|
|
10 | Gentoo systems are completely broken (missing or mismatched header |
|
|
11 | files, broken compiler etc. are just the tip of the iceberg); secondly, |
|
|
12 | it should be called Gentoo GNU/Linux. |
|
|
13 | |
|
|
14 | For these reasons, it is impossible to support rxvt-unicode on Gentoo. |
|
|
15 | Problems appearing on Gentoo systems will usually simply be ignored |
|
|
16 | unless they can be reproduced on non-Gentoo systems. |
| 7 | |
17 | |
| 8 | Does it support tabs, can I have a tabbed rxvt-unicode? |
18 | Does it support tabs, can I have a tabbed rxvt-unicode? |
| 9 | Beginning with version 7.3, there is a perl extension that implements a |
19 | Beginning with version 7.3, there is a perl extension that implements a |
| 10 | simple tabbed terminal. It is installed by default, so any of these |
20 | simple tabbed terminal. It is installed by default, so any of these |
| 11 | should give you tabs: |
21 | should give you tabs: |
| … | |
… | |
| 42 | |
52 | |
| 43 | How can I start urxvtd in a race-free way? |
53 | How can I start urxvtd in a race-free way? |
| 44 | Try "urxvtd -f -o", which tells urxvtd to open the display, create the |
54 | Try "urxvtd -f -o", which tells urxvtd to open the display, create the |
| 45 | listening socket and then fork. |
55 | listening socket and then fork. |
| 46 | |
56 | |
| 47 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
57 | How can I start urxvtd automatically when I run urxvtc? |
| 48 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
58 | If you want to start urxvtd automatically whenever you run urxvtc and |
| 49 | check and see if that is set. Note that several programs, JED, slrn, |
59 | the daemon isn't running yet, use this script: |
| 50 | Midnight Commander automatically check this variable to decide whether |
60 | |
| 51 | or not to use color. |
61 | #!/bin/sh |
|
|
62 | urxvtc "$@" |
|
|
63 | if [ $? -eq 2 ]; then |
|
|
64 | urxvtd -q -o -f |
|
|
65 | urxvtc "$@" |
|
|
66 | fi |
|
|
67 | |
|
|
68 | This tries to create a new terminal, and if fails with exit status 2, |
|
|
69 | meaning it couldn't connect to the daemon, it will start the daemon and |
|
|
70 | re-run the command. Subsequent invocations of the script will re-use the |
|
|
71 | existing daemon. |
|
|
72 | |
|
|
73 | Another option is to use systemd socket-based activation (see |
|
|
74 | systemd.socket(5)). Here is an example of a service unit file and of a |
|
|
75 | socket unit file for the default socket path: |
|
|
76 | |
|
|
77 | urxvtd.service |
|
|
78 | [Unit] |
|
|
79 | Description=urxvt terminal daemon |
|
|
80 | Requires=urxvtd.socket |
|
|
81 | |
|
|
82 | [Service] |
|
|
83 | ExecStart=/usr/bin/urxvtd -o |
|
|
84 | |
|
|
85 | urxvtd.socket |
|
|
86 | [Unit] |
|
|
87 | Description=urxvt terminal daemon socket |
|
|
88 | |
|
|
89 | [Socket] |
|
|
90 | ListenStream=%h/.urxvt/urxvtd-%H |
|
|
91 | |
|
|
92 | [Install] |
|
|
93 | WantedBy=sockets.target |
|
|
94 | |
|
|
95 | How do I distinguish whether I'm running rxvt-unicode or a regular |
|
|
96 | xterm? I need this to decide about setting colours etc. |
|
|
97 | The original rxvt and rxvt-unicode always export the variable |
|
|
98 | "COLORTERM", so you can check and see if that is set. Note that several |
|
|
99 | programs, JED, slrn, Midnight Commander automatically check this |
|
|
100 | variable to decide whether or not to use colour. |
| 52 | |
101 | |
| 53 | How do I set the correct, full IP address for the DISPLAY variable? |
102 | How do I set the correct, full IP address for the DISPLAY variable? |
| 54 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
103 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
| 55 | insecure mode then it is possible to use the following shell script |
104 | insecure mode then it is possible to use the following shell script |
| 56 | snippets to correctly set the display. If your version of rxvt-unicode |
105 | snippets to correctly set the display. If your version of rxvt-unicode |
| … | |
… | |
| 63 | |
112 | |
| 64 | # Bourne/Korn/POSIX family of shells: |
113 | # Bourne/Korn/POSIX family of shells: |
| 65 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
114 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
| 66 | if [ ${TERM:-foo} = xterm ]; then |
115 | if [ ${TERM:-foo} = xterm ]; then |
| 67 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
116 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
| 68 | echo -n '^[Z' |
117 | printf "\eZ" |
| 69 | read term_id |
118 | read term_id |
| 70 | stty icanon echo |
119 | stty icanon echo |
| 71 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
120 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
| 72 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
121 | printf '\e[7n' # query the rxvt we are in for the DISPLAY string |
| 73 | read DISPLAY # set it in our local shell |
122 | read DISPLAY # set it in our local shell |
| 74 | fi |
123 | fi |
| 75 | fi |
124 | fi |
| 76 | |
125 | |
| 77 | How do I compile the manual pages on my own? |
126 | How do I compile the manual pages on my own? |
| 78 | You need to have a recent version of perl installed as /usr/bin/perl, |
127 | You need to have a recent version of perl installed as /usr/bin/perl, |
| 79 | one that comes with pod2man, pod2text and pod2html. Then go to the doc |
128 | one that comes with pod2man, pod2text and pod2xhtml (from Pod::Xhtml). |
| 80 | subdirectory and enter "make alldoc". |
129 | Then go to the doc subdirectory and enter "make alldoc". |
| 81 | |
130 | |
| 82 | Isn't rxvt-unicode supposed to be small? Don't all those features bloat? |
131 | Isn't rxvt-unicode supposed to be small? Don't all those features bloat? |
| 83 | I often get asked about this, and I think, no, they didn't cause extra |
132 | I often get asked about this, and I think, no, they didn't cause extra |
| 84 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
133 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
| 85 | that the urxvt binary is larger (due to some encoding tables always |
134 | that the urxvt binary is larger (due to some encoding tables always |
| … | |
… | |
| 90 | |
139 | |
| 91 | text data bss drs rss filename |
140 | text data bss drs rss filename |
| 92 | 98398 1664 24 15695 1824 rxvt --disable-everything |
141 | 98398 1664 24 15695 1824 rxvt --disable-everything |
| 93 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
142 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
| 94 | |
143 | |
| 95 | When you "--enable-everything" (which _is_ unfair, as this involves xft |
144 | When you "--enable-everything" (which *is* unfair, as this involves xft |
| 96 | and full locale/XIM support which are quite bloaty inside libX11 and my |
145 | and full locale/XIM support which are quite bloaty inside libX11 and my |
| 97 | libc), the two diverge, but not unreasnobaly so. |
146 | libc), the two diverge, but not unreasonably so. |
| 98 | |
147 | |
| 99 | text data bss drs rss filename |
148 | text data bss drs rss filename |
| 100 | 163431 2152 24 20123 2060 rxvt --enable-everything |
149 | 163431 2152 24 20123 2060 rxvt --enable-everything |
| 101 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
150 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
| 102 | |
151 | |
| … | |
… | |
| 130 | the case of rxvt-unicode this hardly matters, as its portability limits |
179 | the case of rxvt-unicode this hardly matters, as its portability limits |
| 131 | are defined by things like X11, pseudo terminals, locale support and |
180 | are defined by things like X11, pseudo terminals, locale support and |
| 132 | unix domain sockets, which are all less portable than C++ itself. |
181 | unix domain sockets, which are all less portable than C++ itself. |
| 133 | |
182 | |
| 134 | Regarding the bloat, see the above question: It's easy to write programs |
183 | Regarding the bloat, see the above question: It's easy to write programs |
| 135 | in C that use gobs of memory, an certainly possible to write programs in |
184 | in C that use gobs of memory, and certainly possible to write programs |
| 136 | C++ that don't. C++ also often comes with large libraries, but this is |
185 | in C++ that don't. C++ also often comes with large libraries, but this |
| 137 | not necessarily the case with GCC. Here is what rxvt links against on my |
186 | is not necessarily the case with GCC. Here is what rxvt links against on |
| 138 | system with a minimal config: |
187 | my system with a minimal config: |
| 139 | |
188 | |
| 140 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
189 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
| 141 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
190 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
| 142 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
191 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
| 143 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
192 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
| 144 | |
193 | |
| 145 | And here is rxvt-unicode: |
194 | And here is rxvt-unicode: |
| 146 | |
195 | |
| 147 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
196 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
| 148 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
197 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
| 149 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
198 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
| 150 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
199 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
| 151 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
200 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
| 152 | |
201 | |
| 153 | No large bloated libraries (of course, none were linked in statically), |
202 | No large bloated libraries (of course, none were linked in statically), |
| 154 | except maybe libX11 :) |
203 | except maybe libX11 :) |
| 155 | |
204 | |
| 156 | Rendering, Font & Look and Feel Issues |
205 | Rendering, Font & Look and Feel Issues |
| … | |
… | |
| 161 | rite of passage: ... and you failed. |
210 | rite of passage: ... and you failed. |
| 162 | |
211 | |
| 163 | Here are four ways to get transparency. Do read the manpage and option |
212 | Here are four ways to get transparency. Do read the manpage and option |
| 164 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
213 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
| 165 | |
214 | |
| 166 | 1. Use inheritPixmap: |
215 | 1. Use pseudo-transparency: |
| 167 | |
216 | |
| 168 | Esetroot wallpaper.jpg |
217 | Esetroot wallpaper.jpg |
| 169 | urxvt -ip -tint red -sh 40 |
218 | urxvt -tr -tint red -sh 40 |
| 170 | |
219 | |
| 171 | That works. If you think it doesn't, you lack transparency and tinting |
220 | That works. If you think it doesn't, you lack transparency and tinting |
| 172 | support, or you are unable to read. |
221 | support, or you are unable to read. This method requires that the |
|
|
222 | background-setting program sets the _XROOTPMAP_ID or ESETROOT_PMAP_ID |
|
|
223 | property. Compatible programs are Esetroot, hsetroot and feh. |
| 173 | |
224 | |
| 174 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
225 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
| 175 | to use effects other than tinting and shading: Just shade/tint/whatever |
226 | to use effects other than tinting and shading: Just shade/tint/whatever |
| 176 | your picture with gimp or any other tool: |
227 | your picture with gimp or any other tool: |
| 177 | |
228 | |
| 178 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
229 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
| 179 | urxvt -pixmap background.xpm -pe automove-background |
230 | urxvt -pixmap "background.jpg;:root" |
| 180 | |
231 | |
| 181 | That works. If you think it doesn't, you lack XPM and Perl support, or |
232 | That works. If you think it doesn't, you lack GDK-PixBuf support, or you |
| 182 | you are unable to read. |
233 | are unable to read. |
| 183 | |
234 | |
| 184 | 3. Use an ARGB visual: |
235 | 3. Use an ARGB visual: |
| 185 | |
236 | |
| 186 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
237 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
| 187 | |
238 | |
| 188 | This requires XFT support, and the support of your X-server. If that |
239 | This requires XFT support, and the support of your X-server. If that |
| 189 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
240 | doesn't work for you, find a working composite manager or window |
| 190 | there yet, no matter what they claim. Rxvt-Unicode contains the |
241 | manager, both are required to support ARGB visuals for client windows. |
| 191 | neccessary bugfixes and workarounds for Xft and Xlib to make it work, |
|
|
| 192 | but that doesn't mean that your WM has the required kludges in place. |
|
|
| 193 | |
242 | |
| 194 | 4. Use xcompmgr and let it do the job: |
243 | 4. Use xcompmgr and let it do the job: |
| 195 | |
244 | |
| 196 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
245 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
| 197 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
246 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
| 198 | |
247 | |
| 199 | Then click on a window you want to make transparent. Replace 0xc0000000 |
248 | Then click on a window you want to make transparent. Replace 0xc0000000 |
| 200 | by other values to change the degree of opacity. If it doesn't work and |
249 | by other values to change the degree of opacity. If it doesn't work and |
| 201 | your server crashes, you got to keep the pieces. |
250 | your server crashes, you got to keep the pieces. |
| 202 | |
|
|
| 203 | Why do some chinese characters look so different than others? |
|
|
| 204 | This is because there is a difference between script and language -- |
|
|
| 205 | rxvt-unicode does not know which language the text that is output is, as |
|
|
| 206 | it only knows the unicode character codes. If rxvt-unicode first sees a |
|
|
| 207 | japanese/chinese character, it might choose a japanese font for display. |
|
|
| 208 | Subsequent japanese characters will use that font. Now, many chinese |
|
|
| 209 | characters aren't represented in japanese fonts, so when the first |
|
|
| 210 | non-japanese character comes up, rxvt-unicode will look for a chinese |
|
|
| 211 | font -- unfortunately at this point, it will still use the japanese font |
|
|
| 212 | for chinese characters that are also in the japanese font. |
|
|
| 213 | |
|
|
| 214 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
| 215 | list (see the previous question). The key is to view the font list as a |
|
|
| 216 | preference list: If you expect more japanese, list a japanese font |
|
|
| 217 | first. If you expect more chinese, put a chinese font first. |
|
|
| 218 | |
|
|
| 219 | In the future it might be possible to switch language preferences at |
|
|
| 220 | runtime (the internal data structure has no problem with using different |
|
|
| 221 | fonts for the same character at the same time, but no interface for this |
|
|
| 222 | has been designed yet). |
|
|
| 223 | |
|
|
| 224 | Until then, you might get away with switching fonts at runtime (see "Can |
|
|
| 225 | I switch the fonts at runtime?" later in this document). |
|
|
| 226 | |
251 | |
| 227 | Why does rxvt-unicode sometimes leave pixel droppings? |
252 | Why does rxvt-unicode sometimes leave pixel droppings? |
| 228 | Most fonts were not designed for terminal use, which means that |
253 | Most fonts were not designed for terminal use, which means that |
| 229 | character size varies a lot. A font that is otherwise fine for terminal |
254 | character size varies a lot. A font that is otherwise fine for terminal |
| 230 | use might contain some characters that are simply too wide. Rxvt-unicode |
255 | use might contain some characters that are simply too wide. Rxvt-unicode |
| … | |
… | |
| 236 | however: Xft fonts often draw glyphs larger than their acclaimed |
261 | however: Xft fonts often draw glyphs larger than their acclaimed |
| 237 | bounding box, and rxvt-unicode has no way of detecting this (the correct |
262 | bounding box, and rxvt-unicode has no way of detecting this (the correct |
| 238 | way is to ask for the character bounding box, which unfortunately is |
263 | way is to ask for the character bounding box, which unfortunately is |
| 239 | wrong in these cases). |
264 | wrong in these cases). |
| 240 | |
265 | |
| 241 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
266 | It's not clear (to me at least), whether this is a bug in Xft, freetype, |
| 242 | or the respective font. If you encounter this problem you might try |
267 | or the respective font. If you encounter this problem you might try |
| 243 | using the "-lsp" option to give the font more height. If that doesn't |
268 | using the "-lsp" option to give the font more height. If that doesn't |
| 244 | work, you might be forced to use a different font. |
269 | work, you might be forced to use a different font. |
| 245 | |
270 | |
| 246 | All of this is not a problem when using X11 core fonts, as their |
271 | All of this is not a problem when using X11 core fonts, as their |
| … | |
… | |
| 268 | |
293 | |
| 269 | Can I switch the fonts at runtime? |
294 | Can I switch the fonts at runtime? |
| 270 | Yes, using an escape sequence. Try something like this, which has the |
295 | Yes, using an escape sequence. Try something like this, which has the |
| 271 | same effect as using the "-fn" switch, and takes effect immediately: |
296 | same effect as using the "-fn" switch, and takes effect immediately: |
| 272 | |
297 | |
| 273 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
298 | printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic" |
| 274 | |
299 | |
| 275 | This is useful if you e.g. work primarily with japanese (and prefer a |
300 | This is useful if you e.g. work primarily with japanese (and prefer a |
| 276 | japanese font), but you have to switch to chinese temporarily, where |
301 | japanese font), but you have to switch to chinese temporarily, where |
| 277 | japanese fonts would only be in your way. |
302 | japanese fonts would only be in your way. |
| 278 | |
303 | |
| 279 | You can think of this as a kind of manual ISO-2022 switching. |
304 | You can think of this as a kind of manual ISO-2022 switching. |
| 280 | |
305 | |
| 281 | Why do italic characters look as if clipped? |
306 | Why do italic characters look as if clipped? |
| 282 | Many fonts have difficulties with italic characters and hinting. For |
307 | Many fonts have difficulties with italic characters and hinting. For |
| 283 | example, the otherwise very nicely hinted font "xft:Bitstream Vera Sans |
308 | example, the otherwise very nicely hinted font "xft:Bitstream Vera Sans |
| 284 | Mono" completely fails in it's italic face. A workaround might be to |
309 | Mono" completely fails in its italic face. A workaround might be to |
| 285 | enable freetype autohinting, i.e. like this: |
310 | enable freetype autohinting, i.e. like this: |
| 286 | |
311 | |
| 287 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
312 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
| 288 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
313 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
| 289 | |
314 | |
| … | |
… | |
| 293 | antialiasing (by appending ":antialias=false"), which saves lots of |
318 | antialiasing (by appending ":antialias=false"), which saves lots of |
| 294 | memory and also speeds up rendering considerably. |
319 | memory and also speeds up rendering considerably. |
| 295 | |
320 | |
| 296 | Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
321 | Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
| 297 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
322 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
| 298 | fall back to it's default font search list it will prefer X11 core |
323 | fall back to its default font search list it will prefer X11 core fonts, |
| 299 | fonts, because they are small and fast, and then use Xft fonts. It has |
324 | because they are small and fast, and then use Xft fonts. It has |
| 300 | antialiasing disabled for most of them, because the author thinks they |
325 | antialiasing disabled for most of them, because the author thinks they |
| 301 | look best that way. |
326 | look best that way. |
| 302 | |
327 | |
| 303 | If you want antialiasing, you have to specify the fonts manually. |
328 | If you want antialiasing, you have to specify the fonts manually. |
| 304 | |
329 | |
| 305 | What's with this bold/blink stuff? |
330 | What's with this bold/blink stuff? |
| 306 | If no bold colour is set via "colorBD:", bold will invert text using the |
331 | If no bold colour is set via "colorBD:", bold will invert text using the |
| 307 | standard foreground colour. |
332 | standard foreground colour. |
| 308 | |
333 | |
| 309 | For the standard background colour, blinking will actually make the text |
334 | For the standard background colour, blinking will actually make the text |
| 310 | blink when compiled with "--enable-blinking". with standard colours. |
335 | blink when compiled with "--enable-text-blink". Without |
| 311 | Without "--enable-blinking", the blink attribute will be ignored. |
336 | "--enable-text-blink", the blink attribute will be ignored. |
| 312 | |
337 | |
| 313 | On ANSI colours, bold/blink attributes are used to set high-intensity |
338 | On ANSI colours, bold/blink attributes are used to set high-intensity |
| 314 | foreground/background colors. |
339 | foreground/background colours. |
| 315 | |
340 | |
| 316 | color0-7 are the low-intensity colors. |
341 | color0-7 are the low-intensity colours. |
| 317 | |
342 | |
| 318 | color8-15 are the corresponding high-intensity colors. |
343 | color8-15 are the corresponding high-intensity colours. |
| 319 | |
344 | |
| 320 | I don't like the screen colors. How do I change them? |
345 | I don't like the screen colours. How do I change them? |
| 321 | You can change the screen colors at run-time using ~/.Xdefaults |
346 | You can change the screen colours at run-time using ~/.Xdefaults |
| 322 | resources (or as long-options). |
347 | resources (or as long-options). |
| 323 | |
348 | |
| 324 | Here are values that are supposed to resemble a VGA screen, including |
349 | Here are values that are supposed to resemble a VGA screen, including |
| 325 | the murky brown that passes for low-intensity yellow: |
350 | the murky brown that passes for low-intensity yellow: |
| 326 | |
351 | |
| … | |
… | |
| 340 | URxvt.color12: #0000FF |
365 | URxvt.color12: #0000FF |
| 341 | URxvt.color13: #FF00FF |
366 | URxvt.color13: #FF00FF |
| 342 | URxvt.color14: #00FFFF |
367 | URxvt.color14: #00FFFF |
| 343 | URxvt.color15: #FFFFFF |
368 | URxvt.color15: #FFFFFF |
| 344 | |
369 | |
| 345 | And here is a more complete set of non-standard colors described (not by |
370 | And here is a more complete set of non-standard colours. |
| 346 | me) as "pretty girly". |
|
|
| 347 | |
371 | |
| 348 | URxvt.cursorColor: #dc74d1 |
372 | URxvt.cursorColor: #dc74d1 |
| 349 | URxvt.pointerColor: #dc74d1 |
373 | URxvt.pointerColor: #dc74d1 |
| 350 | URxvt.background: #0e0e0e |
374 | URxvt.background: #0e0e0e |
| 351 | URxvt.foreground: #4ad5e1 |
375 | URxvt.foreground: #4ad5e1 |
| … | |
… | |
| 362 | URxvt.color6: #73f7ff |
386 | URxvt.color6: #73f7ff |
| 363 | URxvt.color14: #73f7ff |
387 | URxvt.color14: #73f7ff |
| 364 | URxvt.color7: #e1dddd |
388 | URxvt.color7: #e1dddd |
| 365 | URxvt.color15: #e1dddd |
389 | URxvt.color15: #e1dddd |
| 366 | |
390 | |
|
|
391 | They have been described (not by me) as "pretty girly". |
|
|
392 | |
| 367 | Why do some characters look so much different than others? |
393 | Why do some characters look so much different than others? |
| 368 | See next entry. |
394 | See next entry. |
| 369 | |
395 | |
| 370 | How does rxvt-unicode choose fonts? |
396 | How does rxvt-unicode choose fonts? |
| 371 | Most fonts do not contain the full range of Unicode, which is fine. |
397 | Most fonts do not contain the full range of Unicode, which is fine. |
| … | |
… | |
| 382 | |
408 | |
| 383 | In that case, select a font of your taste and add it to the font list, |
409 | In that case, select a font of your taste and add it to the font list, |
| 384 | e.g.: |
410 | e.g.: |
| 385 | |
411 | |
| 386 | urxvt -fn basefont,font2,font3... |
412 | urxvt -fn basefont,font2,font3... |
| 387 | |
413 | |
| 388 | When rxvt-unicode sees a character, it will first look at the base font. |
414 | When rxvt-unicode sees a character, it will first look at the base font. |
| 389 | If the base font does not contain the character, it will go to the next |
415 | If the base font does not contain the character, it will go to the next |
| 390 | font, and so on. Specifying your own fonts will also speed up this |
416 | font, and so on. Specifying your own fonts will also speed up this |
| 391 | search and use less resources within rxvt-unicode and the X-server. |
417 | search and use less resources within rxvt-unicode and the X-server. |
| 392 | |
418 | |
| 393 | The only limitation is that none of the fonts may be larger than the |
419 | The only limitation is that none of the fonts may be larger than the |
| 394 | base font, as the base font defines the terminal character cell size, |
420 | base font, as the base font defines the terminal character cell size, |
| 395 | which must be the same due to the way terminals work. |
421 | which must be the same due to the way terminals work. |
| 396 | |
422 | |
|
|
423 | Why do some chinese characters look so different than others? |
|
|
424 | This is because there is a difference between script and language -- |
|
|
425 | rxvt-unicode does not know which language the text that is output is, as |
|
|
426 | it only knows the unicode character codes. If rxvt-unicode first sees a |
|
|
427 | japanese/chinese character, it might choose a japanese font for display. |
|
|
428 | Subsequent japanese characters will use that font. Now, many chinese |
|
|
429 | characters aren't represented in japanese fonts, so when the first |
|
|
430 | non-japanese character comes up, rxvt-unicode will look for a chinese |
|
|
431 | font -- unfortunately at this point, it will still use the japanese font |
|
|
432 | for chinese characters that are also in the japanese font. |
|
|
433 | |
|
|
434 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
435 | list (see the previous question). The key is to view the font list as a |
|
|
436 | preference list: If you expect more japanese, list a japanese font |
|
|
437 | first. If you expect more chinese, put a chinese font first. |
|
|
438 | |
|
|
439 | In the future it might be possible to switch language preferences at |
|
|
440 | runtime (the internal data structure has no problem with using different |
|
|
441 | fonts for the same character at the same time, but no interface for this |
|
|
442 | has been designed yet). |
|
|
443 | |
|
|
444 | Until then, you might get away with switching fonts at runtime (see "Can |
|
|
445 | I switch the fonts at runtime?" later in this document). |
|
|
446 | |
|
|
447 | How can I make mplayer display video correctly? |
|
|
448 | We are working on it, in the meantime, as a workaround, use something |
|
|
449 | like: |
|
|
450 | |
|
|
451 | urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' |
|
|
452 | |
|
|
453 | Why is the cursor now blinking in emacs/vi/...? |
|
|
454 | This is likely caused by your editor/program's use of the "cvvis" |
|
|
455 | terminfo capability. Emacs uses it by default, as well as some versions |
|
|
456 | of vi and possibly other programs. |
|
|
457 | |
|
|
458 | In emacs, you can switch that off by adding this to your ".emacs" file: |
|
|
459 | |
|
|
460 | (setq visible-cursor nil) |
|
|
461 | |
|
|
462 | For other programs, if they do not have an option, your have to remove |
|
|
463 | the "cvvis" capability from the terminfo description. |
|
|
464 | |
|
|
465 | When urxvt first added the blinking cursor option, it didn't add a |
|
|
466 | "cvvis" capability, which served no purpose before. Version 9.21 |
|
|
467 | introduced "cvvis" (and the ability to control blinking independent of |
|
|
468 | cursor shape) for compatibility with other terminals, which |
|
|
469 | traditionally use a blinking cursor for "cvvis". This also reflects the |
|
|
470 | intent of programs such as emacs, who expect "cvvis" to enable a |
|
|
471 | blinking cursor. |
|
|
472 | |
| 397 | Keyboard, Mouse & User Interaction |
473 | Keyboard, Mouse & User Interaction |
| 398 | The new selection selects pieces that are too big, how can I select single words? |
474 | The new selection selects pieces that are too big, how can I select single words? |
| 399 | If you want to select e.g. alphanumeric words, you can use the following |
475 | If you want to select e.g. alphanumeric words, you can use the following |
| 400 | setting: |
476 | setting: |
| 401 | |
477 | |
| … | |
… | |
| 407 | To get a selection that is very similar to the old code, try this |
483 | To get a selection that is very similar to the old code, try this |
| 408 | pattern: |
484 | pattern: |
| 409 | |
485 | |
| 410 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
486 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
| 411 | |
487 | |
| 412 | Please also note that the *LeftClick Shift-LeftClik* combination also |
488 | Please also note that the *LeftClick Shift-LeftClick* combination also |
| 413 | selects words like the old code. |
489 | selects words like the old code. |
| 414 | |
490 | |
| 415 | I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
491 | I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
| 416 | You can disable the perl extension completely by setting the |
492 | You can disable the perl extension completely by setting the |
| 417 | perl-ext-common resource to the empty string, which also keeps |
493 | perl-ext-common resource to the empty string, which also keeps |
| … | |
… | |
| 426 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
502 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
| 427 | |
503 | |
| 428 | This will keep the default extensions, but disable the two popup |
504 | This will keep the default extensions, but disable the two popup |
| 429 | extensions. Some extensions can also be configured, for example, |
505 | extensions. Some extensions can also be configured, for example, |
| 430 | scrollback search mode is triggered by M-s. You can move it to any other |
506 | scrollback search mode is triggered by M-s. You can move it to any other |
| 431 | combination either by setting the searchable-scrollback resource: |
507 | combination by adding a keysym resource that binds the desired |
|
|
508 | combination to the "start" action of "searchable-scrollback" and another |
|
|
509 | one that binds M-s to the "builtin:" action: |
| 432 | |
510 | |
| 433 | URxvt.searchable-scrollback: CM-s |
511 | URxvt.keysym.CM-s: searchable-scrollback:start |
|
|
512 | URxvt.keysym.M-s: builtin: |
| 434 | |
513 | |
| 435 | The cursor moves when selecting text in the current input line, how do I switch this off? |
514 | The cursor moves when selecting text in the current input line, how do I switch this off? |
| 436 | See next entry. |
515 | See next entry. |
| 437 | |
516 | |
| 438 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
517 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
| … | |
… | |
| 440 | circumstances, it will move your cursor around when you click into the |
519 | circumstances, it will move your cursor around when you click into the |
| 441 | line that contains it. It tries hard not to do this at the wrong moment, |
520 | line that contains it. It tries hard not to do this at the wrong moment, |
| 442 | but when running a program that doesn't parse cursor movements or in |
521 | but when running a program that doesn't parse cursor movements or in |
| 443 | some cases during rlogin sessions, it fails to detect this properly. |
522 | some cases during rlogin sessions, it fails to detect this properly. |
| 444 | |
523 | |
| 445 | You can permamently switch this feature off by disabling the "readline" |
524 | You can permanently switch this feature off by disabling the "readline" |
| 446 | extension: |
525 | extension: |
| 447 | |
526 | |
| 448 | URxvt.perl-ext-common: default,-readline |
527 | URxvt.perl-ext-common: default,-readline |
| 449 | |
528 | |
| 450 | My numerical keypad acts weird and generates differing output? |
529 | My numeric keypad acts weird and generates differing output? |
| 451 | Some Debian GNUL/Linux users seem to have this problem, although no |
530 | Some Debian GNU/Linux users seem to have this problem, although no |
| 452 | specific details were reported so far. It is possible that this is |
531 | specific details were reported so far. It is possible that this is |
| 453 | caused by the wrong "TERM" setting, although the details of wether and |
532 | caused by the wrong "TERM" setting, although the details of whether and |
| 454 | how this can happen are unknown, as "TERM=rxvt" should offer a |
533 | how this can happen are unknown, as "TERM=rxvt" should offer a |
| 455 | compatible keymap. See the answer to the previous question, and please |
534 | compatible keymap. See the answer to the previous question, and please |
| 456 | report if that helped. |
535 | report if that helped. |
| 457 | |
536 | |
| 458 | My Compose (Multi_key) key is no longer working. |
537 | My Compose (Multi_key) key is no longer working. |
| 459 | The most common causes for this are that either your locale is not set |
538 | The most common causes for this are that either your locale is not set |
| 460 | correctly, or you specified a preeditStyle that is not supported by your |
539 | correctly, or you specified a preeditType that is not supported by your |
| 461 | input method. For example, if you specified OverTheSpot and your input |
540 | input method. For example, if you specified OverTheSpot and your input |
| 462 | method (e.g. the default input method handling Compose keys) does not |
541 | method (e.g. the default input method handling Compose keys) does not |
| 463 | support this (for instance because it is not visual), then rxvt-unicode |
542 | support this (for instance because it is not visual), then rxvt-unicode |
| 464 | will continue without an input method. |
543 | will continue without an input method. |
| 465 | |
544 | |
| 466 | In this case either do not specify a preeditStyle or specify more than |
545 | In this case either do not specify a preeditType or specify more than |
| 467 | one pre-edit style, such as OverTheSpot,Root,None. |
546 | one pre-edit style, such as OverTheSpot,Root,None. |
|
|
547 | |
|
|
548 | If it still doesn't work, then maybe your input method doesn't support |
|
|
549 | compose sequences - to fall back to the built-in one, make sure you |
|
|
550 | don't specify an input method via "-im" or "XMODIFIERS". |
| 468 | |
551 | |
| 469 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
552 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
| 470 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
553 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
| 471 | international keyboards) or simply use ISO 14755 support to your |
554 | international keyboards) or simply use ISO 14755 support to your |
| 472 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
555 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
| 473 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
556 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
| 474 | escape character and so on. |
557 | escape character and so on. |
| 475 | |
558 | |
| 476 | Mouse cut/paste suddenly no longer works. |
559 | Mouse cut/paste suddenly no longer works. |
| 477 | Make sure that mouse reporting is actually turned off since killing some |
560 | Make sure that mouse reporting is actually turned off since killing some |
| 478 | editors prematurely may leave the mouse in mouse report mode. I've heard |
561 | editors prematurely may leave it active. I've heard that tcsh may use |
| 479 | that tcsh may use mouse reporting unless it otherwise specified. A quick |
562 | mouse reporting unless it is otherwise specified. A quick check is to |
| 480 | check is to see if cut/paste works when the Alt or Shift keys are |
563 | see if cut/paste works when the Alt or Shift keys are pressed. |
| 481 | depressed. |
|
|
| 482 | |
564 | |
| 483 | What's with the strange Backspace/Delete key behaviour? |
565 | What's with the strange Backspace/Delete key behaviour? |
| 484 | Assuming that the physical Backspace key corresponds to the BackSpace |
566 | Assuming that the physical Backspace key corresponds to the Backspace |
| 485 | keysym (not likely for Linux ... see the following question) there are |
567 | keysym (not likely for Linux ... see the following question) there are |
| 486 | two standard values that can be used for Backspace: "^H" and "^?". |
568 | two standard values that can be used for Backspace: "^H" and "^?". |
| 487 | |
569 | |
| 488 | Historically, either value is correct, but rxvt-unicode adopts the |
570 | Historically, either value is correct, but rxvt-unicode adopts the |
| 489 | debian policy of using "^?" when unsure, because it's the one only only |
571 | debian policy of using "^?" when unsure, because it's the one and only |
| 490 | correct choice :). |
572 | correct choice :). |
| 491 | |
573 | |
| 492 | Rxvt-unicode tries to inherit the current stty settings and uses the |
574 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
| 493 | value of `erase' to guess the value for backspace. If rxvt-unicode |
575 | mode: |
| 494 | wasn't started from a terminal (say, from a menu or by remote shell), |
|
|
| 495 | then the system value of `erase', which corresponds to CERASE in |
|
|
| 496 | <termios.h>, will be used (which may not be the same as your stty |
|
|
| 497 | setting). |
|
|
| 498 | |
|
|
| 499 | For starting a new rxvt-unicode: |
|
|
| 500 | |
576 | |
| 501 | # use Backspace = ^H |
577 | # use Backspace = ^H |
| 502 | $ stty erase ^H |
578 | $ stty erase ^H |
| 503 | $ urxvt |
579 | $ printf "\e[?67h" |
| 504 | |
580 | |
| 505 | # use Backspace = ^? |
581 | # use Backspace = ^? |
| 506 | $ stty erase ^? |
582 | $ stty erase ^? |
| 507 | $ urxvt |
583 | $ printf "\e[?67l" |
| 508 | |
|
|
| 509 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
|
|
| 510 | |
|
|
| 511 | For an existing rxvt-unicode: |
|
|
| 512 | |
|
|
| 513 | # use Backspace = ^H |
|
|
| 514 | $ stty erase ^H |
|
|
| 515 | $ echo -n "^[[36h" |
|
|
| 516 | |
|
|
| 517 | # use Backspace = ^? |
|
|
| 518 | $ stty erase ^? |
|
|
| 519 | $ echo -n "^[[36l" |
|
|
| 520 | |
584 | |
| 521 | This helps satisfy some of the Backspace discrepancies that occur, but |
585 | This helps satisfy some of the Backspace discrepancies that occur, but |
| 522 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
586 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
| 523 | properly reflects that. |
587 | properly reflects that. |
| 524 | |
588 | |
| … | |
… | |
| 540 | use the `keysym' resource to alter the keystrings associated with |
604 | use the `keysym' resource to alter the keystrings associated with |
| 541 | keysyms. |
605 | keysyms. |
| 542 | |
606 | |
| 543 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
607 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
| 544 | |
608 | |
|
|
609 | URxvt.keysym.Prior: \033[5~ |
|
|
610 | URxvt.keysym.Next: \033[6~ |
| 545 | URxvt.keysym.Home: \033[1~ |
611 | URxvt.keysym.Home: \033[7~ |
| 546 | URxvt.keysym.End: \033[4~ |
612 | URxvt.keysym.End: \033[8~ |
| 547 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
| 548 | URxvt.keysym.C-slash: \033<C-/> |
|
|
| 549 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
| 550 | URxvt.keysym.C-grave: \033<C-`> |
|
|
| 551 | URxvt.keysym.C-comma: \033<C-,> |
|
|
| 552 | URxvt.keysym.C-period: \033<C-.> |
|
|
| 553 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
| 554 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
| 555 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
| 556 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
| 557 | URxvt.keysym.S-space: \033<S-Space> |
|
|
| 558 | URxvt.keysym.M-Up: \033<M-Up> |
613 | URxvt.keysym.Up: \033[A |
| 559 | URxvt.keysym.M-Down: \033<M-Down> |
614 | URxvt.keysym.Down: \033[B |
|
|
615 | URxvt.keysym.Right: \033[C |
| 560 | URxvt.keysym.M-Left: \033<M-Left> |
616 | URxvt.keysym.Left: \033[D |
| 561 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
| 562 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
| 563 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
| 564 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
|
|
| 565 | |
617 | |
| 566 | See some more examples in the documentation for the keysym resource. |
618 | See some more examples in the documentation for the keysym resource. |
| 567 | |
619 | |
| 568 | I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map |
620 | I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map |
| 569 | KP_Insert == Insert |
621 | KP_Insert == Insert |
| … | |
… | |
| 576 | Rather than have rxvt-unicode try to accommodate all the various |
628 | Rather than have rxvt-unicode try to accommodate all the various |
| 577 | possible keyboard mappings, it is better to use `xmodmap' to remap the |
629 | possible keyboard mappings, it is better to use `xmodmap' to remap the |
| 578 | keys as required for your particular machine. |
630 | keys as required for your particular machine. |
| 579 | |
631 | |
| 580 | Terminal Configuration |
632 | Terminal Configuration |
|
|
633 | Can I see a typical configuration? |
|
|
634 | The default configuration tries to be xterm-like, which I don't like |
|
|
635 | that much, but it's least surprise to regular users. |
|
|
636 | |
|
|
637 | As a rxvt or rxvt-unicode user, you are practically supposed to invest |
|
|
638 | time into customising your terminal. To get you started, here is the |
|
|
639 | author's .Xdefaults entries, with comments on what they do. It's |
|
|
640 | certainly not *typical*, but what's typical... |
|
|
641 | |
|
|
642 | URxvt.cutchars: "()*,<>[]{}|' |
|
|
643 | URxvt.print-pipe: cat >/some/path |
|
|
644 | |
|
|
645 | These are just for testing stuff. |
|
|
646 | |
|
|
647 | URxvt.imLocale: ja_JP.UTF-8 |
|
|
648 | URxvt.preeditType: OnTheSpot,None |
|
|
649 | |
|
|
650 | This tells rxvt-unicode to use a special locale when communicating with |
|
|
651 | the X Input Method, and also tells it to only use the OnTheSpot pre-edit |
|
|
652 | type, which requires the "xim-onthespot" perl extension but rewards me |
|
|
653 | with correct-looking fonts. |
|
|
654 | |
|
|
655 | URxvt.perl-lib: /root/lib/urxvt |
|
|
656 | URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard |
|
|
657 | URxvt.selection.pattern-0: ( at .*? line \\d+) |
|
|
658 | URxvt.selection.pattern-1: ^(/[^:]+):\ |
|
|
659 | URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/ |
|
|
660 | URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/ |
|
|
661 | |
|
|
662 | This is my perl configuration. The first two set the perl library |
|
|
663 | directory and also tells urxvt to use a large number of extensions. I |
|
|
664 | develop for myself mostly, so I actually use most of the extensions I |
|
|
665 | write. |
|
|
666 | |
|
|
667 | The selection stuff mainly makes the selection perl-error-message aware |
|
|
668 | and tells it to convert perl error messages into vi-commands to load the |
|
|
669 | relevant file and go to the error line number. |
|
|
670 | |
|
|
671 | URxvt.scrollstyle: plain |
|
|
672 | URxvt.secondaryScroll: true |
|
|
673 | |
|
|
674 | As the documentation says: plain is the preferred scrollbar for the |
|
|
675 | author. The "secondaryScroll" configures urxvt to scroll in full-screen |
|
|
676 | apps, like screen, so lines scrolled out of screen end up in urxvt's |
|
|
677 | scrollback buffer. |
|
|
678 | |
|
|
679 | URxvt.background: #000000 |
|
|
680 | URxvt.foreground: gray90 |
|
|
681 | URxvt.color7: gray90 |
|
|
682 | URxvt.colorBD: #ffffff |
|
|
683 | URxvt.cursorColor: #e0e080 |
|
|
684 | URxvt.throughColor: #8080f0 |
|
|
685 | URxvt.highlightColor: #f0f0f0 |
|
|
686 | |
|
|
687 | Some colours. Not sure which ones are being used or even non-defaults, |
|
|
688 | but these are in my .Xdefaults. Most notably, they set |
|
|
689 | foreground/background to light gray/black, and also make sure that the |
|
|
690 | colour 7 matches the default foreground colour. |
|
|
691 | |
|
|
692 | URxvt.underlineColor: yellow |
|
|
693 | |
|
|
694 | Another colour, makes underline lines look different. Sometimes hurts, |
|
|
695 | but is mostly a nice effect. |
|
|
696 | |
|
|
697 | URxvt.geometry: 154x36 |
|
|
698 | URxvt.loginShell: false |
|
|
699 | URxvt.meta: ignore |
|
|
700 | URxvt.utmpInhibit: true |
|
|
701 | |
|
|
702 | Uh, well, should be mostly self-explanatory. By specifying some defaults |
|
|
703 | manually, I can quickly switch them for testing. |
|
|
704 | |
|
|
705 | URxvt.saveLines: 8192 |
|
|
706 | |
|
|
707 | A large scrollback buffer is essential. Really. |
|
|
708 | |
|
|
709 | URxvt.mapAlert: true |
|
|
710 | |
|
|
711 | The only case I use it is for my IRC window, which I like to keep |
|
|
712 | iconified till people msg me (which beeps). |
|
|
713 | |
|
|
714 | URxvt.visualBell: true |
|
|
715 | |
|
|
716 | The audible bell is often annoying, especially when in a crowd. |
|
|
717 | |
|
|
718 | URxvt.insecure: true |
|
|
719 | |
|
|
720 | Please don't hack my mutt! Ooops... |
|
|
721 | |
|
|
722 | URxvt.pastableTabs: false |
|
|
723 | |
|
|
724 | I once thought this is a great idea. |
|
|
725 | |
|
|
726 | urxvt.font: 9x15bold,\ |
|
|
727 | -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\ |
|
|
728 | -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \ |
|
|
729 | [codeset=JISX0208]xft:Kochi Gothic, \ |
|
|
730 | xft:Bitstream Vera Sans Mono:autohint=true, \ |
|
|
731 | xft:Code2000:antialias=false |
|
|
732 | urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
|
|
733 | urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
734 | urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
735 | |
|
|
736 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
|
|
737 | overwhelmed. A special note: the "9x15bold" mentioned above is actually |
|
|
738 | the version from XFree-3.3, as XFree-4 replaced it by a totally |
|
|
739 | different font (different glyphs for ";" and many other harmless |
|
|
740 | characters), while the second font is actually the "9x15bold" from |
|
|
741 | XFree4/XOrg. The bold version has less chars than the medium version, so |
|
|
742 | I use it for rare characters, too. When editing sources with vim, I use |
|
|
743 | italic for comments and other stuff, which looks quite good with |
|
|
744 | Bitstream Vera anti-aliased. |
|
|
745 | |
|
|
746 | Terminus is a quite bad font (many very wrong glyphs), but for most of |
|
|
747 | my purposes, it works, and gives a different look, as my normal |
|
|
748 | (Non-bold) font is already bold, and I want to see a difference between |
|
|
749 | bold and normal fonts. |
|
|
750 | |
|
|
751 | Please note that I used the "urxvt" instance name and not the "URxvt" |
|
|
752 | class name. That is because I use different configs for different |
|
|
753 | purposes, for example, my IRC window is started with "-name IRC", and |
|
|
754 | uses these defaults: |
|
|
755 | |
|
|
756 | IRC*title: IRC |
|
|
757 | IRC*geometry: 87x12+535+542 |
|
|
758 | IRC*saveLines: 0 |
|
|
759 | IRC*mapAlert: true |
|
|
760 | IRC*font: suxuseuro |
|
|
761 | IRC*boldFont: suxuseuro |
|
|
762 | IRC*colorBD: white |
|
|
763 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
|
|
764 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
|
|
765 | |
|
|
766 | "Alt-Ctrl-1" and "Alt-Ctrl-2" switch between two different font sizes. |
|
|
767 | "suxuseuro" allows me to keep an eye (and actually read) stuff while |
|
|
768 | keeping a very small window. If somebody pastes something complicated |
|
|
769 | (e.g. japanese), I temporarily switch to a larger font. |
|
|
770 | |
|
|
771 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
|
|
772 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
|
|
773 | file for different hosts, for example, on my main desktop, I use: |
|
|
774 | |
|
|
775 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
|
|
776 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
|
|
777 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
|
|
778 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
|
|
779 | URxvt.keysym.C-M-p: perl:test |
|
|
780 | |
|
|
781 | The first for keysym definitions allow me to quickly bring some windows |
|
|
782 | in the layout I like most. Ion users might start laughing but will stop |
|
|
783 | immediately when I tell them that I use my own Fvwm2 module for much the |
|
|
784 | same effect as Ion provides, and I only very rarely use the above key |
|
|
785 | combinations :-> |
|
|
786 | |
| 581 | Why doesn't rxvt-unicode read my resources? |
787 | Why doesn't rxvt-unicode read my resources? |
| 582 | Well, why, indeed? It does, in a way very similar to other X |
788 | Well, why, indeed? It does, in a way very similar to other X |
| 583 | applications. Most importantly, this means that if you or your OS loads |
789 | applications. Most importantly, this means that if you or your OS loads |
| 584 | resources into the X display (the right way to do it), rxvt-unicode will |
790 | resources into the X display (the right way to do it), rxvt-unicode will |
| 585 | ignore any resource files in your home directory. It will only read |
791 | ignore any resource files in your home directory. It will only read |
| … | |
… | |
| 592 | Also consider the form resources have to use: |
798 | Also consider the form resources have to use: |
| 593 | |
799 | |
| 594 | URxvt.resource: value |
800 | URxvt.resource: value |
| 595 | |
801 | |
| 596 | If you want to use another form (there are lots of different ways of |
802 | If you want to use another form (there are lots of different ways of |
| 597 | specifying resources), make sure you understand wether and why it works. |
803 | specifying resources), make sure you understand whether and why it |
| 598 | If unsure, use the form above. |
804 | works. If unsure, use the form above. |
| 599 | |
805 | |
| 600 | When I log-in to another system it tells me about missing terminfo data? |
806 | When I log-in to another system it tells me about missing terminfo data? |
| 601 | The terminal description used by rxvt-unicode is not as widely available |
807 | The terminal description used by rxvt-unicode is not as widely available |
| 602 | as that for xterm, or even rxvt (for which the same problem often |
808 | as that for xterm, or even rxvt (for which the same problem often |
| 603 | arises). |
809 | arises). |
| 604 | |
810 | |
| 605 | The correct solution for this problem is to install the terminfo, this |
811 | The correct solution for this problem is to install the terminfo, this |
| 606 | can be done like this (with ncurses' infocmp): |
812 | can be done by simply installing rxvt-unicode on the remote system as |
|
|
813 | well (in case you have a nice package manager ready), or you can install |
|
|
814 | the terminfo database manually like this (with ncurses infocmp. works as |
|
|
815 | user and root): |
| 607 | |
816 | |
| 608 | REMOTE=remotesystem.domain |
817 | REMOTE=remotesystem.domain |
| 609 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
818 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
| 610 | |
819 | |
| 611 | ... or by installing rxvt-unicode normally on the remote system, |
820 | One some systems you might need to set $TERMINFO to the full path of |
|
|
821 | $HOME/.terminfo for this to work. |
| 612 | |
822 | |
| 613 | If you cannot or do not want to do this, then you can simply set |
823 | If you cannot or do not want to do this, then you can simply set |
| 614 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
824 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
| 615 | problems arising, which includes wrong keymapping, less and different |
825 | problems arising, which includes wrong keymapping, less and different |
| 616 | colours and some refresh errors in fullscreen applications. It's a nice |
826 | colours and some refresh errors in fullscreen applications. It's a nice |
| … | |
… | |
| 621 | resource to set it: |
831 | resource to set it: |
| 622 | |
832 | |
| 623 | URxvt.termName: rxvt |
833 | URxvt.termName: rxvt |
| 624 | |
834 | |
| 625 | If you don't plan to use rxvt (quite common...) you could also replace |
835 | If you don't plan to use rxvt (quite common...) you could also replace |
| 626 | the rxvt terminfo file with the rxvt-unicode one. |
836 | the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". |
|
|
837 | |
|
|
838 | nano fails with "Error opening terminal: rxvt-unicode" |
|
|
839 | This exceptionally confusing and useless error message is printed by |
|
|
840 | nano when it can't find the terminfo database. Nothing is wrong with |
|
|
841 | your terminal, read the previous answer for a solution. |
| 627 | |
842 | |
| 628 | "tic" outputs some error when compiling the terminfo entry. |
843 | "tic" outputs some error when compiling the terminfo entry. |
| 629 | Most likely it's the empty definition for "enacs=". Just replace it by |
844 | Most likely it's the empty definition for "enacs=". Just replace it by |
| 630 | "enacs=\E[0@" and try again. |
845 | "enacs=\E[0@" and try again. |
| 631 | |
846 | |
| … | |
… | |
| 633 | See next entry. |
848 | See next entry. |
| 634 | |
849 | |
| 635 | I need a termcap file entry. |
850 | I need a termcap file entry. |
| 636 | One reason you might want this is that some distributions or operating |
851 | One reason you might want this is that some distributions or operating |
| 637 | systems still compile some programs using the long-obsoleted termcap |
852 | systems still compile some programs using the long-obsoleted termcap |
| 638 | library (Fedora Core's bash is one example) and rely on a termcap entry |
853 | library (Fedora's bash is one example) and rely on a termcap entry for |
| 639 | for "rxvt-unicode". |
854 | "rxvt-unicode". |
| 640 | |
855 | |
| 641 | You could use rxvt's termcap entry with resonable results in many cases. |
856 | You could use rxvt's termcap entry with reasonable results in many |
| 642 | You can also create a termcap entry by using terminfo's infocmp program |
857 | cases. You can also create a termcap entry by using terminfo's infocmp |
| 643 | like this: |
858 | program like this: |
| 644 | |
859 | |
| 645 | infocmp -C rxvt-unicode |
860 | infocmp -C rxvt-unicode |
| 646 | |
861 | |
| 647 | Or you could use this termcap entry, generated by the command above: |
862 | Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap, |
| 648 | |
863 | generated by the command above. |
| 649 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
|
|
| 650 | :am:bw:eo:km:mi:ms:xn:xo:\ |
|
|
| 651 | :co#80:it#8:li#24:lm#0:\ |
|
|
| 652 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
|
|
| 653 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
|
|
| 654 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
|
|
| 655 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
|
|
| 656 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
|
|
| 657 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
|
|
| 658 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
|
|
| 659 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
|
|
| 660 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
|
|
| 661 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
|
|
| 662 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
|
|
| 663 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
|
|
| 664 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
|
|
| 665 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
|
|
| 666 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
|
|
| 667 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
|
|
| 668 | :vs=\E[?25h: |
|
|
| 669 | |
864 | |
| 670 | Why does "ls" no longer have coloured output? |
865 | Why does "ls" no longer have coloured output? |
| 671 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
866 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
| 672 | decide wether a terminal has colour, but uses it's own configuration |
867 | decide whether a terminal has colour, but uses its own configuration |
| 673 | file. Needless to say, "rxvt-unicode" is not in it's default file (among |
868 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
| 674 | with most other terminals supporting colour). Either add: |
869 | with most other terminals supporting colour). Either add: |
| 675 | |
870 | |
| 676 | TERM rxvt-unicode |
871 | TERM rxvt-unicode |
| 677 | |
872 | |
| 678 | to "/etc/DIR_COLORS" or simply add: |
873 | to "/etc/DIR_COLORS" or simply add: |
| … | |
… | |
| 687 | Why doesn't vim/emacs etc. make use of italic? |
882 | Why doesn't vim/emacs etc. make use of italic? |
| 688 | See next entry. |
883 | See next entry. |
| 689 | |
884 | |
| 690 | Why are the secondary screen-related options not working properly? |
885 | Why are the secondary screen-related options not working properly? |
| 691 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
886 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
| 692 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
887 | distributions break rxvt-unicode by setting "TERM" to "rxvt", which |
| 693 | setting "TERM" to "rxvt", which doesn't have these extra features. |
888 | doesn't have these extra features. Unfortunately, some of these |
| 694 | Unfortunately, some of these (most notably, again, Debian GNU/Linux) |
|
|
| 695 | furthermore fail to even install the "rxvt-unicode" terminfo file, so |
889 | furthermore fail to even install the "rxvt-unicode" terminfo file, so |
| 696 | you will need to install it on your own (See the question When I log-in |
890 | you will need to install it on your own (See the question When I log-in |
| 697 | to another system it tells me about missing terminfo data? on how to do |
891 | to another system it tells me about missing terminfo data? on how to do |
| 698 | this). |
892 | this). |
| 699 | |
893 | |
| … | |
… | |
| 705 | If you encounter strange problems like typing an accented character but |
899 | If you encounter strange problems like typing an accented character but |
| 706 | getting two unrelated other characters or similar, or if program output |
900 | getting two unrelated other characters or similar, or if program output |
| 707 | is subtly garbled, then you should check your locale settings. |
901 | is subtly garbled, then you should check your locale settings. |
| 708 | |
902 | |
| 709 | Rxvt-unicode must be started with the same "LC_CTYPE" setting as the |
903 | Rxvt-unicode must be started with the same "LC_CTYPE" setting as the |
| 710 | programs. Often rxvt-unicode is started in the "C" locale, while the |
904 | programs running in it. Often rxvt-unicode is started in the "C" locale, |
| 711 | login script running within the rxvt-unicode window changes the locale |
905 | while the login script running within the rxvt-unicode window changes |
| 712 | to something else, e.g. "en_GB.UTF-8". Needless to say, this is not |
906 | the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this |
| 713 | going to work. |
907 | is not going to work, and is the most common cause for problems. |
| 714 | |
908 | |
| 715 | The best thing is to fix your startup environment, as you will likely |
909 | The best thing is to fix your startup environment, as you will likely |
| 716 | run into other problems. If nothing works you can try this in your |
910 | run into other problems. If nothing works you can try this in your |
| 717 | .profile. |
911 | .profile. |
| 718 | |
912 | |
| 719 | printf '\e]701;%s\007' "$LC_CTYPE" |
913 | printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too |
| 720 | |
914 | |
| 721 | If this doesn't work, then maybe you use a "LC_CTYPE" specification not |
915 | If this doesn't work, then maybe you use a "LC_CTYPE" specification not |
| 722 | supported on your systems. Some systems have a "locale" command which |
916 | supported on your systems. Some systems have a "locale" command which |
| 723 | displays this (also, "perl -e0" can be used to check locale settings, as |
917 | displays this (also, "perl -e0" can be used to check locale settings, as |
| 724 | it will complain loudly if it cannot set the locale). If it displays |
918 | it will complain loudly if it cannot set the locale). If it displays |
| … | |
… | |
| 743 | The reasons is that there exists a perfectly fine mechanism for |
937 | The reasons is that there exists a perfectly fine mechanism for |
| 744 | selecting the encoding, doing I/O and (most important) communicating |
938 | selecting the encoding, doing I/O and (most important) communicating |
| 745 | this to all applications so everybody agrees on character properties |
939 | this to all applications so everybody agrees on character properties |
| 746 | such as width and code number. This mechanism is the *locale*. |
940 | such as width and code number. This mechanism is the *locale*. |
| 747 | Applications not using that info will have problems (for example, |
941 | Applications not using that info will have problems (for example, |
| 748 | "xterm" gets the width of characters wrong as it uses it's own, |
942 | "xterm" gets the width of characters wrong as it uses its own, |
| 749 | locale-independent table under all locales). |
943 | locale-independent table under all locales). |
| 750 | |
944 | |
| 751 | Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. All |
945 | Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. All |
| 752 | programs doing the same (that is, most) will automatically agree in the |
946 | programs doing the same (that is, most) will automatically agree in the |
| 753 | interpretation of characters. |
947 | interpretation of characters. |
| … | |
… | |
| 770 | |
964 | |
| 771 | Can I switch locales at runtime? |
965 | Can I switch locales at runtime? |
| 772 | Yes, using an escape sequence. Try something like this, which sets |
966 | Yes, using an escape sequence. Try something like this, which sets |
| 773 | rxvt-unicode's idea of "LC_CTYPE". |
967 | rxvt-unicode's idea of "LC_CTYPE". |
| 774 | |
968 | |
| 775 | printf '\e]701;%s\007' ja_JP.SJIS |
969 | printf '\33]701;%s\007' ja_JP.SJIS |
| 776 | |
970 | |
| 777 | See also the previous answer. |
971 | See also the previous answer. |
| 778 | |
972 | |
| 779 | Sometimes this capability is rather handy when you want to work in one |
973 | Sometimes this capability is rather handy when you want to work in one |
| 780 | locale (e.g. "de_DE.UTF-8") but some programs don't support it (e.g. |
974 | locale (e.g. "de_DE.UTF-8") but some programs don't support it (e.g. |
| 781 | UTF-8). For example, I use this script to start "xjdic", which first |
975 | UTF-8). For example, I use this script to start "xjdic", which first |
| 782 | switches to a locale supported by xjdic and back later: |
976 | switches to a locale supported by xjdic and back later: |
| 783 | |
977 | |
| 784 | printf '\e]701;%s\007' ja_JP.SJIS |
978 | printf '\33]701;%s\007' ja_JP.SJIS |
| 785 | xjdic -js |
979 | xjdic -js |
| 786 | printf '\e]701;%s\007' de_DE.UTF-8 |
980 | printf '\33]701;%s\007' de_DE.UTF-8 |
| 787 | |
981 | |
| 788 | You can also use xterm's "luit" program, which usually works fine, |
982 | You can also use xterm's "luit" program, which usually works fine, |
| 789 | except for some locales where character width differs between program- |
983 | except for some locales where character width differs between program- |
| 790 | and rxvt-unicode-locales. |
984 | and rxvt-unicode-locales. |
| 791 | |
985 | |
|
|
986 | I have problems getting my input method working. |
|
|
987 | Try a search engine, as this is slightly different for every input |
|
|
988 | method server. |
|
|
989 | |
|
|
990 | Here is a checklist: |
|
|
991 | |
|
|
992 | - Make sure your locale *and* the imLocale are supported on your OS. |
|
|
993 | Try "locale -a" or check the documentation for your OS. |
|
|
994 | |
|
|
995 | - Make sure your locale or imLocale matches a locale supported by your |
|
|
996 | XIM. |
|
|
997 | For example, kinput2 does not support UTF-8 locales, you should use |
|
|
998 | "ja_JP.EUC-JP" or equivalent. |
|
|
999 | |
|
|
1000 | - Make sure your XIM server is actually running. |
|
|
1001 | - Make sure the "XMODIFIERS" environment variable is set correctly when |
|
|
1002 | *starting* rxvt-unicode. |
|
|
1003 | When you want to use e.g. kinput2, it must be set to "@im=kinput2". |
|
|
1004 | For scim, use "@im=SCIM". You can see what input method servers are |
|
|
1005 | running with this command: |
|
|
1006 | |
|
|
1007 | xprop -root XIM_SERVERS |
|
|
1008 | |
| 792 | My input method wants <some encoding> but I want UTF-8, what can I do? |
1009 | My input method wants <some encoding> but I want UTF-8, what can I do? |
| 793 | You can specify separate locales for the input method and the rest of |
1010 | You can specify separate locales for the input method and the rest of |
| 794 | the terminal, using the resource "imlocale": |
1011 | the terminal, using the resource "imlocale": |
| 795 | |
1012 | |
| 796 | URxvt.imlocale: ja_JP.EUC-JP |
1013 | URxvt.imlocale: ja_JP.EUC-JP |
| 797 | |
1014 | |
| 798 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and still |
1015 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and still |
| 799 | use your input method. Please note, however, that you will not be able |
1016 | use your input method. Please note, however, that, depending on your |
| 800 | to input characters outside "EUC-JP" in a normal way then, as your input |
1017 | Xlib version, you may not be able to input characters outside "EUC-JP" |
| 801 | method limits you. |
1018 | in a normal way then, as your input method limits you. |
| 802 | |
1019 | |
| 803 | Rxvt-unicode crashes when the X Input Method changes or exits. |
1020 | Rxvt-unicode crashes when the X Input Method changes or exits. |
| 804 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
1021 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
| 805 | design. Applications can avoid some crashes at the expense of memory |
1022 | design. Applications can avoid some crashes at the expense of memory |
| 806 | leaks, and Input Methods can avoid some crashes by careful ordering at |
1023 | leaks, and Input Methods can avoid some crashes by careful ordering at |
| … | |
… | |
| 809 | cannot be completely avoided even if both sides cooperate. |
1026 | cannot be completely avoided even if both sides cooperate. |
| 810 | |
1027 | |
| 811 | So the only workaround is not to kill your Input Method Servers. |
1028 | So the only workaround is not to kill your Input Method Servers. |
| 812 | |
1029 | |
| 813 | Operating Systems / Package Maintaining |
1030 | Operating Systems / Package Maintaining |
| 814 | I am using Debian GNU/Linux and have a problem... |
|
|
| 815 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
| 816 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
| 817 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
| 818 | the original rxvt-unicode author please download and install the genuine |
|
|
| 819 | version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
|
|
| 820 | the problem. If you cannot, chances are that the problems are specific |
|
|
| 821 | to Debian GNU/Linux, in which case it should be reported via the Debian |
|
|
| 822 | Bug Tracking System (use "reportbug" to report the bug). |
|
|
| 823 | |
|
|
| 824 | For other problems that also affect the Debian package, you can and |
|
|
| 825 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
| 826 | bug in the Debian version and it serves as a reminder for other users |
|
|
| 827 | that might encounter the same issue. |
|
|
| 828 | |
|
|
| 829 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1031 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
| 830 | You should build one binary with the default options. configure now |
1032 | You should build one binary with the default options. configure now |
| 831 | enables most useful options, and the trend goes to making them |
1033 | enables most useful options, and the trend goes to making them |
| 832 | runtime-switchable, too, so there is usually no drawback to enbaling |
1034 | runtime-switchable, too, so there is usually no drawback to enabling |
| 833 | them, except higher disk and possibly memory usage. The perl interpreter |
1035 | them, except higher disk and possibly memory usage. The perl interpreter |
| 834 | should be enabled, as important functionality (menus, selection, likely |
1036 | should be enabled, as important functionality (menus, selection, likely |
| 835 | more in the future) depends on it. |
1037 | more in the future) depends on it. |
| 836 | |
1038 | |
| 837 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
1039 | You should not overwrite the "perl-ext-common" and "perl-ext" resources |
| 838 | system-wide (except maybe with "defaults"). This will result in useful |
1040 | system-wide (except maybe with "defaults"). This will result in useful |
| 839 | behaviour. If your distribution aims at low memory, add an empty |
1041 | behaviour. If your distribution aims at low memory, add an empty |
| 840 | "perl-ext-common" resource to the app-defaults file. This will keep the |
1042 | "perl-ext-common" resource to the app-defaults file. This will keep the |
| 841 | perl interpreter disabled until the user enables it. |
1043 | perl interpreter disabled until the user enables it. |
| 842 | |
1044 | |
| … | |
… | |
| 859 | This forking is done as the very first within main(), which is very |
1061 | This forking is done as the very first within main(), which is very |
| 860 | early and reduces possible bugs to initialisation code run before |
1062 | early and reduces possible bugs to initialisation code run before |
| 861 | main(), or things like the dynamic loader of your system, which should |
1063 | main(), or things like the dynamic loader of your system, which should |
| 862 | result in very little risk. |
1064 | result in very little risk. |
| 863 | |
1065 | |
| 864 | On Solaris 9, many line-drawing characters are too wide. |
|
|
| 865 | Seems to be a known bug, read |
|
|
| 866 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
|
|
| 867 | following ugly workaround to get non-double-wide-characters working: |
|
|
| 868 | |
|
|
| 869 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
|
|
| 870 | |
|
|
| 871 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
1066 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
| 872 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
1067 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
| 873 | your compile environment, or an implementation that implements it, |
1068 | your compile environment, or an implementation that implements it, |
| 874 | wether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
1069 | whether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
| 875 | wchar_t is represented as unicode. |
1070 | wchar_t is represented as unicode. |
| 876 | |
1071 | |
| 877 | As you might have guessed, FreeBSD does neither define this symobl nor |
1072 | As you might have guessed, FreeBSD does neither define this symbol nor |
| 878 | does it support it. Instead, it uses it's own internal representation of |
1073 | does it support it. Instead, it uses its own internal representation of |
| 879 | wchar_t. This is, of course, completely fine with respect to standards. |
1074 | wchar_t. This is, of course, completely fine with respect to standards. |
| 880 | |
1075 | |
| 881 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
1076 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
| 882 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
1077 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t). |
| 883 | |
1078 | |
| 884 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
1079 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
| 885 | in an OS, as using a locale-dependent (and non-standardized) |
1080 | in an OS, as using a locale-dependent (and non-standardized) |
| 886 | representation of wchar_t makes it impossible to convert between wchar_t |
1081 | representation of wchar_t makes it impossible to convert between wchar_t |
| 887 | (as used by X11 and your applications) and any other encoding without |
1082 | (as used by X11 and your applications) and any other encoding without |
| … | |
… | |
| 897 | |
1092 | |
| 898 | The rxvt-unicode author insists that the right way to fix this is in the |
1093 | The rxvt-unicode author insists that the right way to fix this is in the |
| 899 | system libraries once and for all, instead of forcing every app to carry |
1094 | system libraries once and for all, instead of forcing every app to carry |
| 900 | complete replacements for them :) |
1095 | complete replacements for them :) |
| 901 | |
1096 | |
| 902 | I use Solaris 9 and it doesn't compile/work/etc. |
|
|
| 903 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
|
|
| 904 | problems with "wcwidth" and a compile problem. |
|
|
| 905 | |
|
|
| 906 | How can I use rxvt-unicode under cygwin? |
1097 | How can I use rxvt-unicode under cygwin? |
| 907 | rxvt-unicode should compile and run out of the box on cygwin, using the |
1098 | rxvt-unicode should compile and run out of the box on cygwin, using the |
| 908 | X11 libraries that come with cygwin. libW11 emulation is no longer |
1099 | X11 libraries that come with cygwin. libW11 emulation is no longer |
| 909 | supported (and makes no sense, either, as it only supported a single |
1100 | supported (and makes no sense, either, as it only supported a single |
| 910 | font). I recommend starting the X-server in "-multiwindow" or |
1101 | font). I recommend starting the X-server in "-multiwindow" or |
| … | |
… | |
| 913 | |
1104 | |
| 914 | At the time of this writing, cygwin didn't seem to support any |
1105 | At the time of this writing, cygwin didn't seem to support any |
| 915 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
1106 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
| 916 | likely limited to 8-bit encodings. |
1107 | likely limited to 8-bit encodings. |
| 917 | |
1108 | |
|
|
1109 | Character widths are not correct. |
|
|
1110 | urxvt uses the system wcwidth function to know the information about the |
|
|
1111 | width of characters, so on systems with incorrect locale data you will |
|
|
1112 | likely get bad results. Two notorious examples are Solaris 9, where |
|
|
1113 | single-width characters like U+2514 are reported as double-width, and |
|
|
1114 | Darwin 8, where combining chars are reported having width 1. |
|
|
1115 | |
|
|
1116 | The solution is to upgrade your system or switch to a better one. A |
|
|
1117 | possibly working workaround is to use a wcwidth implementation like |
|
|
1118 | |
|
|
1119 | http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c |
|
|
1120 | |
