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.freenode.net", 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 :). |
… | |
… | |
8 | Does it support tabs, can I have a tabbed rxvt-unicode? |
8 | 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 |
9 | 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 |
10 | simple tabbed terminal. It is installed by default, so any of these |
11 | should give you tabs: |
11 | should give you tabs: |
12 | |
12 | |
13 | rxvt -pe tabbed |
13 | urxvt -pe tabbed |
14 | |
14 | |
15 | URxvt.perl-ext-common: default,tabbed |
15 | URxvt.perl-ext-common: default,tabbed |
16 | |
16 | |
17 | It will also work fine with tabbing functionality of many window |
17 | It will also work fine with tabbing functionality of many window |
18 | managers or similar tabbing programs, and its embedding-features allow |
18 | managers or similar tabbing programs, and its embedding-features allow |
… | |
… | |
21 | (murxvt) terminal as an example embedding application. |
21 | (murxvt) terminal as an example embedding application. |
22 | |
22 | |
23 | How do I know which rxvt-unicode version I'm using? |
23 | How do I know which rxvt-unicode version I'm using? |
24 | The version number is displayed with the usage (-h). Also the escape |
24 | The version number is displayed with the usage (-h). Also the escape |
25 | sequence "ESC [ 8 n" sets the window title to the version number. When |
25 | sequence "ESC [ 8 n" sets the window title to the version number. When |
26 | using the rxvtc client, the version displayed is that of the daemon. |
26 | using the urxvtc client, the version displayed is that of the daemon. |
27 | |
27 | |
28 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
28 | Rxvt-unicode uses gobs of memory, how can I reduce that? |
29 | Rxvt-unicode tries to obey the rule of not charging you for something |
29 | Rxvt-unicode tries to obey the rule of not charging you for something |
30 | you don't use. One thing you should try is to configure out all settings |
30 | you don't use. One thing you should try is to configure out all settings |
31 | that you don't need, for example, Xft support is a resource hog by |
31 | that you don't need, for example, Xft support is a resource hog by |
… | |
… | |
38 | bytes per screen cell. For a 160x?? window this amounts to almost a |
38 | bytes per screen cell. For a 160x?? window this amounts to almost a |
39 | kilobyte per line. A scrollback buffer of 10000 lines will then (if |
39 | kilobyte per line. A scrollback buffer of 10000 lines will then (if |
40 | full) use 10 Megabytes of memory. With "--enable-unicode3" it gets |
40 | full) use 10 Megabytes of memory. With "--enable-unicode3" it gets |
41 | worse, as rxvt-unicode then uses 8 bytes per screen cell. |
41 | worse, as rxvt-unicode then uses 8 bytes per screen cell. |
42 | |
42 | |
43 | How can I start rxvtd in a race-free way? |
43 | How can I start urxvtd in a race-free way? |
44 | Try "rxvtd -f -o", which tells rxvtd to open the display, create the |
44 | Try "urxvtd -f -o", which tells urxvtd to open the display, create the |
45 | listening socket and then fork. |
45 | listening socket and then fork. |
46 | |
46 | |
|
|
47 | How can I start urxvtd automatically when I run URXVT_NAME@@c? |
|
|
48 | If you want to start urxvtd automatically whenever you run urxvtc and |
|
|
49 | the daemon isn't running yet, use this script: |
|
|
50 | |
|
|
51 | #!/bin/sh |
|
|
52 | urxvtc "$@" |
|
|
53 | if [ $? -eq 2 ]; then |
|
|
54 | urxvtd -q -o -f |
|
|
55 | urxvtc "$@" |
|
|
56 | fi |
|
|
57 | |
|
|
58 | This tries to create a new terminal, and if fails with exit status 2, |
|
|
59 | meaning it couldn't connect to the daemon, it will start the daemon and |
|
|
60 | re-run the command. Subsequent invocations of the script will re-use the |
|
|
61 | existing daemon. |
|
|
62 | |
47 | How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
63 | How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
48 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
64 | The original rxvt and rxvt-unicode always export the variable |
49 | check and see if that is set. Note that several programs, JED, slrn, |
65 | "COLORTERM", so you can check and see if that is set. Note that several |
50 | Midnight Commander automatically check this variable to decide whether |
66 | programs, JED, slrn, Midnight Commander automatically check this |
51 | or not to use color. |
67 | variable to decide whether or not to use color. |
52 | |
68 | |
53 | How do I set the correct, full IP address for the DISPLAY variable? |
69 | 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 |
70 | 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 |
71 | 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 |
72 | snippets to correctly set the display. If your version of rxvt-unicode |
… | |
… | |
90 | |
106 | |
91 | text data bss drs rss filename |
107 | text data bss drs rss filename |
92 | 98398 1664 24 15695 1824 rxvt --disable-everything |
108 | 98398 1664 24 15695 1824 rxvt --disable-everything |
93 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
109 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
94 | |
110 | |
95 | When you "--enable-everything" (which _is_ unfair, as this involves xft |
111 | 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 |
112 | and full locale/XIM support which are quite bloaty inside libX11 and my |
97 | libc), the two diverge, but not unreasnobaly so. |
113 | libc), the two diverge, but not unreasonably so. |
98 | |
114 | |
99 | text data bss drs rss filename |
115 | text data bss drs rss filename |
100 | 163431 2152 24 20123 2060 rxvt --enable-everything |
116 | 163431 2152 24 20123 2060 rxvt --enable-everything |
101 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
117 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
102 | |
118 | |
… | |
… | |
146 | |
162 | |
147 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
163 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
148 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
164 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
149 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
165 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
150 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
166 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
151 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
167 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
152 | |
168 | |
153 | No large bloated libraries (of course, none were linked in statically), |
169 | No large bloated libraries (of course, none were linked in statically), |
154 | except maybe libX11 :) |
170 | except maybe libX11 :) |
155 | |
171 | |
156 | Rendering, Font & Look and Feel Issues |
172 | Rendering, Font & Look and Feel Issues |
… | |
… | |
164 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
180 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
165 | |
181 | |
166 | 1. Use inheritPixmap: |
182 | 1. Use inheritPixmap: |
167 | |
183 | |
168 | Esetroot wallpaper.jpg |
184 | Esetroot wallpaper.jpg |
169 | rxvt -ip -tint red -sh 40 |
185 | urxvt -ip -tint red -sh 40 |
170 | |
186 | |
171 | That works. If you think it doesn't, you lack transparency and tinting |
187 | That works. If you think it doesn't, you lack transparency and tinting |
172 | support, or you are unable to read. |
188 | support, or you are unable to read. |
173 | |
189 | |
174 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
190 | 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 |
191 | to use effects other than tinting and shading: Just shade/tint/whatever |
176 | your picture with gimp or any other tool: |
192 | your picture with gimp or any other tool: |
177 | |
193 | |
178 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
194 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
179 | rxvt -pixmap background.xpm -pe automove-background |
195 | urxvt -pixmap background.xpm -pe automove-background |
180 | |
196 | |
181 | That works. If you think it doesn't, you lack XPM and Perl support, or |
197 | That works. If you think it doesn't, you lack XPM and Perl support, or |
182 | you are unable to read. |
198 | you are unable to read. |
183 | |
199 | |
184 | 3. Use an ARGB visual: |
200 | 3. Use an ARGB visual: |
185 | |
201 | |
186 | rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
202 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
187 | |
203 | |
188 | This requires XFT support, and the support of your X-server. If that |
204 | 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 |
205 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
190 | there yet, no matter what they claim. Rxvt-Unicode contains the |
206 | there yet, no matter what they claim. Rxvt-Unicode contains the |
191 | neccessary bugfixes and workarounds for Xft and Xlib to make it work, |
207 | necessary bugfixes and workarounds for Xft and Xlib to make it work, but |
192 | but that doesn't mean that your WM has the required kludges in place. |
208 | that doesn't mean that your WM has the required kludges in place. |
193 | |
209 | |
194 | 4. Use xcompmgr and let it do the job: |
210 | 4. Use xcompmgr and let it do the job: |
195 | |
211 | |
196 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
212 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
197 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
213 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
198 | |
214 | |
199 | Then click on a window you want to make transparent. Replace 0xc0000000 |
215 | 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 |
216 | 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. |
217 | 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 | |
218 | |
227 | Why does rxvt-unicode sometimes leave pixel droppings? |
219 | Why does rxvt-unicode sometimes leave pixel droppings? |
228 | Most fonts were not designed for terminal use, which means that |
220 | 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 |
221 | 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 |
222 | use might contain some characters that are simply too wide. Rxvt-unicode |
… | |
… | |
236 | however: Xft fonts often draw glyphs larger than their acclaimed |
228 | however: Xft fonts often draw glyphs larger than their acclaimed |
237 | bounding box, and rxvt-unicode has no way of detecting this (the correct |
229 | 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 |
230 | way is to ask for the character bounding box, which unfortunately is |
239 | wrong in these cases). |
231 | wrong in these cases). |
240 | |
232 | |
241 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
233 | 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 |
234 | 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 |
235 | 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. |
236 | work, you might be forced to use a different font. |
245 | |
237 | |
246 | All of this is not a problem when using X11 core fonts, as their |
238 | All of this is not a problem when using X11 core fonts, as their |
… | |
… | |
268 | |
260 | |
269 | Can I switch the fonts at runtime? |
261 | Can I switch the fonts at runtime? |
270 | Yes, using an escape sequence. Try something like this, which has the |
262 | Yes, using an escape sequence. Try something like this, which has the |
271 | same effect as using the "-fn" switch, and takes effect immediately: |
263 | same effect as using the "-fn" switch, and takes effect immediately: |
272 | |
264 | |
273 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
265 | printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic" |
274 | |
266 | |
275 | This is useful if you e.g. work primarily with japanese (and prefer a |
267 | 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 |
268 | japanese font), but you have to switch to chinese temporarily, where |
277 | japanese fonts would only be in your way. |
269 | japanese fonts would only be in your way. |
278 | |
270 | |
279 | You can think of this as a kind of manual ISO-2022 switching. |
271 | You can think of this as a kind of manual ISO-2022 switching. |
280 | |
272 | |
281 | Why do italic characters look as if clipped? |
273 | Why do italic characters look as if clipped? |
282 | Many fonts have difficulties with italic characters and hinting. For |
274 | Many fonts have difficulties with italic characters and hinting. For |
283 | example, the otherwise very nicely hinted font "xft:Bitstream Vera Sans |
275 | 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 |
276 | Mono" completely fails in its italic face. A workaround might be to |
285 | enable freetype autohinting, i.e. like this: |
277 | enable freetype autohinting, i.e. like this: |
286 | |
278 | |
287 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
279 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
288 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
280 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
289 | |
281 | |
… | |
… | |
293 | antialiasing (by appending ":antialias=false"), which saves lots of |
285 | antialiasing (by appending ":antialias=false"), which saves lots of |
294 | memory and also speeds up rendering considerably. |
286 | memory and also speeds up rendering considerably. |
295 | |
287 | |
296 | Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
288 | 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 |
289 | 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 |
290 | 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 |
291 | 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 |
292 | antialiasing disabled for most of them, because the author thinks they |
301 | look best that way. |
293 | look best that way. |
302 | |
294 | |
303 | If you want antialiasing, you have to specify the fonts manually. |
295 | If you want antialiasing, you have to specify the fonts manually. |
304 | |
296 | |
… | |
… | |
340 | URxvt.color12: #0000FF |
332 | URxvt.color12: #0000FF |
341 | URxvt.color13: #FF00FF |
333 | URxvt.color13: #FF00FF |
342 | URxvt.color14: #00FFFF |
334 | URxvt.color14: #00FFFF |
343 | URxvt.color15: #FFFFFF |
335 | URxvt.color15: #FFFFFF |
344 | |
336 | |
345 | And here is a more complete set of non-standard colors described (not by |
337 | And here is a more complete set of non-standard colors. |
346 | me) as "pretty girly". |
|
|
347 | |
338 | |
348 | URxvt.cursorColor: #dc74d1 |
339 | URxvt.cursorColor: #dc74d1 |
349 | URxvt.pointerColor: #dc74d1 |
340 | URxvt.pointerColor: #dc74d1 |
350 | URxvt.background: #0e0e0e |
341 | URxvt.background: #0e0e0e |
351 | URxvt.foreground: #4ad5e1 |
342 | URxvt.foreground: #4ad5e1 |
… | |
… | |
362 | URxvt.color6: #73f7ff |
353 | URxvt.color6: #73f7ff |
363 | URxvt.color14: #73f7ff |
354 | URxvt.color14: #73f7ff |
364 | URxvt.color7: #e1dddd |
355 | URxvt.color7: #e1dddd |
365 | URxvt.color15: #e1dddd |
356 | URxvt.color15: #e1dddd |
366 | |
357 | |
|
|
358 | They have been described (not by me) as "pretty girly". |
|
|
359 | |
367 | Why do some characters look so much different than others? |
360 | Why do some characters look so much different than others? |
368 | See next entry. |
361 | See next entry. |
369 | |
362 | |
370 | How does rxvt-unicode choose fonts? |
363 | How does rxvt-unicode choose fonts? |
371 | Most fonts do not contain the full range of Unicode, which is fine. |
364 | Most fonts do not contain the full range of Unicode, which is fine. |
… | |
… | |
381 | the font that the characters it claims to contain indeed look correct. |
374 | the font that the characters it claims to contain indeed look correct. |
382 | |
375 | |
383 | In that case, select a font of your taste and add it to the font list, |
376 | In that case, select a font of your taste and add it to the font list, |
384 | e.g.: |
377 | e.g.: |
385 | |
378 | |
386 | rxvt -fn basefont,font2,font3... |
379 | urxvt -fn basefont,font2,font3... |
387 | |
380 | |
388 | When rxvt-unicode sees a character, it will first look at the base font. |
381 | 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 |
382 | 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 |
383 | 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. |
384 | search and use less resources within rxvt-unicode and the X-server. |
392 | |
385 | |
393 | The only limitation is that none of the fonts may be larger than the |
386 | 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, |
387 | base font, as the base font defines the terminal character cell size, |
395 | which must be the same due to the way terminals work. |
388 | which must be the same due to the way terminals work. |
396 | |
389 | |
|
|
390 | Why do some chinese characters look so different than others? |
|
|
391 | This is because there is a difference between script and language -- |
|
|
392 | rxvt-unicode does not know which language the text that is output is, as |
|
|
393 | it only knows the unicode character codes. If rxvt-unicode first sees a |
|
|
394 | japanese/chinese character, it might choose a japanese font for display. |
|
|
395 | Subsequent japanese characters will use that font. Now, many chinese |
|
|
396 | characters aren't represented in japanese fonts, so when the first |
|
|
397 | non-japanese character comes up, rxvt-unicode will look for a chinese |
|
|
398 | font -- unfortunately at this point, it will still use the japanese font |
|
|
399 | for chinese characters that are also in the japanese font. |
|
|
400 | |
|
|
401 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
402 | list (see the previous question). The key is to view the font list as a |
|
|
403 | preference list: If you expect more japanese, list a japanese font |
|
|
404 | first. If you expect more chinese, put a chinese font first. |
|
|
405 | |
|
|
406 | In the future it might be possible to switch language preferences at |
|
|
407 | runtime (the internal data structure has no problem with using different |
|
|
408 | fonts for the same character at the same time, but no interface for this |
|
|
409 | has been designed yet). |
|
|
410 | |
|
|
411 | Until then, you might get away with switching fonts at runtime (see "Can |
|
|
412 | I switch the fonts at runtime?" later in this document). |
|
|
413 | |
397 | Keyboard, Mouse & User Interaction |
414 | Keyboard, Mouse & User Interaction |
398 | The new selection selects pieces that are too big, how can I select single words? |
415 | 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 |
416 | If you want to select e.g. alphanumeric words, you can use the following |
400 | setting: |
417 | setting: |
401 | |
418 | |
… | |
… | |
417 | perl-ext-common resource to the empty string, which also keeps |
434 | perl-ext-common resource to the empty string, which also keeps |
418 | rxvt-unicode from initialising perl, saving memory. |
435 | rxvt-unicode from initialising perl, saving memory. |
419 | |
436 | |
420 | If you only want to disable specific features, you first have to |
437 | If you only want to disable specific features, you first have to |
421 | identify which perl extension is responsible. For this, read the section |
438 | identify which perl extension is responsible. For this, read the section |
422 | PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For example, to |
439 | PREPACKAGED EXTENSIONS in the urxvtperl(3) manpage. For example, to |
423 | disable the selection-popup and option-popup, specify this |
440 | disable the selection-popup and option-popup, specify this |
424 | perl-ext-common resource: |
441 | perl-ext-common resource: |
425 | |
442 | |
426 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
443 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
427 | |
444 | |
… | |
… | |
440 | circumstances, it will move your cursor around when you click into the |
457 | 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, |
458 | 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 |
459 | 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. |
460 | some cases during rlogin sessions, it fails to detect this properly. |
444 | |
461 | |
445 | You can permamently switch this feature off by disabling the "readline" |
462 | You can permanently switch this feature off by disabling the "readline" |
446 | extension: |
463 | extension: |
447 | |
464 | |
448 | URxvt.perl-ext-common: default,-readline |
465 | URxvt.perl-ext-common: default,-readline |
449 | |
466 | |
450 | My numerical keypad acts weird and generates differing output? |
467 | My numerical keypad acts weird and generates differing output? |
451 | Some Debian GNUL/Linux users seem to have this problem, although no |
468 | Some Debian GNUL/Linux users seem to have this problem, although no |
452 | specific details were reported so far. It is possible that this is |
469 | 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 |
470 | 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 |
471 | how this can happen are unknown, as "TERM=rxvt" should offer a |
455 | compatible keymap. See the answer to the previous question, and please |
472 | compatible keymap. See the answer to the previous question, and please |
456 | report if that helped. |
473 | report if that helped. |
457 | |
474 | |
458 | My Compose (Multi_key) key is no longer working. |
475 | My Compose (Multi_key) key is no longer working. |
… | |
… | |
479 | that tcsh may use mouse reporting unless it otherwise specified. A quick |
496 | that tcsh may use mouse reporting unless it otherwise specified. A quick |
480 | check is to see if cut/paste works when the Alt or Shift keys are |
497 | check is to see if cut/paste works when the Alt or Shift keys are |
481 | depressed. |
498 | depressed. |
482 | |
499 | |
483 | What's with the strange Backspace/Delete key behaviour? |
500 | What's with the strange Backspace/Delete key behaviour? |
484 | Assuming that the physical Backspace key corresponds to the BackSpace |
501 | Assuming that the physical Backspace key corresponds to the Backspace |
485 | keysym (not likely for Linux ... see the following question) there are |
502 | keysym (not likely for Linux ... see the following question) there are |
486 | two standard values that can be used for Backspace: "^H" and "^?". |
503 | two standard values that can be used for Backspace: "^H" and "^?". |
487 | |
504 | |
488 | Historically, either value is correct, but rxvt-unicode adopts the |
505 | Historically, either value is correct, but rxvt-unicode adopts the |
489 | debian policy of using "^?" when unsure, because it's the one only only |
506 | debian policy of using "^?" when unsure, because it's the one only only |
… | |
… | |
498 | |
515 | |
499 | For starting a new rxvt-unicode: |
516 | For starting a new rxvt-unicode: |
500 | |
517 | |
501 | # use Backspace = ^H |
518 | # use Backspace = ^H |
502 | $ stty erase ^H |
519 | $ stty erase ^H |
503 | $ rxvt |
520 | $ urxvt |
504 | |
521 | |
505 | # use Backspace = ^? |
522 | # use Backspace = ^? |
506 | $ stty erase ^? |
523 | $ stty erase ^? |
507 | $ rxvt |
524 | $ urxvt |
508 | |
525 | |
509 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
526 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
510 | |
527 | |
511 | For an existing rxvt-unicode: |
528 | For an existing rxvt-unicode: |
512 | |
529 | |
… | |
… | |
538 | There are some compile-time selections available via configure. Unless |
555 | There are some compile-time selections available via configure. Unless |
539 | you have run "configure" with the "--disable-resources" option you can |
556 | you have run "configure" with the "--disable-resources" option you can |
540 | use the `keysym' resource to alter the keystrings associated with |
557 | use the `keysym' resource to alter the keystrings associated with |
541 | keysyms. |
558 | keysyms. |
542 | |
559 | |
543 | Here's an example for a URxvt session started using "rxvt -name URxvt" |
560 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
544 | |
561 | |
545 | URxvt.keysym.Home: \033[1~ |
562 | URxvt.keysym.Home: \033[1~ |
546 | URxvt.keysym.End: \033[4~ |
563 | URxvt.keysym.End: \033[4~ |
547 | URxvt.keysym.C-apostrophe: \033<C-'> |
564 | URxvt.keysym.C-apostrophe: \033<C-'> |
548 | URxvt.keysym.C-slash: \033<C-/> |
565 | URxvt.keysym.C-slash: \033<C-/> |
… | |
… | |
576 | Rather than have rxvt-unicode try to accommodate all the various |
593 | Rather than have rxvt-unicode try to accommodate all the various |
577 | possible keyboard mappings, it is better to use `xmodmap' to remap the |
594 | possible keyboard mappings, it is better to use `xmodmap' to remap the |
578 | keys as required for your particular machine. |
595 | keys as required for your particular machine. |
579 | |
596 | |
580 | Terminal Configuration |
597 | Terminal Configuration |
|
|
598 | Can I see a typical configuration? |
|
|
599 | The default configuration tries to be xterm-like, which I don't like |
|
|
600 | that much, but it's least surprise to regular users. |
|
|
601 | |
|
|
602 | As a rxvt or rxvt-unicode user, you are practically supposed to invest |
|
|
603 | time into customising your terminal. To get you started, here is the |
|
|
604 | author's .Xdefaults entries, with comments on what they do. It's |
|
|
605 | certainly not *typical*, but what's typical... |
|
|
606 | |
|
|
607 | URxvt.cutchars: "()*,<>[]{}|' |
|
|
608 | URxvt.print-pipe: cat >/tmp/xxx |
|
|
609 | |
|
|
610 | These are just for testing stuff. |
|
|
611 | |
|
|
612 | URxvt.imLocale: ja_JP.UTF-8 |
|
|
613 | URxvt.preeditType: OnTheSpot,None |
|
|
614 | |
|
|
615 | This tells rxvt-unicode to use a special locale when communicating with |
|
|
616 | the X Input Method, and also tells it to only use the OnTheSpot pre-edit |
|
|
617 | type, which requires the "xim-onthespot" perl extension but rewards me |
|
|
618 | with correct-looking fonts. |
|
|
619 | |
|
|
620 | URxvt.perl-lib: /root/lib/urxvt |
|
|
621 | URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard |
|
|
622 | URxvt.selection.pattern-0: ( at .*? line \\d+) |
|
|
623 | URxvt.selection.pattern-1: ^(/[^:]+):\ |
|
|
624 | URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/ |
|
|
625 | URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/ |
|
|
626 | |
|
|
627 | This is my perl configuration. The first two set the perl library |
|
|
628 | directory and also tells urxvt to use a large number of extensions. I |
|
|
629 | develop for myself mostly, so I actually use most of the extensions I |
|
|
630 | write. |
|
|
631 | |
|
|
632 | The selection stuff mainly makes the selection perl-error-message aware |
|
|
633 | and tells it to convert perl error messages into vi-commands to load the |
|
|
634 | relevant file and go tot he error line number. |
|
|
635 | |
|
|
636 | URxvt.scrollstyle: plain |
|
|
637 | URxvt.secondaryScroll: true |
|
|
638 | |
|
|
639 | As the documentation says: plain is the preferred scrollbar for the |
|
|
640 | author. The "secondaryScroll" configures urxvt to scroll in full-screen |
|
|
641 | apps, like screen, so lines scrolled out of screen end up in urxvt's |
|
|
642 | scrollback buffer. |
|
|
643 | |
|
|
644 | URxvt.background: #000000 |
|
|
645 | URxvt.foreground: gray90 |
|
|
646 | URxvt.color7: gray90 |
|
|
647 | URxvt.colorBD: #ffffff |
|
|
648 | URxvt.cursorColor: #e0e080 |
|
|
649 | URxvt.throughColor: #8080f0 |
|
|
650 | URxvt.highlightColor: #f0f0f0 |
|
|
651 | |
|
|
652 | Some colours. Not sure which ones are being used or even non-defaults, |
|
|
653 | but these are in my .Xdefaults. Most notably, they set |
|
|
654 | foreground/background to light gray/black, and also make sure that the |
|
|
655 | colour 7 matches the default foreground colour. |
|
|
656 | |
|
|
657 | URxvt.underlineColor: yellow |
|
|
658 | |
|
|
659 | Another colour, makes underline lines look different. Sometimes hurts, |
|
|
660 | but is mostly a nice effect. |
|
|
661 | |
|
|
662 | URxvt.geometry: 154x36 |
|
|
663 | URxvt.loginShell: false |
|
|
664 | URxvt.meta: ignore |
|
|
665 | URxvt.utmpInhibit: true |
|
|
666 | |
|
|
667 | Uh, well, should be mostly self-explanatory. By specifying some defaults |
|
|
668 | manually, I can quickly switch them for testing. |
|
|
669 | |
|
|
670 | URxvt.saveLines: 8192 |
|
|
671 | |
|
|
672 | A large scrollback buffer is essential. Really. |
|
|
673 | |
|
|
674 | URxvt.mapAlert: true |
|
|
675 | |
|
|
676 | The only case I use it is for my IRC window, which I like to keep |
|
|
677 | iconified till people msg me (which beeps). |
|
|
678 | |
|
|
679 | URxvt.visualBell: true |
|
|
680 | |
|
|
681 | The audible bell is often annoying, especially when in a crowd. |
|
|
682 | |
|
|
683 | URxvt.insecure: true |
|
|
684 | |
|
|
685 | Please don't hack my mutt! Ooops... |
|
|
686 | |
|
|
687 | URxvt.pastableTabs: false |
|
|
688 | |
|
|
689 | I once thought this is a great idea. |
|
|
690 | |
|
|
691 | urxvt.font: 9x15bold,\ |
|
|
692 | -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\ |
|
|
693 | -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \ |
|
|
694 | [codeset=JISX0208]xft:Kochi Gothic, \ |
|
|
695 | xft:Bitstream Vera Sans Mono:autohint=true, \ |
|
|
696 | xft:Code2000:antialias=false |
|
|
697 | urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
|
|
698 | urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
699 | urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
700 | |
|
|
701 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
|
|
702 | overwhelmed. A special note: the "9x15bold" mentioned above is actually |
|
|
703 | the version from XFree-3.3, as XFree-4 replaced it by a totally |
|
|
704 | different font (different glyphs for ";" and many other harmless |
|
|
705 | characters), while the second font is actually the "9x15bold" from |
|
|
706 | XFree4/XOrg. The bold version has less chars than the medium version, so |
|
|
707 | I use it for rare characters, too. When editing sources with vim, I use |
|
|
708 | italic for comments and other stuff, which looks quite good with |
|
|
709 | Bitstream Vera anti-aliased. |
|
|
710 | |
|
|
711 | Terminus is a quite bad font (many very wrong glyphs), but for most of |
|
|
712 | my purposes, it works, and gives a different look, as my normal |
|
|
713 | (Non-bold) font is already bold, and I want to see a difference between |
|
|
714 | bold and normal fonts. |
|
|
715 | |
|
|
716 | Please note that I used the "urxvt" instance name and not the "URxvt" |
|
|
717 | class name. Thats because I use different configs for different |
|
|
718 | purposes, for example, my IRC window is started with "-name IRC", and |
|
|
719 | uses these defaults: |
|
|
720 | |
|
|
721 | IRC*title: IRC |
|
|
722 | IRC*geometry: 87x12+535+542 |
|
|
723 | IRC*saveLines: 0 |
|
|
724 | IRC*mapAlert: true |
|
|
725 | IRC*font: suxuseuro |
|
|
726 | IRC*boldFont: suxuseuro |
|
|
727 | IRC*colorBD: white |
|
|
728 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
|
|
729 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
|
|
730 | |
|
|
731 | "Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes. |
|
|
732 | "suxuseuro" allows me to keep an eye (and actually read) stuff while |
|
|
733 | keeping a very small window. If somebody pastes something complicated |
|
|
734 | (e.g. japanese), I temporarily switch to a larger font. |
|
|
735 | |
|
|
736 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
|
|
737 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
|
|
738 | file for different hosts, for example, on ym main desktop, I use: |
|
|
739 | |
|
|
740 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
|
|
741 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
|
|
742 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
|
|
743 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
|
|
744 | URxvt.keysym.C-M-p: perl:test |
|
|
745 | |
|
|
746 | The first for keysym definitions allow me to quickly bring some windows |
|
|
747 | in the layout I like most. Ion users might start laughing but will stop |
|
|
748 | immediately when I tell them that I use my own Fvwm2 module for much the |
|
|
749 | same effect as Ion provides, and I only very rarely use the above key |
|
|
750 | combinations :-> |
|
|
751 | |
581 | Why doesn't rxvt-unicode read my resources? |
752 | Why doesn't rxvt-unicode read my resources? |
582 | Well, why, indeed? It does, in a way very similar to other X |
753 | 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 |
754 | 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 |
755 | 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 |
756 | ignore any resource files in your home directory. It will only read |
… | |
… | |
592 | Also consider the form resources have to use: |
763 | Also consider the form resources have to use: |
593 | |
764 | |
594 | URxvt.resource: value |
765 | URxvt.resource: value |
595 | |
766 | |
596 | If you want to use another form (there are lots of different ways of |
767 | 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. |
768 | specifying resources), make sure you understand whether and why it |
598 | If unsure, use the form above. |
769 | works. If unsure, use the form above. |
599 | |
770 | |
600 | When I log-in to another system it tells me about missing terminfo data? |
771 | 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 |
772 | 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 |
773 | as that for xterm, or even rxvt (for which the same problem often |
603 | arises). |
774 | arises). |
… | |
… | |
621 | resource to set it: |
792 | resource to set it: |
622 | |
793 | |
623 | URxvt.termName: rxvt |
794 | URxvt.termName: rxvt |
624 | |
795 | |
625 | If you don't plan to use rxvt (quite common...) you could also replace |
796 | If you don't plan to use rxvt (quite common...) you could also replace |
626 | the rxvt terminfo file with the rxvt-unicode one. |
797 | the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". |
627 | |
798 | |
628 | "tic" outputs some error when compiling the terminfo entry. |
799 | "tic" outputs some error when compiling the terminfo entry. |
629 | Most likely it's the empty definition for "enacs=". Just replace it by |
800 | Most likely it's the empty definition for "enacs=". Just replace it by |
630 | "enacs=\E[0@" and try again. |
801 | "enacs=\E[0@" and try again. |
631 | |
802 | |
632 | "bash"'s readline does not work correctly under rxvt. |
803 | "bash"'s readline does not work correctly under urxvt. |
633 | See next entry. |
804 | See next entry. |
634 | |
805 | |
635 | I need a termcap file entry. |
806 | I need a termcap file entry. |
636 | One reason you might want this is that some distributions or operating |
807 | One reason you might want this is that some distributions or operating |
637 | systems still compile some programs using the long-obsoleted termcap |
808 | 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 |
809 | library (Fedora Core's bash is one example) and rely on a termcap entry |
639 | for "rxvt-unicode". |
810 | for "rxvt-unicode". |
640 | |
811 | |
641 | You could use rxvt's termcap entry with resonable results in many cases. |
812 | 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 |
813 | cases. You can also create a termcap entry by using terminfo's infocmp |
643 | like this: |
814 | program like this: |
644 | |
815 | |
645 | infocmp -C rxvt-unicode |
816 | infocmp -C rxvt-unicode |
646 | |
817 | |
647 | Or you could use this termcap entry, generated by the command above: |
818 | Or you could use this termcap entry, generated by the command above: |
648 | |
819 | |
… | |
… | |
667 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
838 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
668 | :vs=\E[?25h: |
839 | :vs=\E[?25h: |
669 | |
840 | |
670 | Why does "ls" no longer have coloured output? |
841 | Why does "ls" no longer have coloured output? |
671 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
842 | 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 |
843 | 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 |
844 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
674 | with most other terminals supporting colour). Either add: |
845 | with most other terminals supporting colour). Either add: |
675 | |
846 | |
676 | TERM rxvt-unicode |
847 | TERM rxvt-unicode |
677 | |
848 | |
678 | to "/etc/DIR_COLORS" or simply add: |
849 | to "/etc/DIR_COLORS" or simply add: |
… | |
… | |
714 | |
885 | |
715 | The best thing is to fix your startup environment, as you will likely |
886 | 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 |
887 | run into other problems. If nothing works you can try this in your |
717 | .profile. |
888 | .profile. |
718 | |
889 | |
719 | printf '\e]701;%s\007' "$LC_CTYPE" |
890 | printf '\33]701;%s\007' "$LC_CTYPE" |
720 | |
891 | |
721 | If this doesn't work, then maybe you use a "LC_CTYPE" specification not |
892 | 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 |
893 | 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 |
894 | 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 |
895 | 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 |
914 | The reasons is that there exists a perfectly fine mechanism for |
744 | selecting the encoding, doing I/O and (most important) communicating |
915 | selecting the encoding, doing I/O and (most important) communicating |
745 | this to all applications so everybody agrees on character properties |
916 | this to all applications so everybody agrees on character properties |
746 | such as width and code number. This mechanism is the *locale*. |
917 | such as width and code number. This mechanism is the *locale*. |
747 | Applications not using that info will have problems (for example, |
918 | Applications not using that info will have problems (for example, |
748 | "xterm" gets the width of characters wrong as it uses it's own, |
919 | "xterm" gets the width of characters wrong as it uses its own, |
749 | locale-independent table under all locales). |
920 | locale-independent table under all locales). |
750 | |
921 | |
751 | Rxvt-unicode uses the "LC_CTYPE" locale category to select encoding. All |
922 | 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 |
923 | programs doing the same (that is, most) will automatically agree in the |
753 | interpretation of characters. |
924 | interpretation of characters. |
… | |
… | |
770 | |
941 | |
771 | Can I switch locales at runtime? |
942 | Can I switch locales at runtime? |
772 | Yes, using an escape sequence. Try something like this, which sets |
943 | Yes, using an escape sequence. Try something like this, which sets |
773 | rxvt-unicode's idea of "LC_CTYPE". |
944 | rxvt-unicode's idea of "LC_CTYPE". |
774 | |
945 | |
775 | printf '\e]701;%s\007' ja_JP.SJIS |
946 | printf '\33]701;%s\007' ja_JP.SJIS |
776 | |
947 | |
777 | See also the previous answer. |
948 | See also the previous answer. |
778 | |
949 | |
779 | Sometimes this capability is rather handy when you want to work in one |
950 | 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. |
951 | 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 |
952 | UTF-8). For example, I use this script to start "xjdic", which first |
782 | switches to a locale supported by xjdic and back later: |
953 | switches to a locale supported by xjdic and back later: |
783 | |
954 | |
784 | printf '\e]701;%s\007' ja_JP.SJIS |
955 | printf '\33]701;%s\007' ja_JP.SJIS |
785 | xjdic -js |
956 | xjdic -js |
786 | printf '\e]701;%s\007' de_DE.UTF-8 |
957 | printf '\33]701;%s\007' de_DE.UTF-8 |
787 | |
958 | |
788 | You can also use xterm's "luit" program, which usually works fine, |
959 | You can also use xterm's "luit" program, which usually works fine, |
789 | except for some locales where character width differs between program- |
960 | except for some locales where character width differs between program- |
790 | and rxvt-unicode-locales. |
961 | and rxvt-unicode-locales. |
791 | |
962 | |
|
|
963 | I have problems getting my input method working. |
|
|
964 | Try a search engine, as this is slightly different for every input |
|
|
965 | method server. |
|
|
966 | |
|
|
967 | Here is a checklist: |
|
|
968 | |
|
|
969 | - Make sure your locale *and* the imLocale are supported on your OS. |
|
|
970 | Try "locale -a" or check the documentation for your OS. |
|
|
971 | |
|
|
972 | - Make sure your locale or imLocale matches a locale supported by your |
|
|
973 | XIM. |
|
|
974 | For example, kinput2 does not support UTF-8 locales, you should use |
|
|
975 | "ja_JP.EUC-JP" or equivalent. |
|
|
976 | |
|
|
977 | - Make sure your XIM server is actually running. |
|
|
978 | - Make sure the "XMODIFIERS" environment variable is set correctly when |
|
|
979 | *starting* rxvt-unicode. |
|
|
980 | When you want to use e.g. kinput2, it must be set to "@im=kinput2". |
|
|
981 | For scim, use "@im=SCIM". You can see what input method servers are |
|
|
982 | running with this command: |
|
|
983 | |
|
|
984 | xprop -root XIM_SERVERS |
|
|
985 | |
|
|
986 | |
|
|
987 | |
792 | My input method wants <some encoding> but I want UTF-8, what can I do? |
988 | 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 |
989 | You can specify separate locales for the input method and the rest of |
794 | the terminal, using the resource "imlocale": |
990 | the terminal, using the resource "imlocale": |
795 | |
991 | |
796 | URxvt.imlocale: ja_JP.EUC-JP |
992 | URxvt.imlocale: ja_JP.EUC-JP |
797 | |
993 | |
798 | Now you can start your terminal with "LC_CTYPE=ja_JP.UTF-8" and still |
994 | 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 |
995 | 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 |
996 | Xlib version, you may not be able to input characters outside "EUC-JP" |
801 | method limits you. |
997 | in a normal way then, as your input method limits you. |
802 | |
998 | |
803 | Rxvt-unicode crashes when the X Input Method changes or exits. |
999 | Rxvt-unicode crashes when the X Input Method changes or exits. |
804 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
1000 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
805 | design. Applications can avoid some crashes at the expense of memory |
1001 | design. Applications can avoid some crashes at the expense of memory |
806 | leaks, and Input Methods can avoid some crashes by careful ordering at |
1002 | leaks, and Input Methods can avoid some crashes by careful ordering at |
… | |
… | |
827 | that might encounter the same issue. |
1023 | that might encounter the same issue. |
828 | |
1024 | |
829 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1025 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
830 | You should build one binary with the default options. configure now |
1026 | You should build one binary with the default options. configure now |
831 | enables most useful options, and the trend goes to making them |
1027 | enables most useful options, and the trend goes to making them |
832 | runtime-switchable, too, so there is usually no drawback to enbaling |
1028 | runtime-switchable, too, so there is usually no drawback to enabling |
833 | them, except higher disk and possibly memory usage. The perl interpreter |
1029 | them, except higher disk and possibly memory usage. The perl interpreter |
834 | should be enabled, as important functionality (menus, selection, likely |
1030 | should be enabled, as important functionality (menus, selection, likely |
835 | more in the future) depends on it. |
1031 | more in the future) depends on it. |
836 | |
1032 | |
837 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
1033 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
… | |
… | |
869 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
1065 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
870 | |
1066 | |
871 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
1067 | 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 |
1068 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
873 | your compile environment, or an implementation that implements it, |
1069 | your compile environment, or an implementation that implements it, |
874 | wether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
1070 | whether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
875 | wchar_t is represented as unicode. |
1071 | wchar_t is represented as unicode. |
876 | |
1072 | |
877 | As you might have guessed, FreeBSD does neither define this symobl nor |
1073 | 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 |
1074 | 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. |
1075 | wchar_t. This is, of course, completely fine with respect to standards. |
880 | |
1076 | |
881 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
1077 | 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. |
1078 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
883 | |
1079 | |