… | |
… | |
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, |
… | |
… | |
158 | the case of rxvt-unicode this hardly matters, as its portability limits |
158 | the case of rxvt-unicode this hardly matters, as its portability limits |
159 | are defined by things like X11, pseudo terminals, locale support and |
159 | are defined by things like X11, pseudo terminals, locale support and |
160 | unix domain sockets, which are all less portable than C++ itself. |
160 | unix domain sockets, which are all less portable than C++ itself. |
161 | |
161 | |
162 | Regarding the bloat, see the above question: It's easy to write programs |
162 | Regarding the bloat, see the above question: It's easy to write programs |
163 | in C that use gobs of memory, an certainly possible to write programs in |
163 | in C that use gobs of memory, and certainly possible to write programs |
164 | C++ that don't. C++ also often comes with large libraries, but this is |
164 | in C++ that don't. C++ also often comes with large libraries, but this |
165 | not necessarily the case with GCC. Here is what rxvt links against on my |
165 | is not necessarily the case with GCC. Here is what rxvt links against on |
166 | system with a minimal config: |
166 | my system with a minimal config: |
167 | |
167 | |
168 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
168 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
169 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
169 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
170 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
170 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
171 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
171 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
… | |
… | |
181 | No large bloated libraries (of course, none were linked in statically), |
181 | No large bloated libraries (of course, none were linked in statically), |
182 | except maybe libX11 :) |
182 | except maybe libX11 :) |
183 | |
183 | |
184 | Rendering, Font & Look and Feel Issues |
184 | Rendering, Font & Look and Feel Issues |
185 | I can't get transparency working, what am I doing wrong? |
185 | I can't get transparency working, what am I doing wrong? |
186 | First of all, please address all transparency related issues to Sasha |
186 | First of all, transparency isn't officially supported in rxvt-unicode, |
187 | Vasko at sasha@aftercode.net and do not bug the author about it. Also, |
187 | so you are mostly on your own. Do not bug the author about it (but you |
188 | if you can't get it working consider it a rite of passage: ... and you |
188 | may bug everybody else). Also, if you can't get it working consider it a |
189 | failed. |
189 | rite of passage: ... and you failed. |
190 | |
190 | |
191 | Here are four ways to get transparency. Do read the manpage and option |
191 | Here are four ways to get transparency. Do read the manpage and option |
192 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
192 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
193 | |
193 | |
194 | 1. Use transparent mode: |
194 | 1. Use transparent mode: |
195 | |
195 | |
196 | Esetroot wallpaper.jpg |
196 | Esetroot wallpaper.jpg |
197 | urxvt -tr -tint red -sh 40 |
197 | urxvt -tr -tint red -sh 40 |
198 | |
198 | |
199 | That works. If you think it doesn't, you lack transparency and tinting |
199 | That works. If you think it doesn't, you lack transparency and tinting |
200 | support, or you are unable to read. |
200 | support, or you are unable to read. This method requires that the |
|
|
201 | background-setting program sets the _XROOTPMAP_ID or ESETROOT_PMAP_ID |
|
|
202 | property. Compatible programs are Esetroot, hsetroot and feh. |
201 | |
203 | |
202 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
204 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
203 | to use effects other than tinting and shading: Just shade/tint/whatever |
205 | to use effects other than tinting and shading: Just shade/tint/whatever |
204 | your picture with gimp or any other tool: |
206 | your picture with gimp or any other tool: |
205 | |
207 | |
206 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
208 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
207 | urxvt -pixmap "background.jpg;:root" |
209 | urxvt -pixmap "background.jpg;:root" |
208 | |
210 | |
209 | That works. If you think it doesn't, you lack AfterImage support, or you |
211 | That works. If you think it doesn't, you lack GDK-PixBuf support, or you |
210 | are unable to read. |
212 | are unable to read. |
211 | |
213 | |
212 | 3. Use an ARGB visual: |
214 | 3. Use an ARGB visual: |
213 | |
215 | |
214 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
216 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
… | |
… | |
512 | 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 |
513 | escape character and so on. |
515 | escape character and so on. |
514 | |
516 | |
515 | Mouse cut/paste suddenly no longer works. |
517 | Mouse cut/paste suddenly no longer works. |
516 | 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 |
517 | 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 |
518 | 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 |
519 | 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. |
520 | depressed. |
|
|
521 | |
522 | |
522 | What's with the strange Backspace/Delete key behaviour? |
523 | What's with the strange Backspace/Delete key behaviour? |
523 | Assuming that the physical Backspace key corresponds to the Backspace |
524 | Assuming that the physical Backspace key corresponds to the Backspace |
524 | keysym (not likely for Linux ... see the following question) there are |
525 | keysym (not likely for Linux ... see the following question) there are |
525 | two standard values that can be used for Backspace: "^H" and "^?". |
526 | two standard values that can be used for Backspace: "^H" and "^?". |
526 | |
527 | |
527 | Historically, either value is correct, but rxvt-unicode adopts the |
528 | Historically, either value is correct, but rxvt-unicode adopts the |
528 | debian policy of using "^?" when unsure, because it's the one and only |
529 | debian policy of using "^?" when unsure, because it's the one and only |
529 | correct choice :). |
530 | correct choice :). |
530 | |
531 | |
531 | Rxvt-unicode tries to inherit the current stty settings and uses the |
532 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
532 | value of `erase' to guess the value for backspace. If rxvt-unicode |
533 | mode: |
533 | wasn't started from a terminal (say, from a menu or by remote shell), |
|
|
534 | then the system value of `erase', which corresponds to CERASE in |
|
|
535 | <termios.h>, will be used (which may not be the same as your stty |
|
|
536 | setting). |
|
|
537 | |
|
|
538 | For starting a new rxvt-unicode: |
|
|
539 | |
534 | |
540 | # use Backspace = ^H |
535 | # use Backspace = ^H |
541 | $ stty erase ^H |
536 | $ stty erase ^H |
542 | $ urxvt |
537 | $ printf "\e[?67h" |
543 | |
538 | |
544 | # use Backspace = ^? |
539 | # use Backspace = ^? |
545 | $ stty erase ^? |
540 | $ stty erase ^? |
546 | $ urxvt |
541 | $ printf "\e[?67l" |
547 | |
|
|
548 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
|
|
549 | |
|
|
550 | For an existing rxvt-unicode: |
|
|
551 | |
|
|
552 | # use Backspace = ^H |
|
|
553 | $ stty erase ^H |
|
|
554 | $ echo -n "^[[36h" |
|
|
555 | |
|
|
556 | # use Backspace = ^? |
|
|
557 | $ stty erase ^? |
|
|
558 | $ echo -n "^[[36l" |
|
|
559 | |
542 | |
560 | This helps satisfy some of the Backspace discrepancies that occur, but |
543 | This helps satisfy some of the Backspace discrepancies that occur, but |
561 | 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 |
562 | properly reflects that. |
545 | properly reflects that. |
563 | |
546 | |
… | |
… | |
579 | use the `keysym' resource to alter the keystrings associated with |
562 | use the `keysym' resource to alter the keystrings associated with |
580 | keysyms. |
563 | keysyms. |
581 | |
564 | |
582 | 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" |
583 | |
566 | |
|
|
567 | URxvt.keysym.Prior: \033[5~ |
|
|
568 | URxvt.keysym.Next: \033[6~ |
584 | URxvt.keysym.Home: \033[1~ |
569 | URxvt.keysym.Home: \033[7~ |
585 | URxvt.keysym.End: \033[4~ |
570 | URxvt.keysym.End: \033[8~ |
586 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
587 | URxvt.keysym.C-slash: \033<C-/> |
|
|
588 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
589 | URxvt.keysym.C-grave: \033<C-`> |
|
|
590 | URxvt.keysym.C-comma: \033<C-,> |
|
|
591 | URxvt.keysym.C-period: \033<C-.> |
|
|
592 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
593 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
594 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
595 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
596 | URxvt.keysym.S-space: \033<S-Space> |
|
|
597 | URxvt.keysym.M-Up: \033<M-Up> |
571 | URxvt.keysym.Up: \033[A |
598 | URxvt.keysym.M-Down: \033<M-Down> |
572 | URxvt.keysym.Down: \033[B |
|
|
573 | URxvt.keysym.Right: \033[C |
599 | URxvt.keysym.M-Left: \033<M-Left> |
574 | URxvt.keysym.Left: \033[D |
600 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
601 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
602 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
603 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
|
|
604 | |
575 | |
605 | See some more examples in the documentation for the keysym resource. |
576 | See some more examples in the documentation for the keysym resource. |
606 | |
577 | |
607 | 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 |
608 | KP_Insert == Insert |
579 | KP_Insert == Insert |
… | |
… | |
755 | keeping a very small window. If somebody pastes something complicated |
726 | keeping a very small window. If somebody pastes something complicated |
756 | (e.g. japanese), I temporarily switch to a larger font. |
727 | (e.g. japanese), I temporarily switch to a larger font. |
757 | |
728 | |
758 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
729 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
759 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
730 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
760 | file for different hosts, for example, on ym main desktop, I use: |
731 | file for different hosts, for example, on my main desktop, I use: |
761 | |
732 | |
762 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
733 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
763 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
734 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
764 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
735 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
765 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
736 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
… | |
… | |
803 | |
774 | |
804 | REMOTE=remotesystem.domain |
775 | REMOTE=remotesystem.domain |
805 | 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" |
806 | |
777 | |
807 | 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 |
808 | $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. |
809 | |
783 | |
810 | 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 |
811 | "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 |
812 | problems arising, which includes wrong keymapping, less and different |
786 | problems arising, which includes wrong keymapping, less and different |
813 | 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 |
… | |
… | |
992 | For scim, use "@im=SCIM". You can see what input method servers are |
966 | For scim, use "@im=SCIM". You can see what input method servers are |
993 | running with this command: |
967 | running with this command: |
994 | |
968 | |
995 | xprop -root XIM_SERVERS |
969 | xprop -root XIM_SERVERS |
996 | |
970 | |
997 | |
|
|
998 | |
|
|
999 | My input method wants <some encoding> but I want UTF-8, what can I do? |
971 | My input method wants <some encoding> but I want UTF-8, what can I do? |
1000 | You can specify separate locales for the input method and the rest of |
972 | You can specify separate locales for the input method and the rest of |
1001 | the terminal, using the resource "imlocale": |
973 | the terminal, using the resource "imlocale": |
1002 | |
974 | |
1003 | URxvt.imlocale: ja_JP.EUC-JP |
975 | URxvt.imlocale: ja_JP.EUC-JP |
… | |
… | |
1021 | I am using Debian GNU/Linux and have a problem... |
993 | I am using Debian GNU/Linux and have a problem... |
1022 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
994 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
1023 | patches that considerably change the behaviour of rxvt-unicode (but |
995 | patches that considerably change the behaviour of rxvt-unicode (but |
1024 | unfortunately this notice has been removed). Before reporting a bug to |
996 | unfortunately this notice has been removed). Before reporting a bug to |
1025 | the original rxvt-unicode author please download and install the genuine |
997 | the original rxvt-unicode author please download and install the genuine |
1026 | version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
998 | version (<http://software.schmorp.de/pkg/rxvt-unicode.html>) and try to |
1027 | the problem. If you cannot, chances are that the problems are specific |
999 | reproduce the problem. If you cannot, chances are that the problems are |
1028 | to Debian GNU/Linux, in which case it should be reported via the Debian |
1000 | specific to Debian GNU/Linux, in which case it should be reported via |
1029 | Bug Tracking System (use "reportbug" to report the bug). |
1001 | the Debian Bug Tracking System (use "reportbug" to report the bug). |
1030 | |
1002 | |
1031 | For other problems that also affect the Debian package, you can and |
1003 | For other problems that also affect the Debian package, you can and |
1032 | probably should use the Debian BTS, too, because, after all, it's also a |
1004 | probably should use the Debian BTS, too, because, after all, it's also a |
1033 | bug in the Debian version and it serves as a reminder for other users |
1005 | bug in the Debian version and it serves as a reminder for other users |
1034 | that might encounter the same issue. |
1006 | that might encounter the same issue. |