… | |
… | |
69 | This tries to create a new terminal, and if fails with exit status 2, |
69 | This tries to create a new terminal, and if fails with exit status 2, |
70 | meaning it couldn't connect to the daemon, it will start the daemon and |
70 | meaning it couldn't connect to the daemon, it will start the daemon and |
71 | re-run the command. Subsequent invocations of the script will re-use the |
71 | re-run the command. Subsequent invocations of the script will re-use the |
72 | existing daemon. |
72 | existing daemon. |
73 | |
73 | |
74 | How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
74 | How do I distinguish whether I'm running rxvt-unicode or a regular |
|
|
75 | xterm? I need this to decide about setting colours etc. |
75 | The original rxvt and rxvt-unicode always export the variable |
76 | The original rxvt and rxvt-unicode always export the variable |
76 | "COLORTERM", so you can check and see if that is set. Note that several |
77 | "COLORTERM", so you can check and see if that is set. Note that several |
77 | programs, JED, slrn, Midnight Commander automatically check this |
78 | programs, JED, slrn, Midnight Commander automatically check this |
78 | variable to decide whether or not to use color. |
79 | variable to decide whether or not to use colour. |
79 | |
80 | |
80 | How do I set the correct, full IP address for the DISPLAY variable? |
81 | How do I set the correct, full IP address for the DISPLAY variable? |
81 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
82 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
82 | insecure mode then it is possible to use the following shell script |
83 | insecure mode then it is possible to use the following shell script |
83 | snippets to correctly set the display. If your version of rxvt-unicode |
84 | snippets to correctly set the display. If your version of rxvt-unicode |
… | |
… | |
157 | 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 |
158 | are defined by things like X11, pseudo terminals, locale support and |
159 | are defined by things like X11, pseudo terminals, locale support and |
159 | unix domain sockets, which are all less portable than C++ itself. |
160 | unix domain sockets, which are all less portable than C++ itself. |
160 | |
161 | |
161 | 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 |
162 | 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 |
163 | 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 |
164 | 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 |
165 | system with a minimal config: |
166 | my system with a minimal config: |
166 | |
167 | |
167 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
168 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
168 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
169 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
169 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
170 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
170 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
171 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
… | |
… | |
180 | No large bloated libraries (of course, none were linked in statically), |
181 | No large bloated libraries (of course, none were linked in statically), |
181 | except maybe libX11 :) |
182 | except maybe libX11 :) |
182 | |
183 | |
183 | Rendering, Font & Look and Feel Issues |
184 | Rendering, Font & Look and Feel Issues |
184 | I can't get transparency working, what am I doing wrong? |
185 | I can't get transparency working, what am I doing wrong? |
185 | First of all, please address all transparency related issues to Sasha |
186 | First of all, transparency isn't officially supported in rxvt-unicode, |
186 | 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 |
187 | 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 |
188 | failed. |
189 | rite of passage: ... and you failed. |
189 | |
190 | |
190 | 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 |
191 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
192 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
192 | |
193 | |
193 | 1. Use transparent mode: |
194 | 1. Use transparent mode: |
194 | |
195 | |
195 | Esetroot wallpaper.jpg |
196 | Esetroot wallpaper.jpg |
196 | urxvt -tr -tint red -sh 40 |
197 | urxvt -tr -tint red -sh 40 |
197 | |
198 | |
198 | 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 |
199 | 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. |
200 | |
203 | |
201 | 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 |
202 | 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 |
203 | your picture with gimp or any other tool: |
206 | your picture with gimp or any other tool: |
204 | |
207 | |
205 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
208 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
206 | urxvt -pixmap "background.jpg;:root" |
209 | urxvt -pixmap "background.jpg;:root" |
207 | |
210 | |
208 | 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 |
209 | are unable to read. |
212 | GDK-PixBuf support, or you are unable to read. |
210 | |
213 | |
211 | 3. Use an ARGB visual: |
214 | 3. Use an ARGB visual: |
212 | |
215 | |
213 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
216 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
214 | |
217 | |
… | |
… | |
312 | For the standard background colour, blinking will actually make the text |
315 | For the standard background colour, blinking will actually make the text |
313 | blink when compiled with "--enable-text-blink". Without |
316 | blink when compiled with "--enable-text-blink". Without |
314 | "--enable-text-blink", the blink attribute will be ignored. |
317 | "--enable-text-blink", the blink attribute will be ignored. |
315 | |
318 | |
316 | On ANSI colours, bold/blink attributes are used to set high-intensity |
319 | On ANSI colours, bold/blink attributes are used to set high-intensity |
317 | foreground/background colors. |
320 | foreground/background colours. |
318 | |
321 | |
319 | color0-7 are the low-intensity colors. |
322 | color0-7 are the low-intensity colours. |
320 | |
323 | |
321 | color8-15 are the corresponding high-intensity colors. |
324 | color8-15 are the corresponding high-intensity colours. |
322 | |
325 | |
323 | I don't like the screen colors. How do I change them? |
326 | I don't like the screen colours. How do I change them? |
324 | You can change the screen colors at run-time using ~/.Xdefaults |
327 | You can change the screen colours at run-time using ~/.Xdefaults |
325 | resources (or as long-options). |
328 | resources (or as long-options). |
326 | |
329 | |
327 | Here are values that are supposed to resemble a VGA screen, including |
330 | Here are values that are supposed to resemble a VGA screen, including |
328 | the murky brown that passes for low-intensity yellow: |
331 | the murky brown that passes for low-intensity yellow: |
329 | |
332 | |
… | |
… | |
343 | URxvt.color12: #0000FF |
346 | URxvt.color12: #0000FF |
344 | URxvt.color13: #FF00FF |
347 | URxvt.color13: #FF00FF |
345 | URxvt.color14: #00FFFF |
348 | URxvt.color14: #00FFFF |
346 | URxvt.color15: #FFFFFF |
349 | URxvt.color15: #FFFFFF |
347 | |
350 | |
348 | And here is a more complete set of non-standard colors. |
351 | And here is a more complete set of non-standard colours. |
349 | |
352 | |
350 | URxvt.cursorColor: #dc74d1 |
353 | URxvt.cursorColor: #dc74d1 |
351 | URxvt.pointerColor: #dc74d1 |
354 | URxvt.pointerColor: #dc74d1 |
352 | URxvt.background: #0e0e0e |
355 | URxvt.background: #0e0e0e |
353 | URxvt.foreground: #4ad5e1 |
356 | URxvt.foreground: #4ad5e1 |
… | |
… | |
525 | |
528 | |
526 | Historically, either value is correct, but rxvt-unicode adopts the |
529 | Historically, either value is correct, but rxvt-unicode adopts the |
527 | 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 |
528 | correct choice :). |
531 | correct choice :). |
529 | |
532 | |
530 | 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 |
531 | value of `erase' to guess the value for backspace. If rxvt-unicode |
534 | mode: |
532 | wasn't started from a terminal (say, from a menu or by remote shell), |
|
|
533 | then the system value of `erase', which corresponds to CERASE in |
|
|
534 | <termios.h>, will be used (which may not be the same as your stty |
|
|
535 | setting). |
|
|
536 | |
|
|
537 | For starting a new rxvt-unicode: |
|
|
538 | |
535 | |
539 | # use Backspace = ^H |
536 | # use Backspace = ^H |
540 | $ stty erase ^H |
537 | $ stty erase ^H |
541 | $ urxvt |
538 | $ echo -n "^[[?67h" |
542 | |
539 | |
543 | # use Backspace = ^? |
540 | # use Backspace = ^? |
544 | $ stty erase ^? |
541 | $ stty erase ^? |
545 | $ urxvt |
|
|
546 | |
|
|
547 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
|
|
548 | |
|
|
549 | For an existing rxvt-unicode: |
|
|
550 | |
|
|
551 | # use Backspace = ^H |
|
|
552 | $ stty erase ^H |
|
|
553 | $ echo -n "^[[36h" |
|
|
554 | |
|
|
555 | # use Backspace = ^? |
|
|
556 | $ stty erase ^? |
|
|
557 | $ echo -n "^[[36l" |
542 | $ echo -n "^[[?67l" |
558 | |
543 | |
559 | This helps satisfy some of the Backspace discrepancies that occur, but |
544 | This helps satisfy some of the Backspace discrepancies that occur, but |
560 | 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 |
561 | properly reflects that. |
546 | properly reflects that. |
562 | |
547 | |
… | |
… | |
650 | develop for myself mostly, so I actually use most of the extensions I |
635 | develop for myself mostly, so I actually use most of the extensions I |
651 | write. |
636 | write. |
652 | |
637 | |
653 | The selection stuff mainly makes the selection perl-error-message aware |
638 | The selection stuff mainly makes the selection perl-error-message aware |
654 | and tells it to convert perl error messages into vi-commands to load the |
639 | and tells it to convert perl error messages into vi-commands to load the |
655 | relevant file and go tot he error line number. |
640 | relevant file and go to the error line number. |
656 | |
641 | |
657 | URxvt.scrollstyle: plain |
642 | URxvt.scrollstyle: plain |
658 | URxvt.secondaryScroll: true |
643 | URxvt.secondaryScroll: true |
659 | |
644 | |
660 | As the documentation says: plain is the preferred scrollbar for the |
645 | As the documentation says: plain is the preferred scrollbar for the |
… | |
… | |
733 | my purposes, it works, and gives a different look, as my normal |
718 | my purposes, it works, and gives a different look, as my normal |
734 | (Non-bold) font is already bold, and I want to see a difference between |
719 | (Non-bold) font is already bold, and I want to see a difference between |
735 | bold and normal fonts. |
720 | bold and normal fonts. |
736 | |
721 | |
737 | Please note that I used the "urxvt" instance name and not the "URxvt" |
722 | Please note that I used the "urxvt" instance name and not the "URxvt" |
738 | class name. Thats because I use different configs for different |
723 | class name. That is because I use different configs for different |
739 | purposes, for example, my IRC window is started with "-name IRC", and |
724 | purposes, for example, my IRC window is started with "-name IRC", and |
740 | uses these defaults: |
725 | uses these defaults: |
741 | |
726 | |
742 | IRC*title: IRC |
727 | IRC*title: IRC |
743 | IRC*geometry: 87x12+535+542 |
728 | IRC*geometry: 87x12+535+542 |
… | |
… | |
754 | keeping a very small window. If somebody pastes something complicated |
739 | keeping a very small window. If somebody pastes something complicated |
755 | (e.g. japanese), I temporarily switch to a larger font. |
740 | (e.g. japanese), I temporarily switch to a larger font. |
756 | |
741 | |
757 | 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 |
758 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
743 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
759 | 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: |
760 | |
745 | |
761 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
746 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
762 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
747 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
763 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
748 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
764 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
749 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
… | |
… | |
1038 | runtime-switchable, too, so there is usually no drawback to enabling |
1023 | runtime-switchable, too, so there is usually no drawback to enabling |
1039 | them, except higher disk and possibly memory usage. The perl interpreter |
1024 | them, except higher disk and possibly memory usage. The perl interpreter |
1040 | should be enabled, as important functionality (menus, selection, likely |
1025 | should be enabled, as important functionality (menus, selection, likely |
1041 | more in the future) depends on it. |
1026 | more in the future) depends on it. |
1042 | |
1027 | |
1043 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
1028 | You should not overwrite the "perl-ext-common" and "perl-ext" resources |
1044 | system-wide (except maybe with "defaults"). This will result in useful |
1029 | system-wide (except maybe with "defaults"). This will result in useful |
1045 | behaviour. If your distribution aims at low memory, add an empty |
1030 | behaviour. If your distribution aims at low memory, add an empty |
1046 | "perl-ext-common" resource to the app-defaults file. This will keep the |
1031 | "perl-ext-common" resource to the app-defaults file. This will keep the |
1047 | perl interpreter disabled until the user enables it. |
1032 | perl interpreter disabled until the user enables it. |
1048 | |
1033 | |
… | |
… | |
1120 | The solution is to upgrade your system or switch to a better one. A |
1105 | The solution is to upgrade your system or switch to a better one. A |
1121 | possibly working workaround is to use a wcwidth implementation like |
1106 | possibly working workaround is to use a wcwidth implementation like |
1122 | |
1107 | |
1123 | http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c |
1108 | http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c |
1124 | |
1109 | |
1125 | I want 256 colors |
|
|
1126 | Are you sure you need 256 colors? 88 colors should be enough for most |
|
|
1127 | purposes. If you really need more, there is an unsupported patch for it |
|
|
1128 | in the doc directory, but please do not ask for it to be applied. |
|
|
1129 | |
|
|