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

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.102 by ayin, Fri Jan 20 18:04:32 2006 UTC vs.
Revision 1.117 by root, Fri Jul 28 09:14:10 2006 UTC

 world. Being a terminal emulator, however, some things are very difficult,
 especially cursive scripts such as arabic, vertically written scripts
 like mongolian or scripts requiring extremely complex combining rules,
 like tibetan or devenagari. Don't expect pretty output when using these
 scripts. Most other scripts, latin, cyrillic, kanji, thai etc. should work
-fine, though. A somewhat difficult case are left-to-right scripts, such
+fine, though. A somewhat difficult case are right-to-left scripts, such
 as hebrew: B<rxvt-unicode> adopts the view that bidirectional algorithms
 belong into the application, not the terminal emulator (too many things --
 such as cursor-movement while editing -- break otherwise), but that might
 change.
 because the author couldn't get C<mlterm> to use one font for latin1 and
 another for japanese.
 Therefore another design rationale was the use of multiple fonts to
 display characters: The idea of a single unicode font which many other
-programs force onto it's users never made sense to me: You should be able
+programs force onto its users never made sense to me: You should be able
 to choose any font for any script freely.
 Apart from that, rxvt-unicode is also much better internationalised than
-it's predecessor, supports things such as XFT and ISO 14755 that are handy
+its predecessor, supports things such as XFT and ISO 14755 that are handy
-in i18n-environments, is faster, and has a lot less bugs than the original
+in i18n-environments, is faster, and has a lot bugs less than the original
 rxvt. This all in addition to dozens of other small improvements.
 It is still faithfully following the original rxvt idea of being lean
 and nice on resources: for example, you can still configure rxvt-unicode
-without most of it's features to get a lean binary. It also comes with
+without most of its features to get a lean binary. It also comes with
 a client/daemon pair that lets you open any number of terminal windows
 from within a single process, which makes startup time very fast and
 drastically reduces memory usage. See @@RXVT_NAME@@d(1) (daemon) and
 @@RXVT_NAME@@c(1) (client).
 It also makes technical information about escape sequences (which have
-been extended) easier accessible: see @@RXVT_NAME@@(7) for technical
+been extended) more accessible: see @@RXVT_NAME@@(7) for technical
 reference documentation (escape sequences etc.).
 =head1 OPTIONS
 The B<@@RXVT_NAME@@> options (mostly a subset of I<xterm>'s) are listed
 Attempt to open a window on the named X display (B<-d> still
 respected). In the absence of this option, the display specified by the
 B<DISPLAY> environment variable is used.
+=item B<-depth> I<bitdepth>
+Compile I<xft>: Attempt to find a visual with the given bit depth;
+resource B<depth>.
 =item B<-geometry> I<geom>
 Window geometry (B<-g> still respected); resource B<geometry>.
 =item B<-rv>|B<+rv>
 =item B<-ip>|B<+ip> | B<-tr>|B<+tr>
 Turn on/off inheriting parent window's pixmap. Alternative form is
 B<-tr>; resource B<inheritPixmap>.
+I<Please note that transparency of any kind if completely unsupported by
+the author. Don't bug him with installation questions! Read the FAQ (man 7
+@@RXVT_NAME@@)!>
 =item B<-fade> I<number>
 Fade the text by the given percentage when focus is lost. Small values
 fade a little only, 100 completely replaces all colours by the fade
 colour; resource B<fading>.
 =item B<-fadecolor> I<colour>
 Fade to this colour when fading is used (see B<-fade>). The default colour
-is black. resource B<fadeColor>.
+is opaque black. resource B<fadeColor>.
 =item B<-tint> I<colour>
 Tint the transparent background pixmap with the given colour when
 transparency is enabled with B<-tr> or B<-ip>. This only works for
 that are checked in order when trying to find glyphs for 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<font> for more details.
