… | |
… | |
2 | How do I know which rxvt-unicode version I'm using? |
2 | How do I know which rxvt-unicode version I'm using? |
3 | The version number is displayed with the usage (-h). Also the escape |
3 | The version number is displayed with the usage (-h). Also the escape |
4 | sequence "ESC [ 8 n" sets the window title to the version number. |
4 | sequence "ESC [ 8 n" sets the window title to the version number. |
5 | |
5 | |
6 | I am using Debian GNU/Linux and have a problem... |
6 | I am using Debian GNU/Linux and have a problem... |
7 | The Debian GNU/Linux package of rxvt-unicode contains large patches |
7 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
8 | that considerably change the behaviour of rxvt-unicode. Before |
8 | patches that considerably change the behaviour of rxvt-unicode. |
9 | reporting a bug to the original rxvt-unicode author please download |
9 | Before reporting a bug to the original rxvt-unicode author please |
10 | and install the genuine version |
10 | download and install the genuine version |
11 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
11 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
12 | problem. If you cannot, chances are that the problems are specific |
12 | problem. If you cannot, chances are that the problems are specific |
13 | to Debian GNU/Linux, in which case it should be reported via the |
13 | to Debian GNU/Linux, in which case it should be reported via the |
14 | Debian Bug Tracking System (use "reportbug" to report the bug). |
14 | Debian Bug Tracking System (use "reportbug" to report the bug). |
15 | |
15 | |
… | |
… | |
45 | URxvt.termName: rxvt |
45 | URxvt.termName: rxvt |
46 | |
46 | |
47 | If you don't plan to use rxvt (quite common...) you could also |
47 | If you don't plan to use rxvt (quite common...) you could also |
48 | replace the rxvt terminfo file with the rxvt-unicode one. |
48 | replace the rxvt terminfo file with the rxvt-unicode one. |
49 | |
49 | |
|
|
50 | "tic" outputs some error when compiling the terminfo entry. |
|
|
51 | Most likely it's the empty definition for "enacs=". Just replace it |
|
|
52 | by "enacs=\E[0@" and try again. |
|
|
53 | |
50 | "bash"'s readline does not work correctly under rxvt. |
54 | "bash"'s readline does not work correctly under rxvt. |
51 | I need a termcap file entry. |
55 | I need a termcap file entry. |
52 | One reason you might want this is that some distributions or |
56 | One reason you might want this is that some distributions or |
53 | operating systems still compile some programs using the |
57 | operating systems still compile some programs using the |
54 | long-obsoleted termcap (Fedora Core's bash is one example) and rely |
58 | long-obsoleted termcap library (Fedora Core's bash is one example) |
55 | on a termcap entry for "rxvt-unicode". |
59 | and rely on a termcap entry for "rxvt-unicode". |
56 | |
60 | |
57 | You could use rxvt's termcap entry with resonable results in many |
61 | You could use rxvt's termcap entry with resonable results in many |
58 | cases. You can also create a termcap entry by using terminfo's |
62 | cases. You can also create a termcap entry by using terminfo's |
59 | infocmp program like this: |
63 | infocmp program like this: |
60 | |
64 | |
… | |
… | |
62 | |
66 | |
63 | Or you could use this termcap entry, generated by the command above: |
67 | Or you could use this termcap entry, generated by the command above: |
64 | |
68 | |
65 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
69 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
66 | :am:bw:eo:km:mi:ms:xn:xo:\ |
70 | :am:bw:eo:km:mi:ms:xn:xo:\ |
67 | :co#80:it#8:li#24:\ |
71 | :co#80:it#8:li#24:lm#0:\ |
68 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
72 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
69 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
73 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
70 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\ |
74 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
71 | :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\ |
75 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
72 | :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\ |
76 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
73 | :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\ |
77 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
|
|
78 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
74 | :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
79 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
75 | :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\ |
80 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
76 | :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\ |
81 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
77 | :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\ |
82 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
78 | :ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\ |
83 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
79 | :ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\ |
84 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
80 | :nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\ |
85 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
81 | :st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\ |
86 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
82 | :up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
87 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
83 | :vs=\E[?25h: |
88 | :vs=\E[?25h: |
84 | |
89 | |
85 | Why does "ls" no longer have coloured output? |
90 | Why does "ls" no longer have coloured output? |
86 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
91 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
87 | decide wether a terminal has colour, but uses it's own configuration |
92 | decide wether a terminal has colour, but uses it's own configuration |
… | |
… | |
225 | that doesn't work, you might be forced to use a different font. |
230 | that doesn't work, you might be forced to use a different font. |
226 | |
231 | |
227 | All of this is not a problem when using X11 core fonts, as their |
232 | All of this is not a problem when using X11 core fonts, as their |
228 | bounding box data is correct. |
233 | bounding box data is correct. |
229 | |
234 | |
|
|
235 | On Solaris 9, many line-drawing characters are too wide. |
|
|
236 | Seems to be a known bug, read |
|
|
237 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
|
|
238 | following ugly workaround to get non-double-wide-characters working: |
|
|
239 | |
|
|
240 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
|
|
241 | |
230 | My Compose (Multi_key) key is no longer working. |
242 | My Compose (Multi_key) key is no longer working. |
231 | The most common causes for this are that either your locale is not |
243 | The most common causes for this are that either your locale is not |
232 | set correctly, or you specified a preeditStyle that is not supported |
244 | set correctly, or you specified a preeditStyle that is not supported |
233 | by your input method. For example, if you specified OverTheSpot and |
245 | by your input method. For example, if you specified OverTheSpot and |
234 | your input method (e.g. the default input method handling Compose |
246 | your input method (e.g. the default input method handling Compose |
… | |
… | |
278 | As you might have guessed, FreeBSD does neither define this symobl |
290 | As you might have guessed, FreeBSD does neither define this symobl |
279 | nor does it support it. Instead, it uses it's own internal |
291 | nor does it support it. Instead, it uses it's own internal |
280 | representation of wchar_t. This is, of course, completely fine with |
292 | representation of wchar_t. This is, of course, completely fine with |
281 | respect to standards. |
293 | respect to standards. |
282 | |
294 | |
|
|
295 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" |
|
|
296 | and "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
|
|
297 | |
283 | However, "__STDC_ISO_10646__" is the only sane way to support |
298 | "__STDC_ISO_10646__" is the only sane way to support multi-language |
284 | multi-language apps in an OS, as using a locale-dependent (and |
299 | apps in an OS, as using a locale-dependent (and non-standardized) |
285 | non-standardized) representation of wchar_t makes it impossible to |
300 | representation of wchar_t makes it impossible to convert between |
286 | convert between wchar_t (as used by X11 and your applications) and |
301 | wchar_t (as used by X11 and your applications) and any other |
287 | any other encoding without implementing OS-specific-wrappers for |
302 | encoding without implementing OS-specific-wrappers for each and |
288 | each and every locale. There simply are no APIs to convert wchar_t |
303 | every locale. There simply are no APIs to convert wchar_t into |
289 | into anything except the current locale encoding. |
304 | anything except the current locale encoding. |
290 | |
305 | |
291 | Some applications (such as the formidable mlterm) work around this |
306 | Some applications (such as the formidable mlterm) work around this |
292 | by carrying their own replacement functions for character set |
307 | by carrying their own replacement functions for character set |
293 | handling with them, and either implementing OS-dependent hacks or |
308 | handling with them, and either implementing OS-dependent hacks or |
294 | doing multiple conversions (which is slow and unreliable in case the |
309 | doing multiple conversions (which is slow and unreliable in case the |
… | |
… | |
296 | emulator). |
311 | emulator). |
297 | |
312 | |
298 | The rxvt-unicode author insists that the right way to fix this is in |
313 | The rxvt-unicode author insists that the right way to fix this is in |
299 | the system libraries once and for all, instead of forcing every app |
314 | the system libraries once and for all, instead of forcing every app |
300 | to carry complete replacements for them :) |
315 | to carry complete replacements for them :) |
|
|
316 | |
|
|
317 | I use Solaris 9 and it doesn't compile/work/etc. |
|
|
318 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
|
|
319 | problems with "wcwidth" and a compile problem. |
|
|
320 | |
|
|
321 | How can I use rxvt-unicode under cygwin? |
|
|
322 | rxvt-unicode should compile and run out of the box on cygwin, using |
|
|
323 | the X11 libraries that come with cygwin. libW11 emulation is no |
|
|
324 | longer supported (and makes no sense, either, as it only supported a |
|
|
325 | single font). I recommend starting the X-server in "-multiwindow" or |
|
|
326 | "-rootless" mode instead, which will result in similar look&feel as |
|
|
327 | the old libW11 emulation. |
|
|
328 | |
|
|
329 | At the time of this writing, cygwin didn't seem to support any |
|
|
330 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
|
|
331 | likely limited to 8-bit encodings. |
301 | |
332 | |
302 | How does rxvt-unicode determine the encoding to use? |
333 | How does rxvt-unicode determine the encoding to use? |
303 | Is there an option to switch encodings? |
334 | Is there an option to switch encodings? |
304 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
335 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
305 | and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
336 | and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
… | |
… | |
500 | URxvt.color14: #73f7ff |
531 | URxvt.color14: #73f7ff |
501 | URxvt.color7: #e1dddd |
532 | URxvt.color7: #e1dddd |
502 | URxvt.color15: #e1dddd |
533 | URxvt.color15: #e1dddd |
503 | |
534 | |
504 | How can I start rxvtd in a race-free way? |
535 | How can I start rxvtd in a race-free way? |
505 | Despite it's name, rxvtd is not a real daemon, but more like a |
536 | Try "rxvtd -f -o", which tells rxvtd to open the display, create the |
506 | server that answers rxvtc's requests, so it doesn't background |
537 | listening socket and then fork. |
507 | itself. |
|
|
508 | |
|
|
509 | To ensure rxvtd is listening on it's socket, you can use the |
|
|
510 | following method to wait for the startup message before continuing: |
|
|
511 | |
|
|
512 | { rxvtd & } | read |
|
|
513 | |
538 | |
514 | What's with the strange Backspace/Delete key behaviour? |
539 | What's with the strange Backspace/Delete key behaviour? |
515 | Assuming that the physical Backspace key corresponds to the |
540 | Assuming that the physical Backspace key corresponds to the |
516 | BackSpace keysym (not likely for Linux ... see the following |
541 | BackSpace keysym (not likely for Linux ... see the following |
517 | question) there are two standard values that can be used for |
542 | question) there are two standard values that can be used for |