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

Comparing rxvt-unicode/doc/rxvt.7.html (file contents):
Revision 1.66 by root, Tue Jan 31 21:06:26 2006 UTC vs.
Revision 1.67 by root, Tue Jan 31 21:10:44 2006 UTC

 		<li><a href="#rendering__font___look_and_feel_issues">Rendering, Font &amp; Look and Feel Issues</a></li>
 		<ul>
 			<li><a href="#i_can_t_get_transparency_working__what_am_i_doing_wrong">I can't get transparency working, what am I doing wrong?</a></li>
-			<li><a href="#why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></li>
 			<li><a href="#why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></li>
 			<li><a href="#how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></li>
 			<li><a href="#some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></li>
 			<li><a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></li>
 			<li><a href="#why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></li>
 			<li><a href="#can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></li>
 			<li><a href="#rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></li>
 			<li><a href="#what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></li>
 			<li><a href="#i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors.  How do I change them?</a></li>
 			<li><a href="#why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></li>
+			<li><a href="#how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></li>
+			<li><a href="#why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></li>
 		</ul>
 		<li><a href="#keyboard__mouse___user_interaction">Keyboard, Mouse &amp; User Interaction</a></li>
 		<ul>
 		</ul>
 	</ul>
 	<li><a href="#rxvtunicode_technical_reference">RXVT-UNICODE TECHNICAL REFERENCE</a></li>
-	<li><a href="#description">DESCRIPTION</a></li>
+	<ul>
-	<li><a href="#definitions">Definitions</a></li>
+		<li><a href="#definitions">Definitions</a></li>
-	<li><a href="#values">Values</a></li>
+		<li><a href="#values">Values</a></li>
-	<li><a href="#escape_sequences">Escape Sequences</a></li>
+		<li><a href="#escape_sequences">Escape Sequences</a></li>
-	<li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li>
+		<li><a href="#csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></li>
-	<li><a href="#dec_private_modes">DEC Private Modes</a></li>
+		<li><a href="#dec_private_modes">DEC Private Modes</a></li>
-	<li><a href="#xterm_operating_system_commands">XTerm Operating System Commands</a></li>
+		<li><a href="#xterm_operating_system_commands">XTerm Operating System Commands</a></li>
+	</ul>
 	<li><a href="#xpm">XPM</a></li>
 	<li><a href="#mouse_reporting">Mouse Reporting</a></li>
 	<li><a href="#key_codes">Key Codes</a></li>
 	<li><a href="#configure_options">CONFIGURE OPTIONS</a></li>
 	<li><a href="#authors">AUTHORS</a></li>
 <p>Then click on a window you want to make transparent. Replace <code>0xc0000000</code>
 by other values to change the degree of opacity. If it doesn't work and
 your server crashes, you got to keep the pieces.</p>
 <p>
 </p>
