| … | |
… | |
| 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 | |
| … | |
… | |
| 44 | |
44 | |
| 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 | |
|
|
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. |
| 49 | |
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 |
| … | |
… | |
| 226 | 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. |
| 227 | |
231 | |
| 228 | 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 |
| 229 | bounding box data is correct. |
233 | bounding box data is correct. |
| 230 | |
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 | |
| 231 | My Compose (Multi_key) key is no longer working. |
242 | My Compose (Multi_key) key is no longer working. |
| 232 | 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 |
| 233 | set correctly, or you specified a preeditStyle that is not supported |
244 | set correctly, or you specified a preeditStyle that is not supported |
| 234 | by your input method. For example, if you specified OverTheSpot and |
245 | by your input method. For example, if you specified OverTheSpot and |
| 235 | your input method (e.g. the default input method handling Compose |
246 | your input method (e.g. the default input method handling Compose |
| … | |
… | |
| 300 | emulator). |
311 | emulator). |
| 301 | |
312 | |
| 302 | 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 |
| 303 | 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 |
| 304 | 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. |
| 305 | |
332 | |
| 306 | How does rxvt-unicode determine the encoding to use? |
333 | How does rxvt-unicode determine the encoding to use? |
| 307 | Is there an option to switch encodings? |
334 | Is there an option to switch encodings? |
| 308 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
335 | Unlike some other terminals, rxvt-unicode has no encoding switch, |
| 309 | 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 |
| … | |
… | |
| 421 | it gets worse, as rxvt-unicode then uses 8 bytes per screen cell. |
448 | it gets worse, as rxvt-unicode then uses 8 bytes per screen cell. |
| 422 | |
449 | |
| 423 | Can I speed up Xft rendering somehow? |
450 | Can I speed up Xft rendering somehow? |
| 424 | Yes, the most obvious way to speed it up is to avoid Xft entirely, |
451 | Yes, the most obvious way to speed it up is to avoid Xft entirely, |
| 425 | as it is simply slow. If you still want Xft fonts you might try to |
452 | as it is simply slow. If you still want Xft fonts you might try to |
| 426 | disable antialiasing (by appending ":antialiasing=false"), which |
453 | disable antialiasing (by appending ":antialias=false"), which saves |
| 427 | saves lots of memory and also speeds up rendering considerably. |
454 | lots of memory and also speeds up rendering considerably. |
| 428 | |
455 | |
| 429 | Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
456 | Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
| 430 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
457 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
| 431 | fall back to it's default font search list it will prefer X11 core |
458 | fall back to it's default font search list it will prefer X11 core |
| 432 | fonts, because they are small and fast, and then use Xft fonts. It |
459 | fonts, because they are small and fast, and then use Xft fonts. It |
| … | |
… | |
| 504 | URxvt.color14: #73f7ff |
531 | URxvt.color14: #73f7ff |
| 505 | URxvt.color7: #e1dddd |
532 | URxvt.color7: #e1dddd |
| 506 | URxvt.color15: #e1dddd |
533 | URxvt.color15: #e1dddd |
| 507 | |
534 | |
| 508 | How can I start rxvtd in a race-free way? |
535 | How can I start rxvtd in a race-free way? |
| 509 | 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 |
| 510 | server that answers rxvtc's requests, so it doesn't background |
537 | listening socket and then fork. |
| 511 | itself. |
|
|
| 512 | |
|
|
| 513 | To ensure rxvtd is listening on it's socket, you can use the |
|
|
| 514 | following method to wait for the startup message before continuing: |
|
|
| 515 | |
|
|
| 516 | { rxvtd & } | read |
|
|
| 517 | |
538 | |
| 518 | What's with the strange Backspace/Delete key behaviour? |
539 | What's with the strange Backspace/Delete key behaviour? |
| 519 | Assuming that the physical Backspace key corresponds to the |
540 | Assuming that the physical Backspace key corresponds to the |
| 520 | BackSpace keysym (not likely for Linux ... see the following |
541 | BackSpace keysym (not likely for Linux ... see the following |
| 521 | question) there are two standard values that can be used for |
542 | question) there are two standard values that can be used for |
