--- rxvt-unicode/doc/rxvt.1.pod 2004/08/16 02:09:28 1.12 +++ rxvt-unicode/doc/rxvt.1.pod 2005/01/16 19:22:16 1.43 @@ -14,6 +14,11 @@ configurability. As a result, B uses much less swap space -- a significant advantage on a machine serving many X sessions. +=head1 FREQUENTLY ASKED QUESTIONS + +See @@RXVT_NAME@@(7) (try C) for a list of frequently +asked questions and answer to them and some common problems. + =head1 RXVT-UNICODE VS. RXVT Unlike the original rxvt, B stores all text in Unicode @@ -26,7 +31,7 @@ fine, though. A somewhat difficult case are left-to-right scripts, such as hebrew: B adopts the view that bidirectional algorithms belong into the application, not the terminal emulator (too many things -- -such as cursor-movement while editing -- break othwerwise), but that might +such as cursor-movement while editing -- break otherwise), but that might change. If you are looking for a terminal that supports more exotic scripts, let @@ -55,8 +60,7 @@ It also makes technical information about escape sequences (which have been extended) easier accessible: see @@RXVT_NAME@@(7) for technical -reference documentation (escape sequences etc.) and the FAQ section at the -end of this document. +reference documentation (escape sequences etc.). =head1 OPTIONS @@ -108,7 +112,7 @@ =item B<-fade> I -Fade the text by the given percentage when focus is lost. +Fade the text by the given percentage when focus is lost. resource B. =item B<-tint> I @@ -121,7 +125,7 @@ I Darken (0 .. 100) or lighten (-1 .. -100) the transparent background image in addition to tinting it (i.e. B<-tint> must be -specified, too). +specified, too, e.g. C<-tint white>). =item B<-bg> I @@ -134,8 +138,8 @@ =item B<-pixmap> I Compile I: Specify XPM file for the background and also optionally -specify its scaling with a geometry string. Note you may need to add -quotes to avoid special shell interpretation of the `;' in the +specify its scaling with a geometry string. Note you may need to +add quotes to avoid special shell interpretation of the C<;> in the command-line; resource B. =item B<-cr> I @@ -152,27 +156,41 @@ =item B<-bd> I -The colour of the border between the xterm scrollbar and the text; +The colour of the border around the text area and between the scrollbar and the text; resource B. -=item B<-fn> I +=item B<-fn> I -Select the fonts to be used. This is a comma seperated list of font -names that are used in turn when trying to display Unicode characters. -The first font defines the cell size for characters; other fonts might -be smaller, but not larger. A reasonable default font list is always -appended to it. resource B. +Select the fonts to be used. This is a comma separated list of font names +that are used in turn when trying to display Unicode characters. The +first font defines the cell size for characters; other fonts might be +smaller, but not (in general) larger. A (hopefully) reasonable default +font list is always appended to it. See resource B for more details. + +In short, to specify an X11 core font, just specify it's name or prefix it +with C. To specify an XFT-font, you need to prefix it with C, +e.g.: + + @@RXVT_NAME@@ -fn "xft:Bitstream Vera Sans Mono:pixelsize=15" + @@RXVT_NAME@@ -fn "9x15bold,xft:Bitstream Vera Sans Mono" See also the question "How does rxvt-unicode choose fonts?" in the FAQ -section. +section of @@RXVT_NAME@@(7). + +=item B<-fb> I + +Compile font-styles: The bold font list to use when bold characters are to +be printed. See resource B for details. -=item B<-rb>|B<+rb> +=item B<-fi> I -Enable "real bold" support. When this option is on, bold text will be -displayed using the first available bold font in the font list. Bold -fonts should thus be specified in the font list after their -corresponding regular fonts. If no bold font can be found, a regular -font will be used. resource B. +Compile font-styles: The italic font list to use when bold characters are to +be printed. See resource B for details. + +=item B<-fbi> I + +Compile font-styles: The bold italic font list to use when bold characters are to +be printed. See resource B for details. =item B<-name> I @@ -223,6 +241,14 @@ Display normal (non XTerm/NeXT) scrollbar without/with a trough; resource B. +=item B<-ptab>|B<+ptab> + +If enabled (default), "Horizontal Tab" characters are being stored as +actual wide characters in the screen buffer, which makes it possible to +select and paste them. Since a horizontal tab is a cursor movement and +not an actual glyph, this can sometimes be visually annoying as the cursor +on a tab character is displayed as a wide cursor; resource B. + =item B<-bc>|B<+bc> Blink the cursor; resource B. @@ -256,8 +282,9 @@ =item B<-lsp> I -Compile I: Lines (pixel height) to insert between each row -of the display; resource B. +Compile I: Lines (pixel height) to insert between each row of +the display. Useful to work around font rendering problems; resource +B. =item B<-tn> I @@ -391,11 +418,19 @@ 3=yellow, 4=blue, 5=magenta, 6=cyan, 7=white, but the actual colour names used are listed in the B section. +Colours higher than 15 cannot be set using resources (yet), but can be +changed using an escape command (see @@RXVT_NAME@@(7)). + +Colours 16-79 form a standard 4x4x4 colour cube (the same as xterm with +88 colour support). Colours 80-87 are evenly spaces grey steps. + =item B I -Use the specified colour to display bold characters when the foreground -colour is the default. This option will be ignored if B is -enabled. +=item B I + +Use the specified colour to display bold or italic characters when the +foreground colour is the default. If font styles are not available +(Compile I) and this option is unset, reverse video is used instead. =item B I @@ -407,6 +442,11 @@ Use the specified colour as the background for reverse video characters. +=item B I + +If set, use the specified colour as the colour for the underline +itself. If unset, use the foreground colour. + =item B I Use the specified colour for the cursor. The default is to use the @@ -449,10 +489,6 @@ Darken (0 .. 100) or lighten (-1 .. -100) the transparent background image in addition to tinting it. -=item B I - -Scale the tint colour by the given percentage. - =item B I Use the specified colour for the scrollbar [default #B2B2B2]. @@ -462,6 +498,11 @@ Use the specified colour for the scrollbar's trough area [default #969696]. Only relevant for normal (non XTerm/NeXT) scrollbar. +=item B I + +The colour of the border around the text area and between the scrollbar +and the text. + =item B I Use the specified XPM file (note the `.xpm' extension is optional) for @@ -486,22 +527,67 @@ menus), in addition to the paths specified by the B and B environment variables. -=item B I +=item B I -Select the fonts to be used. This is a comma seperated list of font +Select the fonts to be used. This is a comma separated list of font names that are used in turn when trying to display Unicode characters. The first font defines the cell size for characters; other fonts might be smaller, but not larger. A reasonable default font list is always appended to it. option B<-fn>. -=item B I +Each font can either be a standard X11 core font (XLFD) name, with +optional prefix C or a Xft font (Compile I), prefixed with C. + +In addition, each font can be prefixed with additional hints and +specifications enclosed in square brackets (C<[]>). The only available +hint currently is C, and this is only used for Xft +fonts. + +For example, this font resource + + URxvt*font: 9x15bold,\ + -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\ + -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \ + [codeset=JISX0208]xft:Kochi Gothic:antialias=false, \ + xft:Code2000:antialias=false + +specifies five fonts to be used. The first one is C<9x15bold> (actually +the iso8859-1 version of the second font), which is the base font (because +it is named first) and thus defines the character cell grid to be 9 pixels +wide and 15 pixels high. + +The second font is just used to add additional unicode characters not in +the base font, likewise the third, which is unfortunately non-bold, but +the bold version of the font does contain less characters, so this is a +useful supplement. + +The third font is an Xft font with aliasing turned off, and the characters +are limited to the B codeset (i.e. japanese kanji). The font +contains other characters, but we are not interested in them. + +The last font is a useful catch-all font that supplies most of the +remaining unicode characters. + +=item B I + +=item B I + +=item B I + +The font list to use for displaying B, I or B<< I >> characters, respectively. + +If specified and non-empty, then the syntax is the same as for the +B-resource, and the given font list will be used as is, which makes +it possible to substitute completely different font styles for bold and +italic. -B: Enable "real bold" support. When this option is on, bold text -will be displayed using the first available bold font in the font list. -Bold fonts should thus be specified in the font list after their -corresponding regular fonts. If no bold font can be found, a regular -font will be used. option B<-rb>. B: Display bold text in a -regular font, using the color specified with B; option B<+rb>. +If unset (the default), a suitable font list will be synthesized by +"morphing" the normal text font list into the desired shape. If that is +not possible, replacement fonts of the desired shape will be tried. + +If set, but empty, then this specific style is disabled and the normal +text font will being used for the given style. =item B I @@ -582,7 +668,7 @@ =item B I -B: scroll with scrollback buffer when tty recieves new lines (and +B: scroll with scrollback buffer when tty receives new lines (and B is False); option B<+sw>. B: do not scroll with scrollback buffer when tty recieves new lines; option B<-sw>. @@ -633,6 +719,11 @@ B: the mouse wheel scrolls a page full. B: the mouse wheel scrolls five lines [default]. +=item B I + +B: store tabs as wide characters. B: interpret tabs as cursor +movement only; option C<-ptab>. + =item B I B: blink the cursor. B: do not blink the cursor [default]; @@ -691,11 +782,11 @@ extension to be able to input japanese characters while staying in another locale. option B<-imlocale>. -=item B +=item B I Enables "insecure" mode. Rxvt-unicode offers some escape sequences that echo arbitrary strings like the icon name or the locale. This could be -abused if somebody gets 8-bit-clean access to your display, wether +abused if somebody gets 8-bit-clean access to your display, whether throuh a mail client displaying mail bodies unfiltered or though write(1). Therefore, these sequences are disabled by default. (Note that other terminals, including xterm, have these sequences @@ -729,14 +820,50 @@ =item BI: I -Associate I with keysym I (B<0xFF00 - 0xFFFF>). It may -contain escape values (\a: bell, \b: backspace, \e, \E: escape, \n: -newline, \r: return, \t: -tab, \000: octal number) or control characters (^?: delete, ^@: null, -^A ...) and may enclosed with double quotes so that it can start or end -with whitespace. The intervening resource name B cannot be -omitted. This resource is only available when compiled with -KEYSYM_RESOURCE. +Compile I: Associate I with keysym I. The +intervening resource name B cannot be omitted. + +The format of I is "I<(modifiers-)key>", where I can be +any combination of B, B, B, B, +B, B, B, B, B, B, B, B, +and the abbreviated B, B, B, B, B, B, B, B, B<1>, +B<2>, B<3>, B<4>, B<5>. + +The B, B and B modifiers are usually aliased to +whatever modifier the NumLock key, Meta/Alt keys or ISO Level3 Shift/AltGr +keys are being mapped. B is a artificial modifier mapped to the +current application keymap mode state. + +The spellings of I can be obtained by using B(1) command or +searching keysym macros from B and +omitting the prefix B. Alternatively you can specify I by its hex +keysym value (B<0x0000 - 0xFFFF>). Note that the lookup of Is is not +performed in an exact manner; however, the closest match is assured. + +I may contain escape values (C<\a>: bell, C<\b>: backspace, +C<\e>, C<\E>: escape, C<\n>: newline, C<\r>: carriage return, C<\t>: tab, +C<\000>: octal number) or verbatim control characters (C<^?>: delete, +C<^@>: null, C<^A> ...) and may be enclosed with double quotes so that it +can start or end with whitespace. + +You can define a range of keysyms in one shot by providing a I +with pattern B, where the delimeter `/' +should be a character not used by the strings. + +Its usage can be demonstrated by an example: + + URxvt.keysym.M-C-0x61: list|\e + +The above line is equivalent to the following three lines: + + URxvt.keysym.Meta-Control-0x61: \e + URxvt.keysym.Meta-Control-0x62: \e + URxvt.keysym.Meta-Control-0x63: \e + +If I takes the form of C, the specified B is +interpreted and executed as @@RXVT_NAME@@'s control sequence. For example, +C means: change the current locale to +C. =back @@ -779,6 +906,10 @@ double-click to select a word; Left triple-click to select the entire line. +Starting a selection while pressing the B key (or B keys) +(Compile: I) will create a rectangular selection instead of a normal +one. + =item B: Pressing and releasing the Middle mouse button (or B) in @@ -836,7 +967,7 @@ invoke it's usual function but instead will insert the corresponding keycap symbol. The symbol will only be entered when the key has been released, otherwise pressing e.g. C would enter the symbol for -C, although your intention might have beenm to enter a +C, although your intention might have been to enter a reverse tab (Shift-Tab). =item 5.3: Screen-selection entry method @@ -854,6 +985,11 @@ hex code(s) (it might be a combining character) of the character under the pointer is displayed until you release C and C. +In addition to the hex codes it will display the font used to draw this +character - due to implementation reasons, characters combined with +combining characters, line drawing characters and unknown characters will +always be drawn using the built-in support font. + =back With respect to conformance, rxvt-unicode is supposed to be compliant to @@ -915,367 +1051,6 @@ =back -=head1 FREQUENTLY ASKED QUESTIONS (FAQ) - -=over 4 - -=item How do I know which rxvt-unicode version I'm using? - -The version number is displayed with the usage (-h). For rxvt-unicode -version 2.14 and later, the escape sequence C sets the window -title to the version number. - -=item Rxvt-unicode does not seem to understand the selected encoding? - -=item Unicode does not seem to work? - -If you encounter strange problems like typing an accented character but -getting two unrelated other characters or similar, or if program output is -subtly garbled, then you should check your locale settings. - -Rxvt-unicode must be started with the same C setting as the -programs. Often rxvt-unicode is started in the C locale, while the -login script running within the rxvt-unicode window changes the locale to -sth. else, e.h. C. Needless to say, this is not going to work. - -The best thing is to fix your startup environment, as you will likely run -into other problems. If nothing works you can try this in your .profile. - - printf '\e]701;%s\007' "$LC_CTYPE" - -If this doesn't work, then maybe you use a C specification not -supported on your systems. Some systems have a C comamnd which -displays this. If it displays sth. like: - - locale: Cannot set LC_CTYPE to default locale: ... - -Then the locale you specified is not supported on your system. - -If nothing works and you are sure that everything is set correctly then -you will need to remember a little known fact: Some programs just don't -support locales :( - -=item Why do the characters look ugly? - -=item How does rxvt-unicode choose fonts? - -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. - -B makes a best-effort try at finding a replacement -font. Often the result is fine, but sometimes the chosen font looks -bad. In that case, select a font of your taste and add it to the font -list, e.g.: - - @@RXVT_NAME@@ -fn basefont,font2,font3... - -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. - -The only limitation is that all the fonts must not be larger than the base -font, as the base font defines the principial cell size, which must be the -same due to the way terminals work. - -=item Why do some chinese characters look so different than others? - -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 character, it might choose a japanese font for -it. Subseqzuent japanese characters will take that font. Now, many chinese -characters aren't represented in japanese fonts, so when the first -non-japanese character comes up, rxvt-unicode will look for a chinese font --- unfortunately at this point, it will still use the japanese font for -japanese characters that are also chinese. - -The workaround is easy: just tag a chinese font at the end of your font -list (see the previous question). The key is to view the font list as -a preference list: If you expect more japanese, list a japanese font -first. If you expect more chinese, put a chinese font first. - -In the future it might be possible to switch 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). - -=item How does rxvt-unicode determine the encoding to use? - -=item Is there an option to switch encodings? - -Unlike some other terminals, rxvt-unicode has no encoding switch, and no -specific "utf-8" mode, such as xterm. In fact, it doesn't even know about -UTF-8 or any other encodings with respect to terminal I/O. - -The reasons is that there exists a perfectly fine mechanism for selecting -the encoding, doing I/O and (most important) communicating this to all -applications so everybody agrees on character properties such as width and -code number. This mechanism is the I. - -Rxvt-unicode uses the C locale category to select encoding. All -programs doing the same (that is, most) will automatically agree in the -interpretation of characters. - -Unfortunately, there is no system-independent way to select locales, nor -is there a standard on how locale specifiers will look like. - -On most systems, the content of the C environment variable -contains an arbitrary string which corresponds to an already-installed -locale. Common names for locales are C, C, -C, i.e. C, but other forms -(i.e. C or C) are also common. - -Rxvt-unicode ignores all other locale categories, and except for -the encoding, ignores country or language-specific settings, -i.e. C and C are the same for rxvt-unicode. - -If you want to use a specific encoding you have to make sure you start -rxvt-unicode with the correct C category. - -=item Can I switch locales at runtime? - -Yes, using an escape sequence. Try sth. like this, which sets -rxvt-unicode's idea of C. - - printf '\e]701;%s\007' ja_JP.SJIS - -See also the previous question. - -Sometimes this capability is rather handy when you want to work in one -locale (e.g. C) but some programs don't support UTF-8. For -example, I use this script to start C, which first switches to a -locale supported by xjdic and back later: - - printf '\e]701;%s\007' ja_JP.SJIS - xjdic -js - printf '\e]701;%s\007' de_DE.UTF-8 - -=item Can I switch the fonts at runtime? - -Yes, using an escape sequence. Try sth. like this, which has the same -effect as using the C<-fn> switch, and takes effect immediately: - - printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" - -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. - -You can think of this as a kind of manual ISO-2022 switching. - -=item Mouse cut/paste suddenly no longer works. - -Make sure that mouse reporting is actually turned off since killing -some editors prematurely may leave the mouse in mouse report mode. I've -heard that tcsh may use mouse reporting unless it otherwise specified. A -quick check is to see if cut/paste works when the Alt or Shift keys are -depressed. See @@RXVT_NAME@@(7) - -=item What's with this bold/blink stuff? - -If no bold colour is set via C, bold will invert text using the -standard foreground colour. - -For the standard background colour, blinking will actually make the -text blink when compiled with C<--enable-blinking>. with standard -colours. Without C<--enable-blinking>, the blink attribute will be -ignored. - -On ANSI colours, bold/blink attributes are used to set high-intensity -foreground/background colors. - -color0-7 are the low-intensity colors. - -color8-15 are the corresponding high-intensity colors. - -=item I don't like the screen colors. How do I change them? - -You can change the screen colors at run-time using F<~/.Xdefaults> -resources (or as long-options). - -Here are values that are supposed to resemble a VGA screen, -including the murky brown that passes for low-intensity yellow: - - Rxvt*color0: #000000 - Rxvt*color1: #A80000 - Rxvt*color2: #00A800 - Rxvt*color3: #A8A800 - Rxvt*color4: #0000A8 - Rxvt*color5: #A800A8 - Rxvt*color6: #00A8A8 - Rxvt*color7: #A8A8A8 - - Rxvt*color8: #000054 - Rxvt*color9: #FF0054 - Rxvt*color10: #00FF54 - Rxvt*color11: #FFFF54 - Rxvt*color12: #0000FF - Rxvt*color13: #FF00FF - Rxvt*color14: #00FFFF - Rxvt*color15: #FFFFFF - -=item What's with the strange Backspace/Delete key behaviour? - -Assuming that the physical Backspace key corresponds to the -BackSpace keysym (not likely for Linux ... see the following -question) there are two standard values that can be used for -Backspace: C<^H> and C<^?>. - -Historically, either value is correct, but rxvt-unicode adopts the debian -policy of using C<^?> when unsure, because it's the one only only correct -choice :). - -Rxvt-unicode tries to inherit the current stty settings and uses the value -of `erase' to guess the value for backspace. If rxvt-unicode wasn't -started from a terminal (say, from a menu or by remote shell), then the -system value of `erase', which corresponds to CERASE in , will -be used (which may not be the same as your stty setting). - -For starting a new rxvt-unicode: - - # use Backspace = ^H - $ stty erase ^H - $ @@RXVT_NAME@@ - - # use Backspace = ^? - $ stty erase ^? - $ @@RXVT_NAME@@ - -Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7). - -For an existing rxvt-unicode: - - # use Backspace = ^H - $ stty erase ^H - $ echo -n "^[[36h" - - # use Backspace = ^? - $ stty erase ^? - $ echo -n "^[[36l" - -This helps satisfy some of the Backspace discrepancies that occur, but -if you use Backspace = C<^H>, make sure that the termcap/terminfo value -properly reflects that. - -The Delete key is a another casualty of the ill-defined Backspace problem. -To avoid confusion between the Backspace and Delete keys, the Delete -key has been assigned an escape sequence to match the vt100 for Execute -(ESC[3~) and is in the supplied termcap/terminfo. - -Some other Backspace problems: - -some editors use termcap/terminfo, -some editors (vim I'm told) expect Backspace = ^H, -GNU Emacs (and Emacs-like editors) use ^H for help. - -Perhaps someday this will all be resolved in a consistent manner. - -=item I don't like the key-bindings. How do I change them? - -There are some compile-time selections available via configure. Unless -you have run "configure" with the C<--disable-resources> option you can -use the `keysym' resource to alter the keystrings associated with keysym -0xFF00 - 0xFFFF (function, cursor keys, etc). - -Here's an example for a tn3270 session started using `@@RXVT_NAME@@ -name tn3270' - - !# ----- special uses ------: - ! tn3270 login, remap function and arrow keys. - tn3270*font: *clean-bold-*-*--15-* - - ! keysym - used by rxvt only - ! Delete - ^D - tn3270*keysym.0xFFFF: \004 - - ! Home - ^A - tn3270*keysym.0xFF50: \001 - ! Left - ^B - tn3270*keysym.0xFF51: \002 - ! Up - ^P - tn3270*keysym.0xFF52: \020 - ! Right - ^F - tn3270*keysym.0xFF53: \006 - ! Down - ^N - tn3270*keysym.0xFF54: \016 - ! End - ^E - tn3270*keysym.0xFF57: \005 - - ! F1 - F12 - tn3270*keysym.0xFFBE: \e1 - tn3270*keysym.0xFFBF: \e2 - tn3270*keysym.0xFFC0: \e3 - tn3270*keysym.0xFFC1: \e4 - tn3270*keysym.0xFFC2: \e5 - tn3270*keysym.0xFFC3: \e6 - tn3270*keysym.0xFFC4: \e7 - tn3270*keysym.0xFFC5: \e8 - tn3270*keysym.0xFFC6: \e9 - tn3270*keysym.0xFFC7: \e0 - tn3270*keysym.0xFFC8: \e- - tn3270*keysym.0xFFC9: \e= - - ! map Prior/Next to F7/F8 - tn3270*keysym.0xFF55: \e7 - tn3270*keysym.0xFF56: \e8 - -=item I'm using keyboard model XXX that has extra Prior/Next/Insert keys. -How do I make use of them? For example, the Sun Keyboard type 4 -has the following mappings that rxvt-unicode doesn't recognize. - - KP_Insert == Insert - F22 == Print - F27 == Home - F29 == Prior - F33 == End - F35 == Next - -Rather than have rxvt-unicode try to accomodate all the various possible keyboard -mappings, it is better to use `xmodmap' to remap the keys as required for -your particular machine. - -=item How do I distinguish if I'm running rxvt-unicode or a regular xterm? -I need this to decide about setting colors etc. - -rxvt and rxvt-unicode always export the variable "COLORTERM", so you can -check and see if that is set. Note that several programs, JED, slrn, -Midnight Commander automatically check this variable to decide whether or -not to use color. - -=item How do I set the correct, full IP address for the DISPLAY variable? - -If you've compiled rxvt-unicode with DISPLAY_IS_IP and ahve enabled -insecure mode then it is possible to use the following shell script -snippets to correctly set the display. If your version of rxvt-unicode -wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then -the COLORTERM variable can be used to distinguish rxvt-unicode from a -regular xterm. - -Courtesy of Chuck Blake with the following shell script -snippets: - - # Bourne/Korn/POSIX family of shells: - [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know - if [ ${TERM:-foo} = xterm ]; then - stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not - echo -n '^[Z' - read term_id - stty icanon echo - if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then - echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string - read DISPLAY # set it in our local shell - fi - fi - -=item How do I compile the manual pages for myself? - -You need to have a recent version of perl installed as F, -one that comes with F, F and F. Then go to -the doc subdirectory and enter C. - -=back - =head1 ENVIRONMENT B<@@RXVT_NAME@@> sets the environment variables B, B