[ViewVC] Diff of: cvs/rxvt-unicode/doc/rxvt.7.man.in

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.62 by root, Tue Jan 31 20:50:48 2006 UTC vs.
Revision 1.73 by root, Tue Feb 21 01:00:40 2006 UTC

…		…
127	.\}	127	.\}
128	.rm #[ #] #H #V #F C	128	.rm #[ #] #H #V #F C
129	.\" ========================================================================	129	.\" ========================================================================
130	.\"	130	.\"
131	.IX Title "rxvt 7"	131	.IX Title "rxvt 7"
132	.TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE"	132	.TH rxvt 7 "2006-02-21" "7.6" "RXVT-UNICODE"
133	.SH "NAME"	133	.SH "NAME"
134	RXVT REFERENCE \- FAQ, command sequences and other background information	134	RXVT REFERENCE \- FAQ, command sequences and other background information
135	.SH "SYNOPSIS"	135	.SH "SYNOPSIS"
136	.IX Header "SYNOPSIS"	136	.IX Header "SYNOPSIS"
137	.Vb 2	137	.Vb 2
…		…
153	This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting	153	This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting
154	all escape sequences, and other background information.	154	all escape sequences, and other background information.
155	.PP	155	.PP
156	The newest version of this document is also available on the World Wide Web at	156	The newest version of this document is also available on the World Wide Web at
157	<http://cvs.schmorp.de/browse/checkout/rxvt\-unicode/doc/rxvt.7.html>.	157	<http://cvs.schmorp.de/browse/checkout/rxvt\-unicode/doc/rxvt.7.html>.
158	.SH "FREQUENTLY ASKED QUESTIONS"	158	.SH "RXVT\-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS"
159	.IX Header "FREQUENTLY ASKED QUESTIONS"	159	.IX Header "RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS"
160	.Sh "Meta, Features & Commandline Issues"	160	.Sh "Meta, Features & Commandline Issues"
161	.IX Subsection "Meta, Features & Commandline Issues"	161	.IX Subsection "Meta, Features & Commandline Issues"
162	\fIMy question isn't answered here, can I ask a human?\fR	162	\fIMy question isn't answered here, can I ask a human?\fR
163	.IX Subsection "My question isn't answered here, can I ask a human?"	163	.IX Subsection "My question isn't answered here, can I ask a human?"
164	.PP	164	.PP
…		…
172	Beginning with version 7.3, there is a perl extension that implements a	172	Beginning with version 7.3, there is a perl extension that implements a
173	simple tabbed terminal. It is installed by default, so any of these should	173	simple tabbed terminal. It is installed by default, so any of these should
174	give you tabs:	174	give you tabs:
175	.PP	175	.PP
176	.Vb 1	176	.Vb 1
177	\& @@RXVT_NAME@@ -pe tabbed	177	\& @@URXVT_NAME@@ -pe tabbed
178	.Ve	178	.Ve
179	.PP	179	.PP
180	.Vb 1	180	.Vb 1
181	\& URxvt.perl-ext-common: default,tabbed	181	\& URxvt.perl-ext-common: default,tabbed
182	.Ve	182	.Ve
…		…
190	\fIHow do I know which rxvt-unicode version I'm using?\fR	190	\fIHow do I know which rxvt-unicode version I'm using?\fR
191	.IX Subsection "How do I know which rxvt-unicode version I'm using?"	191	.IX Subsection "How do I know which rxvt-unicode version I'm using?"
192	.PP	192	.PP
193	The version number is displayed with the usage (\-h). Also the escape	193	The version number is displayed with the usage (\-h). Also the escape
194	sequence \f(CW\(C`ESC [ 8 n\(C'\fR sets the window title to the version number. When	194	sequence \f(CW\(C`ESC [ 8 n\(C'\fR sets the window title to the version number. When
195	using the @@RXVT_NAME@@c client, the version displayed is that of the	195	using the @@URXVT_NAME@@c client, the version displayed is that of the
196	daemon.	196	daemon.
197	.PP	197	.PP
198	\fIRxvt-unicode uses gobs of memory, how can I reduce that?\fR	198	\fIRxvt-unicode uses gobs of memory, how can I reduce that?\fR
199	.IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?"	199	.IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?"
200	.PP	200	.PP
…		…
209	6 bytes per screen cell. For a 160x?? window this amounts to almost a	209	6 bytes per screen cell. For a 160x?? window this amounts to almost a
210	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)	210	kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
211	use 10 Megabytes of memory. With \f(CW\(C`\-\-enable\-unicode3\(C'\fR it gets worse, as	211	use 10 Megabytes of memory. With \f(CW\(C`\-\-enable\-unicode3\(C'\fR it gets worse, as
212	rxvt-unicode then uses 8 bytes per screen cell.	212	rxvt-unicode then uses 8 bytes per screen cell.
213	.PP	213	.PP
214	\fIHow can I start @@RXVT_NAME@@d in a race-free way?\fR	214	\fIHow can I start @@URXVT_NAME@@d in a race-free way?\fR
215	.IX Subsection "How can I start @@RXVT_NAME@@d in a race-free way?"	215	.IX Subsection "How can I start @@URXVT_NAME@@d in a race-free way?"
216	.PP	216	.PP
217	Try \f(CW\(C`@@RXVT_NAME@@d \-f \-o\(C'\fR, which tells @@RXVT_NAME@@d to open the	217	Try \f(CW\(C`@@URXVT_NAME@@d \-f \-o\(C'\fR, which tells @@URXVT_NAME@@d to open the
218	display, create the listening socket and then fork.	218	display, create the listening socket and then fork.
		219	.PP
		220	\fIHow can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?\fR
		221	.IX Subsection "How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?"
		222	.PP
		223	If you want to start @@URXVT_NAME@@d automatically whenever you run
		224	@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
		225	.PP
		226	.Vb 6
		227	\& #!/bin/sh
		228	\& @@URXVT_NAME@@c "$@"
		229	\& if [ $? -eq 2 ]; then
		230	\& @@URXVT_NAME@@d -q -o -f
		231	\& @@URXVT_NAME@@c "$@"
		232	\& fi
		233	.Ve
		234	.PP
		235	This tries to create a new terminal, and if fails with exit status 2,
		236	meaning it couldn't connect to the daemon, it will start the daemon and
		237	re-run the command. Subsequent invocations of the script will re-use the
		238	existing daemon.
219	.PP	239	.PP
220	\fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR	240	\fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR
221	.IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."	241	.IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
222	.PP	242	.PP
223	rxvt and rxvt-unicode always export the variable \(L"\s-1COLORTERM\s0\(R", so you can	243	The original rxvt and rxvt-unicode always export the variable \(L"\s-1COLORTERM\s0\(R",
224	check and see if that is set. Note that several programs, \s-1JED\s0, slrn,	244	so you can check and see if that is set. Note that several programs, \s-1JED\s0,
225	Midnight Commander automatically check this variable to decide whether or	245	slrn, Midnight Commander automatically check this variable to decide
226	not to use color.	246	whether or not to use color.
227	.PP	247	.PP
228	\fIHow do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?\fR	248	\fIHow do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?\fR
229	.IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?"	249	.IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?"
230	.PP	250	.PP
231	If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled	251	If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled
…		…
275	\& text data bss drs rss filename	295	\& text data bss drs rss filename
276	\& 98398 1664 24 15695 1824 rxvt --disable-everything	296	\& 98398 1664 24 15695 1824 rxvt --disable-everything
277	\& 188985 9048 66616 18222 1788 urxvt --disable-everything	297	\& 188985 9048 66616 18222 1788 urxvt --disable-everything
278	.Ve	298	.Ve
279	.PP	299	.PP
280	When you \f(CW\(C`\-\-enable\-everything\(C'\fR (which _is_ unfair, as this involves xft	300	When you \f(CW\(C`\-\-enable\-everything\(C'\fR (which \fIis\fR unfair, as this involves xft
281	and full locale/XIM support which are quite bloaty inside libX11 and my	301	and full locale/XIM support which are quite bloaty inside libX11 and my
282	libc), the two diverge, but not unreasnobaly so.	302	libc), the two diverge, but not unreasnobaly so.
283	.PP	303	.PP
284	.Vb 3	304	.Vb 3
285	\& text data bss drs rss filename	305	\& text data bss drs rss filename
…		…
360	.PP	380	.PP
361	1. Use inheritPixmap:	381	1. Use inheritPixmap:
362	.PP	382	.PP
363	.Vb 2	383	.Vb 2
364	\& Esetroot wallpaper.jpg	384	\& Esetroot wallpaper.jpg
365	\& @@RXVT_NAME@@ -ip -tint red -sh 40	385	\& @@URXVT_NAME@@ -ip -tint red -sh 40
366	.Ve	386	.Ve
367	.PP	387	.PP
368	That works. If you think it doesn't, you lack transparency and tinting	388	That works. If you think it doesn't, you lack transparency and tinting
369	support, or you are unable to read.	389	support, or you are unable to read.
370	.PP	390	.PP
…		…
372	to use effects other than tinting and shading: Just shade/tint/whatever	392	to use effects other than tinting and shading: Just shade/tint/whatever
373	your picture with gimp or any other tool:	393	your picture with gimp or any other tool:
374	.PP	394	.PP
375	.Vb 2	395	.Vb 2
376	\& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm	396	\& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
377	\& @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background	397	\& @@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
378	.Ve	398	.Ve
379	.PP	399	.PP
380	That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you	400	That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you
381	are unable to read.	401	are unable to read.
382	.PP	402	.PP
383	3. Use an \s-1ARGB\s0 visual:	403	3. Use an \s-1ARGB\s0 visual:
384	.PP	404	.PP
385	.Vb 1	405	.Vb 1
386	\& @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc	406	\& @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
387	.Ve	407	.Ve
388	.PP	408	.PP
389	This requires \s-1XFT\s0 support, and the support of your X\-server. If that	409	This requires \s-1XFT\s0 support, and the support of your X\-server. If that
390	doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't	410	doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't
391	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary	411	there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
…		…
400	.Ve	420	.Ve
401	.PP	421	.PP
402	Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR	422	Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR
403	by other values to change the degree of opacity. If it doesn't work and	423	by other values to change the degree of opacity. If it doesn't work and
404	your server crashes, you got to keep the pieces.	424	your server crashes, you got to keep the pieces.
405	.PP
406	\fIWhy do some chinese characters look so different than others?\fR
407	.IX Subsection "Why do some chinese characters look so different than others?"
408	.PP
409	This is because there is a difference between script and language \*(--
410	rxvt-unicode does not know which language the text that is output is,
411	as it only knows the unicode character codes. If rxvt-unicode first
412	sees a japanese/chinese character, it might choose a japanese font for
413	display. Subsequent japanese characters will use that font. Now, many
414	chinese characters aren't represented in japanese fonts, so when the first
415	non-japanese character comes up, rxvt-unicode will look for a chinese font
416	\&\*(-- unfortunately at this point, it will still use the japanese font for
417	chinese characters that are also in the japanese font.
418	.PP
419	The workaround is easy: just tag a chinese font at the end of your font
420	list (see the previous question). The key is to view the font list as
421	a preference list: If you expect more japanese, list a japanese font
422	first. If you expect more chinese, put a chinese font first.
423	.PP
424	In the future it might be possible to switch language preferences at
425	runtime (the internal data structure has no problem with using different
426	fonts for the same character at the same time, but no interface for this
427	has been designed yet).
428	.PP
429	Until then, you might get away with switching fonts at runtime (see \(L"Can I switch the fonts at runtime?\(R" later in this document).
430	.PP	425	.PP
431	\fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR	426	\fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR
432	.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"	427	.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"
433	.PP	428	.PP
434	Most fonts were not designed for terminal use, which means that character	429	Most fonts were not designed for terminal use, which means that character
…		…
571	\& URxvt.color13: #FF00FF	566	\& URxvt.color13: #FF00FF
572	\& URxvt.color14: #00FFFF	567	\& URxvt.color14: #00FFFF
573	\& URxvt.color15: #FFFFFF	568	\& URxvt.color15: #FFFFFF
574	.Ve	569	.Ve
575	.PP	570	.PP
576	And here is a more complete set of non-standard colors described (not by	571	And here is a more complete set of non-standard colors.
577	me) as \(L"pretty girly\(R".
578	.PP	572	.PP
579	.Vb 18	573	.Vb 18
580	\& URxvt.cursorColor: #dc74d1	574	\& URxvt.cursorColor: #dc74d1
581	\& URxvt.pointerColor: #dc74d1	575	\& URxvt.pointerColor: #dc74d1
582	\& URxvt.background: #0e0e0e	576	\& URxvt.background: #0e0e0e
…		…
595	\& URxvt.color14: #73f7ff	589	\& URxvt.color14: #73f7ff
596	\& URxvt.color7: #e1dddd	590	\& URxvt.color7: #e1dddd
597	\& URxvt.color15: #e1dddd	591	\& URxvt.color15: #e1dddd
598	.Ve	592	.Ve
599	.PP	593	.PP
		594	They have been described (not by me) as \(L"pretty girly\(R".
		595	.PP
600	\fIWhy do some characters look so much different than others?\fR	596	\fIWhy do some characters look so much different than others?\fR
601	.IX Subsection "Why do some characters look so much different than others?"	597	.IX Subsection "Why do some characters look so much different than others?"
602	.PP	598	.PP
603	See next entry.	599	See next entry.
604	.PP	600	.PP
…		…
619	.PP	615	.PP
620	In that case, select a font of your taste and add it to the font list,	616	In that case, select a font of your taste and add it to the font list,
621	e.g.:	617	e.g.:
622	.PP	618	.PP
623	.Vb 1	619	.Vb 1
624	\& @@RXVT_NAME@@ -fn basefont,font2,font3...	620	\& @@URXVT_NAME@@ -fn basefont,font2,font3...
625	.Ve	621	.Ve
626	.PP	622	.PP
627	When rxvt-unicode sees a character, it will first look at the base	623	When rxvt-unicode sees a character, it will first look at the base
628	font. If the base font does not contain the character, it will go to the	624	font. If the base font does not contain the character, it will go to the
629	next font, and so on. Specifying your own fonts will also speed up this	625	next font, and so on. Specifying your own fonts will also speed up this
630	search and use less resources within rxvt-unicode and the X\-server.	626	search and use less resources within rxvt-unicode and the X\-server.
631	.PP	627	.PP
632	The only limitation is that none of the fonts may be larger than the base	628	The only limitation is that none of the fonts may be larger than the base
633	font, as the base font defines the terminal character cell size, which	629	font, as the base font defines the terminal character cell size, which
634	must be the same due to the way terminals work.	630	must be the same due to the way terminals work.
		631	.PP
		632	\fIWhy do some chinese characters look so different than others?\fR
		633	.IX Subsection "Why do some chinese characters look so different than others?"
		634	.PP
		635	This is because there is a difference between script and language \*(--
		636	rxvt-unicode does not know which language the text that is output is,
		637	as it only knows the unicode character codes. If rxvt-unicode first
		638	sees a japanese/chinese character, it might choose a japanese font for
		639	display. Subsequent japanese characters will use that font. Now, many
		640	chinese characters aren't represented in japanese fonts, so when the first
		641	non-japanese character comes up, rxvt-unicode will look for a chinese font
		642	\&\*(-- unfortunately at this point, it will still use the japanese font for
		643	chinese characters that are also in the japanese font.
		644	.PP
		645	The workaround is easy: just tag a chinese font at the end of your font
		646	list (see the previous question). The key is to view the font list as
		647	a preference list: If you expect more japanese, list a japanese font
		648	first. If you expect more chinese, put a chinese font first.
		649	.PP
		650	In the future it might be possible to switch language preferences at
		651	runtime (the internal data structure has no problem with using different
		652	fonts for the same character at the same time, but no interface for this
		653	has been designed yet).
		654	.PP
		655	Until then, you might get away with switching fonts at runtime (see \(L"Can I switch the fonts at runtime?\(R" later in this document).
635	.Sh "Keyboard, Mouse & User Interaction"	656	.Sh "Keyboard, Mouse & User Interaction"
636	.IX Subsection "Keyboard, Mouse & User Interaction"	657	.IX Subsection "Keyboard, Mouse & User Interaction"
637	\fIThe new selection selects pieces that are too big, how can I select single words?\fR	658	\fIThe new selection selects pieces that are too big, how can I select single words?\fR
638	.IX Subsection "The new selection selects pieces that are too big, how can I select single words?"	659	.IX Subsection "The new selection selects pieces that are too big, how can I select single words?"
639	.PP	660	.PP
…		…
663	\&\fBperl-ext-common\fR resource to the empty string, which also keeps	684	\&\fBperl-ext-common\fR resource to the empty string, which also keeps
664	rxvt-unicode from initialising perl, saving memory.	685	rxvt-unicode from initialising perl, saving memory.
665	.PP	686	.PP
666	If you only want to disable specific features, you first have to	687	If you only want to disable specific features, you first have to
667	identify which perl extension is responsible. For this, read the section	688	identify which perl extension is responsible. For this, read the section
668	\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\\|(3) manpage. For	689	\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@URXVT_NAME@@\fIperl\fR\\|(3) manpage. For
669	example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify	690	example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify
670	this \fBperl-ext-common\fR resource:	691	this \fBperl-ext-common\fR resource:
671	.PP	692	.PP
672	.Vb 1	693	.Vb 1
673	\& URxvt.perl-ext-common: default,-selection-popup,-option-popup	694	\& URxvt.perl-ext-common: default,-selection-popup,-option-popup
…		…
765	For starting a new rxvt\-unicode:	786	For starting a new rxvt\-unicode:
766	.PP	787	.PP
767	.Vb 3	788	.Vb 3
768	\& # use Backspace = ^H	789	\& # use Backspace = ^H
769	\& $ stty erase ^H	790	\& $ stty erase ^H
770	\& $ @@RXVT_NAME@@	791	\& $ @@URXVT_NAME@@
771	.Ve	792	.Ve
772	.PP	793	.PP
773	.Vb 3	794	.Vb 3
774	\& # use Backspace = ^?	795	\& # use Backspace = ^?
775	\& $ stty erase ^?	796	\& $ stty erase ^?
776	\& $ @@RXVT_NAME@@	797	\& $ @@URXVT_NAME@@
777	.Ve	798	.Ve
778	.PP	799	.PP
779	Toggle with \f(CW\(C`ESC [ 36 h\(C'\fR / \f(CW\(C`ESC [ 36 l\(C'\fR.	800	Toggle with \f(CW\(C`ESC [ 36 h\(C'\fR / \f(CW\(C`ESC [ 36 l\(C'\fR.
780	.PP	801	.PP
781	For an existing rxvt\-unicode:	802	For an existing rxvt\-unicode:
…		…
814	.PP	835	.PP
815	There are some compile-time selections available via configure. Unless	836	There are some compile-time selections available via configure. Unless
816	you have run \(L"configure\(R" with the \f(CW\(C`\-\-disable\-resources\(C'\fR option you can	837	you have run \(L"configure\(R" with the \f(CW\(C`\-\-disable\-resources\(C'\fR option you can
817	use the `keysym' resource to alter the keystrings associated with keysyms.	838	use the `keysym' resource to alter the keystrings associated with keysyms.
818	.PP	839	.PP
819	Here's an example for a URxvt session started using \f(CW\(C`@@RXVT_NAME@@ \-name URxvt\(C'\fR	840	Here's an example for a URxvt session started using \f(CW\(C`@@URXVT_NAME@@ \-name URxvt\(C'\fR
820	.PP	841	.PP
821	.Vb 20	842	.Vb 20
822	\& URxvt.keysym.Home: \e033[1~	843	\& URxvt.keysym.Home: \e033[1~
823	\& URxvt.keysym.End: \e033[4~	844	\& URxvt.keysym.End: \e033[4~
824	\& URxvt.keysym.C-apostrophe: \e033<C-'>	845	\& URxvt.keysym.C-apostrophe: \e033<C-'>
…		…
858	Rather than have rxvt-unicode try to accommodate all the various possible	879	Rather than have rxvt-unicode try to accommodate all the various possible
859	keyboard mappings, it is better to use `xmodmap' to remap the keys as	880	keyboard mappings, it is better to use `xmodmap' to remap the keys as
860	required for your particular machine.	881	required for your particular machine.
861	.Sh "Terminal Configuration"	882	.Sh "Terminal Configuration"
862	.IX Subsection "Terminal Configuration"	883	.IX Subsection "Terminal Configuration"
		884	\fICan I see a typical configuration?\fR
		885	.IX Subsection "Can I see a typical configuration?"
		886	.PP
		887	The default configuration tries to be xterm\-like, which I don't like that
		888	much, but it's least surprise to regular users.
		889	.PP
		890	As a rxvt or rxvt-unicode user, you are practically supposed to invest
		891	time into customising your terminal. To get you started, here is the
		892	author's .Xdefaults entries, with comments on what they do:
		893	.PP
		894	.Vb 2
		895	\& URxvt.cutchars: "()*,<>[]{}\|'
		896	\& URxvt.print-pipe: cat >/tmp/xxx
		897	.Ve
		898	.PP
		899	These are just for testing stuff.
		900	.PP
		901	.Vb 2
		902	\& URxvt.imLocale: ja_JP.UTF-8
		903	\& URxvt.preeditType: OnTheSpot,None
		904	.Ve
		905	.PP
		906	This tells rxvt-unicode to use a special locale when communicating with
		907	the X Input Method, and also tells it to only use the OnTheSpot pre-edit
		908	type, which requires the \f(CW\(C`xim\-onthespot\(C'\fR perl extension but rewards me
		909	with correct-looking fonts.
		910	.PP
		911	.Vb 6
		912	\& URxvt.perl-lib: /root/lib/urxvt
		913	\& URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
		914	\& URxvt.selection.pattern-0: ( at .*? line \e\ed+)
		915	\& URxvt.selection.pattern-1: ^(/[^:]+):\e
		916	\& URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\e\ed+):?$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/
		917	\& URxvt.selection-autotransform.1: s/^ at (.*?) line (\e\ed+)$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/
		918	.Ve
		919	.PP
		920	This is my perl configuration. The first two set the perl library
		921	directory and also tells urxvt to use a large number of extensions. I
		922	develop for myself mostly, so I actually use most of the extensions I
		923	write.
		924	.PP
		925	The selection stuff mainly makes the selection perl-error-message aware
		926	and tells it to convert pelr error mssages into vi-commands to load the
		927	relevant file and go tot he error line number.
		928	.PP
		929	.Vb 2
		930	\& URxvt.scrollstyle: plain
		931	\& URxvt.secondaryScroll: true
		932	.Ve
		933	.PP
		934	As the documentation says: plain is the preferred scrollbar for the
		935	author. The \f(CW\(C`secondaryScroll\(C'\fR confgiures urxvt to scroll in full-screen
		936	apps, like screen, so lines scorlled out of screen end up in urxvt's
		937	scrollback buffer.
		938	.PP
		939	.Vb 7
		940	\& URxvt.background: #000000
		941	\& URxvt.foreground: gray90
		942	\& URxvt.color7: gray90
		943	\& URxvt.colorBD: #ffffff
		944	\& URxvt.cursorColor: #e0e080
		945	\& URxvt.throughColor: #8080f0
		946	\& URxvt.highlightColor: #f0f0f0
		947	.Ve
		948	.PP
		949	Some colours. Not sure which ones are being used or even non\-defaults, but
		950	these are in my .Xdefaults. Most notably, they set foreground/background
		951	to light gray/black, and also make sure that the colour 7 matches the
		952	default foreground colour.
		953	.PP
		954	.Vb 1
		955	\& URxvt.underlineColor: yellow
		956	.Ve
		957	.PP
		958	Another colour, makes underline lines look different. Sometimes hurts, but
		959	is mostly a nice effect.
		960	.PP
		961	.Vb 4
		962	\& URxvt.geometry: 154x36
		963	\& URxvt.loginShell: false
		964	\& URxvt.meta: ignore
		965	\& URxvt.utmpInhibit: true
		966	.Ve
		967	.PP
		968	Uh, well, should be mostly self\-explanatory. By specifying some defaults
		969	manually, I can quickly switch them for testing.
		970	.PP
		971	.Vb 1
		972	\& URxvt.saveLines: 8192
		973	.Ve
		974	.PP
		975	A large scrollback buffer is essential. Really.
		976	.PP
		977	.Vb 1
		978	\& URxvt.mapAlert: true
		979	.Ve
		980	.PP
		981	The only case I use it is for my \s-1IRC\s0 window, which I like to keep
		982	iconified till people msg me (which beeps).
		983	.PP
		984	.Vb 1
		985	\& URxvt.visualBell: true
		986	.Ve
		987	.PP
		988	The audible bell is often annoying, especially when in a crowd.
		989	.PP
		990	.Vb 1
		991	\& URxvt.insecure: true
		992	.Ve
		993	.PP
		994	Please don't hack my mutt! Ooops...
		995	.PP
		996	.Vb 1
		997	\& URxvt.pastableTabs: false
		998	.Ve
		999	.PP
		1000	I once thought this is a great idea.
		1001	.PP
		1002	.Vb 9
		1003	\& urxvt.font: 9x15bold,\e
		1004	\& -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\e
		1005	\& -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \e
		1006	\& [codeset=JISX0208]xft:Kochi Gothic, \e
		1007	\& xft:Bitstream Vera Sans Mono:autohint=true, \e
		1008	\& xft:Code2000:antialias=false
		1009	\& urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
		1010	\& urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
		1011	\& urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
		1012	.Ve
		1013	.PP
		1014	I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
		1015	overwhelmed. A special note: the \f(CW\(C`9x15bold\(C'\fR mentioend above is actually
		1016	the version from XFree\-3.3, as XFree\-4 replaced it by a totally different
		1017	font (different glyphs for \f(CW\(C`;\(C'\fR and many other harmless characters),
		1018	while the second font is actually the \f(CW\(C`9x15bold\(C'\fR from XFree4/XOrg. The
		1019	bold version has less chars than the medium version, so I use it for rare
		1020	characters, too. Whene ditign sources with vim, I use italic for comments
		1021	and other stuff, which looks quite good with Bitstream Vera anti\-aliased.
		1022	.PP
		1023	Terminus is a quite bad font (many very wrong glyphs), but for most of my
		1024	purposes, it works, and gives a different look, as my normal (Non\-bold)
		1025	font is already bold, and I want to see a difference between bold and
		1026	normal fonts.
		1027	.PP
		1028	Please note that I used the \f(CW\(C`urxvt\(C'\fR instance name and not the \f(CW\(C`URxvt\(C'\fR
		1029	class name. Thats because I use different configs for different purposes,
		1030	for example, my \s-1IRC\s0 window is started with \f(CW\(C`\-name IRC\(C'\fR, and uses these
		1031	defaults:
		1032	.PP
		1033	.Vb 9
		1034	\& IRC*title: IRC
		1035	\& IRC*geometry: 87x12+535+542
		1036	\& IRC*saveLines: 0
		1037	\& IRC*mapAlert: true
		1038	\& IRC*font: suxuseuro
		1039	\& IRC*boldFont: suxuseuro
		1040	\& IRC*colorBD: white
		1041	\& IRC*keysym.M-C-1: command:\e033]710;suxuseuro\e007\e033]711;suxuseuro\e007
		1042	\& IRC*keysym.M-C-2: command:\e033]710;9x15bold\e007\e033]711;9x15bold\e007
		1043	.Ve
		1044	.PP
		1045	\&\f(CW\(C`Alt\-Shift\-1\(C'\fR and \f(CW\(C`Alt\-Shift\-2\(C'\fR switch between two different font
		1046	sizes. \f(CW\(C`suxuseuro\(C'\fR allows me to keep an eye (and actually read)
		1047	stuff while keeping a very small window. If somebody pastes something
		1048	complicated (e.g. japanese), I temporarily switch to a larger font.
		1049	.PP
		1050	The above is all in my \f(CW\(C`.Xdefaults\(C'\fR (I don't use \f(CW\(C`.Xresources\(C'\fR nor
		1051	\&\f(CW\(C`xrdb\(C'\fR). I also have some resources in a separate \f(CW\(C`.Xdefaults\-hostname\(C'\fR
		1052	file for different hosts, for example, on ym main desktop, I use:
		1053	.PP
		1054	.Vb 5
		1055	\& URxvt.keysym.C-M-q: command:\e033[3;5;5t
		1056	\& URxvt.keysym.C-M-y: command:\e033[3;5;606t
		1057	\& URxvt.keysym.C-M-e: command:\e033[3;1605;5t
		1058	\& URxvt.keysym.C-M-c: command:\e033[3;1605;606t
		1059	\& URxvt.keysym.C-M-p: perl:test
		1060	.Ve
		1061	.PP
		1062	The first for keysym definitions allow me to quickly bring some windows
		1063	in the layout I like most. Ion users might start laughing but will stop
		1064	immediately when I tell them that I use my own Fvwm2 module for much the
		1065	same effect as Ion provides, and I only very rarely use the above key
		1066	combinations :\->
		1067	.PP
863	\fIWhy doesn't rxvt-unicode read my resources?\fR	1068	\fIWhy doesn't rxvt-unicode read my resources?\fR
864	.IX Subsection "Why doesn't rxvt-unicode read my resources?"	1069	.IX Subsection "Why doesn't rxvt-unicode read my resources?"
865	.PP	1070	.PP
866	Well, why, indeed? It does, in a way very similar to other X	1071	Well, why, indeed? It does, in a way very similar to other X
867	applications. Most importantly, this means that if you or your \s-1OS\s0 loads	1072	applications. Most importantly, this means that if you or your \s-1OS\s0 loads
…		…
912	.Vb 1	1117	.Vb 1
913	\& URxvt.termName: rxvt	1118	\& URxvt.termName: rxvt
914	.Ve	1119	.Ve
915	.PP	1120	.PP
916	If you don't plan to use \fBrxvt\fR (quite common...) you could also replace	1121	If you don't plan to use \fBrxvt\fR (quite common...) you could also replace
917	the rxvt terminfo file with the rxvt-unicode one.	1122	the rxvt terminfo file with the rxvt-unicode one and use \f(CW\(C`TERM=rxvt\(C'\fR.
918	.PP	1123	.PP
919	\fI\f(CI\(C`tic\(C'\fI outputs some error when compiling the terminfo entry.\fR	1124	\fI\f(CI\(C`tic\(C'\fI outputs some error when compiling the terminfo entry.\fR
920	.IX Subsection "tic outputs some error when compiling the terminfo entry."	1125	.IX Subsection "tic outputs some error when compiling the terminfo entry."
921	.PP	1126	.PP
922	Most likely it's the empty definition for \f(CW\(C`enacs=\(C'\fR. Just replace it by	1127	Most likely it's the empty definition for \f(CW\(C`enacs=\(C'\fR. Just replace it by
923	\&\f(CW\(C`enacs=\eE[0@\(C'\fR and try again.	1128	\&\f(CW\(C`enacs=\eE[0@\(C'\fR and try again.
924	.PP	1129	.PP
925	\fI\f(CI\(C`bash\(C'\fI's readline does not work correctly under @@RXVT_NAME@@.\fR	1130	\fI\f(CI\(C`bash\(C'\fI's readline does not work correctly under @@URXVT_NAME@@.\fR
926	.IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@."	1131	.IX Subsection "bash's readline does not work correctly under @@URXVT_NAME@@."
927	.PP	1132	.PP
928	See next entry.	1133	See next entry.
929	.PP	1134	.PP
930	\fII need a termcap file entry.\fR	1135	\fII need a termcap file entry.\fR
931	.IX Subsection "I need a termcap file entry."	1136	.IX Subsection "I need a termcap file entry."
…		…
1117	.PP	1322	.PP
1118	You can also use xterm's \f(CW\(C`luit\(C'\fR program, which usually works fine, except	1323	You can also use xterm's \f(CW\(C`luit\(C'\fR program, which usually works fine, except
1119	for some locales where character width differs between program\- and	1324	for some locales where character width differs between program\- and
1120	rxvt\-unicode\-locales.	1325	rxvt\-unicode\-locales.
1121	.PP	1326	.PP
		1327	\fII have problems getting my input method working.\fR
		1328	.IX Subsection "I have problems getting my input method working."
		1329	.PP
		1330	Try a search engine, as this is slightly different for every input method server.
		1331	.PP
		1332	Here is a checklist:
		1333	.IP "\- Make sure your locale \fIand\fR the imLocale are supported on your \s-1OS\s0." 4
		1334	.IX Item "- Make sure your locale and the imLocale are supported on your OS."
		1335	Try \f(CW\(C`locale \-a\(C'\fR or check the documentation for your \s-1OS\s0.
		1336	.IP "\- Make sure your locale or imLocale matches a locale supported by your \s-1XIM\s0." 4
		1337	.IX Item "- Make sure your locale or imLocale matches a locale supported by your XIM."
		1338	For example, \fBkinput2\fR does not support \s-1UTF\-8\s0 locales, you should use
		1339	\&\f(CW\(C`ja_JP.EUC\-JP\(C'\fR or equivalent.
		1340	.IP "\- Make sure your \s-1XIM\s0 server is actually running." 4
		1341	.IX Item "- Make sure your XIM server is actually running."
		1342	.PD 0
		1343	.ie n .IP "\- Make sure the ""XMODIFIERS""\fR environment variable is set correctly when \fIstarting rxvt\-unicode." 4
		1344	.el .IP "\- Make sure the \f(CWXMODIFIERS\fR environment variable is set correctly when \fIstarting\fR rxvt\-unicode." 4
		1345	.IX Item "- Make sure the XMODIFIERS environment variable is set correctly when starting rxvt-unicode."
		1346	.PD
		1347	When you want to use e.g. \fBkinput2\fR, it must be set to
		1348	\&\f(CW\(C`@im=kinput2\(C'\fR. For \fBscim\fR, use \f(CW\(C`@im=SCIM\(C'\fR. Youc an see what input
		1349	method servers are running with this command:
		1350	.Sp
		1351	.Vb 1
		1352	\& xprop -root XIM_SERVERS
		1353	.Ve
		1354	.IP "*" 4
		1355	.PP
1122	\fIMy input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?\fR	1356	\fIMy input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?\fR
1123	.IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?"	1357	.IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?"
1124	.PP	1358	.PP
1125	You can specify separate locales for the input method and the rest of the	1359	You can specify separate locales for the input method and the rest of the
1126	terminal, using the resource \f(CW\(C`imlocale\(C'\fR:	1360	terminal, using the resource \f(CW\(C`imlocale\(C'\fR:
…		…
1128	.Vb 1	1362	.Vb 1
1129	\& URxvt.imlocale: ja_JP.EUC-JP	1363	\& URxvt.imlocale: ja_JP.EUC-JP
1130	.Ve	1364	.Ve
1131	.PP	1365	.PP
1132	Now you can start your terminal with \f(CW\(C`LC_CTYPE=ja_JP.UTF\-8\(C'\fR and still	1366	Now you can start your terminal with \f(CW\(C`LC_CTYPE=ja_JP.UTF\-8\(C'\fR and still
1133	use your input method. Please note, however, that you will not be able to	1367	use your input method. Please note, however, that, depending on your Xlib
1134	input characters outside \f(CW\(C`EUC\-JP\(C'\fR in a normal way then, as your input	1368	version, you may not be able to input characters outside \f(CW\(C`EUC\-JP\(C'\fR in a
1135	method limits you.	1369	normal way then, as your input method limits you.
1136	.PP	1370	.PP
1137	\fIRxvt-unicode crashes when the X Input Method changes or exits.\fR	1371	\fIRxvt-unicode crashes when the X Input Method changes or exits.\fR
1138	.IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits."	1372	.IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits."
1139	.PP	1373	.PP
1140	Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by	1374	Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by
…		…
1264	old libW11 emulation.	1498	old libW11 emulation.
1265	.PP	1499	.PP
1266	At the time of this writing, cygwin didn't seem to support any multi-byte	1500	At the time of this writing, cygwin didn't seem to support any multi-byte
1267	encodings (you might try \f(CW\(C`LC_CTYPE=C\-UTF\-8\(C'\fR), so you are likely limited	1501	encodings (you might try \f(CW\(C`LC_CTYPE=C\-UTF\-8\(C'\fR), so you are likely limited
1268	to 8\-bit encodings.	1502	to 8\-bit encodings.
1269	.SH "RXVT TECHNICAL REFERENCE"	1503	.SH "RXVT-UNICODE TECHNICAL REFERENCE"
1270	.IX Header "RXVT TECHNICAL REFERENCE"	1504	.IX Header "RXVT-UNICODE TECHNICAL REFERENCE"
1271	.SH "DESCRIPTION"
1272	.IX Header "DESCRIPTION"
1273	The rest of this document describes various technical aspects of	1505	The rest of this document describes various technical aspects of
1274	\&\fBrxvt-unicode\fR. First the description of supported command sequences,	1506	\&\fBrxvt-unicode\fR. First the description of supported command sequences,
1275	followed by pixmap support and last by a description of all features	1507	followed by pixmap support and last by a description of all features
1276	selectable at \f(CW\(C`configure\(C'\fR time.	1508	selectable at \f(CW\(C`configure\(C'\fR time.
1277	.SH "Definitions"	1509	.Sh "Definitions"
1278	.IX Header "Definitions"	1510	.IX Subsection "Definitions"
1279	.ie n .IP "\fB\fB""c""\fB\fR" 4	1511	.ie n .IP "\fB\fB""c""\fB\fR" 4
1280	.el .IP "\fB\f(CBc\fB\fR" 4	1512	.el .IP "\fB\f(CBc\fB\fR" 4
1281	.IX Item "c"	1513	.IX Item "c"
1282	The literal character c.	1514	The literal character c.
1283	.ie n .IP "\fB\fB""C""\fB\fR" 4	1515	.ie n .IP "\fB\fB""C""\fB\fR" 4
…		…
1296	parameters, separated by \f(CW\(C`;\(C'\fR character(s).	1528	parameters, separated by \f(CW\(C`;\(C'\fR character(s).
1297	.ie n .IP "\fB\fB""Pt""\fB\fR" 4	1529	.ie n .IP "\fB\fB""Pt""\fB\fR" 4
1298	.el .IP "\fB\f(CBPt\fB\fR" 4	1530	.el .IP "\fB\f(CBPt\fB\fR" 4
1299	.IX Item "Pt"	1531	.IX Item "Pt"
1300	A text parameter composed of printable characters.	1532	A text parameter composed of printable characters.
1301	.SH "Values"	1533	.Sh "Values"
1302	.IX Header "Values"	1534	.IX Subsection "Values"
1303	.ie n .IP "\fB\fB""ENQ""\fB\fR" 4	1535	.ie n .IP "\fB\fB""ENQ""\fB\fR" 4
1304	.el .IP "\fB\f(CBENQ\fB\fR" 4	1536	.el .IP "\fB\f(CBENQ\fB\fR" 4
1305	.IX Item "ENQ"	1537	.IX Item "ENQ"
1306	Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0)	1538	Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0)
1307	request attributes from terminal. See \fB\f(CB\(C`ESC [ Ps c\(C'\fB\fR.	1539	request attributes from terminal. See \fB\f(CB\(C`ESC [ Ps c\(C'\fB\fR.
…		…
1345	Switch to Standard Character Set	1577	Switch to Standard Character Set
1346	.ie n .IP "\fB\fB""SPC""\fB\fR" 4	1578	.ie n .IP "\fB\fB""SPC""\fB\fR" 4
1347	.el .IP "\fB\f(CBSPC\fB\fR" 4	1579	.el .IP "\fB\f(CBSPC\fB\fR" 4
1348	.IX Item "SPC"	1580	.IX Item "SPC"
1349	Space Character	1581	Space Character
1350	.SH "Escape Sequences"	1582	.Sh "Escape Sequences"
1351	.IX Header "Escape Sequences"	1583	.IX Subsection "Escape Sequences"
1352	.ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4	1584	.ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4
1353	.el .IP "\fB\f(CBESC # 8\fB\fR" 4	1585	.el .IP "\fB\f(CBESC # 8\fB\fR" 4
1354	.IX Item "ESC # 8"	1586	.IX Item "ESC # 8"
1355	\&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0)	1587	\&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0)
1356	.ie n .IP "\fB\fB""ESC 7""\fB\fR" 4	1588	.ie n .IP "\fB\fB""ESC 7""\fB\fR" 4
…		…
1449	.TE	1681	.TE
1450		1682
1451	.PP	1683	.PP
1452		1684
1453	.IX Xref "CSI"	1685	.IX Xref "CSI"
1454	.SH "CSI (Command Sequence Introducer) Sequences"	1686	.Sh "\s-1CSI\s0 (Command Sequence Introducer) Sequences"
1455	.IX Header "CSI (Command Sequence Introducer) Sequences"	1687	.IX Subsection "CSI (Command Sequence Introducer) Sequences"
1456	.ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4	1688	.ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4
1457	.el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4	1689	.el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4
1458	.IX Item "ESC [ Ps @"	1690	.IX Item "ESC [ Ps @"
1459	Insert \fB\f(CB\(C`Ps\(C'\fB\fR (Blank) Character(s) [default: 1] (\s-1ICH\s0)	1691	Insert \fB\f(CB\(C`Ps\(C'\fB\fR (Blank) Character(s) [default: 1] (\s-1ICH\s0)
1460	.IX Xref "ESCOBPsA"	1692	.IX Xref "ESCOBPsA"
…		…
1723	.IX Item "ESC [ Ps x"	1955	.IX Item "ESC [ Ps x"
1724	Request Terminal Parameters (\s-1DECREQTPARM\s0)	1956	Request Terminal Parameters (\s-1DECREQTPARM\s0)
1725	.PP	1957	.PP
1726		1958
1727	.IX Xref "PrivateModes"	1959	.IX Xref "PrivateModes"
1728	.SH "DEC Private Modes"	1960	.Sh "\s-1DEC\s0 Private Modes"
1729	.IX Header "DEC Private Modes"	1961	.IX Subsection "DEC Private Modes"
1730	.ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4	1962	.ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4
1731	.el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4	1963	.el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4
1732	.IX Item "ESC [ ? Pm h"	1964	.IX Item "ESC [ ? Pm h"
1733	\&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0)	1965	\&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0)
1734	.ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4	1966	.ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4
…		…
2001	.RE	2233	.RE
2002	.PD	2234	.PD
2003	.PP	2235	.PP
2004		2236
2005	.IX Xref "XTerm"	2237	.IX Xref "XTerm"
2006	.SH "XTerm Operating System Commands"	2238	.Sh "XTerm Operating System Commands"
2007	.IX Header "XTerm Operating System Commands"	2239	.IX Subsection "XTerm Operating System Commands"
2008	.ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4	2240	.ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4
2009	.el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4	2241	.el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4
2010	.IX Item "ESC ] Ps;Pt ST"	2242	.IX Item "ESC ] Ps;Pt ST"
2011	Set XTerm Parameters. 8\-bit \s-1ST:\s0 0x9c, 7\-bit \s-1ST\s0 sequence: \s-1ESC\s0 \e (0x1b,	2243	Set XTerm Parameters. 8\-bit \s-1ST:\s0 0x9c, 7\-bit \s-1ST\s0 sequence: \s-1ESC\s0 \e (0x1b,
2012	0x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any	2244	0x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any
…		…
2044	Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).	2276	Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
2045	Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).	2277	Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
2046	Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).	2278	Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).
2047	.TE	2279	.TE
2048		2280
2049	.PP
2050
2051	.IX Xref "XPM"
2052	.SH "XPM"	2281	.SH "XPM"
2053	.IX Header "XPM"	2282	.IX Header "XPM"
2054	For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\(C`ESC ] 20 ; Pt ST\(C'\fB\fR then value	2283	For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\(C`ESC ] 20 ; Pt ST\(C'\fB\fR then value
2055	of \fB\f(CB\(C`Pt\(C'\fB\fR can be the name of the background pixmap followed by a	2284	of \fB\f(CB\(C`Pt\(C'\fB\fR can be the name of the background pixmap followed by a
2056	sequence of scaling/positioning commands separated by semi\-colons. The	2285	sequence of scaling/positioning commands separated by semi\-colons. The
…		…
2126	.TS	2355	.TS
2127	l l .	2356	l l .
2128	4 Shift	2357	4 Shift
2129	8 Meta	2358	8 Meta
2130	16 Control	2359	16 Control
2131	32 Double Click (Rxvt extension)	2360	32 Double Click (rxvt extension)
2132	.TE	2361	.TE
2133		2362
2134	Col = \fB\f(CB\(C`<x> \- SPACE\(C'\fB\fR	2363	Col = \fB\f(CB\(C`<x> \- SPACE\(C'\fB\fR
2135	.Sp	2364	.Sp
2136	Row = \fB\f(CB\(C`<y> \- SPACE\(C'\fB\fR	2365	Row = \fB\f(CB\(C`<y> \- SPACE\(C'\fB\fR
…		…
2425	.IX Item "--disable-new-selection"	2654	.IX Item "--disable-new-selection"
2426	Remove support for mouse selection style like that of xterm.	2655	Remove support for mouse selection style like that of xterm.
2427	.IP "\-\-enable\-dmalloc (default: off)" 4	2656	.IP "\-\-enable\-dmalloc (default: off)" 4
2428	.IX Item "--enable-dmalloc (default: off)"	2657	.IX Item "--enable-dmalloc (default: off)"
2429	Use Gray Watson's malloc \- which is good for debugging See	2658	Use Gray Watson's malloc \- which is good for debugging See
2430	http://www.letters.com/dmalloc/ for details If you use either this or the	2659	<http://www.letters.com/dmalloc/> for details If you use either this or the
2431	next option, you may need to edit src/Makefile after compiling to point	2660	next option, you may need to edit src/Makefile after compiling to point
2432	\&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places.	2661	\&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places.
2433	.Sp	2662	.Sp
2434	You can only use either this option and the following (should	2663	You can only use either this option and the following (should
2435	you use either) .	2664	you use either) .

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents): Revision 1.62 by root, Tue Jan 31 20:50:48 2006 UTC vs. Revision 1.73 by root, Tue Feb 21 01:00:40 2006 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.62 by root, Tue Jan 31 20:50:48 2006 UTC vs.
Revision 1.73 by root, Tue Feb 21 01:00:40 2006 UTC