[ViewVC] Diff of: cvs/rxvt-unicode/doc/rxvt.1.pod

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.4 by root, Fri Aug 13 03:47:09 2004 UTC vs.
Revision 1.22 by root, Tue Aug 24 15:46:27 2004 UTC

…		…
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 while editing -- break othwerwise), but that might
		30	change.
		31
		32	If you are looking for a terminal that supports more exotic scripts, let
		33	me recommend C<mlterm>, which is a very userfriendly, lean and clean
		34	terminal emulator. In fact, the reason rxvt-unicode was born was solely
		35	because the author couldn't get C<mlterm> to use one font for latin1 and
		36	another for japanese.
		37
		38	Therefore another design rationale was the use of multiple fonts to
		39	display characters: The idea of a single unicode font which many other
		40	programs force onto it's users never made sense to me: You should be able
		41	to choose any font for any script freely.
		42
		43	Apart from that, rxvt-unicode is also much better internationalised than
		44	it's predecessor, supports things such as XFT and ISO 14755 that are handy
		45	in i18n-environments, is faster, and has a lot less bugs than the original
		46	rxvt. This all in addition to dozens of other small improvements.
		47
		48	It is still faithfully following the original rxvt idea of being lean
		49	and nice on resources: for example, you can still configure rxvt-unicode
		50	without most of it's features to get a lean binary. It also comes with
		51	a client/daemon pair that lets you open any number of terminal windows
		52	from within a single process, which makes startup time very fast and
		53	drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and
		54	@@RXVT_NAME@@c(1) (client).
		55
		56	It also makes technical information about escape sequences (which have
		57	been extended) easier accessible: see @@RXVT_NAME@@(7) for technical
		58	reference documentation (escape sequences etc.) and the FAQ section at the
		59	end of this document.
19		60
20	=head1 OPTIONS	61	=head1 OPTIONS
21		62
22	The B<@@RXVT_NAME@@> options (mostly a subset of I<xterm>'s) are listed	63	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	64	below. In keeping with the smaller-is-better philosophy, options may be
…		…
109		150
110	The mouse pointer background colour; resource B<pointerColor2>.	151	The mouse pointer background colour; resource B<pointerColor2>.
111		152
112	=item B<-bd> I<colour>	153	=item B<-bd> I<colour>
113		154
114	The colour of the border between the xterm scrollbar and the text;	155	The colour of the border around the text area and between the scrollbar and the text;
115	resource B<borderColor>.	156	resource B<borderColor>.
116		157
117	=item B<-fn> I<fontname>	158	=item B<-fn> I<fontlist>
118		159
119	Select the fonts to be used. This is a comma seperated list of font	160	Select the fonts to be used. This is a comma separated list of font names
120	names that are used in turn when trying to display Unicode characters.	161	that are used in turn when trying to display Unicode characters. The
121	The first font defines the cell size for characters; other fonts might	162	first font defines the cell size for characters; other fonts might be
122	be smaller, but not larger. A reasonable default font list is always	163	smaller, but not (in general) larger. A reasonable default font list is
123	appended to it. resource B<font>.	164	always appended to it. See resource B<font> for details.
124		165
125	=item B<-rb>\|B<+rb>	166	See also the question "How does rxvt-unicode choose fonts?" in the FAQ
		167	section.
126		168
127	Enable "real bold" support. When this option is on, bold text will be	169	=item B<-fb> I<fontlist>
128	displayed using the first available bold font in the font list. Bold	170
129	fonts should thus be specified in the font list after their	171	Compile font-styles: The bold font list to use when bold characters are to
130	corresponding regular fonts. If no bold font can be found, a regular	172	be printed. See resource B<boldFont> for details.
131	font will be used. resource B<realBold>.	173
		174	=item B<-fi> I<fontlist>
		175
		176	Compile font-styles: The italic font list to use when bold characters are to
		177	be printed. See resource B<italicFont> for details.
		178
		179	=item B<-fbi> I<fontlist>
		180
		181	Compile font-styles: The bold italic font list to use when bold characters are to
		182	be printed. See resource B<boldItalicFont> for details.
132		183
133	=item B<-name> I<name>	184	=item B<-name> I<name>
134		185
135	Specify the application name under which resources are to be obtained,	186	Specify the application name under which resources are to be obtained,
136	rather than the default executable file name. Name should not contain	187	rather than the default executable file name. Name should not contain
…		…
345	high-intensity (bold = bright foreground, blink = bright background)	396	high-intensity (bold = bright foreground, blink = bright background)
346	colours. The canonical names are as follows: 0=black, 1=red, 2=green,	397	colours. The canonical names are as follows: 0=black, 1=red, 2=green,
347	3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour	398	3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour
348	names used are listed in the B<COLORS AND GRAPHICS> section.	399	names used are listed in the B<COLORS AND GRAPHICS> section.
349		400
		401	Colours higher than 15 cannot be set using resources (yet), but can be
		402	changed using an escape command (see @@RXVT_NAME@@(7)).
		403
		404	Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with
		405	88 colour support). Colours 80-87 are evenly spaces grey steps.
		406
350	=item B<colorBD:> I<colour>	407	=item B<colorBD:> I<colour>
351		408
		409	=item B<colorIT:> I<colour>
		410
352	Use the specified colour to display bold characters when the foreground	411	Use the specified colour to display bold or italic characters when the
353	colour is the default. This option will be ignored if B<realBold> is	412	foreground colour is the default. If font styles are not available
354	enabled.	413	(Compile styles) and this option is unset, reverse video is used instead.
355		414
356	=item B<colorUL:> I<colour>	415	=item B<colorUL:> I<colour>
357		416
358	Use the specified colour to display underlined characters when the	417	Use the specified colour to display underlined characters when the
359	foreground colour is the default.	418	foreground colour is the default.
…		…
415		474
416	=item B<troughColor:> I<colour>	475	=item B<troughColor:> I<colour>
417		476
418	Use the specified colour for the scrollbar's trough area [default	477	Use the specified colour for the scrollbar's trough area [default
419	#969696]. Only relevant for normal (non XTerm/NeXT) scrollbar.	478	#969696]. Only relevant for normal (non XTerm/NeXT) scrollbar.
		479
		480	=item B<borderColor:> I<colour>
		481
		482	The colour of the border around the text area and between the scrollbar
		483	and the text.
420		484
421	=item B<backgroundPixmap:> I<file[;geom]>	485	=item B<backgroundPixmap:> I<file[;geom]>
422		486
423	Use the specified XPM file (note the `.xpm' extension is optional) for	487	Use the specified XPM file (note the `.xpm' extension is optional) for
424	the background and also optionally specify its scaling with a geometry	488	the background and also optionally specify its scaling with a geometry
…		…
440		504
441	Specify the colon-delimited search path for finding files (XPM and	505	Specify the colon-delimited search path for finding files (XPM and
442	menus), in addition to the paths specified by the B<RXVTPATH> and	506	menus), in addition to the paths specified by the B<RXVTPATH> and
443	B<PATH> environment variables.	507	B<PATH> environment variables.
444		508
445	=item B<font:> I<fontname>	509	=item B<font:> I<fontlist>
446		510
447	Select the fonts to be used. This is a comma seperated list of font	511	Select the fonts to be used. This is a comma separated list of font
448	names that are used in turn when trying to display Unicode characters.	512	names that are used in turn when trying to display Unicode characters.
449	The first font defines the cell size for characters; other fonts might	513	The first font defines the cell size for characters; other fonts might
450	be smaller, but not larger. A reasonable default font list is always	514	be smaller, but not larger. A reasonable default font list is always
451	appended to it. option B<-fn>.	515	appended to it. option B<-fn>.
452		516
453	=item B<realBold:> I<boolean>	517	Each font can either be a standard X11 core font (XLFD) name, with
		518	optional prefix C<x:> or a Xft font (Compile xft), prefixed with C<xft:>.
454		519
455	B<True>: Enable "real bold" support. When this option is on, bold text	520	In addition, each font can be prefixed with additional hints and
456	will be displayed using the first available bold font in the font list.	521	specifications enclosed in square brackets (C<[]>). The only available
457	Bold fonts should thus be specified in the font list after their	522	hint currently is C<codeset=codeset-name>, and this is only used for Xft
458	corresponding regular fonts. If no bold font can be found, a regular	523	fonts.
459	font will be used. option B<-rb>. B<False>: Display bold text in a	524
460	regular font, using the color specified with B<colorBD>; option B<+rb>.	525	For example, this font resource
		526
		527	URxvt*font: 9x15bold,\
		528	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		529	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		530	[codeset=JISX0208]xft:Kochi Gothic:antialias=false, \
		531	xft:Code2000:antialias=false
		532
		533	specifies five fonts to be used. The first one is C<9x15bold> (actually
		534	the iso8859-1 version of the second font), which is the base font (because
		535	it is named first) and thus defines the character cell grid to be 9 pixels
		536	wide and 15 pixels high.
		537
		538	the second font is just used to add additional unicode characters not in
		539	the base font, likewise the third, which is unfortunately non-bold, but
		540	the bold version of the font does contain less characters, so this is a
		541	useful supplement.
		542
		543	The third font is an Xft font with aliasing turned off, and the characters
		544	are limited to the B<JIS 0208> codeset (i.e. japanese kanji). The font
		545	contains other characters, but we are not interested in them.
		546
		547	The last font is a useful catch-all font that supplies most of the
		548	remaining unicode characters.
		549
		550	=item B<boldFont:> I<fontlist>
		551
		552	=item B<italicFont:> I<fontlist>
		553
		554	=item B<boldItalicFont:> I<fontlist>
		555
		556	The font list to use for displaying B<bold>, I<italic> or B<< I<bold
		557	italic> >> characters, respectively.
		558
		559	If specified and non-empty, then the syntax is the same as for the
		560	B<font>-resource, and the given font list will be used as is, which makes
		561	it possible to substitute completely different font styles for bold and
		562	italic.
		563
		564	If unset (the default), a suitable font list will be synthesized by
		565	"morphing" the normal text font list into the desired shape. If that is
		566	not possible, replacement fonts of the desired shape will be tried.
		567
		568	If set, but empty, then this specific style is disabled and the normal
		569	text font will being used for the given style.
461		570
462	=item B<selectstyle:> I<mode>	571	=item B<selectstyle:> I<mode>
463		572
464	Set mouse selection style to B<old> which is 2.20, B<oldword> which is	573	Set mouse selection style to B<old> which is 2.20, B<oldword> which is
465	xterm style with 2.20 old word selection, or anything else which gives	574	xterm style with 2.20 old word selection, or anything else which gives
…		…
547	B<True>: scroll to bottom when a non-special key is pressed. Special keys	656	B<True>: scroll to bottom when a non-special key is pressed. Special keys
548	are those which are intercepted by rxvt-unicode for special handling and	657	are those which are intercepted by rxvt-unicode for special handling and
549	are not passed onto the shell; option B<-sk>. B<False>: do not scroll to	658	are not passed onto the shell; option B<-sk>. B<False>: do not scroll to
550	bottom when a non-special key is pressed; option B<+sk>.	659	bottom when a non-special key is pressed; option B<+sk>.
551		660
552	=item B<smallfont_key:> I<keysym>
553
554	If enabled, use B<@@HOTKEY@@->I<keysym> to toggle to a smaller font
555	[default B<@@HOTKEY@@-@@SMALLFONT@@>]
556
557	=item B<bigfont_key:> I<keysym>
558
559	If enabled, use B<@@HOTKEY@@->I<keysym> to toggle to a bigger font
560	[default B<@@HOTKEY@@-@@BIGFONT@@>]
561
562	=item B<saveLines:> I<number>	661	=item B<saveLines:> I<number>
563		662
564	Save I<number> lines in the scrollback buffer [default 64]. This	663	Save I<number> lines in the scrollback buffer [default 64]. This
565	resource is limited on most machines to 65535; option B<-sl>.	664	resource is limited on most machines to 65535; option B<-sl>.
566		665
…		…
655	The locale to use for opening the IM. You can use an LC_CTYPE of e.g.	754	The locale to use for opening the IM. You can use an LC_CTYPE of e.g.
656	de_DE.UTF-8 for normal text processing but ja_JP.EUC-JP for the input	755	de_DE.UTF-8 for normal text processing but ja_JP.EUC-JP for the input
657	extension to be able to input japanese characters while staying in	756	extension to be able to input japanese characters while staying in
658	another locale. option B<-imlocale>.	757	another locale. option B<-imlocale>.
659		758
660	=item B<insecure>	759	=item B<insecure:> I<boolean>
661		760
662	Enables "insecure" mode. Rxvt-unicode offers some escape sequences that	761	Enables "insecure" mode. Rxvt-unicode offers some escape sequences that
663	echo arbitrary strings like the icon name or the locale. This could be	762	echo arbitrary strings like the icon name or the locale. This could be
664	abused if somebody gets 8-bit-clean access to your display, wether	763	abused if somebody gets 8-bit-clean access to your display, wether
665	throuh a mail client displaying mail bodies unfiltered or though	764	throuh a mail client displaying mail bodies unfiltered or though
…		…
753		852
754	=back	853	=back
755		854
756	=head1 CHANGING FONTS	855	=head1 CHANGING FONTS
757		856
758	You can change fonts on-the-fly, which is to say cycle through the	857	Changing fonts (or font sizes, respectively) via the keypad is not yet
759	default font and others of various sizes, by using B<Shift-KP_Add> and	858	supported in rxvt-unicode. Bug me if you need this.
760	B<Shift-KP_Subtract>. Or, alternatively (if enabled) with	859
761	B<@@HOTKEY@@-@@BIGFONT@@> and B<@@HOTKEY@@-@@SMALLFONT@@>, where the	860	You can, however, switch fonts at runtime using escape sequences (and
762	actual key can be selected using resources	861	therefore using the menubar), e.g.:
763	B<smallfont_key>/B<bigfont_key>.	862
		863	printf '\e]701;%s\007' "9x15bold,xft:Kochi Gothic"
		864
		865	rxvt-unicode will automatically re-apply these fonts to the output so far.
764		866
765	=head1 ISO 14755 SUPPORT	867	=head1 ISO 14755 SUPPORT
766		868
767	Partial ISO 14755-support is implemented. that means that pressing	869	ISO 14755 is a standard for entering and viewing unicode characters
		870	and character codes using the keyboard. It consists of 4 parts. The
		871	first part is available rxvt-unicode has been compiled with
		872	C<--enable-frills>, the rest is available when rxvt-unicode was compiled
		873	with C<--enable-iso14755>.
768		874
769	Section 5.1: Control and Shift together enters unicode input	875	=over 4
770	mode. Entering hex digits composes a Unicode character, pressing space or
771	releasing the modifiers commits the keycode and every other key cancels
772	the current input character.
773		876
774	Section 5.2: Pressing and immediately releasing Control and Shift together	877	=item 5.1: Basic method
775	enters keycap entry mode for the next key: pressing a function key (tab,	878
776	return etc..) will enter the unicode character corresponding to the given	879	This allows you to enter unicode characters using their hexcode.
777	key.	880
		881	Start by pressing and holding both C<Control> and C<Shift>, then enter
		882	hex-digits (between one and six). Releasing C<Control> and C<Shift> will
		883	commit the character as if it were typed directly. While holding down
		884	C<Control> and C<Shift> you can also enter multiple characters by pressing
		885	C<Space>, which will commit the current character and lets you start a new
		886	one.
		887
		888	As an example of use, imagine a business card with a japanese e-mail
		889	address, which you cannot type. Fortunately, the card has the e-mail
		890	address printed as hexcodes, e.g. C<671d 65e5>. You can enter this easily
		891	by pressing C<Control> and C<Shift>, followed by C<6-7-1-D-SPACE-6-5-E-5>,
		892	followed by releasing the modifier keys.
		893
		894	=item 5.2: Keyboard symbols entry method
		895
		896	This mode lets you input characters representing the keycap symbols of
		897	your keyboard, if representable in the current locale encoding.
		898
		899	Start by pressing C<Control> and C<Shift> together, then releasing
		900	them. The next special key (cursor keys, home etc.) you enter will not
		901	invoke it's usual function but instead will insert the corresponding
		902	keycap symbol. The symbol will only be entered when the key has been
		903	released, otherwise pressing e.g. C<Shift> would enter the symbol for
		904	C<ISO Level 2 Switch>, although your intention might have beenm to enter a
		905	reverse tab (Shift-Tab).
		906
		907	=item 5.3: Screen-selection entry method
		908
		909	While this is implemented already (it's basically the selection
		910	mechanism), it could be extended by displaying a unicode character map.
		911
		912	=item 5.4: Feedback method for identifying displayed characters for later input
		913
		914	This method lets you display the unicode character code associated with
		915	characters already displayed.
		916
		917	You enter this mode by holding down C<Control> and C<Shift> together, then
		918	pressing and holding the left mouse button and moving around. The unicode
		919	hex code(s) (it might be a combining character) of the character under the
		920	pointer is displayed until you release C<Control> and C<Shift>.
		921
		922	In addition to the hex codes it will display the font used to draw this
		923	character - due to implementation reasons, characters combined with
		924	combining characters, line drawing characters and unknown characters will
		925	always be drawn using the built-in support font.
		926
		927	=back
		928
		929	With respect to conformance, rxvt-unicode is supposed to be compliant to
		930	both scenario A and B of ISO 14755, including part 5.2.
778		931
779	=head1 LOGIN STAMP	932	=head1 LOGIN STAMP
780		933
781	B<@@RXVT_NAME@@> tries to write an entry into the I<utmp>(5) file so	934	B<@@RXVT_NAME@@> tries to write an entry into the I<utmp>(5) file so
782	that it can be seen via the I<who(1)> command, and can accept messages.	935	that it can be seen via the I<who(1)> command, and can accept messages.
…		…
830	would yield White on Black, while on I<xterm>(1) it would yield Black	983	would yield White on Black, while on I<xterm>(1) it would yield Black
831	on White.	984	on White.
832		985
833	=back	986	=back
834		987
835	=head1 ENVIRONMENT	988	=head1 FREQUENTLY ASKED QUESTIONS (FAQ)
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		989
846	=over 4	990	=over 4
847		991
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)
859
860	=over 4
861
862	=item How do I know which rxvt-unicode version I'm using?	992	=item How do I know which rxvt-unicode version I'm using?
863		993
864	The version number is displayed with the usage (-h). For rxvt-unicode	994	The version number is displayed with the usage (-h). Also the escape
865	version 2.14 and later, the escape sequence C<ESC[8n> sets the window	995	sequence C<ESC[8n> sets the window title to the version number.
866	title to the version number.	996
		997	=item When I log-in to another system it tells me about missing terminfo data?
		998
		999	The terminal description used by rxvt-unicode is not as widely available
		1000	as that for xterm, or even rxvt (for which the same problem often arises).
		1001
		1002	The correct solution for this problem is to install the terminfo, this can be done
		1003	like this:
		1004
		1005	infocmp rxvt-unicode >rxvt.unicode.tic
		1006	scp rxvt-unicode.tic remotesystem:
		1007	ssh remotesystem tic rxvt-unicode.tic
		1008
		1009	... or by installing rxvt-unicode normally on the remote system,
		1010
		1011	If you cannot or do not want to do this, then you can simply set
		1012	C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of
		1013	problems arising, which includes wrong keymapping, less and different
		1014	colours and some refresh errors in fullscreen applications. It's a nice
		1015	quick-and-dirty workaround for rare cases, though.
		1016
		1017	If you always want to do this you can either recompile rxvt-unicode with
		1018	the desired TERM value or use a resource to set it:
		1019
		1020	URxvt.termName: rxvt
		1021
		1022	=item How can I configure rxvt-unicode so that it looks similar to the original rxvt?
		1023
		1024	Felix von Leitner says that these two lines, in your F<.Xdefaults>, will make rxvt-unicode
		1025	behave similar to the original rxvt:
		1026
		1027	URxvt.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1
		1028	URxvt.boldFont: -misc-fixed-bold-r-semicondensed--13-120-75-75-c-60-iso8859-1
		1029
		1030	=item Rxvt-unicode does not seem to understand the selected encoding?
		1031
		1032	=item Unicode does not seem to work?
		1033
		1034	If you encounter strange problems like typing an accented character but
		1035	getting two unrelated other characters or similar, or if program output is
		1036	subtly garbled, then you should check your locale settings.
		1037
		1038	Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the
		1039	programs. Often rxvt-unicode is started in the C<C> locale, while the
		1040	login script running within the rxvt-unicode window changes the locale to
		1041	sth. else, e.h. C<en_GB.UTF-8>. Needless to say, this is not going to work.
		1042
		1043	The best thing is to fix your startup environment, as you will likely run
		1044	into other problems. If nothing works you can try this in your .profile.
		1045
		1046	printf '\e]701;%s\007' "$LC_CTYPE"
		1047
		1048	If this doesn't work, then maybe you use a C<LC_CTYPE> specification not
		1049	supported on your systems. Some systems have a C<locale> comamnd which
		1050	displays this. If it displays sth. like:
		1051
		1052	locale: Cannot set LC_CTYPE to default locale: ...
		1053
		1054	Then the locale you specified is not supported on your system.
		1055
		1056	If nothing works and you are sure that everything is set correctly then
		1057	you will need to remember a little known fact: Some programs just don't
		1058	support locales :(
		1059
		1060	=item Why do the characters look ugly?
		1061
		1062	=item How does rxvt-unicode choose fonts?
		1063
		1064	Most fonts do not contain the full range of Unicode, which is
		1065	fine. Chances are that the font you (or the admin/package maintainer of
		1066	your system/os) have specified does not cover all the characters you want
		1067	to display.
		1068
		1069	B<rxvt-unicode> makes a best-effort try at finding a replacement
		1070	font. Often the result is fine, but sometimes the chosen font looks
		1071	bad. Many fonts have totally strange characters that don't resemble the
		1072	correct glyph at all, and rxvt-unicode lacks the artificial intelligence
		1073	to detetc that a specific glyph is wrong: it has to believe the font that
		1074	the characters it contains indeed look correct.
		1075
		1076	In that case, select a font of your taste and add it to the font list,
		1077	e.g.:
		1078
		1079	@@RXVT_NAME@@ -fn basefont,font2,font3...
		1080
		1081	When rxvt-unicode sees a character, it will first look at the base
		1082	font. If the base font does not contain the character, it will go to the
		1083	next font, and so on. Specifying your own fonts will also speed up this
		1084	search and use less resources within rxvt-unicode and the X-server.
		1085
		1086	The only limitation is that all the fonts must not be larger than the base
		1087	font, as the base font defines the principial cell size, which must be the
		1088	same due to the way terminals work.
		1089
		1090	=item Why do some chinese characters look so different than others?
		1091
		1092	This is because there is a difference between script and language --
		1093	rxvt-unicode does not know which language the text that is output
		1094	is, as it only knows the unicode character codes. If rxvt-unicode
		1095	first sees a japanese character, it might choose a japanese font for
		1096	it. Subseqzuent japanese characters will take that font. Now, many chinese
		1097	characters aren't represented in japanese fonts, so when the first
		1098	non-japanese character comes up, rxvt-unicode will look for a chinese font
		1099	-- unfortunately at this point, it will still use the japanese font for
		1100	japanese characters that are also chinese.
		1101
		1102	The workaround is easy: just tag a chinese font at the end of your font
		1103	list (see the previous question). The key is to view the font list as
		1104	a preference list: If you expect more japanese, list a japanese font
		1105	first. If you expect more chinese, put a chinese font first.
		1106
		1107	In the future it might be possible to switch preferences at runtime (the
		1108	internal data structure has no problem with using different fonts for
		1109	the same character at the same time, but no interface for this has been
		1110	designed yet).
		1111
		1112	=item How can I keep rxvt-unicode from using reverse video so much?
		1113
		1114	First of all, make sure you are running with the right terminfo
		1115	(C<urxvt>), which will get rid of most of these effects. Then make sure
		1116	you have specified colours for italic and bold, as otherwise rxvt-unicode
		1117	might use reverse video to simulate the effect:
		1118
		1119	URxvt*colorBD: white
		1120	URxvt*colorIT: green
		1121
		1122	=item Some programs assume totally weird colours (red instead of blue), how can I fix that?
		1123
		1124	For some unexplainable reason, some programs (i.e. irssi) assume a very
		1125	weird colour palette when confronted with a terminal with more than the
		1126	standard 8 colours (rxvt-unicode supports 88). The right fix is, of
		1127	course, to fix these programs not to assume non-ISO colours without very
		1128	good reasons.
		1129
		1130	In the meantime, you can either edit your C<urxvt> terminfo definition to
		1131	only claim 8 colour support or use C<TERM=rxvt>, which will fix colours
		1132	but keep you from using other rxvt-unicode features.
		1133
		1134	=item How does rxvt-unicode determine the encoding to use?
		1135
		1136	=item Is there an option to switch encodings?
		1137
		1138	Unlike some other terminals, rxvt-unicode has no encoding switch, and no
		1139	specific "utf-8" mode, such as xterm. In fact, it doesn't even know about
		1140	UTF-8 or any other encodings with respect to terminal I/O.
		1141
		1142	The reasons is that there exists a perfectly fine mechanism for selecting
		1143	the encoding, doing I/O and (most important) communicating this to all
		1144	applications so everybody agrees on character properties such as width and
		1145	code number. This mechanism is the I<locale>.
		1146
		1147	Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All
		1148	programs doing the same (that is, most) will automatically agree in the
		1149	interpretation of characters.
		1150
		1151	Unfortunately, there is no system-independent way to select locales, nor
		1152	is there a standard on how locale specifiers will look like.
		1153
		1154	On most systems, the content of the C<LC_CTYPE> environment variable
		1155	contains an arbitrary string which corresponds to an already-installed
		1156	locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>,
		1157	C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms
		1158	(i.e. C<de> or C<german>) are also common.
		1159
		1160	Rxvt-unicode ignores all other locale categories, and except for
		1161	the encoding, ignores country or language-specific settings,
		1162	i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the same for rxvt-unicode.
		1163
		1164	If you want to use a specific encoding you have to make sure you start
		1165	rxvt-unicode with the correct C<LC_CTYPE> category.
		1166
		1167	=item Can I switch locales at runtime?
		1168
		1169	Yes, using an escape sequence. Try sth. like this, which sets
		1170	rxvt-unicode's idea of C<LC_CTYPE>.
		1171
		1172	printf '\e]701;%s\007' ja_JP.SJIS
		1173
		1174	See also the previous question.
		1175
		1176	Sometimes this capability is rather handy when you want to work in one
		1177	locale (e.g. C<de_DE.UTF-8>) but some programs don't support UTF-8. For
		1178	example, I use this script to start C<xjdic>, which first switches to a
		1179	locale supported by xjdic and back later:
		1180
		1181	printf '\e]701;%s\007' ja_JP.SJIS
		1182	xjdic -js
		1183	printf '\e]701;%s\007' de_DE.UTF-8
		1184
		1185	=item Can I switch the fonts at runtime?
		1186
		1187	Yes, using an escape sequence. Try sth. like this, which has the same
		1188	effect as using the C<-fn> switch, and takes effect immediately:
		1189
		1190	printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic"
		1191
		1192	This is useful if you e.g. work primarily with japanese (and prefer a
		1193	japanese font), but you have to switch to chinese temporarily, where
		1194	japanese fonts would only be in your way.
		1195
		1196	You can think of this as a kind of manual ISO-2022 switching.
		1197
		1198	=item Why do italic characters look as if clipped?
		1199
		1200	Many fonts have difficulties with italic characters and hinting. For
		1201	example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans
		1202	Mono> completely fails in it's italic face. A workaround is to enable
		1203	freetype autohinting, i.e. like this:
		1204
		1205	URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		1206	URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		1207
		1208	=item My input method wants <some encoding> but I want UTF-8, what can I do?
		1209
		1210	You cna specify separate locales for the input method and the rest of the
		1211	terminal, using the resource C<imlocale>:
		1212
		1213	URxvt*imlocale: ja_JP.EUC-JP
		1214
		1215	Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still
		1216	use your input method. Please note, however, that you will not be able to
		1217	input characters outside C<EUC-JP> in a normal way then, as your input
		1218	method limits you.
		1219
		1220	=item Rxvt-unicode uses gobs of memory, how can I reduce that?
		1221
		1222	Rxvt-unicode tries to obey the rule of not charging you for sth. you
		1223	don't use. One thing you should try is to configure out all settings that
		1224	you don't need, for example, Xft support is a resource hog by design,
		1225	when used. Compiling it out ensures that no Xft font will be loaded
		1226	accidentally when rxvt-unicode tries to find a font for your characters.
		1227
		1228	Also, many people (me included) like large windows and even larger
		1229	scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use
		1230	6 bytes per screen cell. For a 160x?? window this amounts to almost a
		1231	kilobyte per line. A scorllback buffer of 10000 lines will then (if full)
		1232	use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as
		1233	rxvt-unicode then uses 8 bytes per screen cell.
		1234
		1235	=item Can I speed up Xft rendering somehow?
		1236
		1237	Yes, the most obvious way to speed it up is to avoid Xft entirely, as
		1238	it is simply slow. If you still want Xft fonts you might try to disable
		1239	antialiasing (by appending C<:antialiasing=false>), which saves lots of
		1240	memory and also speeds up rendering considerably.
		1241
		1242	=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
		1243
		1244	Rxvt-unicode will use whatever you specify as a font. If it needs to
		1245	fall back to it's default font search list it will prefer X11 core
		1246	fonts, because they are small and fast, and then use Xft fonts. It has
		1247	antialiaisng disabled for most of them, because the author thinks they
		1248	look best that way.
		1249
		1250	If you want antialiasing, you have to specify the fonts manually.
867		1251
868	=item Mouse cut/paste suddenly no longer works.	1252	=item Mouse cut/paste suddenly no longer works.
869		1253
870	Make sure that mouse reporting is actually turned off since killing	1254	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	1255	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	1458	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
1075	the doc subdirectory and enter C<make alldoc>.	1459	the doc subdirectory and enter C<make alldoc>.
1076		1460
1077	=back	1461	=back
1078		1462
		1463	=head1 ENVIRONMENT
		1464
		1465	B<@@RXVT_NAME@@> sets the environment variables B<TERM>, B<COLORTERM>
		1466	and B<COLORFGBG>. The environment variable B<WINDOWID> is set to the X
		1467	window id number of the B<@@RXVT_NAME@@> window and it also uses and
		1468	sets the environment variable B<DISPLAY> to specify which display
		1469	terminal to use. B<@@RXVT_NAME@@> uses the environment variables
		1470	B<RXVTPATH> and B<PATH> to find XPM files.
		1471
		1472	=head1 FILES
		1473
		1474	=over 4
		1475
		1476	=item B</etc/utmp>
		1477
		1478	System file for login records.
		1479
		1480	=item B</usr/lib/X11/rgb.txt>
		1481
		1482	Color names.
		1483
		1484	=back
		1485
1079	=head1 SEE ALSO	1486	=head1 SEE ALSO
1080		1487
1081	@@RXVT_NAME@@(7), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5)	1488	@@RXVT_NAME@@(7), xterm(1), sh(1), resize(1), X(1), pty(4), tty(4), utmp(5)
1082		1489
1083	=head1 BUGS	1490	=head1 BUGS
…		…
1092		1499
1093	=over 4	1500	=over 4
1094		1501
1095	=item Project Coordinator	1502	=item Project Coordinator
1096		1503
1097	@@RXVTMAINT@@ L<@@RXVT_MAINTEMAIL@@>	1504	@@RXVT_MAINT@@ L<@@RXVT_MAINTEMAIL@@>
1098		1505
1099	=item Web page maintainter	1506	=item Web page maintainter
1100		1507
1101	@@RXVTWEBMAINT@@ L<@@RXVT_WEBMAINTEMAIL@@>	1508	@@RXVT_WEBMAINT@@ L<@@RXVT_WEBMAINTEMAIL@@>
1102		1509
1103	L<@@RXVT_WEBPAGE@@>	1510	L<@@RXVT_WEBPAGE@@>
1104		1511
1105	=back	1512	=back
1106		1513

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents): Revision 1.4 by root, Fri Aug 13 03:47:09 2004 UTC vs. Revision 1.22 by root, Tue Aug 24 15:46:27 2004 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.4 by root, Fri Aug 13 03:47:09 2004 UTC vs.
Revision 1.22 by root, Tue Aug 24 15:46:27 2004 UTC