… | |
… | |
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 | |
… | |
… | |
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 "^?". |
… | |
… | |
561 | use the `keysym' resource to alter the keystrings associated with |
562 | use the `keysym' resource to alter the keystrings associated with |
562 | keysyms. |
563 | keysyms. |
563 | |
564 | |
564 | 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" |
565 | |
566 | |
|
|
567 | URxvt.keysym.Prior: \033[5~ |
|
|
568 | URxvt.keysym.Next: \033[6~ |
566 | URxvt.keysym.Home: \033[1~ |
569 | URxvt.keysym.Home: \033[7~ |
567 | URxvt.keysym.End: \033[4~ |
570 | URxvt.keysym.End: \033[8~ |
568 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
569 | URxvt.keysym.C-slash: \033<C-/> |
|
|
570 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
571 | URxvt.keysym.C-grave: \033<C-`> |
|
|
572 | URxvt.keysym.C-comma: \033<C-,> |
|
|
573 | URxvt.keysym.C-period: \033<C-.> |
|
|
574 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
575 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
576 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
577 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
578 | URxvt.keysym.S-space: \033<S-Space> |
|
|
579 | URxvt.keysym.M-Up: \033<M-Up> |
571 | URxvt.keysym.Up: \033[A |
580 | URxvt.keysym.M-Down: \033<M-Down> |
572 | URxvt.keysym.Down: \033[B |
|
|
573 | URxvt.keysym.Right: \033[C |
581 | URxvt.keysym.M-Left: \033<M-Left> |
574 | URxvt.keysym.Left: \033[D |
582 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
583 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
584 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
585 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
|
|
586 | |
575 | |
587 | See some more examples in the documentation for the keysym resource. |
576 | See some more examples in the documentation for the keysym resource. |
588 | |
577 | |
589 | 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 |
590 | KP_Insert == Insert |
579 | KP_Insert == Insert |
… | |
… | |
1003 | I am using Debian GNU/Linux and have a problem... |
992 | I am using Debian GNU/Linux and have a problem... |
1004 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
993 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
1005 | patches that considerably change the behaviour of rxvt-unicode (but |
994 | patches that considerably change the behaviour of rxvt-unicode (but |
1006 | unfortunately this notice has been removed). Before reporting a bug to |
995 | unfortunately this notice has been removed). Before reporting a bug to |
1007 | the original rxvt-unicode author please download and install the genuine |
996 | the original rxvt-unicode author please download and install the genuine |
1008 | version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
997 | version (<http://software.schmorp.de/pkg/rxvt-unicode.html>) and try to |
1009 | the problem. If you cannot, chances are that the problems are specific |
998 | reproduce the problem. If you cannot, chances are that the problems are |
1010 | to Debian GNU/Linux, in which case it should be reported via the Debian |
999 | specific to Debian GNU/Linux, in which case it should be reported via |
1011 | Bug Tracking System (use "reportbug" to report the bug). |
1000 | the Debian Bug Tracking System (use "reportbug" to report the bug). |
1012 | |
1001 | |
1013 | For other problems that also affect the Debian package, you can and |
1002 | For other problems that also affect the Debian package, you can and |
1014 | probably should use the Debian BTS, too, because, after all, it's also a |
1003 | probably should use the Debian BTS, too, because, after all, it's also a |
1015 | bug in the Debian version and it serves as a reminder for other users |
1004 | bug in the Debian version and it serves as a reminder for other users |
1016 | that might encounter the same issue. |
1005 | that might encounter the same issue. |