… | |
… | |
4 | Before sending me mail, you could go to IRC: "irc.freenode.net", channel |
4 | Before sending me mail, you could go to IRC: "irc.freenode.net", channel |
5 | "#rxvt-unicode" has some rxvt-unicode enthusiasts that might be |
5 | "#rxvt-unicode" has some rxvt-unicode enthusiasts that might be |
6 | interested in learning about new and exciting problems (but not FAQs :). |
6 | interested in learning about new and exciting problems (but not FAQs :). |
7 | |
7 | |
8 | I use Gentoo, and I have a problem... |
8 | I use Gentoo, and I have a problem... |
9 | There are three big problems with Gentoo Linux: first of all, most if |
9 | There are two big problems with Gentoo Linux: first, most if not all |
10 | not all Gentoo systems are completely broken (missing or mismatched |
10 | Gentoo systems are completely broken (missing or mismatched header |
11 | header files, broken compiler etc. are just the tip of the iceberg); |
11 | files, broken compiler etc. are just the tip of the iceberg); secondly, |
12 | secondly, the Gentoo maintainer thinks it is a good idea to add broken |
12 | it should be called Gentoo GNU/Linux. |
13 | patches to the code; and lastly, it should be called Gentoo GNU/Linux. |
|
|
14 | |
13 | |
15 | For these reasons, it is impossible to support rxvt-unicode on Gentoo. |
14 | For these reasons, it is impossible to support rxvt-unicode on Gentoo. |
16 | Problems appearing on Gentoo systems will usually simply be ignored |
15 | Problems appearing on Gentoo systems will usually simply be ignored |
17 | unless they can be reproduced on non-Gentoo systems. |
16 | unless they can be reproduced on non-Gentoo systems. |
18 | |
17 | |
… | |
… | |
91 | |
90 | |
92 | # Bourne/Korn/POSIX family of shells: |
91 | # Bourne/Korn/POSIX family of shells: |
93 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
92 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
94 | if [ ${TERM:-foo} = xterm ]; then |
93 | if [ ${TERM:-foo} = xterm ]; then |
95 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
94 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
96 | echo -n '^[Z' |
95 | printf "\eZ" |
97 | read term_id |
96 | read term_id |
98 | stty icanon echo |
97 | stty icanon echo |
99 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
98 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
100 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
99 | printf '\e[7n' # query the rxvt we are in for the DISPLAY string |
101 | read DISPLAY # set it in our local shell |
100 | read DISPLAY # set it in our local shell |
102 | fi |
101 | fi |
103 | fi |
102 | fi |
104 | |
103 | |
105 | How do I compile the manual pages on my own? |
104 | 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, |
105 | 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 |
157 | the case of rxvt-unicode this hardly matters, as its portability limits |
159 | are defined by things like X11, pseudo terminals, locale support and |
158 | are defined by things like X11, pseudo terminals, locale support and |
160 | unix domain sockets, which are all less portable than C++ itself. |
159 | unix domain sockets, which are all less portable than C++ itself. |
161 | |
160 | |
162 | Regarding the bloat, see the above question: It's easy to write programs |
161 | 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 |
162 | 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 |
163 | 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 |
164 | is not necessarily the case with GCC. Here is what rxvt links against on |
166 | system with a minimal config: |
165 | my system with a minimal config: |
167 | |
166 | |
168 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
167 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
169 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
168 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
170 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
169 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
171 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
170 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
… | |
… | |
181 | No large bloated libraries (of course, none were linked in statically), |
180 | No large bloated libraries (of course, none were linked in statically), |
182 | except maybe libX11 :) |
181 | except maybe libX11 :) |
183 | |
182 | |
184 | Rendering, Font & Look and Feel Issues |
183 | Rendering, Font & Look and Feel Issues |
185 | I can't get transparency working, what am I doing wrong? |
184 | I can't get transparency working, what am I doing wrong? |
186 | First of all, please address all transparency related issues to Sasha |
185 | 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, |
186 | 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 |
187 | may bug everybody else). Also, if you can't get it working consider it a |
189 | failed. |
188 | rite of passage: ... and you failed. |
190 | |
189 | |
191 | Here are four ways to get transparency. Do read the manpage and option |
190 | 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! |
191 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
193 | |
192 | |
194 | 1. Use transparent mode: |
193 | 1. Use transparent mode: |
195 | |
194 | |
196 | Esetroot wallpaper.jpg |
195 | Esetroot wallpaper.jpg |
197 | urxvt -tr -tint red -sh 40 |
196 | urxvt -tr -tint red -sh 40 |
198 | |
197 | |
199 | That works. If you think it doesn't, you lack transparency and tinting |
198 | That works. If you think it doesn't, you lack transparency and tinting |
200 | support, or you are unable to read. |
199 | support, or you are unable to read. This method requires that the |
|
|
200 | background-setting program sets the _XROOTPMAP_ID or ESETROOT_PMAP_ID |
|
|
201 | property. Compatible programs are Esetroot, hsetroot and feh. |
201 | |
202 | |
202 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
203 | 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 |
204 | to use effects other than tinting and shading: Just shade/tint/whatever |
204 | your picture with gimp or any other tool: |
205 | your picture with gimp or any other tool: |
205 | |
206 | |
206 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
207 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
207 | urxvt -pixmap "background.jpg;:root" |
208 | urxvt -pixmap "background.jpg;:root" |
208 | |
209 | |
209 | That works. If you think it doesn't, you lack libAfterImage or |
210 | That works. If you think it doesn't, you lack GDK-PixBuf support, or you |
210 | GDK-PixBuf support, or you are unable to read. |
211 | are unable to read. |
211 | |
212 | |
212 | 3. Use an ARGB visual: |
213 | 3. Use an ARGB visual: |
213 | |
214 | |
214 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
215 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
215 | |
216 | |
… | |
… | |
427 | We are working on it, in the meantime, as a workaround, use something |
428 | We are working on it, in the meantime, as a workaround, use something |
428 | like: |
429 | like: |
429 | |
430 | |
430 | urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' |
431 | urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' |
431 | |
432 | |
|
|
433 | Why is the cursor now blinking in emacs/vi/...? |
|
|
434 | This is likely caused by your editor/program's use of the "cvvis" |
|
|
435 | terminfo capability. Emacs uses it by default, as well as some versions |
|
|
436 | of vi and possibly other programs. |
|
|
437 | |
|
|
438 | In emacs, you can switch that off by adding this to your ".emacs" file: |
|
|
439 | |
|
|
440 | (setq visible-cursor nil) |
|
|
441 | |
|
|
442 | For other programs, if they do not have an option, your have to remove |
|
|
443 | the "cvvis" capability from the terminfo description. |
|
|
444 | |
|
|
445 | When urxvt first added the blinking cursor option, it didn't add a |
|
|
446 | "cvvis" capability, which served no purpose before. Version 9.21 |
|
|
447 | introduced "cvvis" (and the ability to control blinking independent of |
|
|
448 | cursor shape) for compatibility with other terminals, which |
|
|
449 | traditionally use a blinking cursor for "cvvis". This also reflects the |
|
|
450 | intent of programs such as emacs, who expect "cvvis" to enable a |
|
|
451 | blinking cursor. |
|
|
452 | |
432 | Keyboard, Mouse & User Interaction |
453 | Keyboard, Mouse & User Interaction |
433 | The new selection selects pieces that are too big, how can I select single words? |
454 | The new selection selects pieces that are too big, how can I select single words? |
434 | If you want to select e.g. alphanumeric words, you can use the following |
455 | If you want to select e.g. alphanumeric words, you can use the following |
435 | setting: |
456 | setting: |
436 | |
457 | |
… | |
… | |
461 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
482 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
462 | |
483 | |
463 | This will keep the default extensions, but disable the two popup |
484 | This will keep the default extensions, but disable the two popup |
464 | extensions. Some extensions can also be configured, for example, |
485 | extensions. Some extensions can also be configured, for example, |
465 | scrollback search mode is triggered by M-s. You can move it to any other |
486 | scrollback search mode is triggered by M-s. You can move it to any other |
466 | combination either by setting the searchable-scrollback resource: |
487 | combination by adding a keysym resource that binds the desired |
|
|
488 | combination to the "start" action of "searchable-scrollback" and another |
|
|
489 | one that binds M-s to the "builtin:" action: |
467 | |
490 | |
468 | URxvt.searchable-scrollback: CM-s |
491 | URxvt.keysym.CM-s: searchable-scrollback:start |
|
|
492 | URxvt.keysym.M-s: builtin: |
469 | |
493 | |
470 | The cursor moves when selecting text in the current input line, how do I switch this off? |
494 | The cursor moves when selecting text in the current input line, how do I switch this off? |
471 | See next entry. |
495 | See next entry. |
472 | |
496 | |
473 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
497 | During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
… | |
… | |
480 | You can permanently switch this feature off by disabling the "readline" |
504 | You can permanently switch this feature off by disabling the "readline" |
481 | extension: |
505 | extension: |
482 | |
506 | |
483 | URxvt.perl-ext-common: default,-readline |
507 | URxvt.perl-ext-common: default,-readline |
484 | |
508 | |
485 | My numerical keypad acts weird and generates differing output? |
509 | My numeric keypad acts weird and generates differing output? |
486 | Some Debian GNUL/Linux users seem to have this problem, although no |
510 | Some Debian GNU/Linux users seem to have this problem, although no |
487 | specific details were reported so far. It is possible that this is |
511 | specific details were reported so far. It is possible that this is |
488 | caused by the wrong "TERM" setting, although the details of whether and |
512 | caused by the wrong "TERM" setting, although the details of whether and |
489 | how this can happen are unknown, as "TERM=rxvt" should offer a |
513 | how this can happen are unknown, as "TERM=rxvt" should offer a |
490 | compatible keymap. See the answer to the previous question, and please |
514 | compatible keymap. See the answer to the previous question, and please |
491 | report if that helped. |
515 | report if that helped. |
492 | |
516 | |
493 | My Compose (Multi_key) key is no longer working. |
517 | My Compose (Multi_key) key is no longer working. |
494 | The most common causes for this are that either your locale is not set |
518 | The most common causes for this are that either your locale is not set |
495 | correctly, or you specified a preeditStyle that is not supported by your |
519 | correctly, or you specified a preeditType that is not supported by your |
496 | input method. For example, if you specified OverTheSpot and your input |
520 | input method. For example, if you specified OverTheSpot and your input |
497 | method (e.g. the default input method handling Compose keys) does not |
521 | method (e.g. the default input method handling Compose keys) does not |
498 | support this (for instance because it is not visual), then rxvt-unicode |
522 | support this (for instance because it is not visual), then rxvt-unicode |
499 | will continue without an input method. |
523 | will continue without an input method. |
500 | |
524 | |
501 | In this case either do not specify a preeditStyle or specify more than |
525 | In this case either do not specify a preeditType or specify more than |
502 | one pre-edit style, such as OverTheSpot,Root,None. |
526 | one pre-edit style, such as OverTheSpot,Root,None. |
503 | |
527 | |
504 | If it still doesn't work, then maybe your input method doesn't support |
528 | If it still doesn't work, then maybe your input method doesn't support |
505 | compose sequences - to fall back to the built-in one, make sure you |
529 | compose sequences - to fall back to the built-in one, make sure you |
506 | don't specify an input method via "-im" or "XMODIFIERS". |
530 | don't specify an input method via "-im" or "XMODIFIERS". |
… | |
… | |
512 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
536 | other codes, too, such as "Ctrl-Shift-1-d" to type the default telnet |
513 | escape character and so on. |
537 | escape character and so on. |
514 | |
538 | |
515 | Mouse cut/paste suddenly no longer works. |
539 | Mouse cut/paste suddenly no longer works. |
516 | Make sure that mouse reporting is actually turned off since killing some |
540 | 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 |
541 | 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 |
542 | 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 |
543 | see if cut/paste works when the Alt or Shift keys are pressed. |
520 | depressed. |
|
|
521 | |
544 | |
522 | What's with the strange Backspace/Delete key behaviour? |
545 | What's with the strange Backspace/Delete key behaviour? |
523 | Assuming that the physical Backspace key corresponds to the Backspace |
546 | Assuming that the physical Backspace key corresponds to the Backspace |
524 | keysym (not likely for Linux ... see the following question) there are |
547 | keysym (not likely for Linux ... see the following question) there are |
525 | two standard values that can be used for Backspace: "^H" and "^?". |
548 | two standard values that can be used for Backspace: "^H" and "^?". |
… | |
… | |
531 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
554 | It is possible to toggle between "^H" and "^?" with the DECBKM private |
532 | mode: |
555 | mode: |
533 | |
556 | |
534 | # use Backspace = ^H |
557 | # use Backspace = ^H |
535 | $ stty erase ^H |
558 | $ stty erase ^H |
536 | $ echo -n "^[[?67h" |
559 | $ printf "\e[?67h" |
537 | |
560 | |
538 | # use Backspace = ^? |
561 | # use Backspace = ^? |
539 | $ stty erase ^? |
562 | $ stty erase ^? |
540 | $ echo -n "^[[?67l" |
563 | $ printf "\e[?67l" |
541 | |
564 | |
542 | This helps satisfy some of the Backspace discrepancies that occur, but |
565 | This helps satisfy some of the Backspace discrepancies that occur, but |
543 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
566 | if you use Backspace = "^H", make sure that the termcap/terminfo value |
544 | properly reflects that. |
567 | properly reflects that. |
545 | |
568 | |
… | |
… | |
561 | use the `keysym' resource to alter the keystrings associated with |
584 | use the `keysym' resource to alter the keystrings associated with |
562 | keysyms. |
585 | keysyms. |
563 | |
586 | |
564 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
587 | Here's an example for a URxvt session started using "urxvt -name URxvt" |
565 | |
588 | |
|
|
589 | URxvt.keysym.Prior: \033[5~ |
|
|
590 | URxvt.keysym.Next: \033[6~ |
566 | URxvt.keysym.Home: \033[1~ |
591 | URxvt.keysym.Home: \033[7~ |
567 | URxvt.keysym.End: \033[4~ |
592 | 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> |
593 | URxvt.keysym.Up: \033[A |
580 | URxvt.keysym.M-Down: \033<M-Down> |
594 | URxvt.keysym.Down: \033[B |
|
|
595 | URxvt.keysym.Right: \033[C |
581 | URxvt.keysym.M-Left: \033<M-Left> |
596 | 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 | |
597 | |
587 | See some more examples in the documentation for the keysym resource. |
598 | See some more examples in the documentation for the keysym resource. |
588 | |
599 | |
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 |
600 | 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 |
601 | KP_Insert == Insert |
… | |
… | |
817 | See next entry. |
828 | See next entry. |
818 | |
829 | |
819 | I need a termcap file entry. |
830 | I need a termcap file entry. |
820 | One reason you might want this is that some distributions or operating |
831 | One reason you might want this is that some distributions or operating |
821 | systems still compile some programs using the long-obsoleted termcap |
832 | systems still compile some programs using the long-obsoleted termcap |
822 | library (Fedora Core's bash is one example) and rely on a termcap entry |
833 | library (Fedora's bash is one example) and rely on a termcap entry for |
823 | for "rxvt-unicode". |
834 | "rxvt-unicode". |
824 | |
835 | |
825 | You could use rxvt's termcap entry with reasonable results in many |
836 | You could use rxvt's termcap entry with reasonable results in many |
826 | cases. You can also create a termcap entry by using terminfo's infocmp |
837 | cases. You can also create a termcap entry by using terminfo's infocmp |
827 | program like this: |
838 | program like this: |
828 | |
839 | |
… | |
… | |
851 | Why doesn't vim/emacs etc. make use of italic? |
862 | Why doesn't vim/emacs etc. make use of italic? |
852 | See next entry. |
863 | See next entry. |
853 | |
864 | |
854 | Why are the secondary screen-related options not working properly? |
865 | Why are the secondary screen-related options not working properly? |
855 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
866 | Make sure you are using "TERM=rxvt-unicode". Some pre-packaged |
856 | distributions (most notably Debian GNU/Linux) break rxvt-unicode by |
867 | distributions break rxvt-unicode by setting "TERM" to "rxvt", which |
857 | setting "TERM" to "rxvt", which doesn't have these extra features. |
868 | doesn't have these extra features. Unfortunately, some of these |
858 | Unfortunately, some of these (most notably, again, Debian GNU/Linux) |
|
|
859 | furthermore fail to even install the "rxvt-unicode" terminfo file, so |
869 | furthermore fail to even install the "rxvt-unicode" terminfo file, so |
860 | you will need to install it on your own (See the question When I log-in |
870 | you will need to install it on your own (See the question When I log-in |
861 | to another system it tells me about missing terminfo data? on how to do |
871 | to another system it tells me about missing terminfo data? on how to do |
862 | this). |
872 | this). |
863 | |
873 | |
… | |
… | |
974 | For scim, use "@im=SCIM". You can see what input method servers are |
984 | For scim, use "@im=SCIM". You can see what input method servers are |
975 | running with this command: |
985 | running with this command: |
976 | |
986 | |
977 | xprop -root XIM_SERVERS |
987 | xprop -root XIM_SERVERS |
978 | |
988 | |
979 | |
|
|
980 | |
|
|
981 | My input method wants <some encoding> but I want UTF-8, what can I do? |
989 | My input method wants <some encoding> but I want UTF-8, what can I do? |
982 | You can specify separate locales for the input method and the rest of |
990 | You can specify separate locales for the input method and the rest of |
983 | the terminal, using the resource "imlocale": |
991 | the terminal, using the resource "imlocale": |
984 | |
992 | |
985 | URxvt.imlocale: ja_JP.EUC-JP |
993 | URxvt.imlocale: ja_JP.EUC-JP |
… | |
… | |
998 | cannot be completely avoided even if both sides cooperate. |
1006 | cannot be completely avoided even if both sides cooperate. |
999 | |
1007 | |
1000 | So the only workaround is not to kill your Input Method Servers. |
1008 | So the only workaround is not to kill your Input Method Servers. |
1001 | |
1009 | |
1002 | Operating Systems / Package Maintaining |
1010 | Operating Systems / Package Maintaining |
1003 | I am using Debian GNU/Linux and have a problem... |
|
|
1004 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
1005 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
1006 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
1007 | the original rxvt-unicode author please download and install the genuine |
|
|
1008 | version (<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
|
|
1009 | the problem. If you cannot, chances are that the problems are specific |
|
|
1010 | to Debian GNU/Linux, in which case it should be reported via the Debian |
|
|
1011 | Bug Tracking System (use "reportbug" to report the bug). |
|
|
1012 | |
|
|
1013 | 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 |
|
|
1015 | bug in the Debian version and it serves as a reminder for other users |
|
|
1016 | that might encounter the same issue. |
|
|
1017 | |
|
|
1018 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1011 | I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
1019 | You should build one binary with the default options. configure now |
1012 | You should build one binary with the default options. configure now |
1020 | enables most useful options, and the trend goes to making them |
1013 | enables most useful options, and the trend goes to making them |
1021 | runtime-switchable, too, so there is usually no drawback to enabling |
1014 | runtime-switchable, too, so there is usually no drawback to enabling |
1022 | them, except higher disk and possibly memory usage. The perl interpreter |
1015 | them, except higher disk and possibly memory usage. The perl interpreter |