-In short, to specify an X11 core font, just specify it's name or prefix it
+In short, to specify an X11 core font, just specify its name or prefix it
 with C<x:>. To specify an XFT-font, you need to prefix it with C<xft:>,
 e.g.:
    @@RXVT_NAME@@ -fn "xft:Bitstream Vera Sans Mono:pixelsize=15"
    @@RXVT_NAME@@ -fn "9x15bold,xft:Bitstream Vera Sans Mono"
 Remap a key symbol. See resource B<keysym>.
 =item B<-embed> I<windowid>
-Tells @@RXVT_NAME@@ to embed it's windows into an already-existing window,
+Tells @@RXVT_NAME@@ to embed its windows into an already-existing window,
 which enables applications to easily embed a terminal.
 Right now, @@RXVT_NAME@@ will first unmap/map the specified window, so it
 shouldn't be a top-level window. @@RXVT_NAME@@ will also reconfigure it
 quite a bit, so don't expect it to keep some specific state. It's best to
 check the @@RXVT_NAME@@perl(3) manpage for additional settings by perl
 extensions not documented here):
 =over 4
+=item B<depth:> I<bitdepth>
+Compile I<xft>: Attempt to find a visual with the given bit depth;
+option B<-depth>.
 =item B<geometry:> I<geom>
 Create the window with the specified X window geometry [default 80x24];
 option B<-geometry>.
 =item B<inheritPixmap:> I<boolean>
 B<True>: make the background inherit the parent windows' pixmap, giving
 artificial transparency. B<False>: do not inherit the parent windows'
 pixmap.
+I<Please note that transparency of any kind if completely unsupported by
+the author. Don't bug him with installation questions!>
 =item B<fading:> I<number>
 Fade the text by the given percentage when focus is lost; option B<-fade>.
 pressed. If unset it will send the sequence traditionally associated
 with the B<Execute> key.
 =item B<cutchars:> I<string>
-The characters used as delimiters for double-click word selection. The
+The characters used as delimiters for double-click word selection
-built-in default:
+(whitespace delimiting is added automatically if resource is given).
+When the selection extension is in use (the default if compiled in, see
+the @@RXVT_NAME@@perl(3) manpage), a suitable regex using these characters
+will be created (if the resource exists, otherwise, no regex will be
+created). In this mode, characters outside ISO-8859-1 can be used.
+When the selection extension is not used, only ISO-8859-1 characters can
+be used. If not specified, the built-in default is used:
 B<< BACKSLASH `"'&()*,;<=>?@[]{|} >>
 =item B<preeditType:> I<style>
 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.
 Please note that you need to double the C<\> in resource files, as
-Xlib itself does it's own de-escaping (you can use C<\033> instead of
+Xlib itself does its own de-escaping (you can use C<\033> instead of
 C<\e> (and so on), which will work with both Xt and @@RXVT_NAME@@'s own
 processing).
 You can define a range of keysyms in one shot by providing a I<string>
 with pattern B<list/PREFIX/MIDDLE/SUFFIX>, where the delimeter `/'
 selection, and trailing whitespace is visually underlined and removed from
 the selection.
 =item B<Insertion>:
-Pressing and releasing the Middle mouse button in an B<@@RXVT_NAME@@> window
+Pressing and releasing the Middle mouse button in an B<@@RXVT_NAME@@>
-causes the value of the PRIMARY selection (Shift for CLIPBOARD) to be inserted
+window causes the value of the PRIMARY selection (or CLIPBOARD with the
-as if it had been typed on the keyboard.
+Meta modifier) to be inserted as if it had been typed on the keyboard.
-B<Shift-Insert> causes the value of the PRIMARY selection to be inserted too.
+Pressing B<Shift-Insert> causes the value of the PRIMARY selection to be
+inserted too.
 =back
 =head1 CHANGING FONTS
 This mode lets you input characters representing the keycap symbols of
 your keyboard, if representable in the current locale encoding.
 Start by pressing C<Control> and C<Shift> together, then releasing
 them. The next special key (cursor keys, home etc.) you enter will not