+<h3><a name="why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></h3>
+<p>Most fonts were not designed for terminal use, which means that character
+size varies a lot. A font that is otherwise fine for terminal use might
+contain some characters that are simply too wide. Rxvt-unicode will avoid
+these characters. For characters that are just ``a bit'' too wide a special
+``careful'' rendering mode is used that redraws adjacent characters.</p>
+<p>All of this requires that fonts do not lie about character sizes,
+however: Xft fonts often draw glyphs larger than their acclaimed bounding
+box, and rxvt-unicode has no way of detecting this (the correct way is to
+ask for the character bounding box, which unfortunately is wrong in these
+cases).</p>
+<p>It's not clear (to me at least), wether this is a bug in Xft, freetype,
+or the respective font. If you encounter this problem you might try using
+the <code>-lsp</code> option to give the font more height. If that doesn't work, you
+might be forced to use a different font.</p>
+<p>All of this is not a problem when using X11 core fonts, as their bounding
+box data is correct.</p>
+<p>
+</p>
+<h3><a name="how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></h3>
+<p>First of all, make sure you are running with the right terminal settings
+(<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then
+make sure you have specified colours for italic and bold, as otherwise
+rxvt-unicode might use reverse video to simulate the effect:</p>
+<pre>
+   URxvt.colorBD:  white
+   URxvt.colorIT:  green</pre>
+<p>
+</p>
+<h3><a name="some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></h3>
+<p>For some unexplainable reason, some rare programs assume a very weird
+colour palette when confronted with a terminal with more than the standard
+8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
+these programs not to assume non-ISO colours without very good reasons.</p>
+<p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo
+definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will
+fix colours but keep you from using other rxvt-unicode features.</p>
+<p>
+</p>
+<h3><a name="can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></h3>
+<p>Yes, using an escape sequence. Try something like this, which has the same
+effect as using the <code>-fn</code> switch, and takes effect immediately:</p>
+<pre>
+   printf '\e]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre>
+<p>This is useful if you e.g. work primarily with japanese (and prefer a
+japanese font), but you have to switch to chinese temporarily, where
+japanese fonts would only be in your way.</p>
+<p>You can think of this as a kind of manual ISO-2022 switching.</p>
+<p>
+</p>
+<h3><a name="why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></h3>
+<p>Many fonts have difficulties with italic characters and hinting. For
+example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans
+Mono</code> completely fails in it's italic face. A workaround might be to
+enable freetype autohinting, i.e. like this:</p>
+<pre>
+   URxvt.italicFont:        xft:Bitstream Vera Sans Mono:italic:autohint=true
+   URxvt.boldItalicFont:    xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
+<p>
+</p>
+<h3><a name="can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></h3>
+<p>Yes, the most obvious way to speed it up is to avoid Xft entirely, as
+it is simply slow. If you still want Xft fonts you might try to disable
+antialiasing (by appending <code>:antialias=false</code>), which saves lots of
+memory and also speeds up rendering considerably.</p>
+<p>
+</p>
+<h3><a name="rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></h3>
+<p>Rxvt-unicode will use whatever you specify as a font. If it needs to
+fall back to it's default font search list it will prefer X11 core
+fonts, because they are small and fast, and then use Xft fonts. It has
+antialiasing disabled for most of them, because the author thinks they
+look best that way.</p>
+<p>If you want antialiasing, you have to specify the fonts manually.</p>
+<p>
+</p>
+<h3><a name="what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></h3>
+<p>If no bold colour is set via <code>colorBD:</code>, bold will invert text using the
+standard foreground colour.</p>
+<p>For the standard background colour, blinking will actually make the
+text blink when compiled with <code>--enable-blinking</code>. with standard
+colours. Without <code>--enable-blinking</code>, the blink attribute will be
+ignored.</p>
+<p>On ANSI colours, bold/blink attributes are used to set high-intensity
+foreground/background colors.</p>
+<p>color0-7 are the low-intensity colors.</p>
+<p>color8-15 are the corresponding high-intensity colors.</p>
+<p>
+</p>
+<h3><a name="i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors.  How do I change them?</a></h3>
+<p>You can change the screen colors at run-time using <em>~/.Xdefaults</em>
+resources (or as long-options).</p>
+<p>Here are values that are supposed to resemble a VGA screen,
+including the murky brown that passes for low-intensity yellow:</p>
+<pre>
+   URxvt.color0:   #000000
+   URxvt.color1:   #A80000
+   URxvt.color2:   #00A800
+   URxvt.color3:   #A8A800
+   URxvt.color4:   #0000A8
+   URxvt.color5:   #A800A8
+   URxvt.color6:   #00A8A8
+   URxvt.color7:   #A8A8A8</pre>
+<pre>
+   URxvt.color8:   #000054
+   URxvt.color9:   #FF0054
+   URxvt.color10:  #00FF54
+   URxvt.color11:  #FFFF54
+   URxvt.color12:  #0000FF
+   URxvt.color13:  #FF00FF
+   URxvt.color14:  #00FFFF
+   URxvt.color15:  #FFFFFF</pre>
+<p>And here is a more complete set of non-standard colors.</p>
+<pre>
+   URxvt.cursorColor:  #dc74d1
+   URxvt.pointerColor: #dc74d1
+   URxvt.background:   #0e0e0e
+   URxvt.foreground:   #4ad5e1
+   URxvt.color0:       #000000
+   URxvt.color8:       #8b8f93
+   URxvt.color1:       #dc74d1
+   URxvt.color9:       #dc74d1
+   URxvt.color2:       #0eb8c7
+   URxvt.color10:      #0eb8c7
+   URxvt.color3:       #dfe37e
+   URxvt.color11:      #dfe37e
+   URxvt.color5:       #9e88f0
+   URxvt.color13:      #9e88f0
+   URxvt.color6:       #73f7ff
+   URxvt.color14:      #73f7ff
+   URxvt.color7:       #e1dddd
+   URxvt.color15:      #e1dddd</pre>
+<p>They have been described (not by me) as ``pretty girly''.</p>
+<p>
+</p>
+<h3><a name="why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></h3>
+<p>See next entry.</p>
+<p>
+</p>
+<h3><a name="how_does_rxvtunicode_choose_fonts">How does rxvt-unicode choose fonts?</a></h3>
+<p>Most fonts do not contain the full range of Unicode, which is
+fine. Chances are that the font you (or the admin/package maintainer of
+your system/os) have specified does not cover all the characters you want
+to display.</p>
+<p><strong>rxvt-unicode</strong> makes a best-effort try at finding a replacement
+font. Often the result is fine, but sometimes the chosen font looks
+bad/ugly/wrong. Some fonts have totally strange characters that don't
+resemble the correct glyph at all, and rxvt-unicode lacks the artificial
+intelligence to detect that a specific glyph is wrong: it has to believe
+the font that the characters it claims to contain indeed look correct.</p>
+<p>In that case, select a font of your taste and add it to the font list,
+e.g.:</p>
+<pre>
+   urxvt -fn basefont,font2,font3...</pre>
+<p>When rxvt-unicode sees a character, it will first look at the base
+font. If the base font does not contain the character, it will go to the
+next font, and so on. Specifying your own fonts will also speed up this
+search and use less resources within rxvt-unicode and the X-server.</p>
+<p>The only limitation is that none of the fonts may be larger than the base
+font, as the base font defines the terminal character cell size, which
+must be the same due to the way terminals work.</p>
+<p>
+</p>
 <h3><a name="why_do_some_chinese_characters_look_so_different_than_others">Why do some chinese characters look so different than others?</a></h3>
 <p>This is because there is a difference between script and language --
 rxvt-unicode does not know which language the text that is output is,
 as it only knows the unicode character codes. If rxvt-unicode first
 sees a japanese/chinese character, it might choose a japanese font for
 <p>In the future it might be possible to switch language preferences at
 runtime (the internal data structure has no problem with using different
 fonts for the same character at the same time, but no interface for this
 has been designed yet).</p>
 <p>Until then, you might get away with switching fonts at runtime (see <a href="#can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a> later in this document).</p>
-<p>
-</p>
-<h3><a name="why_does_rxvtunicode_sometimes_leave_pixel_droppings">Why does rxvt-unicode sometimes leave pixel droppings?</a></h3>
-<p>Most fonts were not designed for terminal use, which means that character
-size varies a lot. A font that is otherwise fine for terminal use might
-contain some characters that are simply too wide. Rxvt-unicode will avoid
-these characters. For characters that are just ``a bit'' too wide a special
-``careful'' rendering mode is used that redraws adjacent characters.</p>
-<p>All of this requires that fonts do not lie about character sizes,
-however: Xft fonts often draw glyphs larger than their acclaimed bounding
-box, and rxvt-unicode has no way of detecting this (the correct way is to
-ask for the character bounding box, which unfortunately is wrong in these
-cases).</p>
-<p>It's not clear (to me at least), wether this is a bug in Xft, freetype,
-or the respective font. If you encounter this problem you might try using
-the <code>-lsp</code> option to give the font more height. If that doesn't work, you
-might be forced to use a different font.</p>
-<p>All of this is not a problem when using X11 core fonts, as their bounding
-box data is correct.</p>
-<p>
-</p>
-<h3><a name="how_can_i_keep_rxvtunicode_from_using_reverse_video_so_much">How can I keep rxvt-unicode from using reverse video so much?</a></h3>
-<p>First of all, make sure you are running with the right terminal settings
-(<code>TERM=rxvt-unicode</code>), which will get rid of most of these effects. Then
-make sure you have specified colours for italic and bold, as otherwise
-rxvt-unicode might use reverse video to simulate the effect:</p>
-<pre>
-   URxvt.colorBD:  white
-   URxvt.colorIT:  green</pre>
-<p>
-</p>
-<h3><a name="some_programs_assume_totally_weird_colours__red_instead_of_blue___how_can_i_fix_that">Some programs assume totally weird colours (red instead of blue), how can I fix that?</a></h3>
-<p>For some unexplainable reason, some rare programs assume a very weird
-colour palette when confronted with a terminal with more than the standard
-8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix
-these programs not to assume non-ISO colours without very good reasons.</p>
-<p>In the meantime, you can either edit your <code>rxvt-unicode</code> terminfo
-definition to only claim 8 colour support or use <code>TERM=rxvt</code>, which will
-fix colours but keep you from using other rxvt-unicode features.</p>
-<p>
-</p>
-<h3><a name="can_i_switch_the_fonts_at_runtime">Can I switch the fonts at runtime?</a></h3>
-<p>Yes, using an escape sequence. Try something like this, which has the same
-effect as using the <code>-fn</code> switch, and takes effect immediately:</p>
-<pre>
-   printf '\e]50;%s\007' &quot;9x15bold,xft:Kochi Gothic&quot;</pre>
-<p>This is useful if you e.g. work primarily with japanese (and prefer a
-japanese font), but you have to switch to chinese temporarily, where
-japanese fonts would only be in your way.</p>
-<p>You can think of this as a kind of manual ISO-2022 switching.</p>
-<p>
-</p>
-<h3><a name="why_do_italic_characters_look_as_if_clipped">Why do italic characters look as if clipped?</a></h3>
-<p>Many fonts have difficulties with italic characters and hinting. For
-example, the otherwise very nicely hinted font <code>xft:Bitstream Vera Sans
-Mono</code> completely fails in it's italic face. A workaround might be to
-enable freetype autohinting, i.e. like this:</p>
-<pre>
-   URxvt.italicFont:        xft:Bitstream Vera Sans Mono:italic:autohint=true
-   URxvt.boldItalicFont:    xft:Bitstream Vera Sans Mono:bold:italic:autohint=true</pre>
-<p>
-</p>
-<h3><a name="can_i_speed_up_xft_rendering_somehow">Can I speed up Xft rendering somehow?</a></h3>
-<p>Yes, the most obvious way to speed it up is to avoid Xft entirely, as
-it is simply slow. If you still want Xft fonts you might try to disable
-antialiasing (by appending <code>:antialias=false</code>), which saves lots of
-memory and also speeds up rendering considerably.</p>
-<p>
-</p>
-<h3><a name="rxvtunicode_doesn_t_seem_to_antialias_its_fonts__what_is_wrong">Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?</a></h3>
-<p>Rxvt-unicode will use whatever you specify as a font. If it needs to
-fall back to it's default font search list it will prefer X11 core
-fonts, because they are small and fast, and then use Xft fonts. It has
-antialiasing disabled for most of them, because the author thinks they
-look best that way.</p>
-<p>If you want antialiasing, you have to specify the fonts manually.</p>
-<p>
-</p>
-<h3><a name="what_s_with_this_bold_blink_stuff">What's with this bold/blink stuff?</a></h3>
-<p>If no bold colour is set via <code>colorBD:</code>, bold will invert text using the
-standard foreground colour.</p>
-<p>For the standard background colour, blinking will actually make the
-text blink when compiled with <code>--enable-blinking</code>. with standard
-colours. Without <code>--enable-blinking</code>, the blink attribute will be
-ignored.</p>
-<p>On ANSI colours, bold/blink attributes are used to set high-intensity
-foreground/background colors.</p>
-<p>color0-7 are the low-intensity colors.</p>
-<p>color8-15 are the corresponding high-intensity colors.</p>
-<p>
-</p>
-<h3><a name="i_don_t_like_the_screen_colors__how_do_i_change_them">I don't like the screen colors.  How do I change them?</a></h3>
-<p>You can change the screen colors at run-time using <em>~/.Xdefaults</em>
-resources (or as long-options).</p>
-<p>Here are values that are supposed to resemble a VGA screen,
-including the murky brown that passes for low-intensity yellow:</p>
-<pre>
-   URxvt.color0:   #000000
-   URxvt.color1:   #A80000
-   URxvt.color2:   #00A800
-   URxvt.color3:   #A8A800
-   URxvt.color4:   #0000A8
-   URxvt.color5:   #A800A8
-   URxvt.color6:   #00A8A8
-   URxvt.color7:   #A8A8A8</pre>
-<pre>
-   URxvt.color8:   #000054
-   URxvt.color9:   #FF0054
-   URxvt.color10:  #00FF54
-   URxvt.color11:  #FFFF54
-   URxvt.color12:  #0000FF
-   URxvt.color13:  #FF00FF
-   URxvt.color14:  #00FFFF
-   URxvt.color15:  #FFFFFF</pre>
-<p>And here is a more complete set of non-standard colors.</p>
-<pre>
-   URxvt.cursorColor:  #dc74d1
-   URxvt.pointerColor: #dc74d1
-   URxvt.background:   #0e0e0e
-   URxvt.foreground:   #4ad5e1
-   URxvt.color0:       #000000
-   URxvt.color8:       #8b8f93
-   URxvt.color1:       #dc74d1
-   URxvt.color9:       #dc74d1
-   URxvt.color2:       #0eb8c7
-   URxvt.color10:      #0eb8c7
-   URxvt.color3:       #dfe37e
-   URxvt.color11:      #dfe37e
-   URxvt.color5:       #9e88f0
-   URxvt.color13:      #9e88f0
-   URxvt.color6:       #73f7ff
-   URxvt.color14:      #73f7ff
-   URxvt.color7:       #e1dddd
-   URxvt.color15:      #e1dddd</pre>
-<p>They have been described (not by me) as ``pretty girly''.</p>
-<p>
-</p>
-<h3><a name="why_do_some_characters_look_so_much_different_than_others">Why do some characters look so much different than others?</a></h3>
-<pre>
-See next entry.</pre>
-<pre>
-=head3 How does rxvt-unicode choose fonts?</pre>
-<pre>
-Most fonts do not contain the full range of Unicode, which is
-fine. Chances are that the font you (or the admin/package maintainer of
-your system/os) have specified does not cover all the characters you want
-to display.</pre>
-<pre>
-B&lt;rxvt-unicode&gt; makes a best-effort try at finding a replacement
-font. Often the result is fine, but sometimes the chosen font looks
-bad/ugly/wrong. Some fonts have totally strange characters that don't
-resemble the correct glyph at all, and rxvt-unicode lacks the artificial
-intelligence to detect that a specific glyph is wrong: it has to believe
-the font that the characters it claims to contain indeed look correct.</pre>
-<pre>
-In that case, select a font of your taste and add it to the font list,
-e.g.:</pre>
-<pre>
-   urxvt -fn basefont,font2,font3...</pre>
-<pre>
-When rxvt-unicode sees a character, it will first look at the base
-font. If the base font does not contain the character, it will go to the
-next font, and so on. Specifying your own fonts will also speed up this
-search and use less resources within rxvt-unicode and the X-server.</pre>
-<pre>
-The only limitation is that none of the fonts may be larger than the base
-font, as the base font defines the terminal character cell size, which
-must be the same due to the way terminals work.</pre>
 <p>
 </p>
 <h2><a name="keyboard__mouse___user_interaction">Keyboard, Mouse &amp; User Interaction</a></h2>
 <p>
 </p>
 to 8-bit encodings.</p>
 <p>
 </p>
 <hr />
 <h1><a name="rxvtunicode_technical_reference">RXVT-UNICODE TECHNICAL REFERENCE</a></h1>
-<p>
-</p>
-<hr />
-<h1><a name="description">DESCRIPTION</a></h1>
 <p>The rest of this document describes various technical aspects of
 <strong>rxvt-unicode</strong>. First the description of supported command sequences,
 followed by pixmap support and last by a description of all features
 selectable at <code>configure</code> time.</p>
 <p>
 </p>
-<hr />
-<h1><a name="definitions">Definitions</a></h1>
+<h2><a name="definitions">Definitions</a></h2>
 <dl>
 <dt><strong><a name="item_c"><strong><code>c</code> </strong>&gt;</a></strong><br />
 </dt>
 <dd>
 The literal character c.
 A text parameter composed of printable characters.
 </dd>
 <p></p></dl>
 <p>
 </p>
-<hr />
-<h1><a name="values">Values</a></h1>
+<h2><a name="values">Values</a></h2>
 <dl>
 <dt><strong><a name="item_enq"><strong><code>ENQ</code> </strong>&gt;</a></strong><br />
 </dt>
 <dd>
 Enquiry (Ctrl-E) = Send Device Attributes (DA)
 Space Character
 </dd>
 <p></p></dl>
 <p>
 </p>
-<hr />
-<h1><a name="escape_sequences">Escape Sequences</a></h1>
+<h2><a name="escape_sequences">Escape Sequences</a></h2>
 <dl>
 <dt><strong><a name="item_esc__23_8"><strong><code>ESC # 8</code> </strong>&gt;</a></strong><br />
 </dt>
 <dd>
 DEC Screen Alignment Test (DECALN)
 <tr><td>C = K </td><td>German character set unimplemented</td></tr>
 </table><p></p></dl>
 <p></p>
 <p>
 </p>
-<hr />
-<h1><a name="csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></h1>
+<h2><a name="csi__command_sequence_introducer__sequences">CSI (Command Sequence Introducer) Sequences</a></h2>
 <dl>
 <dt><strong><a name="item_esc__5b_ps__40"><strong><code>ESC [ Ps @</code> </strong>&gt;</a></strong><br />
 </dt>
 <dd>
 Insert <strong><a href="#item_ps"><code>Ps</code></a> </strong>&gt; (Blank) <code>Character(s)</code> [default: 1] (ICH)
 </dd>
 <p></p></dl>
 <p></p>
 <p>
 </p>
-<hr />
-<h1><a name="dec_private_modes">DEC Private Modes</a></h1>
+<h2><a name="dec_private_modes">DEC Private Modes</a></h2>
 <dl>
 <dt><strong><a name="item_esc__5b__3f_pm_h"><strong><code>ESC [ ? Pm h</code> </strong>&gt;</a></strong><br />
 </dt>
 <dd>
 DEC Private Mode Set (DECSET)
 </table></dl>
 </dl>
 <p></p>
 <p>
 </p>
-<hr />
-<h1><a name="xterm_operating_system_commands">XTerm Operating System Commands</a></h1>
+<h2><a name="xterm_operating_system_commands">XTerm Operating System Commands</a></h2>
 <dl>
 <dt><strong><a name="item_esc__5d_ps_3bpt_st"><strong><code>ESC ] Ps;Pt ST</code> </strong>&gt;</a></strong><br />
 </dt>
 <dd>
 Set XTerm Parameters. 8-bit ST: 0x9c, 7-bit ST sequence: ESC \ (0x1b,
 <tr><td>Ps = 713</td><td>Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).</td></tr>
 <tr><td>Ps = 720</td><td>Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
 <tr><td>Ps = 721</td><td>Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).</td></tr>
 <tr><td>Ps = 777</td><td>Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).</td></tr>
 </table><p></p></dl>
-<p></p>
 <p>
 </p>
 <hr />
 <h1><a name="xpm">XPM</a></h1>
 <p>For the XPM XTerm escape sequence <strong><code>ESC ] 20 ; Pt ST</code> </strong>&gt; then value
 <p></p>
 <dt><strong><a name="item__2d_2dwith_2dxpm_2dincludes_3ddir">--with-xpm-includes=DIR</a></strong><br />
 </dt>
 <dd>
 Look for the XPM includes in DIR.
 </dd>
 <p></p>
 <dt><strong><a name="item__2d_2dwith_2dxpm_2dlibrary_3ddir">--with-xpm-library=DIR</a></strong><br />
 </dt>
 <dd>
 Look for the XPM library in DIR.
 </dd>
 <p></p>
 <dt><strong><a name="item__2d_2dwith_2dxpm">--with-xpm</a></strong><br />
 </dt>
 <dd>
 Not needed - define via --enable-xpm-background.
 </dd>
 <p></p></dl>
 <p>
 </p>
 <hr />
 <h1><a name="authors">AUTHORS</a></h1>
 <p>Marc Lehmann &lt;<a href="mailto:rxvt@schmorp.de">rxvt@schmorp.de</a>&gt; converted this document to pod and
 reworked it from the original Rxvt documentation, which was done by Geoff
 Wing &lt;<a href="mailto:gcw@pobox.com">gcw@pobox.com</a>&gt;, who in turn used the XTerm documentation and other
-sources.
+sources.</p>
-</p>
 </body>
 </html>

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.7.html (file contents): Revision 1.66 by root, Tue Jan 31 21:06:26 2006 UTC vs. Revision 1.67 by root, Tue Jan 31 21:10:44 2006 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.7.html (file contents):
Revision 1.66 by root, Tue Jan 31 21:06:26 2006 UTC vs.
Revision 1.67 by root, Tue Jan 31 21:10:44 2006 UTC