| … | |
… | |
| 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 "^?". |
| … | |
… | |
| 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 |
| … | |
… | |
| 1005 | I am using Debian GNU/Linux and have a problem... |
995 | I am using Debian GNU/Linux and have a problem... |
| 1006 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
996 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
| 1007 | patches that considerably change the behaviour of rxvt-unicode (but |
997 | patches that considerably change the behaviour of rxvt-unicode (but |
| 1008 | unfortunately this notice has been removed). Before reporting a bug to |
998 | unfortunately this notice has been removed). Before reporting a bug to |
| 1009 | the original rxvt-unicode author please download and install the genuine |
999 | the original rxvt-unicode author please download and install the genuine |
| 1010 | version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
1000 | version (<http://software.schmorp.de/pkg/rxvt-unicode.html>) and try to |
| 1011 | the problem. If you cannot, chances are that the problems are specific |
1001 | reproduce the problem. If you cannot, chances are that the problems are |
| 1012 | to Debian GNU/Linux, in which case it should be reported via the Debian |
1002 | specific to Debian GNU/Linux, in which case it should be reported via |
| 1013 | Bug Tracking System (use "reportbug" to report the bug). |
1003 | the Debian Bug Tracking System (use "reportbug" to report the bug). |
| 1014 | |
1004 | |
| 1015 | For other problems that also affect the Debian package, you can and |
1005 | For other problems that also affect the Debian package, you can and |
| 1016 | probably should use the Debian BTS, too, because, after all, it's also a |
1006 | probably should use the Debian BTS, too, because, after all, it's also a |
| 1017 | bug in the Debian version and it serves as a reminder for other users |
1007 | bug in the Debian version and it serves as a reminder for other users |
| 1018 | that might encounter the same issue. |
1008 | that might encounter the same issue. |
