… | |
… | |
91 | |
91 | |
92 | # Bourne/Korn/POSIX family of shells: |
92 | # Bourne/Korn/POSIX family of shells: |
93 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
93 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
94 | if [ ${TERM:-foo} = xterm ]; then |
94 | if [ ${TERM:-foo} = xterm ]; then |
95 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
95 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
96 | echo -n '^[Z' |
96 | printf "\eZ" |
97 | read term_id |
97 | read term_id |
98 | stty icanon echo |
98 | stty icanon echo |
99 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
99 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
100 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
100 | printf '\e[7n' # query the rxvt we are in for the DISPLAY string |
101 | read DISPLAY # set it in our local shell |
101 | read DISPLAY # set it in our local shell |
102 | fi |
102 | fi |
103 | fi |
103 | fi |
104 | |
104 | |
105 | How do I compile the manual pages on my own? |
105 | How do I compile the manual pages on my own? |
106 | You need to have a recent version of perl installed as /usr/bin/perl, |
106 | You need to have a recent version of perl installed as /usr/bin/perl, |
… | |
… | |
206 | your picture with gimp or any other tool: |
206 | your picture with gimp or any other tool: |
207 | |
207 | |
208 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
208 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
209 | urxvt -pixmap "background.jpg;:root" |
209 | urxvt -pixmap "background.jpg;:root" |
210 | |
210 | |
211 | That works. If you think it doesn't, you lack libAfterImage or |
211 | That works. If you think it doesn't, you lack GDK-PixBuf support, or you |
212 | GDK-PixBuf support, or you are unable to read. |
212 | are unable to read. |
213 | |
213 | |
214 | 3. Use an ARGB visual: |
214 | 3. Use an ARGB visual: |
215 | |
215 | |
216 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
216 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
217 | |
217 | |
… | |
… | |
514 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
514 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
515 | escape character and so on. |
515 | escape character and so on. |
516 | |
516 | |
517 | Mouse cut/paste suddenly no longer works. |
517 | Mouse cut/paste suddenly no longer works. |
518 | Make sure that mouse reporting is actually turned off since killing some |
518 | Make sure that mouse reporting is actually turned off since killing some |
519 | editors prematurely may leave the mouse in mouse report mode. I've heard |
519 | editors prematurely may leave it active. I've heard that tcsh may use |
520 | that tcsh may use mouse reporting unless it otherwise specified. A quick |
520 | mouse reporting unless it is otherwise specified. A quick check is to |
521 | check is to see if cut/paste works when the Alt or Shift keys are |
521 | see if cut/paste works when the Alt or Shift keys are pressed. |
522 | depressed. |
|
|
523 | |
522 | |
524 | What's with the strange Backspace/Delete key behaviour? |
523 | What's with the strange Backspace/Delete key behaviour? |
525 | Assuming that the physical Backspace key corresponds to the Backspace |
524 | Assuming that the physical Backspace key corresponds to the Backspace |
526 | keysym (not likely for Linux ... see the following question) there are |
525 | keysym (not likely for Linux ... see the following question) there are |
527 | two standard values that can be used for Backspace: "^H" and "^?". |
526 | two standard values that can be used for Backspace: "^H" and "^?". |
… | |
… | |
533 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
532 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
534 | mode: |
533 | mode: |
535 | |
534 | |
536 | # use Backspace = ^H |
535 | # use Backspace = ^H |
537 | $ stty erase ^H |
536 | $ stty erase ^H |
538 | $ echo -n "^[[?67h" |
537 | $ printf "\e[?67h" |
539 | |
538 | |
540 | # use Backspace = ^? |
539 | # use Backspace = ^? |
541 | $ stty erase ^? |
540 | $ stty erase ^? |
542 | $ echo -n "^[[?67l" |
541 | $ printf "\e[?67l" |
543 | |
542 | |
544 | This helps satisfy some of the Backspace discrepancies that occur, but |
543 | This helps satisfy some of the Backspace discrepancies that occur, but |
545 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
544 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
546 | properly reflects that. |
545 | properly reflects that. |
547 | |
546 | |
… | |
… | |
563 | use the `keysym' resource to alter the keystrings associated with |
562 | use the `keysym' resource to alter the keystrings associated with |
564 | keysyms. |
563 | keysyms. |
565 | |
564 | |
566 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
565 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
567 | |
566 | |
|
|
567 | URxvt.keysym.Prior: \033[5~ |
|
|
568 | URxvt.keysym.Next: \033[6~ |
568 | URxvt.keysym.Home: \033[1~ |
569 | URxvt.keysym.Home: \033[7~ |
569 | URxvt.keysym.End: \033[4~ |
570 | URxvt.keysym.End: \033[8~ |
570 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
571 | URxvt.keysym.C-slash: \033<C-/> |
|
|
572 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
573 | URxvt.keysym.C-grave: \033<C-`> |
|
|
574 | URxvt.keysym.C-comma: \033<C-,> |
|
|
575 | URxvt.keysym.C-period: \033<C-.> |
|
|
576 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
577 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
578 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
579 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
580 | URxvt.keysym.S-space: \033<S-Space> |
|
|
581 | URxvt.keysym.M-Up: \033<M-Up> |
571 | URxvt.keysym.Up: \033[A |
582 | URxvt.keysym.M-Down: \033<M-Down> |
572 | URxvt.keysym.Down: \033[B |
|
|
573 | URxvt.keysym.Right: \033[C |
583 | URxvt.keysym.M-Left: \033<M-Left> |
574 | URxvt.keysym.Left: \033[D |
584 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
585 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
586 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
587 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
|
|
588 | |
575 | |
589 | See some more examples in the documentation for the keysym resource. |
576 | See some more examples in the documentation for the keysym resource. |
590 | |
577 | |
591 | I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map |
578 | I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map |
592 | KP_Insert == Insert |
579 | KP_Insert == Insert |
… | |
… | |
787 | |
774 | |
788 | REMOTE=remotesystem.domain |
775 | REMOTE=remotesystem.domain |
789 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
776 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
790 | |
777 | |
791 | One some systems you might need to set $TERMINFO to the full path of |
778 | One some systems you might need to set $TERMINFO to the full path of |
792 | $HOME/.terminfo for this to work. |
779 | $HOME/.terminfo for this to work. Debian systems have a broken tic which |
|
|
780 | will not be able to overwrite the existing rxvt-unicode terminfo entry - |
|
|
781 | you might have to manually delete all traces of rxvt-unicode* from |
|
|
782 | /etc/terminfo. |
793 | |
783 | |
794 | If you cannot or do not want to do this, then you can simply set |
784 | If you cannot or do not want to do this, then you can simply set |
795 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
785 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
796 | problems arising, which includes wrong keymapping, less and different |
786 | problems arising, which includes wrong keymapping, less and different |
797 | colours and some refresh errors in fullscreen applications. It's a nice |
787 | colours and some refresh errors in fullscreen applications. It's a nice |