| … | |
… | |
| 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. |
25 | sequence "ESC [ 8 n" sets the window title to the version number. |
| 26 | |
26 | |
| 27 | I am using Debian GNU/Linux and have a problem... |
27 | I am using Debian GNU/Linux and have a problem... |
| 28 | The Debian GNU/Linux package of rxvt-unicode contains large patches |
28 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
| 29 | that considerably change the behaviour of rxvt-unicode. Before |
29 | patches that considerably change the behaviour of rxvt-unicode. |
| 30 | reporting a bug to the original rxvt-unicode author please download |
30 | Before reporting a bug to the original rxvt-unicode author please |
| 31 | and install the genuine version |
31 | download and install the genuine version |
| 32 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
32 | (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce the |
| 33 | problem. If you cannot, chances are that the problems are specific |
33 | problem. If you cannot, chances are that the problems are specific |
| 34 | to Debian GNU/Linux, in which case it should be reported via the |
34 | to Debian GNU/Linux, in which case it should be reported via the |
| 35 | Debian Bug Tracking System (use "reportbug" to report the bug). |
35 | Debian Bug Tracking System (use "reportbug" to report the bug). |
| 36 | |
36 | |
| … | |
… | |
| 65 | |
65 | |
| 66 | URxvt.termName: rxvt |
66 | URxvt.termName: rxvt |
| 67 | |
67 | |
| 68 | If you don't plan to use rxvt (quite common...) you could also |
68 | If you don't plan to use rxvt (quite common...) you could also |
| 69 | replace the rxvt terminfo file with the rxvt-unicode one. |
69 | replace the rxvt terminfo file with the rxvt-unicode one. |
|
|
70 | |
|
|
71 | "tic" outputs some error when compiling the terminfo entry. |
|
|
72 | Most likely it's the empty definition for "enacs=". Just replace it |
|
|
73 | by "enacs=\E[0@" and try again. |
| 70 | |
74 | |
| 71 | "bash"'s readline does not work correctly under rxvt. |
75 | "bash"'s readline does not work correctly under rxvt. |
| 72 | I need a termcap file entry. |
76 | I need a termcap file entry. |
| 73 | One reason you might want this is that some distributions or |
77 | One reason you might want this is that some distributions or |
| 74 | operating systems still compile some programs using the |
78 | operating systems still compile some programs using the |
| … | |
… | |
| 247 | that doesn't work, you might be forced to use a different font. |
251 | that doesn't work, you might be forced to use a different font. |
| 248 | |
252 | |
| 249 | All of this is not a problem when using X11 core fonts, as their |
253 | All of this is not a problem when using X11 core fonts, as their |
| 250 | bounding box data is correct. |
254 | bounding box data is correct. |
| 251 | |
255 | |
|
|
256 | On Solaris 9, many line-drawing characters are too wide. |
|
|
257 | Seems to be a known bug, read |
|
|
258 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
|
|
259 | following ugly workaround to get non-double-wide-characters working: |
|
|
260 | |
|
|
261 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
|
|
262 | |
| 252 | My Compose (Multi_key) key is no longer working. |
263 | My Compose (Multi_key) key is no longer working. |
| 253 | The most common causes for this are that either your locale is not |
264 | The most common causes for this are that either your locale is not |
| 254 | set correctly, or you specified a preeditStyle that is not supported |
265 | set correctly, or you specified a preeditStyle that is not supported |
| 255 | by your input method. For example, if you specified OverTheSpot and |
266 | by your input method. For example, if you specified OverTheSpot and |
| 256 | your input method (e.g. the default input method handling Compose |
267 | your input method (e.g. the default input method handling Compose |
| … | |
… | |
| 321 | emulator). |
332 | emulator). |
| 322 | |
333 | |
| 323 | The rxvt-unicode author insists that the right way to fix this is in |
334 | The rxvt-unicode author insists that the right way to fix this is in |
| 324 | the system libraries once and for all, instead of forcing every app |
335 | the system libraries once and for all, instead of forcing every app |
| 325 | to carry complete replacements for them :) |
336 | to carry complete replacements for them :) |
|
|
337 | |
|
|
338 | I use Solaris 9 and it doesn't compile/work/etc. |
|
|
339 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
|
|
340 | problems with "wcwidth" and a compile problem. |
|
|
341 | |
|
|
342 | How can I use rxvt-unicode under cygwin? |
|
|
343 | rxvt-unicode should compile and run out of the box on cygwin, using |
|
|
344 | the X11 libraries that come with cygwin. libW11 emulation is no |
|
|
345 | longer supported (and makes no sense, either, as it only supported a |
|
|
346 | single font). I recommend starting the X-server in "-multiwindow" or |
|
|
347 | "-rootless" mode instead, which will result in similar look&feel as |
|
|
348 | the old libW11 emulation. |
|
|
349 | |
|
|
350 | At the time of this writing, cygwin didn't seem to support any |
|
|
351 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
|
|
352 | likely limited to 8-bit encodings. |
| 326 | |
353 | |
| 327 | How does rxvt-unicode determine the encoding to use? |
354 | How does rxvt-unicode determine the encoding to use? |
| 328 | Is there an option to switch encodings? |
355 | Is there an option to switch encodings? |
| 329 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
356 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
| 330 | and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
357 | and no specific "utf-8" mode, such as xterm. In fact, it doesn't |
