--- rxvt-unicode/doc/rxvt.7.html 2006/01/04 21:37:55 1.33 +++ rxvt-unicode/doc/rxvt.7.html 2006/01/31 00:25:16 1.54 @@ -24,17 +24,6 @@
  • CSI (Command Sequence Introducer) Sequences
  • DEC Private Modes
  • XTerm Operating System Commands
  • -
  • menuBar
  • - -
  • XPM
  • Mouse Reporting
  • Key Codes
  • @@ -67,14 +56,163 @@

    DESCRIPTION

    This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting all escape sequences, and other background information.

    -

    The newest version of this document is -also available on the World Wide Web at +

    The newest version of this document is also available on the World Wide Web at http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html.


    FREQUENTLY ASKED QUESTIONS

    +
    The new selection selects pieces that are too big, how can I select +single words?
    +
    +
    +Yes. For example, if you want to select alphanumeric words, you can use +the following resource: +
    +
    +
    +   URxvt.selection.pattern-0: ([[:word:]]+)
    +
    +
    +

    If you click more than twice, the selection will be extended +more and more.

    +
    +
    +

    To get a selection that is very similar to the old code, try this pattern:

    +
    +
    +
    +   URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+)
    +
    +
    +

    Please also note that the LeftClick Shift-LeftClik combination also +selects words like the old code.

    +
    +

    +
    I don't like the new selection/popups/hotkeys/perl, how do I +change/disable it?
    +
    +
    +You can disable the perl extension completely by setting the +perl-ext-common resource to the empty string, which also keeps +rxvt-unicode from initialising perl, saving memory. +
    +
    +

    If you only want to disable specific features, you first have to +identify which perl extension is responsible. For this, read the section +PREPACKAGED EXTENSIONS in the rxvtperl(3) manpage. For +example, to disable the selection-popup and option-popup, specify +this perl-ext-common resource:

    +
    +
    +
    +   URxvt.perl-ext-common: default,-selection-popup,-option-popup
    +
    +
    +

    This will keep the default extensions, but disable the two popup +extensions. Some extensions can also be configured, for example, +scrollback search mode is triggered by M-s. You can move it to any +other combination either by setting the searchable-scrollback resource:

    +
    +
    +
    +   URxvt.searchable-scrollback: CM-s
    +
    +

    +
    Why doesn't rxvt-unicode read my resources?
    +
    +
    +Well, why, indeed? It does, in a way very similar to other X +applications. Most importantly, this means that if you or your OS loads +resources into the X display (the right way to do it), rxvt-unicode will +ignore any resource files in your home directory. It will only read +$HOME/.Xdefaults when no resources are attached to the display. +
    +
    +

    If you have or use an $HOME/.Xresources file, chances are that +resources are loaded into your X-server. In this case, you have to +re-login after every change (or run xrdb -merge $HOME/.Xresources).

    +
    +
    +

    Also consider the form resources have to use:

    +
    +
    +
    +  URxvt.resource: value
    +
    +
    +

    If you want to use another form (there are lots of different ways of +specifying resources), make sure you understand wether and why it +works. If unsure, use the form above.

    +
    +

    +
    I can't get transparency working, what am I doing wrong?
    +
    +
    +First of all, transparency isn't officially supported in rxvt-unicode, so +you are mostly on your own. Do not bug the author about it (but you may +bug everybody else). Also, if you can't get it working consider it a rite +of passage: ... and you failed. +
    +
    +

    Here are four ways to get transparency. Do read the manpage and option +descriptions for the programs mentioned and rxvt-unicode. Really, do it!

    +
    +
    +

    1. Use inheritPixmap:

    +
    +
    +
    +   Esetroot wallpaper.jpg
    +   rxvt -ip -tint red -sh 40
    +
    +
    +

    That works. If you think it doesn't, you lack transparency and tinting +support, or you are unable to read.

    +
    +
    +

    2. Use a simple pixmap and emulate pseudo-transparency. This enables you +to use effects other than tinting and shading: Just shade/tint/whatever +your picture with gimp:

    +
    +
    +
    +   convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
    +   rxvt -pixmap background.xpm -pe automove-background
    +
    +
    +

    That works. If you think it doesn't, you lack XPM and Perl support, or you +are unable to read.

    +
    +
    +

    3. Use an ARGB visual:

    +
    +
    +
    +   rxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
    +
    +
    +

    This requires XFT support, and the support of your X-server. If that +doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't +there yet, no matter what they claim. Rxvt-Unicode contains the neccessary +bugfixes and workarounds for Xft and Xlib to make it work, but that +doesn't mean that your WM has the required kludges in place.

    +
    +
    +

    4. Use xcompmgr and let it do the job:

    +
    +
    +
    +  xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \
    +        -set _NET_WM_WINDOW_OPACITY 0xc0000000
    +
    +
    +

    Then click on a window you want to make transparent. Replace 0xc0000000 +by other values to change the degree of opacity. If it doesn't work and +your server crashes, you got to keep the pieces.

    +
    +

    Isn't rxvt supposed to be small? Don't all those features bloat?
    @@ -122,7 +260,7 @@

    Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this still fares rather well. And compared to some monsters like gnome-terminal (21152k + extra 4204k in separate processes) or konsole (22200k + extra -43180k in daemons that stay around after exit, plus half aminute of +43180k in daemons that stay around after exit, plus half a minute of startup time, including the hundreds of warnings it spits out), it fares extremely well *g*.

    @@ -174,12 +312,24 @@
    Does it support tabs, can I have a tabbed rxvt-unicode?
    -rxvt-unicode does not directly support tabs. It will work fine with -tabbing functionality of many window managers or similar tabbing programs, -and its embedding-features allow it to be embedded into other programs, -as witnessed by doc/rxvt-tabbed or the upcoming Gtk2::URxvt perl -module, which features a tabbed urxvt (murxvt) terminal as an example -embedding application. +Beginning with version 7.3, there is a perl extension that implements a +simple tabbed terminal. It is installed by default, so any of these should +give you tabs: +
    +
    +
    +   rxvt -pe tabbed
    +
    +
    +
    +   URxvt.perl-ext-common: default,tabbed
    +
    +
    +

    It will also work fine with tabbing functionality of many window managers +or similar tabbing programs, and its embedding-features allow it to be +embedded into other programs, as witnessed by doc/rxvt-tabbed or +the upcoming Gtk2::URxvt perl module, which features a tabbed urxvt +(murxvt) terminal as an example embedding application.

    How do I know which rxvt-unicode version I'm using?
    @@ -195,13 +345,13 @@
    The Debian GNU/Linux package of rxvt-unicode in sarge contains large -patches that considerably change the behaviour of rxvt-unicode. Before -reporting a bug to the original rxvt-unicode author please download and -install the genuine version (http://software.schmorp.de#rxvt-unicode) -and try to reproduce the problem. If you cannot, chances are that the -problems are specific to Debian GNU/Linux, in which case it should be -reported via the Debian Bug Tracking System (use reportbug to report -the bug). +patches that considerably change the behaviour of rxvt-unicode (but +unfortunately this notice has been removed). Before reporting a bug to +the original rxvt-unicode author please download and install the genuine +version (http://software.schmorp.de#rxvt-unicode) and try to reproduce +the problem. If you cannot, chances are that the problems are specific to +Debian GNU/Linux, in which case it should be reported via the Debian Bug +Tracking System (use reportbug to report the bug).

    For other problems that also affect the Debian package, you can and @@ -210,6 +360,52 @@ might encounter the same issue.

    +
    I am maintaining rxvt-unicode for distribution/OS XXX, any +recommendation?
    +
    +
    +You should build one binary with the default options. configure +now enables most useful options, and the trend goes to making them +runtime-switchable, too, so there is usually no drawback to enbaling them, +except higher disk and possibly memory usage. The perl interpreter should +be enabled, as important functionality (menus, selection, likely more in +the future) depends on it. +
    +
    +

    You should not overwrite the perl-ext-common snd perl-ext resources +system-wide (except maybe with defaults). This will result in useful +behaviour. If your distribution aims at low memory, add an empty +perl-ext-common resource to the app-defaults file. This will keep the +perl interpreter disabled until the user enables it.

    +
    +
    +

    If you can/want build more binaries, I recommend building a minimal +one with --disable-everything (very useful) and a maximal one with +--enable-everything (less useful, it will be very big due to a lot of +encodings built-in that increase download times and are rarely used).

    +
    +

    +
    I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?
    +
    +
    +It should be, starting with release 7.1. You are encouraged to properly +install urxvt with privileges necessary for your OS now. +
    +
    +

    When rxvt-unicode detects that it runs setuid or setgid, it will fork +into a helper process for privileged operations (pty handling on some +systems, utmp/wtmp/lastlog handling on others) and drop privileges +immediately. This is much safer than most other terminals that keep +privileges while running (but is more relevant to urxvt, as it contains +things as perl interpreters, which might be ``helpful'' to attackers).

    +
    +
    +

    This forking is done as the very first within main(), which is very early +and reduces possible bugs to initialisation code run before main(), or +things like the dynamic loader of your system, which should result in very +little risk.

    +
    +

    When I log-in to another system it tells me about missing terminfo data?
    @@ -734,7 +930,7 @@
    -   URxvt*imlocale: ja_JP.EUC-JP
    + URxvt.imlocale: ja_JP.EUC-JP

    Now you can start your terminal with LC_CTYPE=ja_JP.UTF-8 and still @@ -804,7 +1000,7 @@ 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(7) +depressed.

    What's with this bold/blink stuff?
    @@ -931,7 +1127,7 @@ $ rxvt
    -

    Toggle with ESC [ 36 h / ESC [ 36 l as documented in rxvt(7).

    +

    Toggle with ESC [ 36 h / ESC [ 36 l.

    For an existing rxvt-unicode:

    @@ -1092,8 +1288,8 @@

    DESCRIPTION

    The rest of this document describes various technical aspects of rxvt-unicode. First the description of supported command sequences, -followed by menu and pixmap support and last by a description of all -features selectable at configure time.

    +followed by pixmap support and last by a description of all features +selectable at configure time.


    @@ -1736,11 +1932,6 @@ -
    hSend Mouse X & Y on button press.
    lNo mouse reporting.
    Ps = 10 > (rxvt)
    -
    - - -
    hmenuBar visible
    lmenuBar invisible
    Ps = 25 >
    @@ -1861,18 +2052,20 @@ - - - + + + - + + + @@ -1885,583 +2078,6 @@


    -

    menuBar

    -

    The exact syntax used is almost solidified. > -In the menus, DON'T try to use menuBar commands that add or remove a -menuBar.

    -

    Note that in all of the commands, the /path/ > cannot be -omitted: use ./ to specify a menu relative to the current menu.

    -

    -

    -

    Overview of menuBar operation

    -

    For the menuBar XTerm escape sequence ESC ] 703 ; Pt ST, the syntax -of Pt can be used for a variety of tasks:

    -

    At the top level is the current menuBar which is a member of a circular -linked-list of other such menuBars.

    -

    The menuBar acts as a parent for the various drop-down menus, which in -turn, may have labels, separator lines, menuItems and subMenus.

    -

    The menuItems are the useful bits: you can use them to mimic keyboard -input or even to send text or escape sequences back to rxvt.

    -

    The menuBar syntax is intended to provide a simple yet robust method of -constructing and manipulating menus and navigating through the -menuBars.

    -

    The first step is to use the tag [menu:name] > which creates -the menuBar called name and allows access. You may now or menus, -subMenus, and menuItems. Finally, use the tag [done] to set the -menuBar access as readonly to prevent accidental corruption of the -menus. To re-access the current menuBar for alterations, use the tag -[menu], make the alterations and then use [done]

    -

    -

    -

    -

    Commands

    -
    -
    [menu:+name] >
    -
    -
    -access the named menuBar for creation or alteration. If a new menuBar -is created, it is called name (max of 15 chars) and the current -menuBar is pushed onto the stack -
    -

    -
    [menu]
    -
    -
    -access the current menuBar for alteration -
    -

    -
    [title:+string] >
    -
    -
    -set the current menuBar's title to string, which may contain the -following format specifiers: -
    -
    -
    -   B<%n>  rxvt name (as per the B<-name> command-line option)
    -   B<%v>  rxvt version
    -   B<%%>  literal B<%> character
    -
    -

    -
    [done]
    -
    -
    -set menuBar access as readonly. -End-of-file tag for [read:+file] > operations. -
    -

    -
    [read:+file] >
    -
    -
    -read menu commands directly from file (extension ``.menu'' will be -appended if required.) Start reading at a line with [menu] or < -[menu:+name > and continuing until [done] is encountered. -
    -
    -

    Blank and comment lines (starting with #) are ignored. Actually, -since any invalid menu commands are also ignored, almost anything could -be construed as a comment line, but this may be tightened up in the -future ... so don't count on it!.

    -
    -

    -
    [read:+file;+name] >
    -
    -
    -The same as [read:+file] >, but start reading at a line with -[menu:+name] > and continuing until [done:+name] > or -[done] is encountered. -
    -

    -
    [dump]
    -
    -
    -dump all menuBars to the file /tmp/rxvt-PID in a format suitable for -later rereading. -
    -

    -
    [rm:name]
    -
    -
    -remove the named menuBar -
    -

    -
    [rm] [rm:]
    -
    -
    -remove the current menuBar -
    -

    -
    [rm*] [rm:*]
    -
    -
    -remove all menuBars -
    -

    -
    [swap]
    -
    -
    -swap the top two menuBars -
    -

    -
    [prev]
    -
    -
    -access the previous menuBar -
    -

    -
    [next]
    -
    -
    -access the next menuBar -
    -

    -
    [show]
    -
    -
    -Enable display of the menuBar -
    -

    -
    [hide]
    -
    -
    -Disable display of the menuBar -
    -

    -
    [pixmap:+name] >
    -
    -
    [pixmap:+name;scaling] >
    -
    -
    -(set the background pixmap globally -
    -
    -

    A Future implementation may make this local to the menubar >)

    -
    -

    -
    [:+command:] >
    -
    -
    -ignore the menu readonly status and issue a command to or a menu or -menuitem or change the ; a useful shortcut for setting the quick arrows -from a menuBar. -
    -

    -

    -

    -

    -

    Adding and accessing menus

    -

    The following commands may also be + prefixed.

    -
    -
    /+
    -
    -
    -access menuBar top level -
    -

    -
    ./+
    -
    -
    -access current menu level -
    -

    -
    ../+
    -
    -
    -access parent menu (1 level up) -
    -

    -
    ../../
    -
    -
    -access parent menu (multiple levels up) -
    -

    -
    /path/menu >
    -
    -
    -add/access menu -
    -

    -
    /path/menu/* >
    -
    -
    -add/access menu and clear it if it exists -
    -

    -
    /path/{-} >
    -
    -
    -add separator -
    -

    -
    /path/{item} >
    -
    -
    -add item as a label -
    -

    -
    /path/{item} action >
    -
    -
    -add/alter menuitem with an associated action -
    -

    -
    /path/{item}{right-text} >
    -
    -
    -add/alter menuitem with right-text as the right-justified text -and as the associated action -
    -

    -
    /path/{item}{rtext} action >
    -
    -
    -add/alter menuitem with an associated action and with rtext as -the right-justified text. -
    -

    -
    -
    Special characters in action must be backslash-escaped:
    -
    -
    -\a \b \E \e \n \r \t \octal -
    -

    -
    or in control-character notation:
    -
    -
    -^@, ^A .. ^Z .. ^_, ^? -
    -

    -

    To send a string starting with a NUL (^@) character to the -program, start action with a pair of NUL characters (^@^@), -the first of which will be stripped off and the balance directed to the -program. Otherwise if action begins with NUL followed by -non-+NUL characters, the leading NUL is stripped off and the -balance is sent back to rxvt.

    -

    As a convenience for the many Emacs-type editors, action may start -with M- (eg, M-$ is equivalent to \E$) and a CR will be -appended if missed from M-x commands.

    -

    As a convenience for issuing XTerm ESC ] sequences from a menubar (or -quick arrow), a BEL (^G) will be appended if needed.

    -
    -
    For example,
    -
    -
    -M-xapropos is equivalent to \Exapropos\r -
    -

    -
    and
    -
    -
    -\E]703;mona;100 is equivalent to \E]703;mona;100\a -
    -

    -

    The option {right-rtext} > will be right-justified. In the -absence of a specified action, this text will be used as the action -as well.

    -
    -
    For example,
    -
    -
    -/File/{Open}{^X^F} is equivalent to /File/{Open}{^X^F} ^X^F -
    -

    -

    The left label is necessary, since it's used for matching, but -implicitly hiding the left label (by using same name for both left and -right labels), or explicitly hiding the left label (by preceeding it -with a dot), makes it possible to have right-justified text only.

    -
    -
    For example,
    -
    -
    -/File/{Open}{Open} Open-File-Action -
    -

    -
    or hiding it
    -
    -
    -/File/{.anylabel}{Open} Open-File-Action -
    -

    -

    -

    -

    -

    Removing menus

    -
    -
    -/*+ >
    -
    -
    -remove all menus from the menuBar, the same as [clear] -
    -

    -
    -+/pathmenu+ >
    -
    -
    -remove menu -
    -

    -
    -+/path{item}+ >
    -
    -
    -remove item -
    -

    -
    -+/path{-} >
    -
    -
    -remove separator) -
    -

    -
    -/path/menu/*
    -
    -
    -remove all items, separators and submenus from menu -
    -

    -

    -

    -

    -

    Quick Arrows

    -

    The menus also provide a hook for quick arrows to provide easier -user access. If nothing has been explicitly set, the default is to -emulate the curror keys. The syntax permits each arrow to be altered -individually or all four at once without re-entering their common -beginning/end text. For example, to explicitly associate cursor actions -with the arrows, any of the following forms could be used:

    -
    -
    <r+Right >>
    -
    -
    <l+Left >>
    -
    -
    <u+Up >>
    -
    -
    <d+Down >>
    -
    -
    -Define actions for the respective arrow buttons -
    -

    -
    <b+Begin >>
    -
    -
    <e+End >>
    -
    -
    -Define common beginning/end parts for quick arrows which used in -conjunction with the above <r> <l> <u> <d> constructs -
    -

    -
    -
    For example, define arrows individually,
    -
    -
    -
    - <u>\E[A
    -
    -
    -
    - <d>\E[B
    -
    -
    -
    - <r>\E[C
    -
    -
    -
    - <l>\E[D
    -
    -
    or all at once
    -
    -
    -
    - <u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D
    -
    -
    or more compactly (factoring out common parts)
    -
    -
    -
    - <b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D
    -
    -
    -

    -

    -

    -

    Command Summary

    -

    A short summary of the most common commands:

    -
    -
    [menu:name]
    -
    -
    -use an existing named menuBar or start a new one -
    -

    -
    [menu]
    -
    -
    -use the current menuBar -
    -

    -
    [title:string]
    -
    -
    -set menuBar title -
    -

    -
    [done]
    -
    -
    -set menu access to readonly and, if reading from a file, signal EOF -
    -

    -
    [done:name]
    -
    -
    -if reading from a file using [read:file;name] signal EOF -
    -

    -
    [rm:name]
    -
    -
    -remove named menuBar(s) -
    -

    -
    [rm] [rm:]
    -
    -
    -remove current menuBar -
    -

    -
    [rm*] [rm:*]
    -
    -
    -remove all menuBar(s) -
    -

    -
    [swap]
    -
    -
    -swap top two menuBars -
    -

    -
    [prev]
    -
    -
    -access the previous menuBar -
    -

    -
    [next]
    -
    -
    -access the next menuBar -
    -

    -
    [show]
    -
    -
    -map menuBar -
    -

    -
    [hide]
    -
    -
    -unmap menuBar -
    -

    -
    [pixmap;file]
    -
    -
    [pixmap;file;scaling]
    -
    -
    -set a background pixmap -
    -

    -
    [read:file]
    -
    -
    [read:file;name]
    -
    -
    -read in a menu from a file -
    -

    -
    [dump]
    -
    -
    -dump out all menuBars to /tmp/rxvt-PID -
    -

    -
    /
    -
    -
    -access menuBar top level -
    -

    -
    ./
    -
    -
    ../
    -
    -
    ../../
    -
    -
    -access current or parent menu level -
    -

    -
    /path/menu
    -
    -
    -add/access menu -
    -

    -
    /path/{-}
    -
    -
    -add separator -
    -

    -
    /path/{item}{rtext} action
    -
    -
    -add/alter menu item -
    -

    -
    -/*
    -
    -
    -remove all menus from the menuBar -
    -

    -
    -/path/menu
    -
    -
    -remove menu items, separators and submenus from menu -
    -

    -
    -/path/menu
    -
    -
    -remove menu -
    -

    -
    -/path/{item}
    -
    -
    -remove item -
    -

    -
    -/path/{-}
    -
    -
    -remove separator -
    -

    -
    <b>Begin<r>Right<l>Left<u>Up<d>Down<e>End
    -
    -
    -menu quick arrows -
    -

    -

    -

    -

    XPM

    For the XPM XTerm escape sequence ESC ] 20 ; Pt ST > then value of Pt > can be the name of the background pixmap followed by a @@ -2717,10 +2333,13 @@

    --enable-unicode3 (default: off)
    -Enable direct support for displaying unicode codepoints above +Recommended to stay off unless you really need non-BMP characters. +
    +
    +

    Enable direct support for displaying unicode codepoints above 65535 (the basic multilingual page). This increases storage requirements per character from 2 to 4 bytes. X11 fonts do not yet -support these extra characters, but Xft does. +support these extra characters, but Xft does.

    Please note that rxvt-unicode can store unicode code points >65535 @@ -2740,10 +2359,9 @@ new pseudo-characters when no precomposed form exists.

    -

    Without --enable-unicode3, the number of additional precomposed characters -is rather limited (2048, if this is full, rxvt-unicode will use the -private use area, extending the number of combinations to 8448). With ---enable-unicode3, no practical limit exists.

    +

    Without --enable-unicode3, the number of additional precomposed +characters is somewhat limited (the 6400 private use characters will be +(ab-)used). With --enable-unicode3, no practical limit exists.

    This option will also enable storage (but not display) of characters @@ -2758,7 +2376,8 @@

    --enable-fallback(=CLASS) (default: Rxvt)
    -When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback. +When reading resource settings, also read settings for class CLASS. To +disable resource fallback use --disable-fallback.

    --with-res-name=NAME (default: urxvt)
    @@ -2799,13 +2418,13 @@ --enable-utmp to also be specified.

    -
    --enable-xpm-background (default: off)
    +
    --enable-xpm-background (default: on)
    Add support for XPM background pixmaps.

    -
    --enable-transparency (default: off)
    +
    --enable-transparency (default: on)
    Add support for inheriting parent backgrounds thus giving a fake @@ -2824,13 +2443,6 @@ Add support for tinting of transparent backgrounds (requires --enable-transparency).

    -
    --enable-menubar (default: off)
    -
    -
    -Add support for our menu bar system (this interacts badly with -dynamic locale switching currently). -
    -

    --enable-rxvt-scroll (default: on)
    @@ -2857,13 +2469,6 @@ many years.

    -
    --enable-half-shadow (default: off)
    -
    -
    -Make shadows on the scrollbar only half the normal width & height. -only applicable to rxvt scrollbars. -
    -

    --enable-ttygid (default: off)
    @@ -2890,29 +2495,6 @@ Removes any support for resource checking.

    -
    --enable-xgetdefault
    -
    -
    -Make resources checking via XGetDefault() instead of our small -version which only checks ~/.Xdefaults, or if that doesn't exist then -~/.Xresources. -
    -
    -

    Please note that nowadays, things like XIM will automatically pull in and -use the full X resource manager, so the overhead of using it might be very -small, if nonexistant.

    -
    -

    -
    --enable-strings (default: off)
    -
    -
    -Add support for our possibly faster memset() function and other -various routines, overriding your system's versions which may -have been hand-crafted in assembly or may require extra libraries -to link in. (this breaks ANSI-C rules and has problems on many -GNU/Linux systems). -
    -

    --disable-swapscreen
    @@ -2936,10 +2518,9 @@ EWMH-hints (pid, utf8 names) and protocols (ping) seperate underline colour (-underlineColor) settable border widths and borderless switch (-w, -b, -bl) + visual depth selection (-depth) settable extra linespacing /-lsp) iso-14755-2 and -3, and visual feedback - backindex and forwardindex escape sequence - window op and some xterm/OSC escape sequences tripleclickwords (-tcw) settable insecure mode (-insecure) keysym remapping support @@ -2947,8 +2528,24 @@ XEmbed support (-embed) user-pty (-pty-fd) hold on exit (-hold) - skip builtin block graphics (-sbg) - sgr modes 90..97 and 100..107 + skip builtin block graphics (-sbg) +
    +
    +

    It also enabled some non-essential features otherwise disabled, such as:

    +
    +
    +
    +  some round-trip time optimisations
    +  nearest color allocation on pseudocolor screens
    +  UTF8_STRING supporr for selection
    +  sgr modes 90..97 and 100..107
    +  backindex and forwardindex escape sequences
    +  view change/zero scorllback esacpe sequences
    +  locale switching escape sequence
    +  window op and some xterm/OSC escape sequences
    +  rectangular selections
    +  trailing space removal for selections
    +  verbose X error handling

    --enable-iso14755 (default: on)
    @@ -3021,12 +2618,14 @@ Add support to have the pointer disappear when typing or inactive.

    -
    --enable-perl (default: off)
    +
    --enable-perl (default: on)
    Enable an embedded perl interpreter. See the rxvtperl(3) manpage (doc/rxvtperl.txt) for more info on this feature, or the files -in src/perl-ext/ for the extensions that are installed by default. +in src/perl-ext/ for the extensions that are installed by default. The +perl interpreter that is used can be specified via the PERL environment +variable when running configure.

    --with-name=NAME (default: urxvt)
    Ps = 12Change colour of text cursor foreground to Pt
    Ps = 13Change colour of mouse foreground to Pt
    Ps = 17Change colour of highlight characters to Pt
    Ps = 18Change colour of bold characters to Pt
    Ps = 19Change colour of underlined characters to Pt
    Ps = 20Change default background to Pt
    Ps = 18Change colour of bold characters to Pt [deprecated, see 706]
    Ps = 19Change colour of underlined characters to Pt [deprecated, see 707]
    Ps = 20Change background pixmap parameters (see section XPM) (Compile XPM).
    Ps = 39Change default foreground colour to Pt.
    Ps = 46Change Log File to Pt unimplemented
    Ps = 49Change default background colour to Pt.
    Ps = 50Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n
    Ps = 55Log all scrollback buffer and all of screen to Pt
    Ps = 701Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).
    Ps = 703Menubar command Pt (Compile menubar).
    Ps = 702Request version if Pt is ?, returning rxvt-unicode, the resource name, the major and minor version numbers, e.g. ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST.
    Ps = 704Change colour of italic characters to Pt
    Ps = 705Change background pixmap tint colour to Pt (Compile transparency).
    Ps = 706Change colour of bold characters to Pt
    Ps = 707Change colour of underlined characters to Pt
    Ps = 710Set normal fontset to Pt. Same as Ps = 50.
    Ps = 711Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).
    Ps = 712Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).