… | |
… | |
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 GDK-PixBuf support, or you |
209 | are unable to read. |
212 | 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 |
… | |
… | |
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 |
… | |
… | |
498 | will continue without an input method. |
501 | will continue without an input method. |
499 | |
502 | |
500 | In this case either do not specify a preeditStyle or specify more than |
503 | In this case either do not specify a preeditStyle or specify more than |
501 | one pre-edit style, such as OverTheSpot,Root,None. |
504 | one pre-edit style, such as OverTheSpot,Root,None. |
502 | |
505 | |
|
|
506 | If it still doesn't work, then maybe your input method doesn't support |
|
|
507 | compose sequences - to fall back to the built-in one, make sure you |
|
|
508 | don't specify an input method via "-im" or "XMODIFIERS". |
|
|
509 | |
503 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
510 | I cannot type "Ctrl-Shift-2" to get an ASCII NUL character due to ISO 14755 |
504 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
511 | Either try "Ctrl-2" alone (it often is mapped to ASCII NUL even on |
505 | international keyboards) or simply use ISO 14755 support to your |
512 | international keyboards) or simply use ISO 14755 support to your |
506 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
513 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for |
507 | 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 |
508 | escape character and so on. |
515 | escape character and so on. |
509 | |
516 | |
510 | Mouse cut/paste suddenly no longer works. |
517 | Mouse cut/paste suddenly no longer works. |
511 | 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 |
512 | 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 |
513 | 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 |
514 | 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. |
515 | depressed. |
|
|
516 | |
522 | |
517 | What's with the strange Backspace/Delete key behaviour? |
523 | What's with the strange Backspace/Delete key behaviour? |
518 | Assuming that the physical Backspace key corresponds to the Backspace |
524 | Assuming that the physical Backspace key corresponds to the Backspace |
519 | keysym (not likely for Linux ... see the following question) there are |
525 | keysym (not likely for Linux ... see the following question) there are |
520 | two standard values that can be used for Backspace: "^H" and "^?". |
526 | two standard values that can be used for Backspace: "^H" and "^?". |
521 | |
527 | |
522 | Historically, either value is correct, but rxvt-unicode adopts the |
528 | Historically, either value is correct, but rxvt-unicode adopts the |
523 | 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 |
524 | correct choice :). |
530 | correct choice :). |
525 | |
531 | |
526 | 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 |
527 | value of `erase' to guess the value for backspace. If rxvt-unicode |
533 | mode: |
528 | wasn't started from a terminal (say, from a menu or by remote shell), |
|
|
529 | then the system value of `erase', which corresponds to CERASE in |
|
|
530 | <termios.h>, will be used (which may not be the same as your stty |
|
|
531 | setting). |
|
|
532 | |
|
|
533 | For starting a new rxvt-unicode: |
|
|
534 | |
534 | |
535 | # use Backspace = ^H |
535 | # use Backspace = ^H |
536 | $ stty erase ^H |
536 | $ stty erase ^H |
537 | $ urxvt |
537 | $ echo -n "^[[?67h" |
538 | |
538 | |
539 | # use Backspace = ^? |
539 | # use Backspace = ^? |
540 | $ stty erase ^? |
540 | $ stty erase ^? |
541 | $ urxvt |
|
|
542 | |
|
|
543 | Toggle with "ESC [ 36 h" / "ESC [ 36 l". |
|
|
544 | |
|
|
545 | For an existing rxvt-unicode: |
|
|
546 | |
|
|
547 | # use Backspace = ^H |
|
|
548 | $ stty erase ^H |
|
|
549 | $ echo -n "^[[36h" |
|
|
550 | |
|
|
551 | # use Backspace = ^? |
|
|
552 | $ stty erase ^? |
|
|
553 | $ echo -n "^[[36l" |
541 | $ echo -n "^[[?67l" |
554 | |
542 | |
555 | This helps satisfy some of the Backspace discrepancies that occur, but |
543 | This helps satisfy some of the Backspace discrepancies that occur, but |
556 | 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 |
557 | properly reflects that. |
545 | properly reflects that. |
558 | |
546 | |
… | |
… | |
574 | use the `keysym' resource to alter the keystrings associated with |
562 | use the `keysym' resource to alter the keystrings associated with |
575 | keysyms. |
563 | keysyms. |
576 | |
564 | |
577 | 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" |
578 | |
566 | |
|
|
567 | URxvt.keysym.Prior: \033[5~ |
|
|
568 | URxvt.keysym.Next: \033[6~ |
579 | URxvt.keysym.Home: \033[1~ |
569 | URxvt.keysym.Home: \033[7~ |
580 | URxvt.keysym.End: \033[4~ |
570 | URxvt.keysym.End: \033[8~ |
581 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
582 | URxvt.keysym.C-slash: \033<C-/> |
|
|
583 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
584 | URxvt.keysym.C-grave: \033<C-`> |
|
|
585 | URxvt.keysym.C-comma: \033<C-,> |
|
|
586 | URxvt.keysym.C-period: \033<C-.> |
|
|
587 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
588 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
589 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
590 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
591 | URxvt.keysym.S-space: \033<S-Space> |
|
|
592 | URxvt.keysym.M-Up: \033<M-Up> |
571 | URxvt.keysym.Up: \033[A |
593 | URxvt.keysym.M-Down: \033<M-Down> |
572 | URxvt.keysym.Down: \033[B |
|
|
573 | URxvt.keysym.Right: \033[C |
594 | URxvt.keysym.M-Left: \033<M-Left> |
574 | URxvt.keysym.Left: \033[D |
595 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
596 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
597 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
598 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
|
|
599 | |
575 | |
600 | See some more examples in the documentation for the keysym resource. |
576 | See some more examples in the documentation for the keysym resource. |
601 | |
577 | |
602 | 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 |
603 | KP_Insert == Insert |
579 | KP_Insert == Insert |
… | |
… | |
646 | develop for myself mostly, so I actually use most of the extensions I |
622 | develop for myself mostly, so I actually use most of the extensions I |
647 | write. |
623 | write. |
648 | |
624 | |
649 | The selection stuff mainly makes the selection perl-error-message aware |
625 | The selection stuff mainly makes the selection perl-error-message aware |
650 | and tells it to convert perl error messages into vi-commands to load the |
626 | and tells it to convert perl error messages into vi-commands to load the |
651 | relevant file and go tot he error line number. |
627 | relevant file and go to the error line number. |
652 | |
628 | |
653 | URxvt.scrollstyle: plain |
629 | URxvt.scrollstyle: plain |
654 | URxvt.secondaryScroll: true |
630 | URxvt.secondaryScroll: true |
655 | |
631 | |
656 | As the documentation says: plain is the preferred scrollbar for the |
632 | As the documentation says: plain is the preferred scrollbar for the |
… | |
… | |
729 | my purposes, it works, and gives a different look, as my normal |
705 | my purposes, it works, and gives a different look, as my normal |
730 | (Non-bold) font is already bold, and I want to see a difference between |
706 | (Non-bold) font is already bold, and I want to see a difference between |
731 | bold and normal fonts. |
707 | bold and normal fonts. |
732 | |
708 | |
733 | Please note that I used the "urxvt" instance name and not the "URxvt" |
709 | Please note that I used the "urxvt" instance name and not the "URxvt" |
734 | class name. Thats because I use different configs for different |
710 | class name. That is because I use different configs for different |
735 | purposes, for example, my IRC window is started with "-name IRC", and |
711 | purposes, for example, my IRC window is started with "-name IRC", and |
736 | uses these defaults: |
712 | uses these defaults: |
737 | |
713 | |
738 | IRC*title: IRC |
714 | IRC*title: IRC |
739 | IRC*geometry: 87x12+535+542 |
715 | IRC*geometry: 87x12+535+542 |
… | |
… | |
743 | IRC*boldFont: suxuseuro |
719 | IRC*boldFont: suxuseuro |
744 | IRC*colorBD: white |
720 | IRC*colorBD: white |
745 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
721 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
746 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
722 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
747 | |
723 | |
748 | "Alt-Shift-1" and "Alt-Shift-2" switch between two different font sizes. |
724 | "Alt-Ctrl-1" and "Alt-Ctrl-2" switch between two different font sizes. |
749 | "suxuseuro" allows me to keep an eye (and actually read) stuff while |
725 | "suxuseuro" allows me to keep an eye (and actually read) stuff while |
750 | keeping a very small window. If somebody pastes something complicated |
726 | keeping a very small window. If somebody pastes something complicated |
751 | (e.g. japanese), I temporarily switch to a larger font. |
727 | (e.g. japanese), I temporarily switch to a larger font. |
752 | |
728 | |
753 | 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 |
754 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
730 | "xrdb"). I also have some resources in a separate ".Xdefaults-hostname" |
755 | 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: |
756 | |
732 | |
757 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
733 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
758 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
734 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
759 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
735 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
760 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
736 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
… | |
… | |
789 | The terminal description used by rxvt-unicode is not as widely available |
765 | The terminal description used by rxvt-unicode is not as widely available |
790 | as that for xterm, or even rxvt (for which the same problem often |
766 | as that for xterm, or even rxvt (for which the same problem often |
791 | arises). |
767 | arises). |
792 | |
768 | |
793 | The correct solution for this problem is to install the terminfo, this |
769 | The correct solution for this problem is to install the terminfo, this |
794 | can be done like this (with ncurses' infocmp and works as user and |
770 | can be done by simply installing rxvt-unicode on the remote system as |
795 | admin): |
771 | well (in case you have a nice package manager ready), or you can install |
|
|
772 | the terminfo database manually like this (with ncurses infocmp. works as |
|
|
773 | user and root): |
796 | |
774 | |
797 | REMOTE=remotesystem.domain |
775 | REMOTE=remotesystem.domain |
798 | 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" |
799 | |
777 | |
800 | ... or by installing rxvt-unicode normally on the remote system, |
|
|
801 | |
|
|
802 | 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 |
803 | $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. |
804 | |
783 | |
805 | 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 |
806 | "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 |
807 | problems arising, which includes wrong keymapping, less and different |
786 | problems arising, which includes wrong keymapping, less and different |
808 | 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 |
… | |
… | |
814 | |
793 | |
815 | URxvt.termName: rxvt |
794 | URxvt.termName: rxvt |
816 | |
795 | |
817 | If you don't plan to use rxvt (quite common...) you could also replace |
796 | If you don't plan to use rxvt (quite common...) you could also replace |
818 | the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". |
797 | the rxvt terminfo file with the rxvt-unicode one and use "TERM=rxvt". |
|
|
798 | |
|
|
799 | nano fails with "Error opening terminal: rxvt-unicode" |
|
|
800 | This exceptionally confusing and useless error message is printed by |
|
|
801 | nano when it can't find the terminfo database. Nothing is wrong with |
|
|
802 | your terminal, read the previous answer for a solution. |
819 | |
803 | |
820 | "tic" outputs some error when compiling the terminfo entry. |
804 | "tic" outputs some error when compiling the terminfo entry. |
821 | Most likely it's the empty definition for "enacs=". Just replace it by |
805 | Most likely it's the empty definition for "enacs=". Just replace it by |
822 | "enacs=\E[0@" and try again. |
806 | "enacs=\E[0@" and try again. |
823 | |
807 | |
… | |
… | |
1011 | I am using Debian GNU/Linux and have a problem... |
995 | I am using Debian GNU/Linux and have a problem... |
1012 | 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 |
1013 | patches that considerably change the behaviour of rxvt-unicode (but |
997 | patches that considerably change the behaviour of rxvt-unicode (but |
1014 | unfortunately this notice has been removed). Before reporting a bug to |
998 | unfortunately this notice has been removed). Before reporting a bug to |
1015 | the original rxvt-unicode author please download and install the genuine |
999 | the original rxvt-unicode author please download and install the genuine |
1016 | version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
1000 | version (<http://software.schmorp.de/pkg/rxvt-unicode.html>) and try to |
1017 | 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 |
1018 | 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 |
1019 | Bug Tracking System (use "reportbug" to report the bug). |
1003 | the Debian Bug Tracking System (use "reportbug" to report the bug). |
1020 | |
1004 | |
1021 | 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 |
1022 | 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 |
1023 | 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 |
1024 | that might encounter the same issue. |
1008 | that might encounter the same issue. |
… | |
… | |
1029 | runtime-switchable, too, so there is usually no drawback to enabling |
1013 | runtime-switchable, too, so there is usually no drawback to enabling |
1030 | them, except higher disk and possibly memory usage. The perl interpreter |
1014 | them, except higher disk and possibly memory usage. The perl interpreter |
1031 | should be enabled, as important functionality (menus, selection, likely |
1015 | should be enabled, as important functionality (menus, selection, likely |
1032 | more in the future) depends on it. |
1016 | more in the future) depends on it. |
1033 | |
1017 | |
1034 | You should not overwrite the "perl-ext-common" snd "perl-ext" resources |
1018 | You should not overwrite the "perl-ext-common" and "perl-ext" resources |
1035 | system-wide (except maybe with "defaults"). This will result in useful |
1019 | system-wide (except maybe with "defaults"). This will result in useful |
1036 | behaviour. If your distribution aims at low memory, add an empty |
1020 | behaviour. If your distribution aims at low memory, add an empty |
1037 | "perl-ext-common" resource to the app-defaults file. This will keep the |
1021 | "perl-ext-common" resource to the app-defaults file. This will keep the |
1038 | perl interpreter disabled until the user enables it. |
1022 | perl interpreter disabled until the user enables it. |
1039 | |
1023 | |