… | |
… | |
57 | scrollback search mode is triggered by M-s. You can move it to any other |
57 | scrollback search mode is triggered by M-s. You can move it to any other |
58 | combination either by setting the searchable-scrollback resource: |
58 | combination either by setting the searchable-scrollback resource: |
59 | |
59 | |
60 | URxvt.searchable-scrollback: CM-s |
60 | URxvt.searchable-scrollback: CM-s |
61 | |
61 | |
62 | The cursor moves when selecting text in the current input line, how |
62 | The cursor moves when selecting text in the current input line, how |
63 | do I switch this off? |
63 | do I switch this off? |
|
|
64 | See next entry. |
|
|
65 | |
64 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor |
66 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor |
65 | outputs strange escape sequences, how do I fix this? |
67 | outputs strange escape sequences, how do I fix this? |
66 | These are caused by the "readline" perl extension. Under normal |
68 | These are caused by the "readline" perl extension. Under normal |
67 | circumstances, it will move your cursor around when you click into the |
69 | circumstances, it will move your cursor around when you click into the |
68 | line that contains it. It tries hard not to do this at the wrong moment, |
70 | line that contains it. It tries hard not to do this at the wrong moment, |
… | |
… | |
315 | "tic" outputs some error when compiling the terminfo entry. |
317 | "tic" outputs some error when compiling the terminfo entry. |
316 | Most likely it's the empty definition for "enacs=". Just replace it by |
318 | Most likely it's the empty definition for "enacs=". Just replace it by |
317 | "enacs=\E[0@" and try again. |
319 | "enacs=\E[0@" and try again. |
318 | |
320 | |
319 | "bash"'s readline does not work correctly under rxvt. |
321 | "bash"'s readline does not work correctly under rxvt. |
|
|
322 | See next entry. |
|
|
323 | |
320 | I need a termcap file entry. |
324 | I need a termcap file entry. |
321 | One reason you might want this is that some distributions or operating |
325 | One reason you might want this is that some distributions or operating |
322 | systems still compile some programs using the long-obsoleted termcap |
326 | systems still compile some programs using the long-obsoleted termcap |
323 | library (Fedora Core's bash is one example) and rely on a termcap entry |
327 | library (Fedora Core's bash is one example) and rely on a termcap entry |
324 | for "rxvt-unicode". |
328 | for "rxvt-unicode". |
… | |
… | |
365 | alias ls='ls --color=auto' |
369 | alias ls='ls --color=auto' |
366 | |
370 | |
367 | to your ".profile" or ".bashrc". |
371 | to your ".profile" or ".bashrc". |
368 | |
372 | |
369 | Why doesn't vim/emacs etc. use the 88 colour mode? |
373 | Why doesn't vim/emacs etc. use the 88 colour mode? |
|
|
374 | See next entry. |
|
|
375 | |
370 | Why doesn't vim/emacs etc. make use of italic? |
376 | Why doesn't vim/emacs etc. make use of italic? |
|
|
377 | See next entry. |
|
|
378 | |
371 | Why are the secondary screen-related options not working properly? |
379 | Why are the secondary screen-related options not working properly? |
372 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
380 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
373 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
381 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
374 | setting "TERM" to "rxvt", which doesn't have these extra features. |
382 | setting "TERM" to "rxvt", which doesn't have these extra features. |
375 | Unfortunately, some of these (most notably, again, Debian GNU/Linux) |
383 | Unfortunately, some of these (most notably, again, Debian GNU/Linux) |
… | |
… | |
385 | how this can happen are unknown, as "TERM=rxvt" should offer a |
393 | how this can happen are unknown, as "TERM=rxvt" should offer a |
386 | compatible keymap. See the answer to the previous question, and please |
394 | compatible keymap. See the answer to the previous question, and please |
387 | report if that helped. |
395 | report if that helped. |
388 | |
396 | |
389 | Rxvt-unicode does not seem to understand the selected encoding? |
397 | Rxvt-unicode does not seem to understand the selected encoding? |
|
|
398 | See next entry. |
|
|
399 | |
390 | Unicode does not seem to work? |
400 | Unicode does not seem to work? |
391 | If you encounter strange problems like typing an accented character but |
401 | If you encounter strange problems like typing an accented character but |
392 | getting two unrelated other characters or similar, or if program output |
402 | getting two unrelated other characters or similar, or if program output |
393 | is subtly garbled, then you should check your locale settings. |
403 | is subtly garbled, then you should check your locale settings. |
394 | |
404 | |
… | |
… | |
417 | If nothing works and you are sure that everything is set correctly then |
427 | If nothing works and you are sure that everything is set correctly then |
418 | you will need to remember a little known fact: Some programs just don't |
428 | you will need to remember a little known fact: Some programs just don't |
419 | support locales :( |
429 | support locales :( |
420 | |
430 | |
421 | Why do some characters look so much different than others? |
431 | Why do some characters look so much different than others? |
|
|
432 | See next entry. |
|
|
433 | |
422 | How does rxvt-unicode choose fonts? |
434 | How does rxvt-unicode choose fonts? |
423 | Most fonts do not contain the full range of Unicode, which is fine. |
435 | Most fonts do not contain the full range of Unicode, which is fine. |
424 | Chances are that the font you (or the admin/package maintainer of your |
436 | Chances are that the font you (or the admin/package maintainer of your |
425 | system/os) have specified does not cover all the characters you want to |
437 | system/os) have specified does not cover all the characters you want to |
426 | display. |
438 | display. |
… | |
… | |
583 | At the time of this writing, cygwin didn't seem to support any |
595 | At the time of this writing, cygwin didn't seem to support any |
584 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
596 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
585 | likely limited to 8-bit encodings. |
597 | likely limited to 8-bit encodings. |
586 | |
598 | |
587 | How does rxvt-unicode determine the encoding to use? |
599 | How does rxvt-unicode determine the encoding to use? |
|
|
600 | See next entry. |
|
|
601 | |
588 | Is there an option to switch encodings? |
602 | Is there an option to switch encodings? |
589 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
603 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
590 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know |
604 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know |
591 | about UTF-8 or any other encodings with respect to terminal I/O. |
605 | about UTF-8 or any other encodings with respect to terminal I/O. |
592 | |
606 | |