… | |
… | |
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 libAfterImage or |
210 | are unable to read. |
212 | GDK-PixBuf support, or you 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 |
215 | |
217 | |
… | |
… | |
526 | |
528 | |
527 | Historically, either value is correct, but rxvt-unicode adopts the |
529 | Historically, either value is correct, but rxvt-unicode adopts the |
528 | debian policy of using "^?" when unsure, because it's the one and only |
530 | debian policy of using "^?" when unsure, because it's the one and only |
529 | correct choice :). |
531 | correct choice :). |
530 | |
532 | |
531 | Rxvt-unicode tries to inherit the current stty settings and uses the |
533 | 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 |
534 | 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 | |
535 | |
540 | # use Backspace = ^H |
536 | # use Backspace = ^H |
541 | $ stty erase ^H |
537 | $ stty erase ^H |
542 | $ urxvt |
538 | $ echo -n "^[[?67h" |
543 | |
539 | |
544 | # use Backspace = ^? |
540 | # use Backspace = ^? |
545 | $ stty erase ^? |
541 | $ stty erase ^? |
546 | $ urxvt |
|
|
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" |
542 | $ echo -n "^[[?67l" |
559 | |
543 | |
560 | This helps satisfy some of the Backspace discrepancies that occur, but |
544 | This helps satisfy some of the Backspace discrepancies that occur, but |
561 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
545 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
562 | properly reflects that. |
546 | properly reflects that. |
563 | |
547 | |
… | |
… | |
755 | keeping a very small window. If somebody pastes something complicated |
739 | keeping a very small window. If somebody pastes something complicated |
756 | (e.g. japanese), I temporarily switch to a larger font. |
740 | (e.g. japanese), I temporarily switch to a larger font. |
757 | |
741 | |
758 | The above is all in my ".Xdefaults" (I don't use ".Xresources" nor |
742 | 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" |
743 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
760 | file for different hosts, for example, on ym main desktop, I use: |
744 | file for different hosts, for example, on my main desktop, I use: |
761 | |
745 | |
762 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
746 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
763 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
747 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
764 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
748 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
765 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
749 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |