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

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.5 by root, Sat Aug 14 03:00:32 2004 UTC vs.
Revision 1.30 by root, Wed Sep 8 17:10:23 2004 UTC

…		…
11	B<rxvt-unicode>, version B<@@RXVT_VERSION@@>, is a colour vt102 terminal	11	B<rxvt-unicode>, version B<@@RXVT_VERSION@@>, is a colour vt102 terminal
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
		17	=head1 FREQUENTLY ASKED QUESTIONS
		18
		19	See @@RXVT_NAME@@(7) (try C<man 7 @@RXVT_NAME@@>) for a list of frequently
		20	asked questions and answer to them and some common problems.
16		21
17	=head1 RXVT-UNICODE VS. RXVT	22	=head1 RXVT-UNICODE VS. RXVT
18		23
19	Unlike the original rxvt, B<rxvt-unicode> stores all text in Unicode	24	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	25	internally. That means it can store and display most scripts in the
…		…
24	like tibetan or devenagari. Don't expect pretty output when using these	29	like tibetan or devenagari. Don't expect pretty output when using these
25	scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work	30	scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work
26	fine, though. A somewhat difficult case are left-to-right scripts, such	31	fine, though. A somewhat difficult case are left-to-right scripts, such
27	as hebrew: B<rxvt-unicode> adopts the view that bidirectional algorithms	32	as hebrew: B<rxvt-unicode> adopts the view that bidirectional algorithms
28	belong into the application, not the terminal emulator (too many things --	33	belong into the application, not the terminal emulator (too many things --
29	such as cursor-movement -- break othwerwise).	34	such as cursor-movement while editing -- break otherwise), but that might
		35	change.
30		36
		37	If you are looking for a terminal that supports more exotic scripts, let
		38	me recommend C<mlterm>, which is a very userfriendly, lean and clean
		39	terminal emulator. In fact, the reason rxvt-unicode was born was solely
		40	because the author couldn't get C<mlterm> to use one font for latin1 and
		41	another for japanese.
		42
31	Another design rationale was the use of multiple fonts to display	43	Therefore another design rationale was the use of multiple fonts to
32	characters: The idea of a single unicode font which many other programs	44	display characters: The idea of a single unicode font which many other
33	force onto it's users never made sense to me: You should be able to choose	45	programs force onto it's users never made sense to me: You should be able
34	any font for any script.	46	to choose any font for any script freely.
35		47
36	Apart from that, rxvt-unicode is also much better internationalised than	48	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	49	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	50	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.	51	rxvt. This all in addition to dozens of other small improvements.
…		…
46	drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and	58	drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and
47	@@RXVT_NAME@@c(1) (client).	59	@@RXVT_NAME@@c(1) (client).
48		60
49	It also makes technical information about escape sequences (which have	61	It also makes technical information about escape sequences (which have
50	been extended) easier accessible: see @@RXVT_NAME@@(7) for technical	62	been extended) easier accessible: see @@RXVT_NAME@@(7) for technical
51	reference documentation (escape sequences etc.) and the FAQ section at the	63	reference documentation (escape sequences etc.).
52	end of this document.
53		64
54	=head1 OPTIONS	65	=head1 OPTIONS
55		66
56	The B<@@RXVT_NAME@@> options (mostly a subset of I<xterm>'s) are listed	67	The B<@@RXVT_NAME@@> options (mostly a subset of I<xterm>'s) are listed
57	below. In keeping with the smaller-is-better philosophy, options may be	68	below. In keeping with the smaller-is-better philosophy, options may be
…		…
143		154
144	The mouse pointer background colour; resource B<pointerColor2>.	155	The mouse pointer background colour; resource B<pointerColor2>.
145		156
146	=item B<-bd> I<colour>	157	=item B<-bd> I<colour>
147		158
148	The colour of the border between the xterm scrollbar and the text;	159	The colour of the border around the text area and between the scrollbar and the text;
149	resource B<borderColor>.	160	resource B<borderColor>.
150		161
151	=item B<-fn> I<fontname>	162	=item B<-fn> I<fontlist>
152		163
153	Select the fonts to be used. This is a comma seperated list of font	164	Select the fonts to be used. This is a comma separated list of font names
154	names that are used in turn when trying to display Unicode characters.	165	that are used in turn when trying to display Unicode characters. The
155	The first font defines the cell size for characters; other fonts might	166	first font defines the cell size for characters; other fonts might be
156	be smaller, but not larger. A reasonable default font list is always	167	smaller, but not (in general) larger. A reasonable default font list is
157	appended to it. resource B<font>.	168	always appended to it. See resource B<font> for details.
158		169
159	See also the question "How does rxvt-unicode choose fonts?" in the FAQ	170	See also the question "How does rxvt-unicode choose fonts?" in the FAQ
160	section.	171	section of @@RXVT_NAME@@(7).
161		172
162	=item B<-rb>\|B<+rb>	173	=item B<-fb> I<fontlist>
163		174
164	Enable "real bold" support. When this option is on, bold text will be	175	Compile font-styles: The bold font list to use when bold characters are to
165	displayed using the first available bold font in the font list. Bold	176	be printed. See resource B<boldFont> for details.
166	fonts should thus be specified in the font list after their	177
167	corresponding regular fonts. If no bold font can be found, a regular	178	=item B<-fi> I<fontlist>
168	font will be used. resource B<realBold>.	179
		180	Compile font-styles: The italic font list to use when bold characters are to
		181	be printed. See resource B<italicFont> for details.
		182
		183	=item B<-fbi> I<fontlist>
		184
		185	Compile font-styles: The bold italic font list to use when bold characters are to
		186	be printed. See resource B<boldItalicFont> for details.
169		187
170	=item B<-name> I<name>	188	=item B<-name> I<name>
171		189
172	Specify the application name under which resources are to be obtained,	190	Specify the application name under which resources are to be obtained,
173	rather than the default executable file name. Name should not contain	191	rather than the default executable file name. Name should not contain
…		…
382	high-intensity (bold = bright foreground, blink = bright background)	400	high-intensity (bold = bright foreground, blink = bright background)
383	colours. The canonical names are as follows: 0=black, 1=red, 2=green,	401	colours. The canonical names are as follows: 0=black, 1=red, 2=green,
384	3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour	402	3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour
385	names used are listed in the B<COLORS AND GRAPHICS> section.	403	names used are listed in the B<COLORS AND GRAPHICS> section.
386		404
		405	Colours higher than 15 cannot be set using resources (yet), but can be
		406	changed using an escape command (see @@RXVT_NAME@@(7)).
		407
		408	Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with
		409	88 colour support). Colours 80-87 are evenly spaces grey steps.
		410
387	=item B<colorBD:> I<colour>	411	=item B<colorBD:> I<colour>
388		412
		413	=item B<colorIT:> I<colour>
		414
389	Use the specified colour to display bold characters when the foreground	415	Use the specified colour to display bold or italic characters when the
390	colour is the default. This option will be ignored if B<realBold> is	416	foreground colour is the default. If font styles are not available
391	enabled.	417	(Compile styles) and this option is unset, reverse video is used instead.
392		418
393	=item B<colorUL:> I<colour>	419	=item B<colorUL:> I<colour>
394		420
395	Use the specified colour to display underlined characters when the	421	Use the specified colour to display underlined characters when the
396	foreground colour is the default.	422	foreground colour is the default.
…		…
452		478
453	=item B<troughColor:> I<colour>	479	=item B<troughColor:> I<colour>
454		480
455	Use the specified colour for the scrollbar's trough area [default	481	Use the specified colour for the scrollbar's trough area [default
456	#969696]. Only relevant for normal (non XTerm/NeXT) scrollbar.	482	#969696]. Only relevant for normal (non XTerm/NeXT) scrollbar.
		483
		484	=item B<borderColor:> I<colour>
		485
		486	The colour of the border around the text area and between the scrollbar
		487	and the text.
457		488
458	=item B<backgroundPixmap:> I<file[;geom]>	489	=item B<backgroundPixmap:> I<file[;geom]>
459		490
460	Use the specified XPM file (note the `.xpm' extension is optional) for	491	Use the specified XPM file (note the `.xpm' extension is optional) for
461	the background and also optionally specify its scaling with a geometry	492	the background and also optionally specify its scaling with a geometry
…		…
477		508
478	Specify the colon-delimited search path for finding files (XPM and	509	Specify the colon-delimited search path for finding files (XPM and
479	menus), in addition to the paths specified by the B<RXVTPATH> and	510	menus), in addition to the paths specified by the B<RXVTPATH> and
480	B<PATH> environment variables.	511	B<PATH> environment variables.
481		512
482	=item B<font:> I<fontname>	513	=item B<font:> I<fontlist>
483		514
484	Select the fonts to be used. This is a comma seperated list of font	515	Select the fonts to be used. This is a comma separated list of font
485	names that are used in turn when trying to display Unicode characters.	516	names that are used in turn when trying to display Unicode characters.
486	The first font defines the cell size for characters; other fonts might	517	The first font defines the cell size for characters; other fonts might
487	be smaller, but not larger. A reasonable default font list is always	518	be smaller, but not larger. A reasonable default font list is always
488	appended to it. option B<-fn>.	519	appended to it. option B<-fn>.
489		520
490	=item B<realBold:> I<boolean>	521	Each font can either be a standard X11 core font (XLFD) name, with
		522	optional prefix C<x:> or a Xft font (Compile xft), prefixed with C<xft:>.
491		523
492	B<True>: Enable "real bold" support. When this option is on, bold text	524	In addition, each font can be prefixed with additional hints and
493	will be displayed using the first available bold font in the font list.	525	specifications enclosed in square brackets (C<[]>). The only available
494	Bold fonts should thus be specified in the font list after their	526	hint currently is C<codeset=codeset-name>, and this is only used for Xft
495	corresponding regular fonts. If no bold font can be found, a regular	527	fonts.
496	font will be used. option B<-rb>. B<False>: Display bold text in a	528
497	regular font, using the color specified with B<colorBD>; option B<+rb>.	529	For example, this font resource
		530
		531	URxvt*font: 9x15bold,\
		532	-misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\
		533	-misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \
		534	[codeset=JISX0208]xft:Kochi Gothic:antialias=false, \
		535	xft:Code2000:antialias=false
		536
		537	specifies five fonts to be used. The first one is C<9x15bold> (actually
		538	the iso8859-1 version of the second font), which is the base font (because
		539	it is named first) and thus defines the character cell grid to be 9 pixels
		540	wide and 15 pixels high.
		541
		542	the second font is just used to add additional unicode characters not in
		543	the base font, likewise the third, which is unfortunately non-bold, but
		544	the bold version of the font does contain less characters, so this is a
		545	useful supplement.
		546
		547	The third font is an Xft font with aliasing turned off, and the characters
		548	are limited to the B<JIS 0208> codeset (i.e. japanese kanji). The font
		549	contains other characters, but we are not interested in them.
		550
		551	The last font is a useful catch-all font that supplies most of the
		552	remaining unicode characters.
		553
		554	=item B<boldFont:> I<fontlist>
		555
		556	=item B<italicFont:> I<fontlist>
		557
		558	=item B<boldItalicFont:> I<fontlist>
		559
		560	The font list to use for displaying B<bold>, I<italic> or B<< I<bold
		561	italic> >> characters, respectively.
		562
		563	If specified and non-empty, then the syntax is the same as for the
		564	B<font>-resource, and the given font list will be used as is, which makes
		565	it possible to substitute completely different font styles for bold and
		566	italic.
		567
		568	If unset (the default), a suitable font list will be synthesized by
		569	"morphing" the normal text font list into the desired shape. If that is
		570	not possible, replacement fonts of the desired shape will be tried.
		571
		572	If set, but empty, then this specific style is disabled and the normal
		573	text font will being used for the given style.
498		574
499	=item B<selectstyle:> I<mode>	575	=item B<selectstyle:> I<mode>
500		576
501	Set mouse selection style to B<old> which is 2.20, B<oldword> which is	577	Set mouse selection style to B<old> which is 2.20, B<oldword> which is
502	xterm style with 2.20 old word selection, or anything else which gives	578	xterm style with 2.20 old word selection, or anything else which gives
…		…
573	B<False>: do not scroll to bottom when tty receives output; option	649	B<False>: do not scroll to bottom when tty receives output; option
574	B<+si>.	650	B<+si>.
575		651
576	=item B<scrollWithBuffer:> I<boolean>	652	=item B<scrollWithBuffer:> I<boolean>
577		653
578	B<True>: scroll with scrollback buffer when tty recieves new lines (and	654	B<True>: scroll with scrollback buffer when tty receives new lines (and
579	B<scrollTtyOutput> is False); option B<+sw>. B<False>: do not scroll	655	B<scrollTtyOutput> is False); option B<+sw>. B<False>: do not scroll
580	with scrollback buffer when tty recieves new lines; option B<-sw>.	656	with scrollback buffer when tty recieves new lines; option B<-sw>.
581		657
582	=item B<scrollTtyKeypress:> I<boolean>	658	=item B<scrollTtyKeypress:> I<boolean>
583		659
584	B<True>: scroll to bottom when a non-special key is pressed. Special keys	660	B<True>: scroll to bottom when a non-special key is pressed. Special keys
585	are those which are intercepted by rxvt-unicode for special handling and	661	are those which are intercepted by rxvt-unicode for special handling and
586	are not passed onto the shell; option B<-sk>. B<False>: do not scroll to	662	are not passed onto the shell; option B<-sk>. B<False>: do not scroll to
587	bottom when a non-special key is pressed; option B<+sk>.	663	bottom when a non-special key is pressed; option B<+sk>.
588		664
589	=item B<smallfont_key:> I<keysym>
590
591	If enabled, use B<@@HOTKEY@@->I<keysym> to toggle to a smaller font
592	[default B<@@HOTKEY@@-@@SMALLFONT@@>]
593
594	=item B<bigfont_key:> I<keysym>
595
596	If enabled, use B<@@HOTKEY@@->I<keysym> to toggle to a bigger font
597	[default B<@@HOTKEY@@-@@BIGFONT@@>]
598
599	=item B<saveLines:> I<number>	665	=item B<saveLines:> I<number>
600		666
601	Save I<number> lines in the scrollback buffer [default 64]. This	667	Save I<number> lines in the scrollback buffer [default 64]. This
602	resource is limited on most machines to 65535; option B<-sl>.	668	resource is limited on most machines to 65535; option B<-sl>.
603		669
…		…
692	The locale to use for opening the IM. You can use an LC_CTYPE of e.g.	758	The locale to use for opening the IM. You can use an LC_CTYPE of e.g.
693	de_DE.UTF-8 for normal text processing but ja_JP.EUC-JP for the input	759	de_DE.UTF-8 for normal text processing but ja_JP.EUC-JP for the input
694	extension to be able to input japanese characters while staying in	760	extension to be able to input japanese characters while staying in
695	another locale. option B<-imlocale>.	761	another locale. option B<-imlocale>.
696		762
697	=item B<insecure>	763	=item B<insecure:> I<boolean>
698		764
699	Enables "insecure" mode. Rxvt-unicode offers some escape sequences that	765	Enables "insecure" mode. Rxvt-unicode offers some escape sequences that
700	echo arbitrary strings like the icon name or the locale. This could be	766	echo arbitrary strings like the icon name or the locale. This could be
701	abused if somebody gets 8-bit-clean access to your display, wether	767	abused if somebody gets 8-bit-clean access to your display, whether
702	throuh a mail client displaying mail bodies unfiltered or though	768	throuh a mail client displaying mail bodies unfiltered or though
703	write(1). Therefore, these sequences are disabled by default. (Note	769	write(1). Therefore, these sequences are disabled by default. (Note
704	that other terminals, including xterm, have these sequences	770	that other terminals, including xterm, have these sequences
705	enabled by default). You can enable them by setting this boolean	771	enabled by default). You can enable them by setting this boolean
706	resource or specifying B<-insecure> as an option. At the moment, this	772	resource or specifying B<-insecure> as an option. At the moment, this
…		…
780	Left click at the beginning of the region, drag to the end of the	846	Left click at the beginning of the region, drag to the end of the
781	region and release; Right click to extend the marked region; Left	847	region and release; Right click to extend the marked region; Left
782	double-click to select a word; Left triple-click to select the entire	848	double-click to select a word; Left triple-click to select the entire
783	line.	849	line.
784		850
		851	Starting a selection while pressing the B<Meta> key (or B<Meta+Ctrl> keys)
		852	(Compile: frills) will create a rectangular selection instead of a normal
		853	one.
		854
785	=item B<Insertion>:	855	=item B<Insertion>:
786		856
787	Pressing and releasing the Middle mouse button (or B<Shift-Insert>) in	857	Pressing and releasing the Middle mouse button (or B<Shift-Insert>) in
788	an B<@@RXVT_NAME@@> window causes the current text selection to be	858	an B<@@RXVT_NAME@@> window causes the current text selection to be
789	inserted as if it had been typed on the keyboard.	859	inserted as if it had been typed on the keyboard.
790		860
791	=back	861	=back
792		862
793	=head1 CHANGING FONTS	863	=head1 CHANGING FONTS
794		864
795	You can change fonts on-the-fly, which is to say cycle through the	865	Changing fonts (or font sizes, respectively) via the keypad is not yet
796	default font and others of various sizes, by using B<Shift-KP_Add> and	866	supported in rxvt-unicode. Bug me if you need this.
797	B<Shift-KP_Subtract>. Or, alternatively (if enabled) with	867
798	B<@@HOTKEY@@-@@BIGFONT@@> and B<@@HOTKEY@@-@@SMALLFONT@@>, where the	868	You can, however, switch fonts at runtime using escape sequences (and
799	actual key can be selected using resources	869	therefore using the menubar), e.g.:
800	B<smallfont_key>/B<bigfont_key>.	870
		871	printf '\e]701;%s\007' "9x15bold,xft:Kochi Gothic"
		872
		873	rxvt-unicode will automatically re-apply these fonts to the output so far.
801		874
802	=head1 ISO 14755 SUPPORT	875	=head1 ISO 14755 SUPPORT
803		876
804	Partial ISO 14755-support is implemented. that means that pressing	877	ISO 14755 is a standard for entering and viewing unicode characters
		878	and character codes using the keyboard. It consists of 4 parts. The
		879	first part is available rxvt-unicode has been compiled with
		880	C<--enable-frills>, the rest is available when rxvt-unicode was compiled
		881	with C<--enable-iso14755>.
805		882
806	Section 5.1: Control and Shift together enters unicode input	883	=over 4
807	mode. Entering hex digits composes a Unicode character, pressing space or
808	releasing the modifiers commits the keycode and every other key cancels
809	the current input character.
810		884
811	Section 5.2: Pressing and immediately releasing Control and Shift together	885	=item 5.1: Basic method
812	enters keycap entry mode for the next key: pressing a function key (tab,	886
813	return etc..) will enter the unicode character corresponding to the given	887	This allows you to enter unicode characters using their hexcode.
814	key.	888
		889	Start by pressing and holding both C<Control> and C<Shift>, then enter
		890	hex-digits (between one and six). Releasing C<Control> and C<Shift> will
		891	commit the character as if it were typed directly. While holding down
		892	C<Control> and C<Shift> you can also enter multiple characters by pressing
		893	C<Space>, which will commit the current character and lets you start a new
		894	one.
		895
		896	As an example of use, imagine a business card with a japanese e-mail
		897	address, which you cannot type. Fortunately, the card has the e-mail
		898	address printed as hexcodes, e.g. C<671d 65e5>. You can enter this easily
		899	by pressing C<Control> and C<Shift>, followed by C<6-7-1-D-SPACE-6-5-E-5>,
		900	followed by releasing the modifier keys.
		901
		902	=item 5.2: Keyboard symbols entry method
		903
		904	This mode lets you input characters representing the keycap symbols of
		905	your keyboard, if representable in the current locale encoding.
		906
		907	Start by pressing C<Control> and C<Shift> together, then releasing
		908	them. The next special key (cursor keys, home etc.) you enter will not
		909	invoke it's usual function but instead will insert the corresponding
		910	keycap symbol. The symbol will only be entered when the key has been
		911	released, otherwise pressing e.g. C<Shift> would enter the symbol for
		912	C<ISO Level 2 Switch>, although your intention might have been to enter a
		913	reverse tab (Shift-Tab).
		914
		915	=item 5.3: Screen-selection entry method
		916
		917	While this is implemented already (it's basically the selection
		918	mechanism), it could be extended by displaying a unicode character map.
		919
		920	=item 5.4: Feedback method for identifying displayed characters for later input
		921
		922	This method lets you display the unicode character code associated with
		923	characters already displayed.
		924
		925	You enter this mode by holding down C<Control> and C<Shift> together, then
		926	pressing and holding the left mouse button and moving around. The unicode
		927	hex code(s) (it might be a combining character) of the character under the
		928	pointer is displayed until you release C<Control> and C<Shift>.
		929
		930	In addition to the hex codes it will display the font used to draw this
		931	character - due to implementation reasons, characters combined with
		932	combining characters, line drawing characters and unknown characters will
		933	always be drawn using the built-in support font.
		934
		935	=back
		936
		937	With respect to conformance, rxvt-unicode is supposed to be compliant to
		938	both scenario A and B of ISO 14755, including part 5.2.
815		939
816	=head1 LOGIN STAMP	940	=head1 LOGIN STAMP
817		941
818	B<@@RXVT_NAME@@> tries to write an entry into the I<utmp>(5) file so	942	B<@@RXVT_NAME@@> tries to write an entry into the I<utmp>(5) file so
819	that it can be seen via the I<who(1)> command, and can accept messages.	943	that it can be seen via the I<who(1)> command, and can accept messages.
…		…
867	would yield White on Black, while on I<xterm>(1) it would yield Black	991	would yield White on Black, while on I<xterm>(1) it would yield Black
868	on White.	992	on White.
869		993
870	=back	994	=back
871		995
872	=head1 FREQUENTLY ASKED QUESTIONS (FAQ)
873
874	=over 4
875
876	=item How do I know which rxvt-unicode version I'm using?
877
878	The version number is displayed with the usage (-h). For rxvt-unicode
879	version 2.14 and later, the escape sequence C<ESC[8n> sets the window
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).
927
928	=item Mouse cut/paste suddenly no longer works.
929
930	Make sure that mouse reporting is actually turned off since killing
931	some editors prematurely may leave the mouse in mouse report mode. I've
932	heard that tcsh may use mouse reporting unless it otherwise specified. A
933	quick check is to see if cut/paste works when the Alt or Shift keys are
934	depressed. See @@RXVT_NAME@@(7)
935
936	=item What's with this bold/blink stuff?
937
938	If no bold colour is set via C<colorBD:>, bold will invert text using the
939	standard foreground colour.
940
941	For the standard background colour, blinking will actually make the
942	text blink when compiled with C<--enable-blinking>. with standard
943	colours. Without C<--enable-blinking>, the blink attribute will be
944	ignored.
945
946	On ANSI colours, bold/blink attributes are used to set high-intensity
947	foreground/background colors.
948
949	color0-7 are the low-intensity colors.
950
951	color8-15 are the corresponding high-intensity colors.
952
953	=item I don't like the screen colors. How do I change them?
954
955	You can change the screen colors at run-time using F<~/.Xdefaults>
956	resources (or as long-options).
957
958	Here are values that are supposed to resemble a VGA screen,
959	including the murky brown that passes for low-intensity yellow:
960
961	Rxvt*color0: #000000
962	Rxvt*color1: #A80000
963	Rxvt*color2: #00A800
964	Rxvt*color3: #A8A800
965	Rxvt*color4: #0000A8
966	Rxvt*color5: #A800A8
967	Rxvt*color6: #00A8A8
968	Rxvt*color7: #A8A8A8
969
970	Rxvt*color8: #000054
971	Rxvt*color9: #FF0054
972	Rxvt*color10: #00FF54
973	Rxvt*color11: #FFFF54
974	Rxvt*color12: #0000FF
975	Rxvt*color13: #FF00FF
976	Rxvt*color14: #00FFFF
977	Rxvt*color15: #FFFFFF
978
979	=item What's with the strange Backspace/Delete key behaviour?
980
981	Assuming that the physical Backspace key corresponds to the
982	BackSpace keysym (not likely for Linux ... see the following
983	question) there are two standard values that can be used for
984	Backspace: C<^H> and C<^?>.
985
986	Historically, either value is correct, but rxvt-unicode adopts the debian
987	policy of using C<^?> when unsure, because it's the one only only correct
988	choice :).
989
990	Rxvt-unicode tries to inherit the current stty settings and uses the value
991	of `erase' to guess the value for backspace. If rxvt-unicode wasn't
992	started from a terminal (say, from a menu or by remote shell), then the
993	system value of `erase', which corresponds to CERASE in <termios.h>, will
994	be used (which may not be the same as your stty setting).
995
996	For starting a new rxvt-unicode:
997
998	# use Backspace = ^H
999	$ stty erase ^H
1000	$ @@RXVT_NAME@@
1001
1002	# use Backspace = ^?
1003	$ stty erase ^?
1004	$ @@RXVT_NAME@@
1005
1006	Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7).
1007
1008	For an existing rxvt-unicode:
1009
1010	# use Backspace = ^H
1011	$ stty erase ^H
1012	$ echo -n "^[[36h"
1013
1014	# use Backspace = ^?
1015	$ stty erase ^?
1016	$ echo -n "^[[36l"
1017
1018	This helps satisfy some of the Backspace discrepancies that occur, but
1019	if you use Backspace = C<^H>, make sure that the termcap/terminfo value
1020	properly reflects that.
1021
1022	The Delete key is a another casualty of the ill-defined Backspace problem.
1023	To avoid confusion between the Backspace and Delete keys, the Delete
1024	key has been assigned an escape sequence to match the vt100 for Execute
1025	(ESC[3~) and is in the supplied termcap/terminfo.
1026
1027	Some other Backspace problems:
1028
1029	some editors use termcap/terminfo,
1030	some editors (vim I'm told) expect Backspace = ^H,
1031	GNU Emacs (and Emacs-like editors) use ^H for help.
1032
1033	Perhaps someday this will all be resolved in a consistent manner.
1034
1035	=item I don't like the key-bindings. How do I change them?
1036
1037	There are some compile-time selections available via configure. Unless
1038	you have run "configure" with the C<--disable-resources> option you can
1039	use the `keysym' resource to alter the keystrings associated with keysym
1040	0xFF00 - 0xFFFF (function, cursor keys, etc).
1041
1042	Here's an example for a tn3270 session started using `@@RXVT_NAME@@ -name tn3270'
1043
1044	!# ----- special uses ------:
1045	! tn3270 login, remap function and arrow keys.
1046	tn3270font: clean-bold----15-*
1047
1048	! keysym - used by rxvt only
1049	! Delete - ^D
1050	tn3270*keysym.0xFFFF: \004
1051
1052	! Home - ^A
1053	tn3270*keysym.0xFF50: \001
1054	! Left - ^B
1055	tn3270*keysym.0xFF51: \002
1056	! Up - ^P
1057	tn3270*keysym.0xFF52: \020
1058	! Right - ^F
1059	tn3270*keysym.0xFF53: \006
1060	! Down - ^N
1061	tn3270*keysym.0xFF54: \016
1062	! End - ^E
1063	tn3270*keysym.0xFF57: \005
1064
1065	! F1 - F12
1066	tn3270*keysym.0xFFBE: \e1
1067	tn3270*keysym.0xFFBF: \e2
1068	tn3270*keysym.0xFFC0: \e3
1069	tn3270*keysym.0xFFC1: \e4
1070	tn3270*keysym.0xFFC2: \e5
1071	tn3270*keysym.0xFFC3: \e6
1072	tn3270*keysym.0xFFC4: \e7
1073	tn3270*keysym.0xFFC5: \e8
1074	tn3270*keysym.0xFFC6: \e9
1075	tn3270*keysym.0xFFC7: \e0
1076	tn3270*keysym.0xFFC8: \e-
1077	tn3270*keysym.0xFFC9: \e=
1078
1079	! map Prior/Next to F7/F8
1080	tn3270*keysym.0xFF55: \e7
1081	tn3270*keysym.0xFF56: \e8
1082
1083	=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys.
1084	How do I make use of them? For example, the Sun Keyboard type 4
1085	has the following mappings that rxvt-unicode doesn't recognize.
1086
1087	KP_Insert == Insert
1088	F22 == Print
1089	F27 == Home
1090	F29 == Prior
1091	F33 == End
1092	F35 == Next
1093
1094	Rather than have rxvt-unicode try to accomodate all the various possible keyboard
1095	mappings, it is better to use `xmodmap' to remap the keys as required for
1096	your particular machine.
1097
1098	=item How do I distinguish if I'm running rxvt-unicode or a regular xterm?
1099	I need this to decide about setting colors etc.
1100
1101	rxvt and rxvt-unicode always export the variable "COLORTERM", so you can
1102	check and see if that is set. Note that several programs, JED, slrn,
1103	Midnight Commander automatically check this variable to decide whether or
1104	not to use color.
1105
1106	=item How do I set the correct, full IP address for the DISPLAY variable?
1107
1108	If you've compiled rxvt-unicode with DISPLAY_IS_IP and ahve enabled
1109	insecure mode then it is possible to use the following shell script
1110	snippets to correctly set the display. If your version of rxvt-unicode
1111	wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then
1112	the COLORTERM variable can be used to distinguish rxvt-unicode from a
1113	regular xterm.
1114
1115	Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
1116	snippets:
1117
1118	# Bourne/Korn/POSIX family of shells:
1119	[ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
1120	if [ ${TERM:-foo} = xterm ]; then
1121	stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
1122	echo -n '^[Z'
1123	read term_id
1124	stty icanon echo
1125	if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
1126	echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
1127	read DISPLAY # set it in our local shell
1128	fi
1129	fi
1130
1131	=item How do I compile the manual pages for myself?
1132
1133	You need to have a recent version of perl installed as F</usr/bin/perl>,
1134	one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to
1135	the doc subdirectory and enter C<make alldoc>.
1136
1137	=back
1138
1139	=head1 ENVIRONMENT	996	=head1 ENVIRONMENT
1140		997
1141	B<@@RXVT_NAME@@> sets the environment variables B<TERM>, B<COLORTERM>	998	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	999	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	1000	window id number of the B<@@RXVT_NAME@@> window and it also uses and
…		…
1175		1032
1176	=over 4	1033	=over 4
1177		1034
1178	=item Project Coordinator	1035	=item Project Coordinator
1179		1036
1180	@@RXVTMAINT@@ L<@@RXVT_MAINTEMAIL@@>	1037	@@RXVT_MAINT@@ L<@@RXVT_MAINTEMAIL@@>
1181		1038
1182	=item Web page maintainter	1039	=item Web page maintainter
1183		1040
1184	@@RXVTWEBMAINT@@ L<@@RXVT_WEBMAINTEMAIL@@>	1041	@@RXVT_WEBMAINT@@ L<@@RXVT_WEBMAINTEMAIL@@>
1185		1042
1186	L<@@RXVT_WEBPAGE@@>	1043	L<@@RXVT_WEBPAGE@@>
1187		1044
1188	=back	1045	=back
1189		1046

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents): Revision 1.5 by root, Sat Aug 14 03:00:32 2004 UTC vs. Revision 1.30 by root, Wed Sep 8 17:10:23 2004 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.5 by root, Sat Aug 14 03:00:32 2004 UTC vs.
Revision 1.30 by root, Wed Sep 8 17:10:23 2004 UTC