… | |
… | |
12 | emulator intended as an I<xterm>(1) replacement for users who do not |
12 | emulator intended as an I<xterm>(1) replacement for users who do not |
13 | require features such as Tektronix 4014 emulation and toolkit-style |
13 | require features such as Tektronix 4014 emulation and toolkit-style |
14 | configurability. As a result, B<rxvt-unicode> uses much less swap space -- |
14 | configurability. As a result, B<rxvt-unicode> uses much less swap space -- |
15 | a significant advantage on a machine serving many X sessions. |
15 | a significant advantage on a machine serving many X sessions. |
16 | |
16 | |
17 | See also @@RXVT_NAME@@(7) for technical reference documentation (escape |
17 | =head1 RXVT-UNICODE VS. RXVT |
18 | sequences etc.) and the FAQ section at the end of this document. |
18 | |
|
|
19 | Unlike the original rxvt, B<rxvt-unicode> stores all text in Unicode |
|
|
20 | internally. That means it can store and display most scripts in the |
|
|
21 | world. Being a terminal emulator, however, some things are very difficult, |
|
|
22 | especially cursive scripts such as arabic, vertically written scripts |
|
|
23 | like mongolian or scripts requiring extremely complex combining rules, |
|
|
24 | like tibetan or devenagari. Don't expect pretty output when using these |
|
|
25 | scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work |
|
|
26 | fine, though. A somewhat difficult case are left-to-right scripts, such |
|
|
27 | as hebrew: B<rxvt-unicode> adopts the view that bidirectional algorithms |
|
|
28 | belong into the application, not the terminal emulator (too many things -- |
|
|
29 | such as cursor-movement -- break othwerwise). |
|
|
30 | |
|
|
31 | Another design rationale was the use of multiple fonts to display |
|
|
32 | characters: The idea of a single unicode font which many other programs |
|
|
33 | force onto it's users never made sense to me: You should be able to choose |
|
|
34 | any font for any script. |
|
|
35 | |
|
|
36 | Apart from that, rxvt-unicode is also much better internationalised than |
|
|
37 | it's predecessor, supports things such as XFT and ISO 14755 that are handy |
|
|
38 | in i18n-environments, is faster, and has a lot less bugs than the original |
|
|
39 | rxvt. This all in addition to dozens of other small improvements. |
|
|
40 | |
|
|
41 | It is still faithfully following the original rxvt idea of being lean |
|
|
42 | and nice on resources: for example, you can still configure rxvt-unicode |
|
|
43 | without most of it's features to get a lean binary. It also comes with |
|
|
44 | a client/daemon pair that lets you open any number of terminal windows |
|
|
45 | from within a single process, which makes startup time very fast and |
|
|
46 | drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and |
|
|
47 | @@RXVT_NAME@@c(1) (client). |
|
|
48 | |
|
|
49 | It also makes technical information about escape sequences (which have |
|
|
50 | been extended) easier accessible: see @@RXVT_NAME@@(7) for technical |
|
|
51 | reference documentation (escape sequences etc.) and the FAQ section at the |
|
|
52 | end of this document. |
19 | |
53 | |
20 | =head1 OPTIONS |
54 | =head1 OPTIONS |
21 | |
55 | |
22 | The B<@@RXVT_NAME@@> options (mostly a subset of I<xterm>'s) are listed |
56 | The B<@@RXVT_NAME@@> options (mostly a subset of I<xterm>'s) are listed |
23 | below. In keeping with the smaller-is-better philosophy, options may be |
57 | below. In keeping with the smaller-is-better philosophy, options may be |
… | |
… | |
119 | Select the fonts to be used. This is a comma seperated list of font |
153 | Select the fonts to be used. This is a comma seperated list of font |
120 | names that are used in turn when trying to display Unicode characters. |
154 | names that are used in turn when trying to display Unicode characters. |
121 | The first font defines the cell size for characters; other fonts might |
155 | The first font defines the cell size for characters; other fonts might |
122 | be smaller, but not larger. A reasonable default font list is always |
156 | be smaller, but not larger. A reasonable default font list is always |
123 | appended to it. resource B<font>. |
157 | appended to it. resource B<font>. |
|
|
158 | |
|
|
159 | See also the question "How does rxvt-unicode choose fonts?" in the FAQ |
|
|
160 | section. |
124 | |
161 | |
125 | =item B<-rb>|B<+rb> |
162 | =item B<-rb>|B<+rb> |
126 | |
163 | |
127 | Enable "real bold" support. When this option is on, bold text will be |
164 | Enable "real bold" support. When this option is on, bold text will be |
128 | displayed using the first available bold font in the font list. Bold |
165 | displayed using the first available bold font in the font list. Bold |
… | |
… | |
830 | would yield White on Black, while on I<xterm>(1) it would yield Black |
867 | would yield White on Black, while on I<xterm>(1) it would yield Black |
831 | on White. |
868 | on White. |
832 | |
869 | |
833 | =back |
870 | =back |
834 | |
871 | |
835 | =head1 ENVIRONMENT |
|
|
836 | |
|
|
837 | B<@@RXVT_NAME@@> sets the environment variables B<TERM>, B<COLORTERM> |
|
|
838 | and B<COLORFGBG>. The environment variable B<WINDOWID> is set to the X |
|
|
839 | window id number of the B<@@RXVT_NAME@@> window and it also uses and |
|
|
840 | sets the environment variable B<DISPLAY> to specify which display |
|
|
841 | terminal to use. B<@@RXVT_NAME@@> uses the environment variables |
|
|
842 | B<RXVTPATH> and B<PATH> to find XPM files. |
|
|
843 | |
|
|
844 | =head1 FILES |
|
|
845 | |
|
|
846 | =over 4 |
|
|
847 | |
|
|
848 | =item B</etc/utmp> |
|
|
849 | |
|
|
850 | System file for login records. |
|
|
851 | |
|
|
852 | =item B</usr/lib/X11/rgb.txt> |
|
|
853 | |
|
|
854 | Color names. |
|
|
855 | |
|
|
856 | =back |
|
|
857 | |
|
|
858 | =head1 FREQUENTLY ASKED QUESTIONS (FAQ) |
872 | =head1 FREQUENTLY ASKED QUESTIONS (FAQ) |
859 | |
873 | |
860 | =over 4 |
874 | =over 4 |
861 | |
875 | |
862 | =item How do I know which rxvt-unicode version I'm using? |
876 | =item How do I know which rxvt-unicode version I'm using? |
863 | |
877 | |
864 | The version number is displayed with the usage (-h). For rxvt-unicode |
878 | The version number is displayed with the usage (-h). For rxvt-unicode |
865 | version 2.14 and later, the escape sequence C<ESC[8n> sets the window |
879 | version 2.14 and later, the escape sequence C<ESC[8n> sets the window |
866 | title to the version number. |
880 | title to the version number. |
|
|
881 | |
|
|
882 | =item Why do the characters look ugly? |
|
|
883 | |
|
|
884 | =item How does rxvt-unicode choose fonts? |
|
|
885 | |
|
|
886 | Most fonts do not contain the full range of Unicode, which is |
|
|
887 | fine. Chances are that the font you (or the admin/package maintainer of |
|
|
888 | your system/os) have specified does not cover all the characters you want |
|
|
889 | to display. |
|
|
890 | |
|
|
891 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
|
|
892 | font. Often the result is fine, but sometimes the chosen font looks |
|
|
893 | bad. In that case, select a font of your taste and add it to the font |
|
|
894 | list, e.g.: |
|
|
895 | |
|
|
896 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
|
|
897 | |
|
|
898 | When rxvt-unicode sees a character, it will first look at the base |
|
|
899 | font. If the base font does not contain the character, it will go to the |
|
|
900 | next font, and so on. |
|
|
901 | |
|
|
902 | The only limitation is that all the fonts must not be larger than the base |
|
|
903 | font, as the base font defines the principial cell size, which must be the |
|
|
904 | same due to the way terminals work. |
|
|
905 | |
|
|
906 | =item Why do some chinese characters look so different than others? |
|
|
907 | |
|
|
908 | This is because there is a difference between script and language -- |
|
|
909 | rxvt-unicode does not know which language the text that is output |
|
|
910 | is, as it only knows the unicode character codes. If rxvt-unicode |
|
|
911 | first sees a japanese character, it might choose a japanese font for |
|
|
912 | it. Subseqzuent japanese characters will take that font. Now, many chinese |
|
|
913 | characters aren't represented in japanese fonts, so when the first |
|
|
914 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
915 | -- unfortunately at this point, it will still use the japanese font for |
|
|
916 | japanese characters that are also chinese. |
|
|
917 | |
|
|
918 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
919 | list (see the previous question). The key is to view the font list as |
|
|
920 | a preference list: If you expect more japanese, list a japanese font |
|
|
921 | first. If you expect more chinese, put a chinese font first. |
|
|
922 | |
|
|
923 | In the future it might be possible to switch preferences at runtime (the |
|
|
924 | internal data structure has no problem with using different fonts for |
|
|
925 | the same character at the same time, but no interface for this has been |
|
|
926 | designed yet). |
867 | |
927 | |
868 | =item Mouse cut/paste suddenly no longer works. |
928 | =item Mouse cut/paste suddenly no longer works. |
869 | |
929 | |
870 | Make sure that mouse reporting is actually turned off since killing |
930 | Make sure that mouse reporting is actually turned off since killing |
871 | some editors prematurely may leave the mouse in mouse report mode. I've |
931 | some editors prematurely may leave the mouse in mouse report mode. I've |
… | |
… | |
1074 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
1134 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
1075 | the doc subdirectory and enter C<make alldoc>. |
1135 | the doc subdirectory and enter C<make alldoc>. |
1076 | |
1136 | |
1077 | =back |
1137 | =back |
1078 | |
1138 | |
|
|
1139 | =head1 ENVIRONMENT |
|
|
1140 | |
|
|
1141 | B<@@RXVT_NAME@@> sets the environment variables B<TERM>, B<COLORTERM> |
|
|
1142 | and B<COLORFGBG>. The environment variable B<WINDOWID> is set to the X |
|
|
1143 | window id number of the B<@@RXVT_NAME@@> window and it also uses and |
|
|
1144 | sets the environment variable B<DISPLAY> to specify which display |
|
|
1145 | terminal to use. B<@@RXVT_NAME@@> uses the environment variables |
|
|
1146 | B<RXVTPATH> and B<PATH> to find XPM files. |
|
|
1147 | |
|
|
1148 | =head1 FILES |
|
|
1149 | |
|
|
1150 | =over 4 |
|
|
1151 | |
|
|
1152 | =item B</etc/utmp> |
|
|
1153 | |
|
|
1154 | System file for login records. |
|
|
1155 | |
|
|
1156 | =item B</usr/lib/X11/rgb.txt> |
|
|
1157 | |
|
|
1158 | Color names. |
|
|
1159 | |
|
|
1160 | =back |
|
|
1161 | |
1079 | =head1 SEE ALSO |
1162 | =head1 SEE ALSO |
1080 | |
1163 | |
1081 | @@RXVT_NAME@@(7), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5) |
1164 | @@RXVT_NAME@@(7), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5) |
1082 | |
1165 | |
1083 | =head1 BUGS |
1166 | =head1 BUGS |