… | |
… | |
658 | |
658 | |
659 | |
659 | |
660 | |
660 | |
661 | =head2 Terminal Configuration |
661 | =head2 Terminal Configuration |
662 | |
662 | |
|
|
663 | =head3 Can I see a typical configuration? |
|
|
664 | |
|
|
665 | The default configuration tries to be xterm-like, which I don't like that |
|
|
666 | much, but it's least surprise to regular users. |
|
|
667 | |
|
|
668 | As a rxvt or rxvt-unicode user, you are practically supposed to invest |
|
|
669 | time into customising your terminal. To get you started, here is the |
|
|
670 | author's .Xdefaults entries, with comments on what they do. It's certainly |
|
|
671 | not I<typical>, but what's typical... |
|
|
672 | |
|
|
673 | URxvt.cutchars: "()*,<>[]{}|' |
|
|
674 | URxvt.print-pipe: cat >/tmp/xxx |
|
|
675 | |
|
|
676 | These are just for testing stuff. |
|
|
677 | |
|
|
678 | URxvt.imLocale: ja_JP.UTF-8 |
|
|
679 | URxvt.preeditType: OnTheSpot,None |
|
|
680 | |
|
|
681 | This tells rxvt-unicode to use a special locale when communicating with |
|
|
682 | the X Input Method, and also tells it to only use the OnTheSpot pre-edit |
|
|
683 | type, which requires the C<xim-onthespot> perl extension but rewards me |
|
|
684 | with correct-looking fonts. |
|
|
685 | |
|
|
686 | URxvt.perl-lib: /root/lib/urxvt |
|
|
687 | URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard |
|
|
688 | URxvt.selection.pattern-0: ( at .*? line \\d+) |
|
|
689 | URxvt.selection.pattern-1: ^(/[^:]+):\ |
|
|
690 | URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/ |
|
|
691 | URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/ |
|
|
692 | |
|
|
693 | This is my perl configuration. The first two set the perl library |
|
|
694 | directory and also tells urxvt to use a large number of extensions. I |
|
|
695 | develop for myself mostly, so I actually use most of the extensions I |
|
|
696 | write. |
|
|
697 | |
|
|
698 | The selection stuff mainly makes the selection perl-error-message aware |
|
|
699 | and tells it to convert pelr error mssages into vi-commands to load the |
|
|
700 | relevant file and go tot he error line number. |
|
|
701 | |
|
|
702 | URxvt.scrollstyle: plain |
|
|
703 | URxvt.secondaryScroll: true |
|
|
704 | |
|
|
705 | As the documentation says: plain is the preferred scrollbar for the |
|
|
706 | author. The C<secondaryScroll> confgiures urxvt to scroll in full-screen |
|
|
707 | apps, like screen, so lines scorlled out of screen end up in urxvt's |
|
|
708 | scrollback buffer. |
|
|
709 | |
|
|
710 | URxvt.background: #000000 |
|
|
711 | URxvt.foreground: gray90 |
|
|
712 | URxvt.color7: gray90 |
|
|
713 | URxvt.colorBD: #ffffff |
|
|
714 | URxvt.cursorColor: #e0e080 |
|
|
715 | URxvt.throughColor: #8080f0 |
|
|
716 | URxvt.highlightColor: #f0f0f0 |
|
|
717 | |
|
|
718 | Some colours. Not sure which ones are being used or even non-defaults, but |
|
|
719 | these are in my .Xdefaults. Most notably, they set foreground/background |
|
|
720 | to light gray/black, and also make sure that the colour 7 matches the |
|
|
721 | default foreground colour. |
|
|
722 | |
|
|
723 | URxvt.underlineColor: yellow |
|
|
724 | |
|
|
725 | Another colour, makes underline lines look different. Sometimes hurts, but |
|
|
726 | is mostly a nice effect. |
|
|
727 | |
|
|
728 | URxvt.geometry: 154x36 |
|
|
729 | URxvt.loginShell: false |
|
|
730 | URxvt.meta: ignore |
|
|
731 | URxvt.utmpInhibit: true |
|
|
732 | |
|
|
733 | Uh, well, should be mostly self-explanatory. By specifying some defaults |
|
|
734 | manually, I can quickly switch them for testing. |
|
|
735 | |
|
|
736 | URxvt.saveLines: 8192 |
|
|
737 | |
|
|
738 | A large scrollback buffer is essential. Really. |
|
|
739 | |
|
|
740 | URxvt.mapAlert: true |
|
|
741 | |
|
|
742 | The only case I use it is for my IRC window, which I like to keep |
|
|
743 | iconified till people msg me (which beeps). |
|
|
744 | |
|
|
745 | URxvt.visualBell: true |
|
|
746 | |
|
|
747 | The audible bell is often annoying, especially when in a crowd. |
|
|
748 | |
|
|
749 | URxvt.insecure: true |
|
|
750 | |
|
|
751 | Please don't hack my mutt! Ooops... |
|
|
752 | |
|
|
753 | URxvt.pastableTabs: false |
|
|
754 | |
|
|
755 | I once thought this is a great idea. |
|
|
756 | |
|
|
757 | urxvt.font: 9x15bold,\ |
|
|
758 | -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\ |
|
|
759 | -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \ |
|
|
760 | [codeset=JISX0208]xft:Kochi Gothic, \ |
|
|
761 | xft:Bitstream Vera Sans Mono:autohint=true, \ |
|
|
762 | xft:Code2000:antialias=false |
|
|
763 | urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
|
|
764 | urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
765 | urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
766 | |
|
|
767 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
|
|
768 | overwhelmed. A special note: the C<9x15bold> mentioend above is actually |
|
|
769 | the version from XFree-3.3, as XFree-4 replaced it by a totally different |
|
|
770 | font (different glyphs for C<;> and many other harmless characters), |
|
|
771 | while the second font is actually the C<9x15bold> from XFree4/XOrg. The |
|
|
772 | bold version has less chars than the medium version, so I use it for rare |
|
|
773 | characters, too. Whene ditign sources with vim, I use italic for comments |
|
|
774 | and other stuff, which looks quite good with Bitstream Vera anti-aliased. |
|
|
775 | |
|
|
776 | Terminus is a quite bad font (many very wrong glyphs), but for most of my |
|
|
777 | purposes, it works, and gives a different look, as my normal (Non-bold) |
|
|
778 | font is already bold, and I want to see a difference between bold and |
|
|
779 | normal fonts. |
|
|
780 | |
|
|
781 | Please note that I used the C<urxvt> instance name and not the C<URxvt> |
|
|
782 | class name. Thats because I use different configs for different purposes, |
|
|
783 | for example, my IRC window is started with C<-name IRC>, and uses these |
|
|
784 | defaults: |
|
|
785 | |
|
|
786 | IRC*title: IRC |
|
|
787 | IRC*geometry: 87x12+535+542 |
|
|
788 | IRC*saveLines: 0 |
|
|
789 | IRC*mapAlert: true |
|
|
790 | IRC*font: suxuseuro |
|
|
791 | IRC*boldFont: suxuseuro |
|
|
792 | IRC*colorBD: white |
|
|
793 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
|
|
794 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
|
|
795 | |
|
|
796 | C<Alt-Shift-1> and C<Alt-Shift-2> switch between two different font |
|
|
797 | sizes. C<suxuseuro> allows me to keep an eye (and actually read) |
|
|
798 | stuff while keeping a very small window. If somebody pastes something |
|
|
799 | complicated (e.g. japanese), I temporarily switch to a larger font. |
|
|
800 | |
|
|
801 | The above is all in my C<.Xdefaults> (I don't use C<.Xresources> nor |
|
|
802 | C<xrdb>). I also have some resources in a separate C<.Xdefaults-hostname> |
|
|
803 | file for different hosts, for example, on ym main desktop, I use: |
|
|
804 | |
|
|
805 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
|
|
806 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
|
|
807 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
|
|
808 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
|
|
809 | URxvt.keysym.C-M-p: perl:test |
|
|
810 | |
|
|
811 | The first for keysym definitions allow me to quickly bring some windows |
|
|
812 | in the layout I like most. Ion users might start laughing but will stop |
|
|
813 | immediately when I tell them that I use my own Fvwm2 module for much the |
|
|
814 | same effect as Ion provides, and I only very rarely use the above key |
|
|
815 | combinations :-> |
|
|
816 | |
663 | =head3 Why doesn't rxvt-unicode read my resources? |
817 | =head3 Why doesn't rxvt-unicode read my resources? |
664 | |
818 | |
665 | Well, why, indeed? It does, in a way very similar to other X |
819 | Well, why, indeed? It does, in a way very similar to other X |
666 | applications. Most importantly, this means that if you or your OS loads |
820 | applications. Most importantly, this means that if you or your OS loads |
667 | resources into the X display (the right way to do it), rxvt-unicode will |
821 | resources into the X display (the right way to do it), rxvt-unicode will |
… | |
… | |
883 | |
1037 | |
884 | You can also use xterm's C<luit> program, which usually works fine, except |
1038 | You can also use xterm's C<luit> program, which usually works fine, except |
885 | for some locales where character width differs between program- and |
1039 | for some locales where character width differs between program- and |
886 | rxvt-unicode-locales. |
1040 | rxvt-unicode-locales. |
887 | |
1041 | |
|
|
1042 | =head3 I have problems getting my input method working. |
|
|
1043 | |
|
|
1044 | Try a search engine, as this is slightly different for every input method server. |
|
|
1045 | |
|
|
1046 | Here is a checklist: |
|
|
1047 | |
|
|
1048 | =over 4 |
|
|
1049 | |
|
|
1050 | =item - Make sure your locale I<and> the imLocale are supported on your OS. |
|
|
1051 | |
|
|
1052 | Try C<locale -a> or check the documentation for your OS. |
|
|
1053 | |
|
|
1054 | =item - Make sure your locale or imLocale matches a locale supported by your XIM. |
|
|
1055 | |
|
|
1056 | For example, B<kinput2> does not support UTF-8 locales, you should use |
|
|
1057 | C<ja_JP.EUC-JP> or equivalent. |
|
|
1058 | |
|
|
1059 | =item - Make sure your XIM server is actually running. |
|
|
1060 | |
|
|
1061 | =item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode. |
|
|
1062 | |
|
|
1063 | When you want to use e.g. B<kinput2>, it must be set to |
|
|
1064 | C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. Youc an see what input |
|
|
1065 | method servers are running with this command: |
|
|
1066 | |
|
|
1067 | xprop -root XIM_SERVERS |
|
|
1068 | |
|
|
1069 | =item |
|
|
1070 | |
|
|
1071 | =back |
|
|
1072 | |
888 | =head3 My input method wants <some encoding> but I want UTF-8, what can I do? |
1073 | =head3 My input method wants <some encoding> but I want UTF-8, what can I do? |
889 | |
1074 | |
890 | You can specify separate locales for the input method and the rest of the |
1075 | You can specify separate locales for the input method and the rest of the |
891 | terminal, using the resource C<imlocale>: |
1076 | terminal, using the resource C<imlocale>: |
892 | |
1077 | |
893 | URxvt.imlocale: ja_JP.EUC-JP |
1078 | URxvt.imlocale: ja_JP.EUC-JP |
894 | |
1079 | |
895 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
1080 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
896 | use your input method. Please note, however, that you will not be able to |
1081 | use your input method. Please note, however, that, depending on your Xlib |
897 | input characters outside C<EUC-JP> in a normal way then, as your input |
1082 | version, you may not be able to input characters outside C<EUC-JP> in a |
898 | method limits you. |
1083 | normal way then, as your input method limits you. |
899 | |
1084 | |
900 | =head3 Rxvt-unicode crashes when the X Input Method changes or exits. |
1085 | =head3 Rxvt-unicode crashes when the X Input Method changes or exits. |
901 | |
1086 | |
902 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
1087 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
903 | design. Applications can avoid some crashes at the expense of memory |
1088 | design. Applications can avoid some crashes at the expense of memory |
… | |
… | |
2262 | Remove support for mouse selection style like that of xterm. |
2447 | Remove support for mouse selection style like that of xterm. |
2263 | |
2448 | |
2264 | =item --enable-dmalloc (default: off) |
2449 | =item --enable-dmalloc (default: off) |
2265 | |
2450 | |
2266 | Use Gray Watson's malloc - which is good for debugging See |
2451 | Use Gray Watson's malloc - which is good for debugging See |
2267 | http://www.letters.com/dmalloc/ for details If you use either this or the |
2452 | L<http://www.letters.com/dmalloc/> for details If you use either this or the |
2268 | next option, you may need to edit src/Makefile after compiling to point |
2453 | next option, you may need to edit src/Makefile after compiling to point |
2269 | DINCLUDE and DLIB to the right places. |
2454 | DINCLUDE and DLIB to the right places. |
2270 | |
2455 | |
2271 | You can only use either this option and the following (should |
2456 | You can only use either this option and the following (should |
2272 | you use either) . |
2457 | you use either) . |