--- rxvt-unicode/doc/rxvt.7.man.in 2005/02/18 12:15:07 1.17 +++ rxvt-unicode/doc/rxvt.7.man.in 2006/01/19 19:26:31 1.50 @@ -129,7 +129,7 @@ .\" ======================================================================== .\" .IX Title "rxvt 7" -.TH rxvt 7 "2005-02-18" "5.2" "RXVT-UNICODE" +.TH rxvt 7 "2006-01-19" "7.1" "RXVT-UNICODE" .SH "NAME" RXVT REFERENCE \- FAQ, command sequences and other background information .SH "SYNOPSIS" @@ -158,24 +158,196 @@ . .SH "FREQUENTLY ASKED QUESTIONS" .IX Header "FREQUENTLY ASKED QUESTIONS" +.IP "The new selection selects pieces that are too big, how can I select single words?" 4 +.IX Item "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: +.Sp +.Vb 1 +\& URxvt.selection.pattern-0: ([[:word:]]+) +.Ve +.Sp +If you click more than twice, the selection will be extended +more and more. +.Sp +To get a selection that is very similar to the old code, try this pattern: +.Sp +.Vb 1 +\& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+) +.Ve +.Sp +Please also note that the \fILeftClick Shift-LeftClik\fR combination also +selects words like the old code. +.IP "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" 4 +.IX Item "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 +\&\fBperl-ext-common\fR resource to the empty string, which also keeps +rxvt-unicode from initialising perl, saving memory. +.Sp +If you only want to disable specific features, you first have to +identify which perl extension is responsible. For this, read the section +\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For +example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify +this \fBperl-ext-common\fR resource: +.Sp +.Vb 1 +\& URxvt.perl-ext-common: default,-selection-popup,-option-popup +.Ve +.Sp +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 \fBM\-s\fR. You can move it to any +other combination either by setting the \fBsearchable-scrollback\fR resource: +.Sp +.Vb 1 +\& URxvt.searchable-scrollback: CM-s +.Ve +.IP "Isn't rxvt supposed to be small? Don't all those features bloat?" 4 +.IX Item "Isn't rxvt supposed to be small? Don't all those features bloat?" +I often get asked about this, and I think, no, they didn't cause extra +bloat. If you compare a minimal rxvt and a minimal urxvt, you can see +that the urxvt binary is larger (due to some encoding tables always being +compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even +with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many +features unique to urxvt (locale, encoding conversion, iso14755 etc.) are +already in use in this mode. +.Sp +.Vb 3 +\& text data bss drs rss filename +\& 98398 1664 24 15695 1824 rxvt --disable-everything +\& 188985 9048 66616 18222 1788 urxvt --disable-everything +.Ve +.Sp +When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft +and full locale/XIM support which are quite bloaty inside libX11 and my +libc), the two diverge, but not unreasnobaly so. +.Sp +.Vb 3 +\& text data bss drs rss filename +\& 163431 2152 24 20123 2060 rxvt --enable-everything +\& 1035683 49680 66648 29096 3680 urxvt --enable-everything +.Ve +.Sp +The very large size of the text section is explained by the east-asian +encoding tables, which, if unused, take up disk space but nothing else +and can be compiled out unless you rely on X11 core fonts that use those +encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++ +compiler allocates (but of course doesn't use unless you are out of +memory). Also, using an xft font instead of a core font immediately adds a +few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when +not used. +.Sp +Of course, due to every character using two or four bytes instead of one, +a large scrollback buffer will ultimately make rxvt-unicode use more +memory. +.Sp +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 a minute of +startup time, including the hundreds of warnings it spits out), it fares +extremely well *g*. +.IP "Why \*(C+, isn't that unportable/bloated/uncool?" 4 +.IX Item "Why , isn't that unportable/bloated/uncool?" +Is this a question? :) It comes up very often. The simple answer is: I had +to write it, and \*(C+ allowed me to write and maintain it in a fraction +of the time and effort (which is a scarce resource for me). Put even +shorter: It simply wouldn't exist without \*(C+. +.Sp +My personal stance on this is that \*(C+ is less portable than C, but in +the case of rxvt-unicode this hardly matters, as its portability limits +are defined by things like X11, pseudo terminals, locale support and unix +domain sockets, which are all less portable than \*(C+ itself. +.Sp +Regarding the bloat, see the above question: It's easy to write programs +in C that use gobs of memory, an certainly possible to write programs in +\&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is +not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my +system with a minimal config: +.Sp +.Vb 4 +\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) +\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) +\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) +\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) +.Ve +.Sp +And here is rxvt\-unicode: +.Sp +.Vb 5 +\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) +\& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) +\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) +\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) +\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) +.Ve +.Sp +No large bloated libraries (of course, none were linked in statically), +except maybe libX11 :) +.IP "Does it support tabs, can I have a tabbed rxvt\-unicode?" 4 +.IX Item "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 \fIdoc/rxvt\-tabbed\fR or the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl +module, which features a tabbed urxvt (murxvt) terminal as an example +embedding application. .IP "How do I know which rxvt-unicode version I'm using?" 4 .IX Item "How do I know which rxvt-unicode version I'm using?" The version number is displayed with the usage (\-h). Also the escape -sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. +sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When +using the @@RXVT_NAME@@c client, the version displayed is that of the +daemon. .IP "I am using Debian GNU/Linux and have a problem..." 4 .IX Item "I am using Debian GNU/Linux and have a problem..." -The Debian GNU/Linux package of rxvt-unicode 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 () 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 \f(CW\*(C`reportbug\*(C'\fR to report the bug). +The Debian GNU/Linux package of rxvt-unicode in sarge contains large +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 () 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 \f(CW\*(C`reportbug\*(C'\fR to report the bug). .Sp For other problems that also affect the Debian package, you can and probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a bug in the Debian version and it serves as a reminder for other users that might encounter the same issue. +.IP "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?" 4 +.IX Item "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?" +You should build one binary with the default options. \fIconfigure\fR +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. +.Sp +You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources +system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful +behaviour. If your distribution aims at low memory, add an empty +\&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the +perl interpreter disabled until the user enables it. +.Sp +If you can/want build more binaries, I recommend building a minimal +one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with +\&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of +encodings built-in that increase download times and are rarely used). +.IP "I need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?" 4 +.IX Item "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 \s-1OS\s0 now. +.Sp +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 \*(L"helpful\*(R" to attackers). +.Sp +This forking is done as the very first within \fImain()\fR, which is very early +and reduces possible bugs to initialisation code run before \fImain()\fR, or +things like the dynamic loader of your system, which should result in very +little risk. .IP "When I log-in to another system it tells me about missing terminfo data?" 4 .IX Item "When I log-in to another system it tells me about missing terminfo data?" The terminal description used by rxvt-unicode is not as widely available @@ -207,6 +379,11 @@ .Sp If you don't plan to use \fBrxvt\fR (quite common...) you could also replace the rxvt terminfo file with the rxvt-unicode one. +.ie n .IP """tic"" outputs some error when compiling the terminfo entry." 4 +.el .IP "\f(CWtic\fR outputs some error when compiling the terminfo entry." 4 +.IX Item "tic outputs some error when compiling the terminfo entry." +Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by +\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. .ie n .IP """bash""'s readline does not work correctly under @@RXVT_NAME@@." 4 .el .IP "\f(CWbash\fR's readline does not work correctly under @@RXVT_NAME@@." 4 .IX Item "bash's readline does not work correctly under @@RXVT_NAME@@." @@ -408,6 +585,15 @@ .Sp All of this is not a problem when using X11 core fonts, as their bounding box data is correct. +.IP "On Solaris 9, many line-drawing characters are too wide." 4 +.IX Item "On Solaris 9, many line-drawing characters are too wide." +Seems to be a known bug, read +. Some people use the +following ugly workaround to get non-double-wide-characters working: +.Sp +.Vb 1 +\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) +.Ve .IP "My Compose (Multi_key) key is no longer working." 4 .IX Item "My Compose (Multi_key) key is no longer working." The most common causes for this are that either your locale is not set @@ -459,13 +645,16 @@ does it support it. Instead, it uses it's own internal representation of \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. .Sp -However, \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support -multi-language apps in an \s-1OS\s0, as using a locale-dependent (and -non\-standardized) representation of \fBwchar_t\fR makes it impossible to -convert between \fBwchar_t\fR (as used by X11 and your applications) and any -other encoding without implementing OS-specific-wrappers for each and -every locale. There simply are no APIs to convert \fBwchar_t\fR into anything -except the current locale encoding. +However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and +\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. +.Sp +\&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language +apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized) +representation of \fBwchar_t\fR makes it impossible to convert between +\&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding +without implementing OS-specific-wrappers for each and every locale. There +simply are no APIs to convert \fBwchar_t\fR into anything except the current +locale encoding. .Sp Some applications (such as the formidable \fBmlterm\fR) work around this by carrying their own replacement functions for character set handling @@ -476,6 +665,22 @@ The rxvt-unicode author insists that the right way to fix this is in the system libraries once and for all, instead of forcing every app to carry complete replacements for them :) +.IP "I use Solaris 9 and it doesn't compile/work/etc." 4 +.IX Item "I use Solaris 9 and it doesn't compile/work/etc." +Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst +problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem. +.IP "How can I use rxvt-unicode under cygwin?" 4 +.IX Item "How can I use rxvt-unicode under cygwin?" +rxvt-unicode should compile and run out of the box on cygwin, using +the X11 libraries that come with cygwin. libW11 emulation is no +longer supported (and makes no sense, either, as it only supported a +single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or +\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the +old libW11 emulation. +.Sp +At the time of this writing, cygwin didn't seem to support any multi-byte +encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited +to 8\-bit encodings. .IP "How does rxvt-unicode determine the encoding to use?" 4 .IX Item "How does rxvt-unicode determine the encoding to use?" .PD 0 @@ -570,7 +775,7 @@ terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR: .Sp .Vb 1 -\& URxvt*imlocale: ja_JP.EUC-JP +\& URxvt.imlocale: ja_JP.EUC-JP .Ve .Sp Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still @@ -605,7 +810,7 @@ .IX Item "Can I speed up Xft rendering somehow?" 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 \f(CW\*(C`:antialiasing=false\*(C'\fR), which saves lots of +antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of memory and also speeds up rendering considerably. .IP "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 4 .IX Item "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" @@ -622,7 +827,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_NAME@@(7) +depressed. .IP "What's with this bold/blink stuff?" 4 .IX Item "What's with this bold/blink stuff?" If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the @@ -694,16 +899,8 @@ .Ve .IP "How can I start @@RXVT_NAME@@d in a race-free way?" 4 .IX Item "How can I start @@RXVT_NAME@@d in a race-free way?" -Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a -server that answers @@RXVT_NAME@@c's requests, so it doesn't background -itself. -.Sp -To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the -following method to wait for the startup message before continuing: -.Sp -.Vb 1 -\& { @@RXVT_NAME@@d & } | read -.Ve +Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the +display, create the listening socket and then fork. .IP "What's with the strange Backspace/Delete key behaviour?" 4 .IX Item "What's with the strange Backspace/Delete key behaviour?" Assuming that the physical Backspace key corresponds to the @@ -735,7 +932,7 @@ \& $ @@RXVT_NAME@@ .Ve .Sp -Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR as documented in @@RXVT_NAME@@(7). +Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. .Sp For an existing rxvt\-unicode: .Sp @@ -861,8 +1058,8 @@ .IX Header "DESCRIPTION" The rest of this document describes various technical aspects of \&\fBrxvt-unicode\fR. First the description of supported command sequences, -followed by menu and pixmap support and last by a description of all -features selectable at \f(CW\*(C`configure\*(C'\fR time. +followed by pixmap support and last by a description of all features +selectable at \f(CW\*(C`configure\*(C'\fR time. .SH "Definitions" .IX Header "Definitions" .ie n .IP "\fB\fB""c""\fB\fR" 4 @@ -1419,15 +1616,6 @@ l No mouse reporting. .TE -.ie n .IP "\fB\fB""Ps = 10""\fB\fR (\fBrxvt\fR)" 4 -.el .IP "\fB\f(CBPs = 10\fB\fR (\fBrxvt\fR)" 4 -.IX Item "Ps = 10 (rxvt)" -.TS -l l . -h menuBar visible -l menuBar invisible -.TE - .ie n .IP "\fB\fB""Ps = 25""\fB\fR" 4 .el .IP "\fB\f(CBPs = 25\fB\fR" 4 .IX Item "Ps = 25" @@ -1558,6 +1746,15 @@ l Don't scroll to bottom when a key is pressed .TE +.ie n .IP "\fB\fB""Ps = 1021""\fB\fR (\fBrxvt\fR)" 4 +.el .IP "\fB\f(CBPs = 1021\fB\fR (\fBrxvt\fR)" 4 +.IX Item "Ps = 1021 (rxvt)" +.TS +l l . +h Bold/italic implies high intensity (see option -is) +l Font styles have no effect on intensity (Compile styles) +.TE + .ie n .IP "\fB\fB""Ps = 1047""\fB\fR" 4 .el .IP "\fB\f(CBPs = 1047\fB\fR" 4 .IX Item "Ps = 1047" @@ -1612,400 +1809,31 @@ Ps = 12 Change colour of text cursor foreground to Pt Ps = 13 Change colour of mouse foreground to Pt Ps = 17 Change colour of highlight characters to Pt -Ps = 18 Change colour of bold characters to Pt -Ps = 19 Change colour of underlined characters to Pt -Ps = 20 Change default background to Pt -Ps = 39 Change default foreground colour to Pt rxvt compile-time option +Ps = 18 Change colour of bold characters to Pt [deprecated, see 706] +Ps = 19 Change colour of underlined characters to Pt [deprecated, see 707] +Ps = 20 Change background pixmap parameters (see section XPM) (Compile XPM). +Ps = 39 Change default foreground colour to Pt. Ps = 46 Change Log File to Pt unimplemented -Ps = 49 Change default background colour to Pt rxvt compile-time option +Ps = 49 Change default background colour to Pt. Ps = 50 Set 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 = 55 Log all scrollback buffer and all of screen to Pt -Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (@@RXVT_NAME@@ extension) -Ps = 703 Menubar command Pt rxvt compile-time option (rxvt-unicode extension) +Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills). Ps = 704 Change colour of italic characters to Pt -Ps = 705 Change background pixmap tint colour to Pt +Ps = 705 Change background pixmap tint colour to Pt (Compile transparency). +Ps = 706 Change colour of bold characters to Pt +Ps = 707 Change colour of underlined characters to Pt Ps = 710 Set normal fontset to Pt. Same as Ps = 50. -Ps = 711 Set bold fontset to Pt. Similar to Ps = 50. -Ps = 712 Set italic fontset to Pt. Similar to Ps = 50. -Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50. +Ps = 711 Set bold fontset to Pt. Similar to Ps = 50 (Compile styles). +Ps = 712 Set italic fontset to Pt. Similar to Ps = 50 (Compile styles). +Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles). +Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). +Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). +Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl). .TE .PP -.IX Xref "menuBar" -.SH "menuBar" -.IX Header "menuBar" -\&\fBThe exact syntax used is \f(BIalmost\fB solidified.\fR -In the menus, \fB\s-1DON\s0'T\fR try to use menuBar commands that add or remove a -menuBar. -.PP -Note that in all of the commands, the \fB\f(BI/path/\fB\fR \fIcannot\fR be -omitted: use \fB./\fR to specify a menu relative to the current menu. -.Sh "Overview of menuBar operation" -.IX Subsection "Overview of menuBar operation" -For the menuBar XTerm escape sequence \f(CW\*(C`ESC ] 703 ; Pt ST\*(C'\fR, the syntax -of \f(CW\*(C`Pt\*(C'\fR can be used for a variety of tasks: -.PP -At the top level is the current menuBar which is a member of a circular -linked-list of other such menuBars. -.PP -The menuBar acts as a parent for the various drop-down menus, which in -turn, may have labels, separator lines, menuItems and subMenus. -.PP -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. -.PP -The menuBar syntax is intended to provide a simple yet robust method of -constructing and manipulating menus and navigating through the -menuBars. -.PP -The first step is to use the tag \fB[menu:\f(BIname\fB]\fR which creates -the menuBar called \fIname\fR and allows access. You may now or menus, -subMenus, and menuItems. Finally, use the tag \fB[done]\fR to set the -menuBar access as \fBreadonly\fR to prevent accidental corruption of the -menus. To re-access the current menuBar for alterations, use the tag -\&\fB[menu]\fR, make the alterations and then use \fB[done]\fR -.PP - -.IX Xref "menuBarCommands" -.Sh "Commands" -.IX Subsection "Commands" -.IP "\fB[menu:+\f(BIname\fB]\fR" 4 -.IX Item "[menu:+name]" -access the named menuBar for creation or alteration. If a new menuBar -is created, it is called \fIname\fR (max of 15 chars) and the current -menuBar is pushed onto the stack -.IP "\fB[menu]\fR" 4 -.IX Item "[menu]" -access the current menuBar for alteration -.IP "\fB[title:+\f(BIstring\fB]\fR" 4 -.IX Item "[title:+string]" -set the current menuBar's title to \fIstring\fR, which may contain the -following format specifiers: -.Sp -.Vb 3 -\& B<%n> rxvt name (as per the B<-name> command-line option) -\& B<%v> rxvt version -\& B<%%> literal B<%> character -.Ve -.IP "\fB[done]\fR" 4 -.IX Item "[done]" -set menuBar access as \fBreadonly\fR. -End-of-file tag for \fB[read:+\f(BIfile\fB]\fR operations. -.IP "\fB[read:+\f(BIfile\fB]\fR" 4 -.IX Item "[read:+file]" -read menu commands directly from \fIfile\fR (extension \*(L".menu\*(R" will be -appended if required.) Start reading at a line with \fB[menu]\fR or \fB[menu:+\f(BIname\fB\fR and continuing until \fB[done]\fR is encountered. -.Sp -Blank and comment lines (starting with \fB#\fR) 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!. -.IP "\fB[read:+\f(BIfile\fB;+\f(BIname\fB]\fR" 4 -.IX Item "[read:+file;+name]" -The same as \fB[read:+\f(BIfile\fB]\fR, but start reading at a line with -\&\fB[menu:+\f(BIname\fB]\fR and continuing until \fB[done:+\f(BIname\fB]\fR or -\&\fB[done]\fR is encountered. -.IP "\fB[dump]\fR" 4 -.IX Item "[dump]" -dump all menuBars to the file \fB/tmp/rxvt\-PID\fR in a format suitable for -later rereading. -.IP "\fB[rm:name]\fR" 4 -.IX Item "[rm:name]" -remove the named menuBar -.IP "\fB[rm] [rm:]\fR" 4 -.IX Item "[rm] [rm:]" -remove the current menuBar -.IP "\fB[rm*] [rm:*]\fR" 4 -.IX Item "[rm*] [rm:*]" -remove all menuBars -.IP "\fB[swap]\fR" 4 -.IX Item "[swap]" -swap the top two menuBars -.IP "\fB[prev]\fR" 4 -.IX Item "[prev]" -access the previous menuBar -.IP "\fB[next]\fR" 4 -.IX Item "[next]" -access the next menuBar -.IP "\fB[show]\fR" 4 -.IX Item "[show]" -Enable display of the menuBar -.IP "\fB[hide]\fR" 4 -.IX Item "[hide]" -Disable display of the menuBar -.IP "\fB[pixmap:+\f(BIname\fB]\fR" 4 -.IX Item "[pixmap:+name]" -.PD 0 -.IP "\fB[pixmap:+\f(BIname\fB;\f(BIscaling\fB]\fR" 4 -.IX Item "[pixmap:+name;scaling]" -.PD -(set the background pixmap globally -.Sp -\&\fBA Future implementation \f(BImay\fB make this local to the menubar\fR) -.IP "\fB[:+\f(BIcommand\fB:]\fR" 4 -.IX Item "[:+command:]" -ignore the menu readonly status and issue a \fIcommand\fR to or a menu or -menuitem or change the ; a useful shortcut for setting the quick arrows -from a menuBar. -.PP - -.IX Xref "menuBarAdd" -.Sh "Adding and accessing menus" -.IX Subsection "Adding and accessing menus" -The following commands may also be \fB+\fR prefixed. -.IP "\fB/+\fR" 4 -.IX Item "/+" -access menuBar top level -.IP "\fB./+\fR" 4 -.IX Item "./+" -access current menu level -.IP "\fB../+\fR" 4 -.IX Item "../+" -access parent menu (1 level up) -.IP "\fB../../\fR" 4 -.IX Item "../../" -access parent menu (multiple levels up) -.IP "\fB\f(BI/path/\fBmenu\fR" 4 -.IX Item "/path/menu" -add/access menu -.IP "\fB\f(BI/path/\fBmenu/*\fR" 4 -.IX Item "/path/menu/*" -add/access menu and clear it if it exists -.IP "\fB\f(BI/path/\fB{\-}\fR" 4 -.IX Item "/path/{-}" -add separator -.IP "\fB\f(BI/path/\fB{item}\fR" 4 -.IX Item "/path/{item}" -add \fBitem\fR as a label -.IP "\fB\f(BI/path/\fB{item} action\fR" 4 -.IX Item "/path/{item} action" -add/alter \fImenuitem\fR with an associated \fIaction\fR -.IP "\fB\f(BI/path/\fB{item}{right\-text}\fR" 4 -.IX Item "/path/{item}{right-text}" -add/alter \fImenuitem\fR with \fBright-text\fR as the right-justified text -and as the associated \fIaction\fR -.IP "\fB\f(BI/path/\fB{item}{rtext} action\fR" 4 -.IX Item "/path/{item}{rtext} action" -add/alter \fImenuitem\fR with an associated \fIaction\fR and with \fBrtext\fR as -the right-justified text. -.IP "Special characters in \fIaction\fR must be backslash\-escaped:" 4 -.IX Item "Special characters in action must be backslash-escaped:" -\&\fB\ea \eb \eE \ee \en \er \et \eoctal\fR -.IP "or in control-character notation:" 4 -.IX Item "or in control-character notation:" -\&\fB^@, ^A .. ^Z .. ^_, ^?\fR -.PP -To send a string starting with a \fB\s-1NUL\s0\fR (\fB^@\fR) character to the -program, start \fIaction\fR with a pair of \fB\s-1NUL\s0\fR characters (\fB^@^@\fR), -the first of which will be stripped off and the balance directed to the -program. Otherwise if \fIaction\fR begins with \fB\s-1NUL\s0\fR followed by -non\-+\fB\s-1NUL\s0\fR characters, the leading \fB\s-1NUL\s0\fR is stripped off and the -balance is sent back to rxvt. -.PP -As a convenience for the many Emacs-type editors, \fIaction\fR may start -with \fBM\-\fR (eg, \fBM\-$\fR is equivalent to \fB\eE$\fR) and a \fB\s-1CR\s0\fR will be -appended if missed from \fBM\-x\fR commands. -.PP -As a convenience for issuing XTerm \fB\s-1ESC\s0 ]\fR sequences from a menubar (or -quick arrow), a \fB\s-1BEL\s0\fR (\fB^G\fR) will be appended if needed. -.IP "For example," 4 -.IX Item "For example," -\&\fBM\-xapropos\fR is equivalent to \fB\eExapropos\er\fR -.IP "and" 4 -.IX Item "and" -\&\fB\eE]703;mona;100\fR is equivalent to \fB\eE]703;mona;100\ea\fR -.PP -The option \fB{\f(BIright-rtext\fB}\fR will be right\-justified. In the -absence of a specified action, this text will be used as the \fIaction\fR -as well. -.IP "For example," 4 -.IX Item "For example," -\&\fB/File/{Open}{^X^F}\fR is equivalent to \fB/File/{Open}{^X^F} ^X^F\fR -.PP -The left label \fIis\fR 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. -.IP "For example," 4 -.IX Item "For example," -\&\fB/File/{Open}{Open} Open-File-Action\fR -.IP "or hiding it" 4 -.IX Item "or hiding it" -\&\fB/File/{.anylabel}{Open} Open-File-Action\fR -.PP - -.IX Xref "menuBarRemove" -.Sh "Removing menus" -.IX Subsection "Removing menus" -.IP "\fB\-/*+\fR" 4 -.IX Item "-/*+" -remove all menus from the menuBar, the same as \fB[clear]\fR -.IP "\fB\-+\f(BI/path\fBmenu+\fR" 4 -.IX Item "-+/pathmenu+" -remove menu -.IP "\fB\-+\f(BI/path\fB{item}+\fR" 4 -.IX Item "-+/path{item}+" -remove item -.IP "\fB\-+\f(BI/path\fB{\-}\fR" 4 -.IX Item "-+/path{-}" -remove separator) -.IP "\fB\-/path/menu/*\fR" 4 -.IX Item "-/path/menu/*" -remove all items, separators and submenus from menu -.PP - -.IX Xref "menuBarArrows" -.Sh "Quick Arrows" -.IX Subsection "Quick Arrows" -The menus also provide a hook for \fIquick arrows\fR 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: -.IP "\fB+\f(BIRight\fB\fR" 4 -.IX Item "+Right" -.PD 0 -.IP "\fB+\f(BILeft\fB\fR" 4 -.IX Item "+Left" -.IP "\fB+\f(BIUp\fB\fR" 4 -.IX Item "+Up" -.IP "\fB+\f(BIDown\fB\fR" 4 -.IX Item "+Down" -.PD -Define actions for the respective arrow buttons -.IP "\fB+\f(BIBegin\fB\fR" 4 -.IX Item "+Begin" -.PD 0 -.IP "\fB+\f(BIEnd\fB\fR" 4 -.IX Item "+End" -.PD -Define common beginning/end parts for \fIquick arrows\fR which used in -conjunction with the above constructs -.IP "For example, define arrows individually," 4 -.IX Item "For example, define arrows individually," -.Vb 1 -\& \eE[A -.Ve -.Sp -.Vb 1 -\& \eE[B -.Ve -.Sp -.Vb 1 -\& \eE[C -.Ve -.Sp -.Vb 1 -\& \eE[D -.Ve -.IP "or all at once" 4 -.IX Item "or all at once" -.Vb 1 -\& \eE[AZ<>\eE[BZ<>\eE[CZ<>\eE[D -.Ve -.IP "or more compactly (factoring out common parts)" 4 -.IX Item "or more compactly (factoring out common parts)" -.Vb 1 -\& \eE[AZ<>BZ<>CZ<>D -.Ve -.PP - -.IX Xref "menuBarSummary" -.Sh "Command Summary" -.IX Subsection "Command Summary" -A short summary of the most \fIcommon\fR commands: -.IP "[menu:name]" 4 -.IX Item "[menu:name]" -use an existing named menuBar or start a new one -.IP "[menu]" 4 -.IX Item "[menu]" -use the current menuBar -.IP "[title:string]" 4 -.IX Item "[title:string]" -set menuBar title -.IP "[done]" 4 -.IX Item "[done]" -set menu access to readonly and, if reading from a file, signal \s-1EOF\s0 -.IP "[done:name]" 4 -.IX Item "[done:name]" -if reading from a file using [read:file;name] signal \s-1EOF\s0 -.IP "[rm:name]" 4 -.IX Item "[rm:name]" -remove named menuBar(s) -.IP "[rm] [rm:]" 4 -.IX Item "[rm] [rm:]" -remove current menuBar -.IP "[rm*] [rm:*]" 4 -.IX Item "[rm*] [rm:*]" -remove all menuBar(s) -.IP "[swap]" 4 -.IX Item "[swap]" -swap top two menuBars -.IP "[prev]" 4 -.IX Item "[prev]" -access the previous menuBar -.IP "[next]" 4 -.IX Item "[next]" -access the next menuBar -.IP "[show]" 4 -.IX Item "[show]" -map menuBar -.IP "[hide]" 4 -.IX Item "[hide]" -unmap menuBar -.IP "[pixmap;file]" 4 -.IX Item "[pixmap;file]" -.PD 0 -.IP "[pixmap;file;scaling]" 4 -.IX Item "[pixmap;file;scaling]" -.PD -set a background pixmap -.IP "[read:file]" 4 -.IX Item "[read:file]" -.PD 0 -.IP "[read:file;name]" 4 -.IX Item "[read:file;name]" -.PD -read in a menu from a file -.IP "[dump]" 4 -.IX Item "[dump]" -dump out all menuBars to /tmp/rxvt\-PID -.IP "/" 4 -access menuBar top level -.IP "./" 4 -.PD 0 -.IP "../" 4 -.IP "../../" 4 -.PD -access current or parent menu level -.IP "/path/menu" 4 -.IX Item "/path/menu" -add/access menu -.IP "/path/{\-}" 4 -.IX Item "/path/{-}" -add separator -.IP "/path/{item}{rtext} action" 4 -.IX Item "/path/{item}{rtext} action" -add/alter menu item -.IP "\-/*" 4 -remove all menus from the menuBar -.IP "\-/path/menu" 4 -.IX Item "-/path/menu" -remove menu items, separators and submenus from menu -.IP "\-/path/menu" 4 -.IX Item "-/path/menu" -remove menu -.IP "\-/path/{item}" 4 -.IX Item "-/path/{item}" -remove item -.IP "\-/path/{\-}" 4 -.IX Item "-/path/{-}" -remove separator -.IP "BeginRightLeftUpDownEnd" 4 -.IX Item "BeginRightLeftUpDownEnd" -menu quick arrows +.IX Xref "XPM" .SH "XPM" .IX Header "XPM" For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value @@ -2165,34 +1993,41 @@ .SH "CONFIGURE OPTIONS" .IX Header "CONFIGURE OPTIONS" General hint: if you get compile errors, then likely your configuration -hasn't been tested well. Either try with \-\-enable\-everything or use the -\&./reconf script as a base for experiments. ./reconf is used by myself, -so it should generally be a working config. Of course, you should always -report when a combination doesn't work, so it can be fixed. Marc Lehmann -. +hasn't been tested well. Either try with \f(CW\*(C`\-\-enable\-everything\*(C'\fR or use +the \fI./reconf\fR script as a base for experiments. \fI./reconf\fR is used by +myself, so it should generally be a working config. Of course, you should +always report when a combination doesn't work, so it can be fixed. Marc +Lehmann . +.PP +All .IP "\-\-enable\-everything" 4 .IX Item "--enable-everything" -Add support for all non-multichoice options listed in \*(L"./configure -\&\-\-help\*(R". Note that unlike other enable options this is order dependant. -You can specify this and then disable options which this enables by -\&\fIfollowing\fR this with the appropriate commands. -.IP "\-\-enable\-xft" 4 -.IX Item "--enable-xft" +Add (or remove) support for all non-multichoice options listed in \*(L"./configure +\&\-\-help\*(R". +.Sp +You can specify this and then disable options you do not like by +\&\fIfollowing\fR this with the appropriate \f(CW\*(C`\-\-disable\-...\*(C'\fR arguments, +or you can start with a minimal configuration by specifying +\&\f(CW\*(C`\-\-disable\-everything\*(C'\fR and than adding just the \f(CW\*(C`\-\-enable\-...\*(C'\fR arguments +you want. +.IP "\-\-enable\-xft (default: enabled)" 4 +.IX Item "--enable-xft (default: enabled)" Add support for Xft (anti\-aliases, among others) fonts. Xft fonts are slower and require lots of memory, but as long as you don't use them, you don't pay for them. -.IP "\-\-enable\-font\-styles" 4 -.IX Item "--enable-font-styles" +.IP "\-\-enable\-font\-styles (default: on)" 4 +.IX Item "--enable-font-styles (default: on)" Add support for \fBbold\fR, \fIitalic\fR and \fB\f(BIbold italic\fB\fR font styles. The fonts can be set manually or automatically. -.IP "\-\-with\-codesets=NAME,..." 4 -.IX Item "--with-codesets=NAME,..." -Compile in support for additional codeset (encoding) groups (eu, vn are -always compiled in, which includes most 8\-bit character sets). These -codeset tables are currently only used for driving X11 core fonts, they -are not required for Xft fonts. Compiling them in will make your binary -bigger (together about 700kB), but it doesn't increase memory usage unless -you use an X11 font requiring one of these encodings. +.IP "\-\-with\-codesets=NAME,... (default: all)" 4 +.IX Item "--with-codesets=NAME,... (default: all)" +Compile in support for additional codeset (encoding) groups (\f(CW\*(C`eu\*(C'\fR, \f(CW\*(C`vn\*(C'\fR +are always compiled in, which includes most 8\-bit character sets). These +codeset tables are used for driving X11 core fonts, they are not required +for Xft fonts, although having them compiled in lets rxvt-unicode choose +replacement fonts more intelligently. Compiling them in will make your +binary bigger (all of together cost about 700kB), but it doesn't increase +memory usage unless you use a font requiring one of these encodings. .TS l l . all all available codeset groups @@ -2203,13 +2038,13 @@ kr korean encodings .TE -.IP "\-\-enable\-xim" 4 -.IX Item "--enable-xim" +.IP "\-\-enable\-xim (default: on)" 4 +.IX Item "--enable-xim (default: on)" Add support for \s-1XIM\s0 (X Input Method) protocol. This allows using alternative input methods (e.g. kinput2) and will also correctly set up the input for people using dead keys or compose keys. -.IP "\-\-enable\-unicode3" 4 -.IX Item "--enable-unicode3" +.IP "\-\-enable\-unicode3 (default: off)" 4 +.IX Item "--enable-unicode3 (default: off)" 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 @@ -2220,8 +2055,8 @@ limited to a view thousand (shared with combining characters, see next switch), and right now rxvt-unicode cannot display them (input/output and cut&paste still work, though). -.IP "\-\-enable\-combining" 4 -.IX Item "--enable-combining" +.IP "\-\-enable\-combining (default: on)" 4 +.IX Item "--enable-combining (default: on)" Enable automatic composition of combining characters into composite characters. This is required for proper viewing of text where accents are encoded as seperate unicode characters. This is @@ -2239,104 +2074,78 @@ The combining table also contains entries for arabic presentation forms, but these are not currently used. Bug me if you want these to be used (and tell me how these are to be used...). -.IP "\-\-enable\-fallback(=CLASS)" 4 -.IX Item "--enable-fallback(=CLASS)" -When reading resource settings, also read settings for class \s-1CLASS\s0 -(default: Rxvt). To disable resource fallback use \-\-disable\-fallback. -.IP "\-\-with\-res\-name=NAME" 4 -.IX Item "--with-res-name=NAME" -Use the given name (default: urxvt) as default application name when +.IP "\-\-enable\-fallback(=CLASS) (default: Rxvt)" 4 +.IX Item "--enable-fallback(=CLASS) (default: Rxvt)" +When reading resource settings, also read settings for class \s-1CLASS\s0. To disable resource fallback use \-\-disable\-fallback. +.IP "\-\-with\-res\-name=NAME (default: urxvt)" 4 +.IX Item "--with-res-name=NAME (default: urxvt)" +Use the given name as default application name when reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt. -.IP "\-\-with\-res\-class=CLASS" 4 -.IX Item "--with-res-class=CLASS" -Use the given class (default: URxvt) as default application class -when reading resources. Specify \-\-with\-res\-class=Rxvt to replace +.IP "\-\-with\-res\-class=CLASS /default: URxvt)" 4 +.IX Item "--with-res-class=CLASS /default: URxvt)" +Use the given class as default application class +when reading resources. Specify \-\-with\-res\-class=Rxvt to replace rxvt. -.IP "\-\-enable\-utmp" 4 -.IX Item "--enable-utmp" +.IP "\-\-enable\-utmp (default: on)" 4 +.IX Item "--enable-utmp (default: on)" Write user and tty to utmp file (used by programs like \fIw\fR) at start of rxvt execution and delete information when rxvt exits. -.IP "\-\-enable\-wtmp" 4 -.IX Item "--enable-wtmp" +.IP "\-\-enable\-wtmp (default: on)" 4 +.IX Item "--enable-wtmp (default: on)" Write user and tty to wtmp file (used by programs like \fIlast\fR) at start of rxvt execution and write logout when rxvt exits. This option requires \-\-enable\-utmp to also be specified. -.IP "\-\-enable\-lastlog" 4 -.IX Item "--enable-lastlog" +.IP "\-\-enable\-lastlog (default: on)" 4 +.IX Item "--enable-lastlog (default: on)" Write user and tty to lastlog file (used by programs like \&\fIlastlogin\fR) at start of rxvt execution. This option requires \&\-\-enable\-utmp to also be specified. -.IP "\-\-enable\-xpm\-background" 4 -.IX Item "--enable-xpm-background" +.IP "\-\-enable\-xpm\-background (default: on)" 4 +.IX Item "--enable-xpm-background (default: on)" Add support for \s-1XPM\s0 background pixmaps. -.IP "\-\-enable\-transparency" 4 -.IX Item "--enable-transparency" +.IP "\-\-enable\-transparency (default: on)" 4 +.IX Item "--enable-transparency (default: on)" Add support for inheriting parent backgrounds thus giving a fake transparency to the term. -.IP "\-\-enable\-fading" 4 -.IX Item "--enable-fading" -Add support for fading the text when focus is lost. -.IP "\-\-enable\-tinting" 4 -.IX Item "--enable-tinting" -Add support for tinting of transparent backgrounds. -.IP "\-\-enable\-menubar" 4 -.IX Item "--enable-menubar" -Add support for our menu bar system (this interacts badly with -dynamic locale switching currently). -.IP "\-\-enable\-rxvt\-scroll" 4 -.IX Item "--enable-rxvt-scroll" +.IP "\-\-enable\-fading (default: on)" 4 +.IX Item "--enable-fading (default: on)" +Add support for fading the text when focus is lost (requires \f(CW\*(C`\-\-enable\-transparency\*(C'\fR). +.IP "\-\-enable\-tinting (default: on)" 4 +.IX Item "--enable-tinting (default: on)" +Add support for tinting of transparent backgrounds (requires \f(CW\*(C`\-\-enable\-transparency\*(C'\fR). +.IP "\-\-enable\-rxvt\-scroll (default: on)" 4 +.IX Item "--enable-rxvt-scroll (default: on)" Add support for the original rxvt scrollbar. -.IP "\-\-enable\-next\-scroll" 4 -.IX Item "--enable-next-scroll" +.IP "\-\-enable\-next\-scroll (default: on)" 4 +.IX Item "--enable-next-scroll (default: on)" Add support for a NeXT-like scrollbar. -.IP "\-\-enable\-xterm\-scroll" 4 -.IX Item "--enable-xterm-scroll" +.IP "\-\-enable\-xterm\-scroll (default: on)" 4 +.IX Item "--enable-xterm-scroll (default: on)" Add support for an Xterm-like scrollbar. -.IP "\-\-enable\-plain\-scroll" 4 -.IX Item "--enable-plain-scroll" +.IP "\-\-enable\-plain\-scroll (default: on)" 4 +.IX Item "--enable-plain-scroll (default: on)" Add support for a very unobtrusive, plain-looking scrollbar that is the favourite of the rxvt-unicode author, having used it for many years. -.IP "\-\-enable\-half\-shadow" 4 -.IX Item "--enable-half-shadow" -Make shadows on the scrollbar only half the normal width & height. -only applicable to rxvt scrollbars. -.IP "\-\-enable\-ttygid" 4 -.IX Item "--enable-ttygid" +.IP "\-\-enable\-ttygid (default: off)" 4 +.IX Item "--enable-ttygid (default: off)" Change tty device setting to group \*(L"tty\*(R" \- only use this if your system uses this type of security. .IP "\-\-disable\-backspace\-key" 4 .IX Item "--disable-backspace-key" -Disable any handling of the backspace key by us \- let the X server -do it. +Removes any handling of the backspace key by us \- let the X server do it. .IP "\-\-disable\-delete\-key" 4 .IX Item "--disable-delete-key" -Disable any handling of the delete key by us \- let the X server +Removes any handling of the delete key by us \- let the X server do it. .IP "\-\-disable\-resources" 4 .IX Item "--disable-resources" -Remove all resources checking. -.IP "\-\-enable\-xgetdefault" 4 -.IX Item "--enable-xgetdefault" -Make resources checking via \fIXGetDefault()\fR instead of our small -version which only checks ~/.Xdefaults, or if that doesn't exist then -~/.Xresources. -.Sp -Please note that nowadays, things like \s-1XIM\s0 will automatically pull in and -use the full X resource manager, so the overhead of using it might be very -small, if nonexistant. -.IP "\-\-enable\-strings" 4 -.IX Item "--enable-strings" -Add support for our possibly faster \fImemset()\fR 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). +Removes any support for resource checking. .IP "\-\-disable\-swapscreen" 4 .IX Item "--disable-swapscreen" -Remove support for swap screen. -.IP "\-\-enable\-frills" 4 -.IX Item "--enable-frills" +Remove support for secondary/swap screen. +.IP "\-\-enable\-frills (default: on)" 4 +.IX Item "--enable-frills (default: on)" Add support for many small features that are not essential but nice to have. Normally you want this, but for very small binaries you may want to disable this. @@ -2344,43 +2153,48 @@ A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly in combination with other switches) is: .Sp -.Vb 12 +.Vb 17 \& MWM-hints -\& seperate underline colour -\& settable border widths and borderless switch -\& settable extra linespacing -\& extra window properties (e.g. UTF-8 window names and PID) +\& EWMH-hints (pid, utf8 names) and protocols (ping) +\& seperate underline colour (-underlineColor) +\& settable border widths and borderless switch (-w, -b, -bl) +\& settable extra linespacing /-lsp) \& iso-14755-2 and -3, and visual feedback \& backindex and forwardindex escape sequence -\& window op and locale change escape sequences -\& tripleclickwords -\& settable insecure mode +\& window op and some xterm/OSC escape sequences +\& tripleclickwords (-tcw) +\& settable insecure mode (-insecure) \& keysym remapping support -\& -embed and -pty-fd options +\& cursor blinking and underline cursor (-cb, -uc) +\& XEmbed support (-embed) +\& user-pty (-pty-fd) +\& hold on exit (-hold) +\& skip builtin block graphics (-sbg) +\& sgr modes 90..97 and 100..107 .Ve -.IP "\-\-enable\-iso14755" 4 -.IX Item "--enable-iso14755" +.IP "\-\-enable\-iso14755 (default: on)" 4 +.IX Item "--enable-iso14755 (default: on)" Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or \&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by \&\f(CW\*(C`\-\-enable\-frills\*(C'\fR, while support for 5.2, 5.3 and 5.4 is enabled with this switch. -.IP "\-\-enable\-keepscrolling" 4 -.IX Item "--enable-keepscrolling" +.IP "\-\-enable\-keepscrolling (default: on)" 4 +.IX Item "--enable-keepscrolling (default: on)" Add support for continual scrolling of the display when you hold the mouse button down on a scrollbar arrow. -.IP "\-\-enable\-mousewheel" 4 -.IX Item "--enable-mousewheel" +.IP "\-\-enable\-mousewheel (default: on)" 4 +.IX Item "--enable-mousewheel (default: on)" Add support for scrolling via mouse wheel or buttons 4 & 5. -.IP "\-\-enable\-slipwheeling" 4 -.IX Item "--enable-slipwheeling" +.IP "\-\-enable\-slipwheeling (default: on)" 4 +.IX Item "--enable-slipwheeling (default: on)" Add support for continual scrolling (using the mouse wheel as an accelerator) while the control key is held down. This option requires \-\-enable\-mousewheel to also be specified. .IP "\-\-disable\-new\-selection" 4 .IX Item "--disable-new-selection" Remove support for mouse selection style like that of xterm. -.IP "\-\-enable\-dmalloc" 4 -.IX Item "--enable-dmalloc" +.IP "\-\-enable\-dmalloc (default: off)" 4 +.IX Item "--enable-dmalloc (default: off)" Use Gray Watson's malloc \- which is good for debugging See http://www.letters.com/dmalloc/ for details If you use either this or the next option, you may need to edit src/Makefile after compiling to point @@ -2388,30 +2202,33 @@ .Sp You can only use either this option and the following (should you use either) . -.IP "\-\-enable\-dlmalloc" 4 -.IX Item "--enable-dlmalloc" +.IP "\-\-enable\-dlmalloc (default: off)" 4 +.IX Item "--enable-dlmalloc (default: off)" Use Doug Lea's malloc \- which is good for a production version See for details. -.IP "\-\-enable\-smart\-resize" 4 -.IX Item "--enable-smart-resize" -Add smart growth/shrink behaviour when changing font size via from hot -keys. This should keep in a fixed position the rxvt corner which is -closest to a corner of the screen. -.IP "\-\-enable\-cursor\-blink" 4 -.IX Item "--enable-cursor-blink" -Add support for a blinking cursor. -.IP "\-\-enable\-pointer\-blank" 4 -.IX Item "--enable-pointer-blank" +.IP "\-\-enable\-smart\-resize (default: on)" 4 +.IX Item "--enable-smart-resize (default: on)" +Add smart growth/shrink behaviour when changing font size via hot +keys. This should keep the window corner which is closest to a corner of +the screen in a fixed position. +.IP "\-\-enable\-pointer\-blank (default: on)" 4 +.IX Item "--enable-pointer-blank (default: on)" Add support to have the pointer disappear when typing or inactive. -.IP "\-\-with\-name=NAME" 4 -.IX Item "--with-name=NAME" -Set the basename for the installed binaries (default: \f(CW\*(C`urxvt\*(C'\fR, resulting +.IP "\-\-enable\-perl (default: off)" 4 +.IX Item "--enable-perl (default: off)" +Enable an embedded perl interpreter. See the \fB@@RXVT_NAME@@\f(BIperl\fB\|(3)\fR +manpage (\fIdoc/rxvtperl.txt\fR) for more info on this feature, or the files +in \fIsrc/perl\-ext/\fR for the extensions that are installed by default. The +perl interpreter that is used can be specified via the \f(CW\*(C`PERL\*(C'\fR environment +variable when running configure. +.IP "\-\-with\-name=NAME (default: urxvt)" 4 +.IX Item "--with-name=NAME (default: urxvt)" +Set the basename for the installed binaries, resulting in \f(CW\*(C`urxvt\*(C'\fR, \f(CW\*(C`urxvtd\*(C'\fR etc.). Specify \f(CW\*(C`\-\-with\-name=rxvt\*(C'\fR to replace with \&\f(CW\*(C`rxvt\*(C'\fR. -.IP "\-\-with\-term=NAME" 4 -.IX Item "--with-term=NAME" -Change the environmental variable for the terminal to \s-1NAME\s0 (default -\&\f(CW\*(C`rxvt\-unicode\*(C'\fR) +.IP "\-\-with\-term=NAME (default: rxvt\-unicode)" 4 +.IX Item "--with-term=NAME (default: rxvt-unicode)" +Change the environmental variable for the terminal to \s-1NAME\s0. .IP "\-\-with\-terminfo=PATH" 4 .IX Item "--with-terminfo=PATH" Change the environmental variable for the path to the terminfo tree to