… | |
… | |
1346 | It is also possible to specify the colour values of B<foreground>, |
1346 | It is also possible to specify the colour values of B<foreground>, |
1347 | B<background>, B<cursorColor>, B<cursorColor2>, B<colorBD>, B<colorUL> as |
1347 | B<background>, B<cursorColor>, B<cursorColor2>, B<colorBD>, B<colorUL> as |
1348 | a number 0-15, as a convenient shorthand to reference the colour name of |
1348 | a number 0-15, as a convenient shorthand to reference the colour name of |
1349 | color0-color15. |
1349 | color0-color15. |
1350 | |
1350 | |
1351 | If Xft support has been compiled in and as long as Xft/Xrender/X don't get |
|
|
1352 | their act together, rxvt-unicode will support C<rgba:rrrr/gggg/bbbb/aaaa> |
|
|
1353 | (recommended, but B<MUST> have 4 digits/component), C<#ARGB>, C<#AARRGGBB> |
|
|
1354 | and C<#AAAARRRRGGGGBBBB> colour specifications, in addition to the ones |
|
|
1355 | provided by X, where the additional A component specifies alpha (opacity) |
|
|
1356 | values (0 is completely transparent and the maximum is opaque). You |
|
|
1357 | probably need to specify B<"-depth 32">, too, and have the luck that your |
|
|
1358 | X-server uses ARGB pixel layout, as X is far from just supporting ARGB |
|
|
1359 | visuals out of the box, and rxvt-unicode just fudges around. |
|
|
1360 | |
|
|
1361 | I<Please note that transparency of any kind if completely unsupported by |
|
|
1362 | the author. Don't bug him with installation questions!> |
|
|
1363 | |
|
|
1364 | Note that B<-rv> (B<"reverseVideo: True">) simulates reverse video by |
1351 | Note that B<-rv> (B<"reverseVideo: True">) simulates reverse video by |
1365 | always swapping the foreground/background colours. This is in contrast to |
1352 | always swapping the foreground/background colours. This is in contrast to |
1366 | I<xterm>(1) where the colours are only swapped if they have not otherwise |
1353 | I<xterm>(1) where the colours are only swapped if they have not otherwise |
1367 | been specified. For example, |
1354 | been specified. For example, |
1368 | |
1355 | |
… | |
… | |
1372 | |
1359 | |
1373 | would yield White on Black, while on I<xterm>(1) it would yield Black |
1360 | would yield White on Black, while on I<xterm>(1) it would yield Black |
1374 | on White. |
1361 | on White. |
1375 | |
1362 | |
1376 | =back |
1363 | =back |
|
|
1364 | |
|
|
1365 | =head2 ALPHA CHANNEL SUPPORT |
|
|
1366 | |
|
|
1367 | If Xft support has been compiled in and as long as Xft/Xrender/X don't get |
|
|
1368 | their act together, rxvt-unicode will support C<rgba:rrrr/gggg/bbbb/aaaa> |
|
|
1369 | (recommended, but B<MUST> have 4 digits/component) colour specifications, |
|
|
1370 | in addition to the ones provided by X, where the additional A component |
|
|
1371 | specifies opacity (alpha) values. The minimum value of C<0> is completely |
|
|
1372 | transparent). You can also prefix any color with C<[a]>, where C<a> is on |
|
|
1373 | to four hex digits specifiying the opacity value. |
|
|
1374 | |
|
|
1375 | You probably need to specify B<"-depth 32">, too, and have the luck that |
|
|
1376 | your X-server uses ARGB pixel layout, as X is far from just supporting |
|
|
1377 | ARGB visuals out of the box, and rxvt-unicode just fudges around. |
|
|
1378 | |
|
|
1379 | For example, the following selects an almost completely transparent red |
|
|
1380 | background, and an almost opaque pink foreground: |
|
|
1381 | |
|
|
1382 | @@RXVT_NAME@@ -depth 32 -bg rgba:0000/0000/0000/2222 -fg "[e]pink" |
|
|
1383 | |
|
|
1384 | I<Please note that transparency of any kind if completely unsupported by |
|
|
1385 | the author. Don't bug him with installation questions!> |
1377 | |
1386 | |
1378 | =head1 ENVIRONMENT |
1387 | =head1 ENVIRONMENT |
1379 | |
1388 | |
1380 | B<@@RXVT_NAME@@> sets and/or uses the following environment variables: |
1389 | B<@@RXVT_NAME@@> sets and/or uses the following environment variables: |
1381 | |
1390 | |