-invoke it's usual function but instead will insert the corresponding
+invoke its 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<Shift> would enter the symbol for
 C<ISO Level 2 Switch>, although your intention might have been to enter a
 reverse tab (Shift-Tab).
 =head1 COLORS AND GRAPHICS
 In addition to the default foreground and background colours,
 B<@@RXVT_NAME@@> can display up to 16 colours (8 ANSI colours plus
 high-intensity bold/blink versions of the same). Here is a list of the
-colours with their B<rgb.txt> names.
+colours with their names.
 =begin table
 	B<color0>	(black)	= Black
 	B<color1>	(red)	= Red3
 It is also possible to specify the colour values of B<foreground>,
 B<background>, B<cursorColor>, B<cursorColor2>, B<colorBD>, B<colorUL> as
 a number 0-15, as a convenient shorthand to reference the colour name of
 color0-color15.
+In addition to the colours defined above, @@RXVT_NAME@@ offers an
+additional 72 colours. The first 64 of those (with indices 16 to 79)
+consist of a 4*4*4 RGB colour cube (i.e. I<index = r * 16 + g * 4 + b +
+16>), followed by 8 additional shades of gray (with indices 80 to 87).
+Together, all those colours implement the 88 colour xterm colours. Only
+the first 16 can be changed using resources currently, the rest can only
+be changed via command sequences ("escape codes").
 Note that B<-rv> (B<"reverseVideo: True">) simulates reverse video by
 always swapping the foreground/background colours. This is in contrast to
 I<xterm>(1) where the colours are only swapped if they have not otherwise
 been specified. For example,
 would yield White on Black, while on I<xterm>(1) it would yield Black
 on White.
 =back
+=head2 ALPHA CHANNEL SUPPORT
+If Xft support has been compiled in and as long as Xft/Xrender/X don't get
+their act together, rxvt-unicode will support C<rgba:rrrr/gggg/bbbb/aaaa>
+(recommended, but B<MUST> have 4 digits/component) colour specifications,
+in addition to the ones provided by X, where the additional A component
+specifies opacity (alpha) values. The minimum value of C<0> is completely
+transparent). You can also prefix any color with C<[a]>, where C<a> is on
+to four hex digits specifiying the opacity value.
+You probably need to specify B<"-depth 32">, too, and have the luck that
+your X-server uses ARGB pixel layout, as X is far from just supporting
+ARGB visuals out of the box, and rxvt-unicode just fudges around.
+For example, the following selects an almost completely transparent red
+background, and an almost opaque pink foreground:
+   @@RXVT_NAME@@ -depth 32 -bg rgba:0000/0000/0000/2222 -fg "[e]pink"
+I<Please note that transparency of any kind if completely unsupported by
+the author. Don't bug him with installation questions!>
 =head1 ENVIRONMENT
 B<@@RXVT_NAME@@> sets and/or uses the following environment variables:
 C<--with-terminfo=PATH>.
 =item B<DISPLAY>
 Used by @@RXVT_NAME@@ to connect to the display and set to the correct
-display in it's child processes.
+display in its child processes.
 =item B<SHELL>
 The shell to be used for command execution, defaults to C</bin/sh>.
 =item Project Coordinator
 Marc A. Lehmann L<< <rxvt-unicode@schmorp.de> >>
-L<http://software.schmorp.de/#rxvt-unicode>
+L<http://software.schmorp.de/pkg/rxvt-unicode.html>
 =back
 =head1 AUTHORS

Diff Legend

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

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents): Revision 1.102 by ayin, Fri Jan 20 18:04:32 2006 UTC vs. Revision 1.117 by root, Fri Jul 28 09:14:10 2006 UTC

Diff Legend

Comparing rxvt-unicode/doc/rxvt.1.pod (file contents):
Revision 1.102 by ayin, Fri Jan 20 18:04:32 2006 UTC vs.
Revision 1.117 by root, Fri Jul 28 09:14:10 2006 UTC