ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.man.in
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.15 by root, Mon Feb 14 18:47:54 2005 UTC vs.
Revision 1.60 by root, Tue Jan 31 01:00:49 2006 UTC

127.\} 127.\}
128.rm #[ #] #H #V #F C 128.rm #[ #] #H #V #F C
129.\" ======================================================================== 129.\" ========================================================================
130.\" 130.\"
131.IX Title "rxvt 7" 131.IX Title "rxvt 7"
132.TH rxvt 7 "2005-02-14" "5.1" "RXVT-UNICODE" 132.TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE"
133.SH "NAME" 133.SH "NAME"
134RXVT REFERENCE \- FAQ, command sequences and other background information 134RXVT REFERENCE \- FAQ, command sequences and other background information
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137.Vb 2 137.Vb 2
151.SH "DESCRIPTION" 151.SH "DESCRIPTION"
152.IX Header "DESCRIPTION" 152.IX Header "DESCRIPTION"
153This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting 153This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting
154all escape sequences, and other background information. 154all escape sequences, and other background information.
155.PP 155.PP
156The newest version of this document is 156The newest version of this document is also available on the World Wide Web at
157also available on the World Wide Web at
158<http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>. 157<http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>.
159.SH "FREQUENTLY ASKED QUESTIONS" 158.SH "FREQUENTLY ASKED QUESTIONS"
160.IX Header "FREQUENTLY ASKED QUESTIONS" 159.IX Header "FREQUENTLY ASKED QUESTIONS"
160.Sh "The new selection selects pieces that are too big, how can I select single words?"
161.IX Subsection "The new selection selects pieces that are too big, how can I select single words?"
162If you want to select e.g. alphanumeric words, you can use the following
163setting:
164.PP
165.Vb 1
166\& URxvt.selection.pattern-0: ([[:word:]]+)
167.Ve
168.PP
169If you click more than twice, the selection will be extended
170more and more.
171.PP
172To get a selection that is very similar to the old code, try this pattern:
173.PP
174.Vb 1
175\& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+)
176.Ve
177.PP
178Please also note that the \fILeftClick Shift-LeftClik\fR combination also
179selects words like the old code.
180.Sh "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?"
181.IX Subsection "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?"
182You can disable the perl extension completely by setting the
183\&\fBperl-ext-common\fR resource to the empty string, which also keeps
184rxvt-unicode from initialising perl, saving memory.
185.PP
186If you only want to disable specific features, you first have to
187identify which perl extension is responsible. For this, read the section
188\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For
189example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify
190this \fBperl-ext-common\fR resource:
191.PP
192.Vb 1
193\& URxvt.perl-ext-common: default,-selection-popup,-option-popup
194.Ve
195.PP
196This will keep the default extensions, but disable the two popup
197extensions. Some extensions can also be configured, for example,
198scrollback search mode is triggered by \fBM\-s\fR. You can move it to any
199other combination either by setting the \fBsearchable-scrollback\fR resource:
200.PP
201.Vb 1
202\& URxvt.searchable-scrollback: CM-s
203.Ve
204.PP
205\fIThe cursor moves when selecting text in the current input line, how do I switch this off?\fR
206.IX Subsection "The cursor moves when selecting text in the current input line, how do I switch this off?"
207.PP
208See next entry.
209.Sh "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?"
210.IX Subsection "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?"
211These are caused by the \f(CW\*(C`readline\*(C'\fR perl extension. Under normal
212circumstances, it will move your cursor around when you click into the
213line that contains it. It tries hard not to do this at the wrong moment,
214but when running a program that doesn't parse cursor movements or in some
215cases during rlogin sessions, it fails to detect this properly.
216.PP
217You can permamently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR
218extension:
219.PP
220.Vb 1
221\& URxvt.perl-ext-common: default,-readline
222.Ve
223.Sh "Why doesn't rxvt-unicode read my resources?"
224.IX Subsection "Why doesn't rxvt-unicode read my resources?"
225Well, why, indeed? It does, in a way very similar to other X
226applications. Most importantly, this means that if you or your \s-1OS\s0 loads
227resources into the X display (the right way to do it), rxvt-unicode will
228ignore any resource files in your home directory. It will only read
229\&\fI$HOME/.Xdefaults\fR when no resources are attached to the display.
230.PP
231If you have or use an \fI$HOME/.Xresources\fR file, chances are that
232resources are loaded into your X\-server. In this case, you have to
233re-login after every change (or run \fIxrdb \-merge \f(CI$HOME\fI/.Xresources\fR).
234.PP
235Also consider the form resources have to use:
236.PP
237.Vb 1
238\& URxvt.resource: value
239.Ve
240.PP
241If you want to use another form (there are lots of different ways of
242specifying resources), make sure you understand wether and why it
243works. If unsure, use the form above.
244.Sh "I can't get transparency working, what am I doing wrong?"
245.IX Subsection "I can't get transparency working, what am I doing wrong?"
246First of all, transparency isn't officially supported in rxvt\-unicode, so
247you are mostly on your own. Do not bug the author about it (but you may
248bug everybody else). Also, if you can't get it working consider it a rite
249of passage: ... and you failed.
250.PP
251Here are four ways to get transparency. \fBDo\fR read the manpage and option
252descriptions for the programs mentioned and rxvt\-unicode. Really, do it!
253.PP
2541. Use inheritPixmap:
255.PP
256.Vb 2
257\& Esetroot wallpaper.jpg
258\& @@RXVT_NAME@@ -ip -tint red -sh 40
259.Ve
260.PP
261That works. If you think it doesn't, you lack transparency and tinting
262support, or you are unable to read.
263.PP
2642. Use a simple pixmap and emulate pseudo\-transparency. This enables you
265to use effects other than tinting and shading: Just shade/tint/whatever
266your picture with gimp:
267.PP
268.Vb 2
269\& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
270\& @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background
271.Ve
272.PP
273That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you
274are unable to read.
275.PP
2763. Use an \s-1ARGB\s0 visual:
277.PP
278.Vb 1
279\& @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
280.Ve
281.PP
282This requires \s-1XFT\s0 support, and the support of your X\-server. If that
283doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't
284there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
285bugfixes and workarounds for Xft and Xlib to make it work, but that
286doesn't mean that your \s-1WM\s0 has the required kludges in place.
287.PP
2884. Use xcompmgr and let it do the job:
289.PP
290.Vb 2
291\& xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \e
292\& -set _NET_WM_WINDOW_OPACITY 0xc0000000
293.Ve
294.PP
295Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR
296by other values to change the degree of opacity. If it doesn't work and
297your server crashes, you got to keep the pieces.
298.Sh "Isn't rxvt supposed to be small? Don't all those features bloat?"
299.IX Subsection "Isn't rxvt supposed to be small? Don't all those features bloat?"
300I often get asked about this, and I think, no, they didn't cause extra
301bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
302that the urxvt binary is larger (due to some encoding tables always being
303compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even
304with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many
305features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
306already in use in this mode.
307.PP
308.Vb 3
309\& text data bss drs rss filename
310\& 98398 1664 24 15695 1824 rxvt --disable-everything
311\& 188985 9048 66616 18222 1788 urxvt --disable-everything
312.Ve
313.PP
314When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft
315and full locale/XIM support which are quite bloaty inside libX11 and my
316libc), the two diverge, but not unreasnobaly so.
317.PP
318.Vb 3
319\& text data bss drs rss filename
320\& 163431 2152 24 20123 2060 rxvt --enable-everything
321\& 1035683 49680 66648 29096 3680 urxvt --enable-everything
322.Ve
323.PP
324The very large size of the text section is explained by the east-asian
325encoding tables, which, if unused, take up disk space but nothing else
326and can be compiled out unless you rely on X11 core fonts that use those
327encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++
328compiler allocates (but of course doesn't use unless you are out of
329memory). Also, using an xft font instead of a core font immediately adds a
330few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when
331not used.
332.PP
333Of course, due to every character using two or four bytes instead of one,
334a large scrollback buffer will ultimately make rxvt-unicode use more
335memory.
336.PP
337Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
338still fares rather well. And compared to some monsters like gnome-terminal
339(21152k + extra 4204k in separate processes) or konsole (22200k + extra
34043180k in daemons that stay around after exit, plus half a minute of
341startup time, including the hundreds of warnings it spits out), it fares
342extremely well *g*.
343.Sh "Why \*(C+, isn't that unportable/bloated/uncool?"
344.IX Subsection "Why , isn't that unportable/bloated/uncool?"
345Is this a question? :) It comes up very often. The simple answer is: I had
346to write it, and \*(C+ allowed me to write and maintain it in a fraction
347of the time and effort (which is a scarce resource for me). Put even
348shorter: It simply wouldn't exist without \*(C+.
349.PP
350My personal stance on this is that \*(C+ is less portable than C, but in
351the case of rxvt-unicode this hardly matters, as its portability limits
352are defined by things like X11, pseudo terminals, locale support and unix
353domain sockets, which are all less portable than \*(C+ itself.
354.PP
355Regarding the bloat, see the above question: It's easy to write programs
356in C that use gobs of memory, an certainly possible to write programs in
357\&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is
358not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my
359system with a minimal config:
360.PP
361.Vb 4
362\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
363\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
364\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
365\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
366.Ve
367.PP
368And here is rxvt\-unicode:
369.PP
370.Vb 5
371\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
372\& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
373\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
374\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
375\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
376.Ve
377.PP
378No large bloated libraries (of course, none were linked in statically),
379except maybe libX11 :)
380.Sh "Does it support tabs, can I have a tabbed rxvt\-unicode?"
381.IX Subsection "Does it support tabs, can I have a tabbed rxvt-unicode?"
382Beginning with version 7.3, there is a perl extension that implements a
383simple tabbed terminal. It is installed by default, so any of these should
384give you tabs:
385.PP
386.Vb 1
387\& @@RXVT_NAME@@ -pe tabbed
388.Ve
389.PP
390.Vb 1
391\& URxvt.perl-ext-common: default,tabbed
392.Ve
393.PP
394It will also work fine with tabbing functionality of many window managers
395or similar tabbing programs, and its embedding-features allow it to be
396embedded into other programs, as witnessed by \fIdoc/rxvt\-tabbed\fR or
397the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl module, which features a tabbed urxvt
398(murxvt) terminal as an example embedding application.
161.IP "How do I know which rxvt-unicode version I'm using?" 4 399.Sh "How do I know which rxvt-unicode version I'm using?"
162.IX Item "How do I know which rxvt-unicode version I'm using?" 400.IX Subsection "How do I know which rxvt-unicode version I'm using?"
163The version number is displayed with the usage (\-h). Also the escape 401The version number is displayed with the usage (\-h). Also the escape
164sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. 402sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When
403using the @@RXVT_NAME@@c client, the version displayed is that of the
404daemon.
165.IP "I am using Debian GNU/Linux and have a problem..." 4 405.Sh "I am using Debian GNU/Linux and have a problem..."
166.IX Item "I am using Debian GNU/Linux and have a problem..." 406.IX Subsection "I am using Debian GNU/Linux and have a problem..."
167The Debian GNU/Linux package of rxvt-unicode contains large patches that 407The Debian GNU/Linux package of rxvt-unicode in sarge contains large
168considerably change the behaviour of rxvt\-unicode. Before reporting a 408patches that considerably change the behaviour of rxvt-unicode (but
409unfortunately this notice has been removed). Before reporting a bug to
169bug to the original rxvt-unicode author please download and install the 410the original rxvt-unicode author please download and install the genuine
170genuine version (<http://software.schmorp.de#rxvt\-unicode>) and try to 411version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce
171reproduce the problem. If you cannot, chances are that the problems are 412the problem. If you cannot, chances are that the problems are specific to
172specific to Debian GNU/Linux, in which case it should be reported via the 413Debian GNU/Linux, in which case it should be reported via the Debian Bug
173Debian Bug Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug). 414Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug).
174.Sp 415.PP
175For other problems that also affect the Debian package, you can and 416For other problems that also affect the Debian package, you can and
176probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a 417probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a
177bug in the Debian version and it serves as a reminder for other users that 418bug in the Debian version and it serves as a reminder for other users that
178might encounter the same issue. 419might encounter the same issue.
420.Sh "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?"
421.IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?"
422You should build one binary with the default options. \fIconfigure\fR
423now enables most useful options, and the trend goes to making them
424runtime\-switchable, too, so there is usually no drawback to enbaling them,
425except higher disk and possibly memory usage. The perl interpreter should
426be enabled, as important functionality (menus, selection, likely more in
427the future) depends on it.
428.PP
429You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources
430system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful
431behaviour. If your distribution aims at low memory, add an empty
432\&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the
433perl interpreter disabled until the user enables it.
434.PP
435If you can/want build more binaries, I recommend building a minimal
436one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with
437\&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of
438encodings built-in that increase download times and are rarely used).
439.Sh "I need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?"
440.IX Subsection "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?"
441It should be, starting with release 7.1. You are encouraged to properly
442install urxvt with privileges necessary for your \s-1OS\s0 now.
443.PP
444When rxvt-unicode detects that it runs setuid or setgid, it will fork
445into a helper process for privileged operations (pty handling on some
446systems, utmp/wtmp/lastlog handling on others) and drop privileges
447immediately. This is much safer than most other terminals that keep
448privileges while running (but is more relevant to urxvt, as it contains
449things as perl interpreters, which might be \*(L"helpful\*(R" to attackers).
450.PP
451This forking is done as the very first within \fImain()\fR, which is very early
452and reduces possible bugs to initialisation code run before \fImain()\fR, or
453things like the dynamic loader of your system, which should result in very
454little risk.
179.IP "When I log-in to another system it tells me about missing terminfo data?" 4 455.Sh "When I log-in to another system it tells me about missing terminfo data?"
180.IX Item "When I log-in to another system it tells me about missing terminfo data?" 456.IX Subsection "When I log-in to another system it tells me about missing terminfo data?"
181The terminal description used by rxvt-unicode is not as widely available 457The terminal description used by rxvt-unicode is not as widely available
182as that for xterm, or even rxvt (for which the same problem often arises). 458as that for xterm, or even rxvt (for which the same problem often arises).
183.Sp 459.PP
184The correct solution for this problem is to install the terminfo, this can 460The correct solution for this problem is to install the terminfo, this can
185be done like this (with ncurses' infocmp): 461be done like this (with ncurses' infocmp):
186.Sp 462.PP
187.Vb 2 463.Vb 2
188\& REMOTE=remotesystem.domain 464\& REMOTE=remotesystem.domain
189\& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" 465\& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
190.Ve 466.Ve
191.Sp 467.PP
192\&... or by installing rxvt-unicode normally on the remote system, 468\&... or by installing rxvt-unicode normally on the remote system,
193.Sp 469.PP
194If you cannot or do not want to do this, then you can simply set 470If you cannot or do not want to do this, then you can simply set
195\&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of 471\&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of
196problems arising, which includes wrong keymapping, less and different 472problems arising, which includes wrong keymapping, less and different
197colours and some refresh errors in fullscreen applications. It's a nice 473colours and some refresh errors in fullscreen applications. It's a nice
198quick-and-dirty workaround for rare cases, though. 474quick-and-dirty workaround for rare cases, though.
199.Sp 475.PP
200If you always want to do this (and are fine with the consequences) you 476If you always want to do this (and are fine with the consequences) you
201can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a 477can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a
202resource to set it: 478resource to set it:
203.Sp 479.PP
204.Vb 1 480.Vb 1
205\& URxvt.termName: rxvt 481\& URxvt.termName: rxvt
206.Ve 482.Ve
207.Sp 483.PP
208If you don't plan to use \fBrxvt\fR (quite common...) you could also replace 484If you don't plan to use \fBrxvt\fR (quite common...) you could also replace
209the rxvt terminfo file with the rxvt-unicode one. 485the rxvt terminfo file with the rxvt-unicode one.
486.ie n .Sh """tic"" outputs some error when compiling the terminfo entry."
487.el .Sh "\f(CWtic\fP outputs some error when compiling the terminfo entry."
488.IX Subsection "tic outputs some error when compiling the terminfo entry."
489Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by
490\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again.
210.ie n .IP """bash""'s readline does not work correctly under @@RXVT_NAME@@." 4 491.ie n .Sh """bash""'s readline does not work correctly under @@RXVT_NAME@@."
211.el .IP "\f(CWbash\fR's readline does not work correctly under @@RXVT_NAME@@." 4 492.el .Sh "\f(CWbash\fP's readline does not work correctly under @@RXVT_NAME@@."
212.IX Item "bash's readline does not work correctly under @@RXVT_NAME@@." 493.IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@."
213.PD 0 494See next entry.
214.IP "I need a termcap file entry." 4 495.Sh "I need a termcap file entry."
215.IX Item "I need a termcap file entry." 496.IX Subsection "I need a termcap file entry."
216.PD
217One reason you might want this is that some distributions or operating 497One reason you might want this is that some distributions or operating
218systems still compile some programs using the long-obsoleted termcap 498systems still compile some programs using the long-obsoleted termcap
219library (Fedora Core's bash is one example) and rely on a termcap entry 499library (Fedora Core's bash is one example) and rely on a termcap entry
220for \f(CW\*(C`rxvt\-unicode\*(C'\fR. 500for \f(CW\*(C`rxvt\-unicode\*(C'\fR.
221.Sp 501.PP
222You could use rxvt's termcap entry with resonable results in many cases. 502You could use rxvt's termcap entry with resonable results in many cases.
223You can also create a termcap entry by using terminfo's infocmp program 503You can also create a termcap entry by using terminfo's infocmp program
224like this: 504like this:
225.Sp 505.PP
226.Vb 1 506.Vb 1
227\& infocmp -C rxvt-unicode 507\& infocmp -C rxvt-unicode
228.Ve 508.Ve
229.Sp 509.PP
230Or you could use this termcap entry, generated by the command above: 510Or you could use this termcap entry, generated by the command above:
231.Sp 511.PP
232.Vb 19 512.Vb 20
233\& rxvt-unicode|rxvt-unicode terminal (X Window System):\e 513\& rxvt-unicode|rxvt-unicode terminal (X Window System):\e
234\& :am:bw:eo:km:mi:ms:xn:xo:\e 514\& :am:bw:eo:km:mi:ms:xn:xo:\e
235\& :co#80:it#8:li#24:lm#0:\e 515\& :co#80:it#8:li#24:lm#0:\e
236\& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e 516\& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e
237\& :K1=\eEOw:K2=\eEOu:K3=\eEOy:K4=\eEOq:K5=\eEOs:LE=\eE[%dD:\e 517\& :K1=\eEOw:K2=\eEOu:K3=\eEOy:K4=\eEOq:K5=\eEOs:LE=\eE[%dD:\e
238\& :RI=\eE[%dC:SF=\eE[%dS:SR=\eE[%dT:UP=\eE[%dA:ae=^O:al=\eE[L:\e 518\& :RI=\eE[%dC:SF=\eE[%dS:SR=\eE[%dT:UP=\eE[%dA:ae=\eE(B:al=\eE[L:\e
239\& :as=^N:bl=^G:cd=\eE[J:ce=\eE[K:cl=\eE[H\eE[2J:cm=\eE[%i%d;%dH:\e 519\& :as=\eE(0:bl=^G:cd=\eE[J:ce=\eE[K:cl=\eE[H\eE[2J:\e
240\& :cr=^M:cs=\eE[%i%d;%dr:ct=\eE[3g:dc=\eE[P:dl=\eE[M:do=^J:\e 520\& :cm=\eE[%i%d;%dH:cr=^M:cs=\eE[%i%d;%dr:ct=\eE[3g:dc=\eE[P:\e
241\& :ec=\eE[%dX:ei=\eE[4l:ho=\eE[H:i1=\eE[?47l\eE=\eE[?1l:ic=\eE[@:\e 521\& :dl=\eE[M:do=^J:ec=\eE[%dX:ei=\eE[4l:ho=\eE[H:\e
522\& :i1=\eE[?47l\eE=\eE[?1l:ic=\eE[@:im=\eE[4h:\e
242\& :im=\eE[4h:is=\eE[r\eE[m\eE[2J\eE[H\eE[?7h\eE[?1;3;4;6l\eE[4l:\e 523\& :is=\eE[r\eE[m\eE[2J\eE[H\eE[?7h\eE[?1;3;4;6l\eE[4l:\e
243\& :k1=\eE[11~:k2=\eE[12~:k3=\eE[13~:k4=\eE[14~:k5=\eE[15~:\e 524\& :k1=\eE[11~:k2=\eE[12~:k3=\eE[13~:k4=\eE[14~:k5=\eE[15~:\e
244\& :k6=\eE[17~:k7=\eE[18~:k8=\eE[19~:k9=\eE[20~:kD=\eE[3~:\e 525\& :k6=\eE[17~:k7=\eE[18~:k8=\eE[19~:k9=\eE[20~:kD=\eE[3~:\e
245\& :kI=\eE[2~:kN=\eE[6~:kP=\eE[5~:kb=\e177:kd=\eEOB:ke=\eE[?1l\eE>:\e 526\& :kI=\eE[2~:kN=\eE[6~:kP=\eE[5~:kb=\e177:kd=\eEOB:ke=\eE[?1l\eE>:\e
246\& :kh=\eE[7~:kl=\eEOD:kr=\eEOC:ks=\eE[?1h\eE=:ku=\eEOA:le=^H:\e 527\& :kh=\eE[7~:kl=\eEOD:kr=\eEOC:ks=\eE[?1h\eE=:ku=\eEOA:le=^H:\e
247\& :mb=\eE[5m:md=\eE[1m:me=\eE[m\e017:mr=\eE[7m:nd=\eE[C:rc=\eE8:\e 528\& :mb=\eE[5m:md=\eE[1m:me=\eE[m\e017:mr=\eE[7m:nd=\eE[C:rc=\eE8:\e
248\& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e 529\& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e
249\& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e 530\& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e
250\& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e 531\& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e
251\& :vs=\eE[?25h: 532\& :vs=\eE[?25h:
252.Ve 533.Ve
253.ie n .IP "Why does ""ls"" no longer have coloured output?" 4 534.ie n .Sh "Why does ""ls"" no longer have coloured output?"
254.el .IP "Why does \f(CWls\fR no longer have coloured output?" 4 535.el .Sh "Why does \f(CWls\fP no longer have coloured output?"
255.IX Item "Why does ls no longer have coloured output?" 536.IX Subsection "Why does ls no longer have coloured output?"
256The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to 537The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to
257decide wether a terminal has colour, but uses it's own configuration 538decide wether a terminal has colour, but uses it's own configuration
258file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among 539file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among
259with most other terminals supporting colour). Either add: 540with most other terminals supporting colour). Either add:
260.Sp 541.PP
261.Vb 1 542.Vb 1
262\& TERM rxvt-unicode 543\& TERM rxvt-unicode
263.Ve 544.Ve
264.Sp 545.PP
265to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add: 546to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add:
266.Sp 547.PP
267.Vb 1 548.Vb 1
268\& alias ls='ls --color=auto' 549\& alias ls='ls --color=auto'
269.Ve 550.Ve
270.Sp 551.PP
271to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR. 552to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR.
272.IP "Why doesn't vim/emacs etc. use the 88 colour mode?" 4 553.Sh "Why doesn't vim/emacs etc. use the 88 colour mode?"
273.IX Item "Why doesn't vim/emacs etc. use the 88 colour mode?" 554.IX Subsection "Why doesn't vim/emacs etc. use the 88 colour mode?"
274.PD 0 555See next entry.
275.IP "Why doesn't vim/emacs etc. make use of italic?" 4 556.Sh "Why doesn't vim/emacs etc. make use of italic?"
276.IX Item "Why doesn't vim/emacs etc. make use of italic?" 557.IX Subsection "Why doesn't vim/emacs etc. make use of italic?"
558See next entry.
277.IP "Why are the secondary screen-related options not working properly?" 4 559.Sh "Why are the secondary screen-related options not working properly?"
278.IX Item "Why are the secondary screen-related options not working properly?" 560.IX Subsection "Why are the secondary screen-related options not working properly?"
279.PD
280Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged 561Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged
281distributions (most notably Debian GNU/Linux) break rxvt-unicode 562distributions (most notably Debian GNU/Linux) break rxvt-unicode
282by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra 563by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra
283features. Unfortunately, some of these (most notably, again, Debian 564features. Unfortunately, some of these (most notably, again, Debian
284GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo 565GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
285file, so you will need to install it on your own (See the question \fBWhen 566file, so you will need to install it on your own (See the question \fBWhen
286I log-in to another system it tells me about missing terminfo data?\fR on 567I log-in to another system it tells me about missing terminfo data?\fR on
287how to do this). 568how to do this).
288.IP "My numerical keypad acts weird and generates differing output?" 4 569.Sh "My numerical keypad acts weird and generates differing output?"
289.IX Item "My numerical keypad acts weird and generates differing output?" 570.IX Subsection "My numerical keypad acts weird and generates differing output?"
290Some Debian GNUL/Linux users seem to have this problem, although no 571Some Debian GNUL/Linux users seem to have this problem, although no
291specific details were reported so far. It is possible that this is caused 572specific details were reported so far. It is possible that this is caused
292by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how 573by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how
293this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible 574this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible
294keymap. See the answer to the previous question, and please report if that 575keymap. See the answer to the previous question, and please report if that
295helped. 576helped.
296.IP "Rxvt-unicode does not seem to understand the selected encoding?" 4 577.Sh "Rxvt-unicode does not seem to understand the selected encoding?"
297.IX Item "Rxvt-unicode does not seem to understand the selected encoding?" 578.IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?"
298.PD 0 579See next entry.
299.IP "Unicode does not seem to work?" 4 580.Sh "Unicode does not seem to work?"
300.IX Item "Unicode does not seem to work?" 581.IX Subsection "Unicode does not seem to work?"
301.PD
302If you encounter strange problems like typing an accented character but 582If you encounter strange problems like typing an accented character but
303getting two unrelated other characters or similar, or if program output is 583getting two unrelated other characters or similar, or if program output is
304subtly garbled, then you should check your locale settings. 584subtly garbled, then you should check your locale settings.
305.Sp 585.PP
306Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the 586Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the
307programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the 587programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the
308login script running within the rxvt-unicode window changes the locale to 588login script running within the rxvt-unicode window changes the locale to
309something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work. 589something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work.
310.Sp 590.PP
311The best thing is to fix your startup environment, as you will likely run 591The best thing is to fix your startup environment, as you will likely run
312into other problems. If nothing works you can try this in your .profile. 592into other problems. If nothing works you can try this in your .profile.
313.Sp 593.PP
314.Vb 1 594.Vb 1
315\& printf '\ee]701;%s\e007' "$LC_CTYPE" 595\& printf '\ee]701;%s\e007' "$LC_CTYPE"
316.Ve 596.Ve
317.Sp 597.PP
318If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not 598If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not
319supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which 599supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which
320displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as 600displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as
321it will complain loudly if it cannot set the locale). If it displays something 601it will complain loudly if it cannot set the locale). If it displays something
322like: 602like:
323.Sp 603.PP
324.Vb 1 604.Vb 1
325\& locale: Cannot set LC_CTYPE to default locale: ... 605\& locale: Cannot set LC_CTYPE to default locale: ...
326.Ve 606.Ve
327.Sp 607.PP
328Then the locale you specified is not supported on your system. 608Then the locale you specified is not supported on your system.
329.Sp 609.PP
330If nothing works and you are sure that everything is set correctly then 610If nothing works and you are sure that everything is set correctly then
331you will need to remember a little known fact: Some programs just don't 611you will need to remember a little known fact: Some programs just don't
332support locales :( 612support locales :(
333.IP "Why do some characters look so much different than others?" 4 613.Sh "Why do some characters look so much different than others?"
334.IX Item "Why do some characters look so much different than others?" 614.IX Subsection "Why do some characters look so much different than others?"
335.PD 0 615See next entry.
336.IP "How does rxvt-unicode choose fonts?" 4 616.Sh "How does rxvt-unicode choose fonts?"
337.IX Item "How does rxvt-unicode choose fonts?" 617.IX Subsection "How does rxvt-unicode choose fonts?"
338.PD
339Most fonts do not contain the full range of Unicode, which is 618Most fonts do not contain the full range of Unicode, which is
340fine. Chances are that the font you (or the admin/package maintainer of 619fine. Chances are that the font you (or the admin/package maintainer of
341your system/os) have specified does not cover all the characters you want 620your system/os) have specified does not cover all the characters you want
342to display. 621to display.
343.Sp 622.PP
344\&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement 623\&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement
345font. Often the result is fine, but sometimes the chosen font looks 624font. Often the result is fine, but sometimes the chosen font looks
346bad/ugly/wrong. Some fonts have totally strange characters that don't 625bad/ugly/wrong. Some fonts have totally strange characters that don't
347resemble the correct glyph at all, and rxvt-unicode lacks the artificial 626resemble the correct glyph at all, and rxvt-unicode lacks the artificial
348intelligence to detect that a specific glyph is wrong: it has to believe 627intelligence to detect that a specific glyph is wrong: it has to believe
349the font that the characters it claims to contain indeed look correct. 628the font that the characters it claims to contain indeed look correct.
350.Sp 629.PP
351In that case, select a font of your taste and add it to the font list, 630In that case, select a font of your taste and add it to the font list,
352e.g.: 631e.g.:
353.Sp 632.PP
354.Vb 1 633.Vb 1
355\& @@RXVT_NAME@@ -fn basefont,font2,font3... 634\& @@RXVT_NAME@@ -fn basefont,font2,font3...
356.Ve 635.Ve
357.Sp 636.PP
358When rxvt-unicode sees a character, it will first look at the base 637When rxvt-unicode sees a character, it will first look at the base
359font. If the base font does not contain the character, it will go to the 638font. If the base font does not contain the character, it will go to the
360next font, and so on. Specifying your own fonts will also speed up this 639next font, and so on. Specifying your own fonts will also speed up this
361search and use less resources within rxvt-unicode and the X\-server. 640search and use less resources within rxvt-unicode and the X\-server.
362.Sp 641.PP
363The only limitation is that none of the fonts may be larger than the base 642The only limitation is that none of the fonts may be larger than the base
364font, as the base font defines the terminal character cell size, which 643font, as the base font defines the terminal character cell size, which
365must be the same due to the way terminals work. 644must be the same due to the way terminals work.
366.IP "Why do some chinese characters look so different than others?" 4 645.Sh "Why do some chinese characters look so different than others?"
367.IX Item "Why do some chinese characters look so different than others?" 646.IX Subsection "Why do some chinese characters look so different than others?"
368This is because there is a difference between script and language \*(-- 647This is because there is a difference between script and language \*(--
369rxvt-unicode does not know which language the text that is output is, 648rxvt-unicode does not know which language the text that is output is,
370as it only knows the unicode character codes. If rxvt-unicode first 649as it only knows the unicode character codes. If rxvt-unicode first
371sees a japanese/chinese character, it might choose a japanese font for 650sees a japanese/chinese character, it might choose a japanese font for
372display. Subsequent japanese characters will use that font. Now, many 651display. Subsequent japanese characters will use that font. Now, many
373chinese characters aren't represented in japanese fonts, so when the first 652chinese characters aren't represented in japanese fonts, so when the first
374non-japanese character comes up, rxvt-unicode will look for a chinese font 653non-japanese character comes up, rxvt-unicode will look for a chinese font
375\&\*(-- unfortunately at this point, it will still use the japanese font for 654\&\*(-- unfortunately at this point, it will still use the japanese font for
376chinese characters that are also in the japanese font. 655chinese characters that are also in the japanese font.
377.Sp 656.PP
378The workaround is easy: just tag a chinese font at the end of your font 657The workaround is easy: just tag a chinese font at the end of your font
379list (see the previous question). The key is to view the font list as 658list (see the previous question). The key is to view the font list as
380a preference list: If you expect more japanese, list a japanese font 659a preference list: If you expect more japanese, list a japanese font
381first. If you expect more chinese, put a chinese font first. 660first. If you expect more chinese, put a chinese font first.
382.Sp 661.PP
383In the future it might be possible to switch language preferences at 662In the future it might be possible to switch language preferences at
384runtime (the internal data structure has no problem with using different 663runtime (the internal data structure has no problem with using different
385fonts for the same character at the same time, but no interface for this 664fonts for the same character at the same time, but no interface for this
386has been designed yet). 665has been designed yet).
387.Sp 666.PP
388Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document). 667Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document).
389.IP "Why does rxvt-unicode sometimes leave pixel droppings?" 4 668.Sh "Why does rxvt-unicode sometimes leave pixel droppings?"
390.IX Item "Why does rxvt-unicode sometimes leave pixel droppings?" 669.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"
391Most fonts were not designed for terminal use, which means that character 670Most fonts were not designed for terminal use, which means that character
392size varies a lot. A font that is otherwise fine for terminal use might 671size varies a lot. A font that is otherwise fine for terminal use might
393contain some characters that are simply too wide. Rxvt-unicode will avoid 672contain some characters that are simply too wide. Rxvt-unicode will avoid
394these characters. For characters that are just \*(L"a bit\*(R" too wide a special 673these characters. For characters that are just \*(L"a bit\*(R" too wide a special
395\&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters. 674\&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters.
396.Sp 675.PP
397All of this requires that fonts do not lie about character sizes, 676All of this requires that fonts do not lie about character sizes,
398however: Xft fonts often draw glyphs larger than their acclaimed bounding 677however: Xft fonts often draw glyphs larger than their acclaimed bounding
399box, and rxvt-unicode has no way of detecting this (the correct way is to 678box, and rxvt-unicode has no way of detecting this (the correct way is to
400ask for the character bounding box, which unfortunately is wrong in these 679ask for the character bounding box, which unfortunately is wrong in these
401cases). 680cases).
402.Sp 681.PP
403It's not clear (to me at least), wether this is a bug in Xft, freetype, 682It's not clear (to me at least), wether this is a bug in Xft, freetype,
404or the respective font. If you encounter this problem you might try using 683or the respective font. If you encounter this problem you might try using
405the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you 684the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you
406might be forced to use a different font. 685might be forced to use a different font.
407.Sp 686.PP
408All of this is not a problem when using X11 core fonts, as their bounding 687All of this is not a problem when using X11 core fonts, as their bounding
409box data is correct. 688box data is correct.
689.Sh "On Solaris 9, many line-drawing characters are too wide."
690.IX Subsection "On Solaris 9, many line-drawing characters are too wide."
691Seems to be a known bug, read
692<http://nixdoc.net/files/forum/about34198.html>. Some people use the
693following ugly workaround to get non-double-wide-characters working:
694.PP
695.Vb 1
696\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
697.Ve
410.IP "My Compose (Multi_key) key is no longer working." 4 698.Sh "My Compose (Multi_key) key is no longer working."
411.IX Item "My Compose (Multi_key) key is no longer working." 699.IX Subsection "My Compose (Multi_key) key is no longer working."
412The most common causes for this are that either your locale is not set 700The most common causes for this are that either your locale is not set
413correctly, or you specified a \fBpreeditStyle\fR that is not supported by 701correctly, or you specified a \fBpreeditStyle\fR that is not supported by
414your input method. For example, if you specified \fBOverTheSpot\fR and 702your input method. For example, if you specified \fBOverTheSpot\fR and
415your input method (e.g. the default input method handling Compose keys) 703your input method (e.g. the default input method handling Compose keys)
416does not support this (for instance because it is not visual), then 704does not support this (for instance because it is not visual), then
417rxvt-unicode will continue without an input method. 705rxvt-unicode will continue without an input method.
418.Sp 706.PP
419In this case either do not specify a \fBpreeditStyle\fR or specify more than 707In this case either do not specify a \fBpreeditStyle\fR or specify more than
420one pre-edit style, such as \fBOverTheSpot,Root,None\fR. 708one pre-edit style, such as \fBOverTheSpot,Root,None\fR.
421.ie n .IP "I cannot type ""Ctrl\-Shift\-2"" to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" 4 709.ie n .Sh "I cannot type ""Ctrl\-Shift\-2"" to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755"
422.el .IP "I cannot type \f(CWCtrl\-Shift\-2\fR to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" 4 710.el .Sh "I cannot type \f(CWCtrl\-Shift\-2\fP to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755"
423.IX Item "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755" 711.IX Subsection "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755"
424Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on 712Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on
425international keyboards) or simply use \s-1ISO\s0 14755 support to your 713international keyboards) or simply use \s-1ISO\s0 14755 support to your
426advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other 714advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other
427codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape 715codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape
428character and so on. 716character and so on.
429.IP "How can I keep rxvt-unicode from using reverse video so much?" 4 717.Sh "How can I keep rxvt-unicode from using reverse video so much?"
430.IX Item "How can I keep rxvt-unicode from using reverse video so much?" 718.IX Subsection "How can I keep rxvt-unicode from using reverse video so much?"
431First of all, make sure you are running with the right terminal settings 719First of all, make sure you are running with the right terminal settings
432(\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then 720(\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then
433make sure you have specified colours for italic and bold, as otherwise 721make sure you have specified colours for italic and bold, as otherwise
434rxvt-unicode might use reverse video to simulate the effect: 722rxvt-unicode might use reverse video to simulate the effect:
435.Sp 723.PP
436.Vb 2 724.Vb 2
437\& URxvt.colorBD: white 725\& URxvt.colorBD: white
438\& URxvt.colorIT: green 726\& URxvt.colorIT: green
439.Ve 727.Ve
440.IP "Some programs assume totally weird colours (red instead of blue), how can I fix that?" 4 728.Sh "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
441.IX Item "Some programs assume totally weird colours (red instead of blue), how can I fix that?" 729.IX Subsection "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
442For some unexplainable reason, some rare programs assume a very weird 730For some unexplainable reason, some rare programs assume a very weird
443colour palette when confronted with a terminal with more than the standard 731colour palette when confronted with a terminal with more than the standard
4448 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix 7328 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix
445these programs not to assume non-ISO colours without very good reasons. 733these programs not to assume non-ISO colours without very good reasons.
446.Sp 734.PP
447In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo 735In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
448definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will 736definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will
449fix colours but keep you from using other rxvt-unicode features. 737fix colours but keep you from using other rxvt-unicode features.
450.IP "I am on FreeBSD and rxvt-unicode does not seem to work at all." 4 738.Sh "I am on FreeBSD and rxvt-unicode does not seem to work at all."
451.IX Item "I am on FreeBSD and rxvt-unicode does not seem to work at all." 739.IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all."
452Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined 740Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined
453in your compile environment, or an implementation that implements it, 741in your compile environment, or an implementation that implements it,
454wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that 742wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that
455\&\fBwchar_t\fR is represented as unicode. 743\&\fBwchar_t\fR is represented as unicode.
456.Sp 744.PP
457As you might have guessed, FreeBSD does neither define this symobl nor 745As you might have guessed, FreeBSD does neither define this symobl nor
458does it support it. Instead, it uses it's own internal representation of 746does it support it. Instead, it uses it's own internal representation of
459\&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. 747\&\fBwchar_t\fR. This is, of course, completely fine with respect to standards.
460.Sp 748.PP
749However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and
750\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR.
751.PP
461However, \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support 752\&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language
462multi-language apps in an \s-1OS\s0, as using a locale-dependent (and 753apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized)
463non\-standardized) representation of \fBwchar_t\fR makes it impossible to 754representation of \fBwchar_t\fR makes it impossible to convert between
464convert between \fBwchar_t\fR (as used by X11 and your applications) and any 755\&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding
465other encoding without implementing OS-specific-wrappers for each and 756without implementing OS-specific-wrappers for each and every locale. There
466every locale. There simply are no APIs to convert \fBwchar_t\fR into anything 757simply are no APIs to convert \fBwchar_t\fR into anything except the current
467except the current locale encoding. 758locale encoding.
468.Sp 759.PP
469Some applications (such as the formidable \fBmlterm\fR) work around this 760Some applications (such as the formidable \fBmlterm\fR) work around this
470by carrying their own replacement functions for character set handling 761by carrying their own replacement functions for character set handling
471with them, and either implementing OS-dependent hacks or doing multiple 762with them, and either implementing OS-dependent hacks or doing multiple
472conversions (which is slow and unreliable in case the \s-1OS\s0 implements 763conversions (which is slow and unreliable in case the \s-1OS\s0 implements
473encodings slightly different than the terminal emulator). 764encodings slightly different than the terminal emulator).
474.Sp 765.PP
475The rxvt-unicode author insists that the right way to fix this is in the 766The rxvt-unicode author insists that the right way to fix this is in the
476system libraries once and for all, instead of forcing every app to carry 767system libraries once and for all, instead of forcing every app to carry
477complete replacements for them :) 768complete replacements for them :)
769.Sh "I use Solaris 9 and it doesn't compile/work/etc."
770.IX Subsection "I use Solaris 9 and it doesn't compile/work/etc."
771Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst
772problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem.
773.Sh "How can I use rxvt-unicode under cygwin?"
774.IX Subsection "How can I use rxvt-unicode under cygwin?"
775rxvt-unicode should compile and run out of the box on cygwin, using
776the X11 libraries that come with cygwin. libW11 emulation is no
777longer supported (and makes no sense, either, as it only supported a
778single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or
779\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the
780old libW11 emulation.
781.PP
782At the time of this writing, cygwin didn't seem to support any multi-byte
783encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited
784to 8\-bit encodings.
478.IP "How does rxvt-unicode determine the encoding to use?" 4 785.Sh "How does rxvt-unicode determine the encoding to use?"
479.IX Item "How does rxvt-unicode determine the encoding to use?" 786.IX Subsection "How does rxvt-unicode determine the encoding to use?"
480.PD 0 787See next entry.
481.IP "Is there an option to switch encodings?" 4 788.Sh "Is there an option to switch encodings?"
482.IX Item "Is there an option to switch encodings?" 789.IX Subsection "Is there an option to switch encodings?"
483.PD
484Unlike some other terminals, rxvt-unicode has no encoding switch, and no 790Unlike some other terminals, rxvt-unicode has no encoding switch, and no
485specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about 791specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about
486\&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O. 792\&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O.
487.Sp 793.PP
488The reasons is that there exists a perfectly fine mechanism for selecting 794The reasons is that there exists a perfectly fine mechanism for selecting
489the encoding, doing I/O and (most important) communicating this to all 795the encoding, doing I/O and (most important) communicating this to all
490applications so everybody agrees on character properties such as width 796applications so everybody agrees on character properties such as width
491and code number. This mechanism is the \fIlocale\fR. Applications not using 797and code number. This mechanism is the \fIlocale\fR. Applications not using
492that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of 798that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of
493characters wrong as it uses it's own, locale-independent table under all 799characters wrong as it uses it's own, locale-independent table under all
494locales). 800locales).
495.Sp 801.PP
496Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All 802Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All
497programs doing the same (that is, most) will automatically agree in the 803programs doing the same (that is, most) will automatically agree in the
498interpretation of characters. 804interpretation of characters.
499.Sp 805.PP
500Unfortunately, there is no system-independent way to select locales, nor 806Unfortunately, there is no system-independent way to select locales, nor
501is there a standard on how locale specifiers will look like. 807is there a standard on how locale specifiers will look like.
502.Sp 808.PP
503On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable 809On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable
504contains an arbitrary string which corresponds to an already-installed 810contains an arbitrary string which corresponds to an already-installed
505locale. Common names for locales are \f(CW\*(C`en_US.UTF\-8\*(C'\fR, \f(CW\*(C`de_DE.ISO\-8859\-15\*(C'\fR, 811locale. Common names for locales are \f(CW\*(C`en_US.UTF\-8\*(C'\fR, \f(CW\*(C`de_DE.ISO\-8859\-15\*(C'\fR,
506\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms 812\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms
507(i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common. 813(i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common.
508.Sp 814.PP
509Rxvt-unicode ignores all other locale categories, and except for 815Rxvt-unicode ignores all other locale categories, and except for
510the encoding, ignores country or language-specific settings, 816the encoding, ignores country or language-specific settings,
511i.e. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR and \f(CW\*(C`ja_JP.UTF\-8\*(C'\fR are the normally same to 817i.e. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR and \f(CW\*(C`ja_JP.UTF\-8\*(C'\fR are the normally same to
512rxvt\-unicode. 818rxvt\-unicode.
513.Sp 819.PP
514If you want to use a specific encoding you have to make sure you start 820If you want to use a specific encoding you have to make sure you start
515rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category. 821rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category.
516.IP "Can I switch locales at runtime?" 4 822.Sh "Can I switch locales at runtime?"
517.IX Item "Can I switch locales at runtime?" 823.IX Subsection "Can I switch locales at runtime?"
518Yes, using an escape sequence. Try something like this, which sets 824Yes, using an escape sequence. Try something like this, which sets
519rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR. 825rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR.
520.Sp 826.PP
521.Vb 1 827.Vb 1
522\& printf '\ee]701;%s\e007' ja_JP.SJIS 828\& printf '\ee]701;%s\e007' ja_JP.SJIS
523.Ve 829.Ve
524.Sp 830.PP
525See also the previous answer. 831See also the previous answer.
526.Sp 832.PP
527Sometimes this capability is rather handy when you want to work in 833Sometimes this capability is rather handy when you want to work in
528one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it 834one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it
529(e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which 835(e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which
530first switches to a locale supported by xjdic and back later: 836first switches to a locale supported by xjdic and back later:
531.Sp 837.PP
532.Vb 3 838.Vb 3
533\& printf '\ee]701;%s\e007' ja_JP.SJIS 839\& printf '\ee]701;%s\e007' ja_JP.SJIS
534\& xjdic -js 840\& xjdic -js
535\& printf '\ee]701;%s\e007' de_DE.UTF-8 841\& printf '\ee]701;%s\e007' de_DE.UTF-8
536.Ve 842.Ve
537.Sp 843.PP
538You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except 844You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except
539for some locales where character width differs between program\- and 845for some locales where character width differs between program\- and
540rxvt\-unicode\-locales. 846rxvt\-unicode\-locales.
541.IP "Can I switch the fonts at runtime?" 4 847.Sh "Can I switch the fonts at runtime?"
542.IX Item "Can I switch the fonts at runtime?" 848.IX Subsection "Can I switch the fonts at runtime?"
543Yes, using an escape sequence. Try something like this, which has the same 849Yes, using an escape sequence. Try something like this, which has the same
544effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately: 850effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately:
545.Sp 851.PP
546.Vb 1 852.Vb 1
547\& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic" 853\& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic"
548.Ve 854.Ve
549.Sp 855.PP
550This is useful if you e.g. work primarily with japanese (and prefer a 856This is useful if you e.g. work primarily with japanese (and prefer a
551japanese font), but you have to switch to chinese temporarily, where 857japanese font), but you have to switch to chinese temporarily, where
552japanese fonts would only be in your way. 858japanese fonts would only be in your way.
553.Sp 859.PP
554You can think of this as a kind of manual \s-1ISO\-2022\s0 switching. 860You can think of this as a kind of manual \s-1ISO\-2022\s0 switching.
555.IP "Why do italic characters look as if clipped?" 4 861.Sh "Why do italic characters look as if clipped?"
556.IX Item "Why do italic characters look as if clipped?" 862.IX Subsection "Why do italic characters look as if clipped?"
557Many fonts have difficulties with italic characters and hinting. For 863Many fonts have difficulties with italic characters and hinting. For
558example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans 864example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans
559Mono\*(C'\fR completely fails in it's italic face. A workaround might be to 865Mono\*(C'\fR completely fails in it's italic face. A workaround might be to
560enable freetype autohinting, i.e. like this: 866enable freetype autohinting, i.e. like this:
561.Sp 867.PP
562.Vb 2 868.Vb 2
563\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 869\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
564\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 870\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
565.Ve 871.Ve
566.IP "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?" 4 872.Sh "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?"
567.IX Item "My input method wants <some encoding> but I want UTF-8, what can I do?" 873.IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?"
568You can specify separate locales for the input method and the rest of the 874You can specify separate locales for the input method and the rest of the
569terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR: 875terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
570.Sp 876.PP
571.Vb 1 877.Vb 1
572\& URxvt*imlocale: ja_JP.EUC-JP 878\& URxvt.imlocale: ja_JP.EUC-JP
573.Ve 879.Ve
574.Sp 880.PP
575Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still 881Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still
576use your input method. Please note, however, that you will not be able to 882use your input method. Please note, however, that you will not be able to
577input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input 883input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input
578method limits you. 884method limits you.
579.IP "Rxvt-unicode crashes when the X Input Method changes or exits." 4 885.Sh "Rxvt-unicode crashes when the X Input Method changes or exits."
580.IX Item "Rxvt-unicode crashes when the X Input Method changes or exits." 886.IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits."
581Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by 887Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by
582design. Applications can avoid some crashes at the expense of memory 888design. Applications can avoid some crashes at the expense of memory
583leaks, and Input Methods can avoid some crashes by careful ordering at 889leaks, and Input Methods can avoid some crashes by careful ordering at
584exit time. \fBkinput2\fR (and derived input methods) generally succeeds, 890exit time. \fBkinput2\fR (and derived input methods) generally succeeds,
585while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however, 891while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however,
586crashes cannot be completely avoided even if both sides cooperate. 892crashes cannot be completely avoided even if both sides cooperate.
587.Sp 893.PP
588So the only workaround is not to kill your Input Method Servers. 894So the only workaround is not to kill your Input Method Servers.
589.IP "Rxvt-unicode uses gobs of memory, how can I reduce that?" 4 895.Sh "Rxvt-unicode uses gobs of memory, how can I reduce that?"
590.IX Item "Rxvt-unicode uses gobs of memory, how can I reduce that?" 896.IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?"
591Rxvt-unicode tries to obey the rule of not charging you for something you 897Rxvt-unicode tries to obey the rule of not charging you for something you
592don't use. One thing you should try is to configure out all settings that 898don't use. One thing you should try is to configure out all settings that
593you don't need, for example, Xft support is a resource hog by design, 899you don't need, for example, Xft support is a resource hog by design,
594when used. Compiling it out ensures that no Xft font will be loaded 900when used. Compiling it out ensures that no Xft font will be loaded
595accidentally when rxvt-unicode tries to find a font for your characters. 901accidentally when rxvt-unicode tries to find a font for your characters.
596.Sp 902.PP
597Also, many people (me included) like large windows and even larger 903Also, many people (me included) like large windows and even larger
598scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use 904scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use
5996 bytes per screen cell. For a 160x?? window this amounts to almost a 9056 bytes per screen cell. For a 160x?? window this amounts to almost a
600kilobyte per line. A scrollback buffer of 10000 lines will then (if full) 906kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
601use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as 907use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as
602rxvt-unicode then uses 8 bytes per screen cell. 908rxvt-unicode then uses 8 bytes per screen cell.
603.IP "Can I speed up Xft rendering somehow?" 4 909.Sh "Can I speed up Xft rendering somehow?"
604.IX Item "Can I speed up Xft rendering somehow?" 910.IX Subsection "Can I speed up Xft rendering somehow?"
605Yes, the most obvious way to speed it up is to avoid Xft entirely, as 911Yes, the most obvious way to speed it up is to avoid Xft entirely, as
606it is simply slow. If you still want Xft fonts you might try to disable 912it is simply slow. If you still want Xft fonts you might try to disable
607antialiasing (by appending \f(CW\*(C`:antialiasing=false\*(C'\fR), which saves lots of 913antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of
608memory and also speeds up rendering considerably. 914memory and also speeds up rendering considerably.
609.IP "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 4 915.Sh "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
610.IX Item "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 916.IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
611Rxvt-unicode will use whatever you specify as a font. If it needs to 917Rxvt-unicode will use whatever you specify as a font. If it needs to
612fall back to it's default font search list it will prefer X11 core 918fall back to it's default font search list it will prefer X11 core
613fonts, because they are small and fast, and then use Xft fonts. It has 919fonts, because they are small and fast, and then use Xft fonts. It has
614antialiasing disabled for most of them, because the author thinks they 920antialiasing disabled for most of them, because the author thinks they
615look best that way. 921look best that way.
616.Sp 922.PP
617If you want antialiasing, you have to specify the fonts manually. 923If you want antialiasing, you have to specify the fonts manually.
618.IP "Mouse cut/paste suddenly no longer works." 4 924.Sh "Mouse cut/paste suddenly no longer works."
619.IX Item "Mouse cut/paste suddenly no longer works." 925.IX Subsection "Mouse cut/paste suddenly no longer works."
620Make sure that mouse reporting is actually turned off since killing 926Make sure that mouse reporting is actually turned off since killing
621some editors prematurely may leave the mouse in mouse report mode. I've 927some editors prematurely may leave the mouse in mouse report mode. I've
622heard that tcsh may use mouse reporting unless it otherwise specified. A 928heard that tcsh may use mouse reporting unless it otherwise specified. A
623quick check is to see if cut/paste works when the Alt or Shift keys are 929quick check is to see if cut/paste works when the Alt or Shift keys are
624depressed. See @@RXVT_NAME@@(7) 930depressed.
625.IP "What's with this bold/blink stuff?" 4 931.Sh "What's with this bold/blink stuff?"
626.IX Item "What's with this bold/blink stuff?" 932.IX Subsection "What's with this bold/blink stuff?"
627If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the 933If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the
628standard foreground colour. 934standard foreground colour.
629.Sp 935.PP
630For the standard background colour, blinking will actually make the 936For the standard background colour, blinking will actually make the
631text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard 937text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard
632colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be 938colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be
633ignored. 939ignored.
634.Sp 940.PP
635On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity 941On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity
636foreground/background colors. 942foreground/background colors.
637.Sp 943.PP
638color0\-7 are the low-intensity colors. 944color0\-7 are the low-intensity colors.
639.Sp 945.PP
640color8\-15 are the corresponding high-intensity colors. 946color8\-15 are the corresponding high-intensity colors.
641.IP "I don't like the screen colors. How do I change them?" 4 947.Sh "I don't like the screen colors. How do I change them?"
642.IX Item "I don't like the screen colors. How do I change them?" 948.IX Subsection "I don't like the screen colors. How do I change them?"
643You can change the screen colors at run-time using \fI~/.Xdefaults\fR 949You can change the screen colors at run-time using \fI~/.Xdefaults\fR
644resources (or as long\-options). 950resources (or as long\-options).
645.Sp 951.PP
646Here are values that are supposed to resemble a \s-1VGA\s0 screen, 952Here are values that are supposed to resemble a \s-1VGA\s0 screen,
647including the murky brown that passes for low-intensity yellow: 953including the murky brown that passes for low-intensity yellow:
648.Sp 954.PP
649.Vb 8 955.Vb 8
650\& URxvt.color0: #000000 956\& URxvt.color0: #000000
651\& URxvt.color1: #A80000 957\& URxvt.color1: #A80000
652\& URxvt.color2: #00A800 958\& URxvt.color2: #00A800
653\& URxvt.color3: #A8A800 959\& URxvt.color3: #A8A800
654\& URxvt.color4: #0000A8 960\& URxvt.color4: #0000A8
655\& URxvt.color5: #A800A8 961\& URxvt.color5: #A800A8
656\& URxvt.color6: #00A8A8 962\& URxvt.color6: #00A8A8
657\& URxvt.color7: #A8A8A8 963\& URxvt.color7: #A8A8A8
658.Ve 964.Ve
659.Sp 965.PP
660.Vb 8 966.Vb 8
661\& URxvt.color8: #000054 967\& URxvt.color8: #000054
662\& URxvt.color9: #FF0054 968\& URxvt.color9: #FF0054
663\& URxvt.color10: #00FF54 969\& URxvt.color10: #00FF54
664\& URxvt.color11: #FFFF54 970\& URxvt.color11: #FFFF54
665\& URxvt.color12: #0000FF 971\& URxvt.color12: #0000FF
666\& URxvt.color13: #FF00FF 972\& URxvt.color13: #FF00FF
667\& URxvt.color14: #00FFFF 973\& URxvt.color14: #00FFFF
668\& URxvt.color15: #FFFFFF 974\& URxvt.color15: #FFFFFF
669.Ve 975.Ve
670.Sp 976.PP
671And here is a more complete set of non-standard colors described (not by 977And here is a more complete set of non-standard colors described (not by
672me) as \*(L"pretty girly\*(R". 978me) as \*(L"pretty girly\*(R".
673.Sp 979.PP
674.Vb 18 980.Vb 18
675\& URxvt.cursorColor: #dc74d1 981\& URxvt.cursorColor: #dc74d1
676\& URxvt.pointerColor: #dc74d1 982\& URxvt.pointerColor: #dc74d1
677\& URxvt.background: #0e0e0e 983\& URxvt.background: #0e0e0e
678\& URxvt.foreground: #4ad5e1 984\& URxvt.foreground: #4ad5e1
689\& URxvt.color6: #73f7ff 995\& URxvt.color6: #73f7ff
690\& URxvt.color14: #73f7ff 996\& URxvt.color14: #73f7ff
691\& URxvt.color7: #e1dddd 997\& URxvt.color7: #e1dddd
692\& URxvt.color15: #e1dddd 998\& URxvt.color15: #e1dddd
693.Ve 999.Ve
694.IP "How can I start @@RXVT_NAME@@d in a race-free way?" 4 1000.Sh "How can I start @@RXVT_NAME@@d in a race-free way?"
695.IX Item "How can I start @@RXVT_NAME@@d in a race-free way?" 1001.IX Subsection "How can I start @@RXVT_NAME@@d in a race-free way?"
696Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a 1002Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the
697server that answers @@RXVT_NAME@@c's requests, so it doesn't background 1003display, create the listening socket and then fork.
698itself.
699.Sp
700To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the
701following method to wait for the startup message before continuing:
702.Sp
703.Vb 1
704\& { @@RXVT_NAME@@d & } | read
705.Ve
706.IP "What's with the strange Backspace/Delete key behaviour?" 4 1004.Sh "What's with the strange Backspace/Delete key behaviour?"
707.IX Item "What's with the strange Backspace/Delete key behaviour?" 1005.IX Subsection "What's with the strange Backspace/Delete key behaviour?"
708Assuming that the physical Backspace key corresponds to the 1006Assuming that the physical Backspace key corresponds to the
709BackSpace keysym (not likely for Linux ... see the following 1007BackSpace keysym (not likely for Linux ... see the following
710question) there are two standard values that can be used for 1008question) there are two standard values that can be used for
711Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR. 1009Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR.
712.Sp 1010.PP
713Historically, either value is correct, but rxvt-unicode adopts the debian 1011Historically, either value is correct, but rxvt-unicode adopts the debian
714policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct 1012policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct
715choice :). 1013choice :).
716.Sp 1014.PP
717Rxvt-unicode tries to inherit the current stty settings and uses the value 1015Rxvt-unicode tries to inherit the current stty settings and uses the value
718of `erase' to guess the value for backspace. If rxvt-unicode wasn't 1016of `erase' to guess the value for backspace. If rxvt-unicode wasn't
719started from a terminal (say, from a menu or by remote shell), then the 1017started from a terminal (say, from a menu or by remote shell), then the
720system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will 1018system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will
721be used (which may not be the same as your stty setting). 1019be used (which may not be the same as your stty setting).
722.Sp 1020.PP
723For starting a new rxvt\-unicode: 1021For starting a new rxvt\-unicode:
724.Sp 1022.PP
725.Vb 3 1023.Vb 3
726\& # use Backspace = ^H 1024\& # use Backspace = ^H
727\& $ stty erase ^H 1025\& $ stty erase ^H
728\& $ @@RXVT_NAME@@ 1026\& $ @@RXVT_NAME@@
729.Ve 1027.Ve
730.Sp 1028.PP
731.Vb 3 1029.Vb 3
732\& # use Backspace = ^? 1030\& # use Backspace = ^?
733\& $ stty erase ^? 1031\& $ stty erase ^?
734\& $ @@RXVT_NAME@@ 1032\& $ @@RXVT_NAME@@
735.Ve 1033.Ve
736.Sp 1034.PP
737Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR as documented in @@RXVT_NAME@@(7). 1035Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR.
738.Sp 1036.PP
739For an existing rxvt\-unicode: 1037For an existing rxvt\-unicode:
740.Sp 1038.PP
741.Vb 3 1039.Vb 3
742\& # use Backspace = ^H 1040\& # use Backspace = ^H
743\& $ stty erase ^H 1041\& $ stty erase ^H
744\& $ echo -n "^[[36h" 1042\& $ echo -n "^[[36h"
745.Ve 1043.Ve
746.Sp 1044.PP
747.Vb 3 1045.Vb 3
748\& # use Backspace = ^? 1046\& # use Backspace = ^?
749\& $ stty erase ^? 1047\& $ stty erase ^?
750\& $ echo -n "^[[36l" 1048\& $ echo -n "^[[36l"
751.Ve 1049.Ve
752.Sp 1050.PP
753This helps satisfy some of the Backspace discrepancies that occur, but 1051This helps satisfy some of the Backspace discrepancies that occur, but
754if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value 1052if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value
755properly reflects that. 1053properly reflects that.
756.Sp 1054.PP
757The Delete key is a another casualty of the ill-defined Backspace problem. 1055The Delete key is a another casualty of the ill-defined Backspace problem.
758To avoid confusion between the Backspace and Delete keys, the Delete 1056To avoid confusion between the Backspace and Delete keys, the Delete
759key has been assigned an escape sequence to match the vt100 for Execute 1057key has been assigned an escape sequence to match the vt100 for Execute
760(\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo. 1058(\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo.
761.Sp 1059.PP
762Some other Backspace problems: 1060Some other Backspace problems:
763.Sp 1061.PP
764some editors use termcap/terminfo, 1062some editors use termcap/terminfo,
765some editors (vim I'm told) expect Backspace = ^H, 1063some editors (vim I'm told) expect Backspace = ^H,
766\&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help. 1064\&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help.
767.Sp 1065.PP
768Perhaps someday this will all be resolved in a consistent manner. 1066Perhaps someday this will all be resolved in a consistent manner.
769.IP "I don't like the key\-bindings. How do I change them?" 4 1067.Sh "I don't like the key\-bindings. How do I change them?"
770.IX Item "I don't like the key-bindings. How do I change them?" 1068.IX Subsection "I don't like the key-bindings. How do I change them?"
771There are some compile-time selections available via configure. Unless 1069There are some compile-time selections available via configure. Unless
772you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can 1070you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can
773use the `keysym' resource to alter the keystrings associated with keysyms. 1071use the `keysym' resource to alter the keystrings associated with keysyms.
774.Sp 1072.PP
775Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR 1073Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR
776.Sp 1074.PP
777.Vb 20 1075.Vb 20
778\& URxvt.keysym.Home: \e033[1~ 1076\& URxvt.keysym.Home: \e033[1~
779\& URxvt.keysym.End: \e033[4~ 1077\& URxvt.keysym.End: \e033[4~
780\& URxvt.keysym.C-apostrophe: \e033<C-'> 1078\& URxvt.keysym.C-apostrophe: \e033<C-'>
781\& URxvt.keysym.C-slash: \e033<C-/> 1079\& URxvt.keysym.C-slash: \e033<C-/>
794\& URxvt.keysym.M-Right: \e033<M-Right> 1092\& URxvt.keysym.M-Right: \e033<M-Right>
795\& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 > 1093\& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 >
796\& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz > 1094\& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz >
797\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007 1095\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007
798.Ve 1096.Ve
799.Sp 1097.PP
800See some more examples in the documentation for the \fBkeysym\fR resource. 1098See some more examples in the documentation for the \fBkeysym\fR resource.
801.IP "I'm using keyboard model \s-1XXX\s0 that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize." 4 1099.Sh "I'm using keyboard model \s-1XXX\s0 that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize."
802.IX Item "I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize." 1100.IX Subsection "I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize."
803.Vb 6 1101.Vb 6
804\& KP_Insert == Insert 1102\& KP_Insert == Insert
805\& F22 == Print 1103\& F22 == Print
806\& F27 == Home 1104\& F27 == Home
807\& F29 == Prior 1105\& F29 == Prior
808\& F33 == End 1106\& F33 == End
809\& F35 == Next 1107\& F35 == Next
810.Ve 1108.Ve
811.Sp 1109.PP
812Rather than have rxvt-unicode try to accommodate all the various possible 1110Rather than have rxvt-unicode try to accommodate all the various possible
813keyboard mappings, it is better to use `xmodmap' to remap the keys as 1111keyboard mappings, it is better to use `xmodmap' to remap the keys as
814required for your particular machine. 1112required for your particular machine.
815.IP "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." 4 1113.Sh "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
816.IX Item "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." 1114.IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
817rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can 1115rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can
818check and see if that is set. Note that several programs, \s-1JED\s0, slrn, 1116check and see if that is set. Note that several programs, \s-1JED\s0, slrn,
819Midnight Commander automatically check this variable to decide whether or 1117Midnight Commander automatically check this variable to decide whether or
820not to use color. 1118not to use color.
821.IP "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?" 4 1119.Sh "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?"
822.IX Item "How do I set the correct, full IP address for the DISPLAY variable?" 1120.IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?"
823If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled 1121If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled
824insecure mode then it is possible to use the following shell script 1122insecure mode then it is possible to use the following shell script
825snippets to correctly set the display. If your version of rxvt-unicode 1123snippets to correctly set the display. If your version of rxvt-unicode
826wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then 1124wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then
827the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a 1125the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a
828regular xterm. 1126regular xterm.
829.Sp 1127.PP
830Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script 1128Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
831snippets: 1129snippets:
832.Sp 1130.PP
833.Vb 12 1131.Vb 12
834\& # Bourne/Korn/POSIX family of shells: 1132\& # Bourne/Korn/POSIX family of shells:
835\& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know 1133\& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
836\& if [ ${TERM:-foo} = xterm ]; then 1134\& if [ ${TERM:-foo} = xterm ]; then
837\& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not 1135\& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
842\& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string 1140\& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
843\& read DISPLAY # set it in our local shell 1141\& read DISPLAY # set it in our local shell
844\& fi 1142\& fi
845\& fi 1143\& fi
846.Ve 1144.Ve
847.IP "How do I compile the manual pages for myself?" 4 1145.Sh "How do I compile the manual pages for myself?"
848.IX Item "How do I compile the manual pages for myself?" 1146.IX Subsection "How do I compile the manual pages for myself?"
849You need to have a recent version of perl installed as \fI/usr/bin/perl\fR, 1147You need to have a recent version of perl installed as \fI/usr/bin/perl\fR,
850one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to 1148one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to
851the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR. 1149the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR.
852.IP "My question isn't answered here, can I ask a human?" 4 1150.Sh "My question isn't answered here, can I ask a human?"
853.IX Item "My question isn't answered here, can I ask a human?" 1151.IX Subsection "My question isn't answered here, can I ask a human?"
854Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR, 1152Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR,
855channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be 1153channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be
856interested in learning about new and exciting problems (but not FAQs :). 1154interested in learning about new and exciting problems (but not FAQs :).
857.SH "RXVT TECHNICAL REFERENCE" 1155.SH "RXVT TECHNICAL REFERENCE"
858.IX Header "RXVT TECHNICAL REFERENCE" 1156.IX Header "RXVT TECHNICAL REFERENCE"
859.SH "DESCRIPTION" 1157.SH "DESCRIPTION"
860.IX Header "DESCRIPTION" 1158.IX Header "DESCRIPTION"
861The rest of this document describes various technical aspects of 1159The rest of this document describes various technical aspects of
862\&\fBrxvt-unicode\fR. First the description of supported command sequences, 1160\&\fBrxvt-unicode\fR. First the description of supported command sequences,
863followed by menu and pixmap support and last by a description of all 1161followed by pixmap support and last by a description of all features
864features selectable at \f(CW\*(C`configure\*(C'\fR time. 1162selectable at \f(CW\*(C`configure\*(C'\fR time.
865.SH "Definitions" 1163.SH "Definitions"
866.IX Header "Definitions" 1164.IX Header "Definitions"
867.ie n .IP "\fB\fB""c""\fB\fR" 4 1165.ie n .IP "\fB\fB""c""\fB\fR" 4
868.el .IP "\fB\f(CBc\fB\fR" 4 1166.el .IP "\fB\f(CBc\fB\fR" 4
869.IX Item "c" 1167.IX Item "c"
1416l l . 1714l l .
1417h Send Mouse X & Y on button press. 1715h Send Mouse X & Y on button press.
1418l No mouse reporting. 1716l No mouse reporting.
1419.TE 1717.TE
1420 1718
1421.ie n .IP "\fB\fB""Ps = 10""\fB\fR (\fBrxvt\fR)" 4
1422.el .IP "\fB\f(CBPs = 10\fB\fR (\fBrxvt\fR)" 4
1423.IX Item "Ps = 10 (rxvt)"
1424.TS
1425l l .
1426h menuBar visible
1427l menuBar invisible
1428.TE
1429
1430.ie n .IP "\fB\fB""Ps = 25""\fB\fR" 4 1719.ie n .IP "\fB\fB""Ps = 25""\fB\fR" 4
1431.el .IP "\fB\f(CBPs = 25\fB\fR" 4 1720.el .IP "\fB\f(CBPs = 25\fB\fR" 4
1432.IX Item "Ps = 25" 1721.IX Item "Ps = 25"
1433.TS 1722.TS
1434l l . 1723l l .
1553.IX Item "Ps = 1011 (rxvt)" 1842.IX Item "Ps = 1011 (rxvt)"
1554.TS 1843.TS
1555l l . 1844l l .
1556h Scroll to bottom when a key is pressed 1845h Scroll to bottom when a key is pressed
1557l Don't scroll to bottom when a key is pressed 1846l Don't scroll to bottom when a key is pressed
1847.TE
1848
1849.ie n .IP "\fB\fB""Ps = 1021""\fB\fR (\fBrxvt\fR)" 4
1850.el .IP "\fB\f(CBPs = 1021\fB\fR (\fBrxvt\fR)" 4
1851.IX Item "Ps = 1021 (rxvt)"
1852.TS
1853l l .
1854h Bold/italic implies high intensity (see option -is)
1855l Font styles have no effect on intensity (Compile styles)
1558.TE 1856.TE
1559 1857
1560.ie n .IP "\fB\fB""Ps = 1047""\fB\fR" 4 1858.ie n .IP "\fB\fB""Ps = 1047""\fB\fR" 4
1561.el .IP "\fB\f(CBPs = 1047\fB\fR" 4 1859.el .IP "\fB\f(CBPs = 1047\fB\fR" 4
1562.IX Item "Ps = 1047" 1860.IX Item "Ps = 1047"
1609Ps = 10 Change colour of text foreground to Pt (NB: may change in future) 1907Ps = 10 Change colour of text foreground to Pt (NB: may change in future)
1610Ps = 11 Change colour of text background to Pt (NB: may change in future) 1908Ps = 11 Change colour of text background to Pt (NB: may change in future)
1611Ps = 12 Change colour of text cursor foreground to Pt 1909Ps = 12 Change colour of text cursor foreground to Pt
1612Ps = 13 Change colour of mouse foreground to Pt 1910Ps = 13 Change colour of mouse foreground to Pt
1613Ps = 17 Change colour of highlight characters to Pt 1911Ps = 17 Change colour of highlight characters to Pt
1614Ps = 18 Change colour of bold characters to Pt 1912Ps = 18 Change colour of bold characters to Pt [deprecated, see 706]
1615Ps = 19 Change colour of underlined characters to Pt 1913Ps = 19 Change colour of underlined characters to Pt [deprecated, see 707]
1616Ps = 20 Change default background to Pt 1914Ps = 20 Change background pixmap parameters (see section XPM) (Compile XPM).
1617Ps = 39 Change default foreground colour to Pt rxvt compile-time option 1915Ps = 39 Change default foreground colour to Pt.
1618Ps = 46 Change Log File to Pt unimplemented 1916Ps = 46 Change Log File to Pt unimplemented
1619Ps = 49 Change default background colour to Pt rxvt compile-time option 1917Ps = 49 Change default background colour to Pt.
1620Ps = 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 1918Ps = 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
1621Ps = 55 Log all scrollback buffer and all of screen to Pt 1919Ps = 55 Log all scrollback buffer and all of screen to Pt
1622Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (@@RXVT_NAME@@ extension) 1920Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).
1623Ps = 703 Menubar command Pt rxvt compile-time option (rxvt-unicode extension) 1921Ps = 702 Request 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.
1624Ps = 704 Change colour of italic characters to Pt 1922Ps = 704 Change colour of italic characters to Pt
1625Ps = 705 Change background pixmap tint colour to Pt 1923Ps = 705 Change background pixmap tint colour to Pt (Compile transparency).
1924Ps = 706 Change colour of bold characters to Pt
1925Ps = 707 Change colour of underlined characters to Pt
1626Ps = 710 Set normal fontset to Pt. Same as Ps = 50. 1926Ps = 710 Set normal fontset to Pt. Same as Ps = 50.
1627Ps = 711 Set bold fontset to Pt. Similar to Ps = 50. 1927Ps = 711 Set bold fontset to Pt. Similar to Ps = 50 (Compile styles).
1628Ps = 712 Set italic fontset to Pt. Similar to Ps = 50. 1928Ps = 712 Set italic fontset to Pt. Similar to Ps = 50 (Compile styles).
1629Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50. 1929Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles).
1930Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1931Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1932Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).
1630.TE 1933.TE
1631 1934
1632.PP 1935.PP
1633 1936
1634.IX Xref "menuBar" 1937.IX Xref "XPM"
1635.SH "menuBar"
1636.IX Header "menuBar"
1637\&\fBThe exact syntax used is \f(BIalmost\fB solidified.\fR
1638In the menus, \fB\s-1DON\s0'T\fR try to use menuBar commands that add or remove a
1639menuBar.
1640.PP
1641Note that in all of the commands, the \fB\f(BI/path/\fB\fR \fIcannot\fR be
1642omitted: use \fB./\fR to specify a menu relative to the current menu.
1643.Sh "Overview of menuBar operation"
1644.IX Subsection "Overview of menuBar operation"
1645For the menuBar XTerm escape sequence \f(CW\*(C`ESC ] 703 ; Pt ST\*(C'\fR, the syntax
1646of \f(CW\*(C`Pt\*(C'\fR can be used for a variety of tasks:
1647.PP
1648At the top level is the current menuBar which is a member of a circular
1649linked-list of other such menuBars.
1650.PP
1651The menuBar acts as a parent for the various drop-down menus, which in
1652turn, may have labels, separator lines, menuItems and subMenus.
1653.PP
1654The menuItems are the useful bits: you can use them to mimic keyboard
1655input or even to send text or escape sequences back to rxvt.
1656.PP
1657The menuBar syntax is intended to provide a simple yet robust method of
1658constructing and manipulating menus and navigating through the
1659menuBars.
1660.PP
1661The first step is to use the tag \fB[menu:\f(BIname\fB]\fR which creates
1662the menuBar called \fIname\fR and allows access. You may now or menus,
1663subMenus, and menuItems. Finally, use the tag \fB[done]\fR to set the
1664menuBar access as \fBreadonly\fR to prevent accidental corruption of the
1665menus. To re-access the current menuBar for alterations, use the tag
1666\&\fB[menu]\fR, make the alterations and then use \fB[done]\fR
1667.PP
1668
1669.IX Xref "menuBarCommands"
1670.Sh "Commands"
1671.IX Subsection "Commands"
1672.IP "\fB[menu:+\f(BIname\fB]\fR" 4
1673.IX Item "[menu:+name]"
1674access the named menuBar for creation or alteration. If a new menuBar
1675is created, it is called \fIname\fR (max of 15 chars) and the current
1676menuBar is pushed onto the stack
1677.IP "\fB[menu]\fR" 4
1678.IX Item "[menu]"
1679access the current menuBar for alteration
1680.IP "\fB[title:+\f(BIstring\fB]\fR" 4
1681.IX Item "[title:+string]"
1682set the current menuBar's title to \fIstring\fR, which may contain the
1683following format specifiers:
1684.Sp
1685.Vb 3
1686\& B<%n> rxvt name (as per the B<-name> command-line option)
1687\& B<%v> rxvt version
1688\& B<%%> literal B<%> character
1689.Ve
1690.IP "\fB[done]\fR" 4
1691.IX Item "[done]"
1692set menuBar access as \fBreadonly\fR.
1693End-of-file tag for \fB[read:+\f(BIfile\fB]\fR operations.
1694.IP "\fB[read:+\f(BIfile\fB]\fR" 4
1695.IX Item "[read:+file]"
1696read menu commands directly from \fIfile\fR (extension \*(L".menu\*(R" will be
1697appended 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.
1698.Sp
1699Blank and comment lines (starting with \fB#\fR) are ignored. Actually,
1700since any invalid menu commands are also ignored, almost anything could
1701be construed as a comment line, but this may be tightened up in the
1702future ... so don't count on it!.
1703.IP "\fB[read:+\f(BIfile\fB;+\f(BIname\fB]\fR" 4
1704.IX Item "[read:+file;+name]"
1705The same as \fB[read:+\f(BIfile\fB]\fR, but start reading at a line with
1706\&\fB[menu:+\f(BIname\fB]\fR and continuing until \fB[done:+\f(BIname\fB]\fR or
1707\&\fB[done]\fR is encountered.
1708.IP "\fB[dump]\fR" 4
1709.IX Item "[dump]"
1710dump all menuBars to the file \fB/tmp/rxvt\-PID\fR in a format suitable for
1711later rereading.
1712.IP "\fB[rm:name]\fR" 4
1713.IX Item "[rm:name]"
1714remove the named menuBar
1715.IP "\fB[rm] [rm:]\fR" 4
1716.IX Item "[rm] [rm:]"
1717remove the current menuBar
1718.IP "\fB[rm*] [rm:*]\fR" 4
1719.IX Item "[rm*] [rm:*]"
1720remove all menuBars
1721.IP "\fB[swap]\fR" 4
1722.IX Item "[swap]"
1723swap the top two menuBars
1724.IP "\fB[prev]\fR" 4
1725.IX Item "[prev]"
1726access the previous menuBar
1727.IP "\fB[next]\fR" 4
1728.IX Item "[next]"
1729access the next menuBar
1730.IP "\fB[show]\fR" 4
1731.IX Item "[show]"
1732Enable display of the menuBar
1733.IP "\fB[hide]\fR" 4
1734.IX Item "[hide]"
1735Disable display of the menuBar
1736.IP "\fB[pixmap:+\f(BIname\fB]\fR" 4
1737.IX Item "[pixmap:+name]"
1738.PD 0
1739.IP "\fB[pixmap:+\f(BIname\fB;\f(BIscaling\fB]\fR" 4
1740.IX Item "[pixmap:+name;scaling]"
1741.PD
1742(set the background pixmap globally
1743.Sp
1744\&\fBA Future implementation \f(BImay\fB make this local to the menubar\fR)
1745.IP "\fB[:+\f(BIcommand\fB:]\fR" 4
1746.IX Item "[:+command:]"
1747ignore the menu readonly status and issue a \fIcommand\fR to or a menu or
1748menuitem or change the ; a useful shortcut for setting the quick arrows
1749from a menuBar.
1750.PP
1751
1752.IX Xref "menuBarAdd"
1753.Sh "Adding and accessing menus"
1754.IX Subsection "Adding and accessing menus"
1755The following commands may also be \fB+\fR prefixed.
1756.IP "\fB/+\fR" 4
1757.IX Item "/+"
1758access menuBar top level
1759.IP "\fB./+\fR" 4
1760.IX Item "./+"
1761access current menu level
1762.IP "\fB../+\fR" 4
1763.IX Item "../+"
1764access parent menu (1 level up)
1765.IP "\fB../../\fR" 4
1766.IX Item "../../"
1767access parent menu (multiple levels up)
1768.IP "\fB\f(BI/path/\fBmenu\fR" 4
1769.IX Item "/path/menu"
1770add/access menu
1771.IP "\fB\f(BI/path/\fBmenu/*\fR" 4
1772.IX Item "/path/menu/*"
1773add/access menu and clear it if it exists
1774.IP "\fB\f(BI/path/\fB{\-}\fR" 4
1775.IX Item "/path/{-}"
1776add separator
1777.IP "\fB\f(BI/path/\fB{item}\fR" 4
1778.IX Item "/path/{item}"
1779add \fBitem\fR as a label
1780.IP "\fB\f(BI/path/\fB{item} action\fR" 4
1781.IX Item "/path/{item} action"
1782add/alter \fImenuitem\fR with an associated \fIaction\fR
1783.IP "\fB\f(BI/path/\fB{item}{right\-text}\fR" 4
1784.IX Item "/path/{item}{right-text}"
1785add/alter \fImenuitem\fR with \fBright-text\fR as the right-justified text
1786and as the associated \fIaction\fR
1787.IP "\fB\f(BI/path/\fB{item}{rtext} action\fR" 4
1788.IX Item "/path/{item}{rtext} action"
1789add/alter \fImenuitem\fR with an associated \fIaction\fR and with \fBrtext\fR as
1790the right-justified text.
1791.IP "Special characters in \fIaction\fR must be backslash\-escaped:" 4
1792.IX Item "Special characters in action must be backslash-escaped:"
1793\&\fB\ea \eb \eE \ee \en \er \et \eoctal\fR
1794.IP "or in control-character notation:" 4
1795.IX Item "or in control-character notation:"
1796\&\fB^@, ^A .. ^Z .. ^_, ^?\fR
1797.PP
1798To send a string starting with a \fB\s-1NUL\s0\fR (\fB^@\fR) character to the
1799program, start \fIaction\fR with a pair of \fB\s-1NUL\s0\fR characters (\fB^@^@\fR),
1800the first of which will be stripped off and the balance directed to the
1801program. Otherwise if \fIaction\fR begins with \fB\s-1NUL\s0\fR followed by
1802non\-+\fB\s-1NUL\s0\fR characters, the leading \fB\s-1NUL\s0\fR is stripped off and the
1803balance is sent back to rxvt.
1804.PP
1805As a convenience for the many Emacs-type editors, \fIaction\fR may start
1806with \fBM\-\fR (eg, \fBM\-$\fR is equivalent to \fB\eE$\fR) and a \fB\s-1CR\s0\fR will be
1807appended if missed from \fBM\-x\fR commands.
1808.PP
1809As a convenience for issuing XTerm \fB\s-1ESC\s0 ]\fR sequences from a menubar (or
1810quick arrow), a \fB\s-1BEL\s0\fR (\fB^G\fR) will be appended if needed.
1811.IP "For example," 4
1812.IX Item "For example,"
1813\&\fBM\-xapropos\fR is equivalent to \fB\eExapropos\er\fR
1814.IP "and" 4
1815.IX Item "and"
1816\&\fB\eE]703;mona;100\fR is equivalent to \fB\eE]703;mona;100\ea\fR
1817.PP
1818The option \fB{\f(BIright-rtext\fB}\fR will be right\-justified. In the
1819absence of a specified action, this text will be used as the \fIaction\fR
1820as well.
1821.IP "For example," 4
1822.IX Item "For example,"
1823\&\fB/File/{Open}{^X^F}\fR is equivalent to \fB/File/{Open}{^X^F} ^X^F\fR
1824.PP
1825The left label \fIis\fR necessary, since it's used for matching, but
1826implicitly hiding the left label (by using same name for both left and
1827right labels), or explicitly hiding the left label (by preceeding it
1828with a dot), makes it possible to have right-justified text only.
1829.IP "For example," 4
1830.IX Item "For example,"
1831\&\fB/File/{Open}{Open} Open-File-Action\fR
1832.IP "or hiding it" 4
1833.IX Item "or hiding it"
1834\&\fB/File/{.anylabel}{Open} Open-File-Action\fR
1835.PP
1836
1837.IX Xref "menuBarRemove"
1838.Sh "Removing menus"
1839.IX Subsection "Removing menus"
1840.IP "\fB\-/*+\fR" 4
1841.IX Item "-/*+"
1842remove all menus from the menuBar, the same as \fB[clear]\fR
1843.IP "\fB\-+\f(BI/path\fBmenu+\fR" 4
1844.IX Item "-+/pathmenu+"
1845remove menu
1846.IP "\fB\-+\f(BI/path\fB{item}+\fR" 4
1847.IX Item "-+/path{item}+"
1848remove item
1849.IP "\fB\-+\f(BI/path\fB{\-}\fR" 4
1850.IX Item "-+/path{-}"
1851remove separator)
1852.IP "\fB\-/path/menu/*\fR" 4
1853.IX Item "-/path/menu/*"
1854remove all items, separators and submenus from menu
1855.PP
1856
1857.IX Xref "menuBarArrows"
1858.Sh "Quick Arrows"
1859.IX Subsection "Quick Arrows"
1860The menus also provide a hook for \fIquick arrows\fR to provide easier
1861user access. If nothing has been explicitly set, the default is to
1862emulate the curror keys. The syntax permits each arrow to be altered
1863individually or all four at once without re-entering their common
1864beginning/end text. For example, to explicitly associate cursor actions
1865with the arrows, any of the following forms could be used:
1866.IP "\fB<r>+\f(BIRight\fB\fR" 4
1867.IX Item "<r>+Right"
1868.PD 0
1869.IP "\fB<l>+\f(BILeft\fB\fR" 4
1870.IX Item "<l>+Left"
1871.IP "\fB<u>+\f(BIUp\fB\fR" 4
1872.IX Item "<u>+Up"
1873.IP "\fB<d>+\f(BIDown\fB\fR" 4
1874.IX Item "<d>+Down"
1875.PD
1876Define actions for the respective arrow buttons
1877.IP "\fB<b>+\f(BIBegin\fB\fR" 4
1878.IX Item "<b>+Begin"
1879.PD 0
1880.IP "\fB<e>+\f(BIEnd\fB\fR" 4
1881.IX Item "<e>+End"
1882.PD
1883Define common beginning/end parts for \fIquick arrows\fR which used in
1884conjunction with the above <r> <l> <u> <d> constructs
1885.IP "For example, define arrows individually," 4
1886.IX Item "For example, define arrows individually,"
1887.Vb 1
1888\& <u>\eE[A
1889.Ve
1890.Sp
1891.Vb 1
1892\& <d>\eE[B
1893.Ve
1894.Sp
1895.Vb 1
1896\& <r>\eE[C
1897.Ve
1898.Sp
1899.Vb 1
1900\& <l>\eE[D
1901.Ve
1902.IP "or all at once" 4
1903.IX Item "or all at once"
1904.Vb 1
1905\& <u>\eE[AZ<><d>\eE[BZ<><r>\eE[CZ<><l>\eE[D
1906.Ve
1907.IP "or more compactly (factoring out common parts)" 4
1908.IX Item "or more compactly (factoring out common parts)"
1909.Vb 1
1910\& <b>\eE[<u>AZ<><d>BZ<><r>CZ<><l>D
1911.Ve
1912.PP
1913
1914.IX Xref "menuBarSummary"
1915.Sh "Command Summary"
1916.IX Subsection "Command Summary"
1917A short summary of the most \fIcommon\fR commands:
1918.IP "[menu:name]" 4
1919.IX Item "[menu:name]"
1920use an existing named menuBar or start a new one
1921.IP "[menu]" 4
1922.IX Item "[menu]"
1923use the current menuBar
1924.IP "[title:string]" 4
1925.IX Item "[title:string]"
1926set menuBar title
1927.IP "[done]" 4
1928.IX Item "[done]"
1929set menu access to readonly and, if reading from a file, signal \s-1EOF\s0
1930.IP "[done:name]" 4
1931.IX Item "[done:name]"
1932if reading from a file using [read:file;name] signal \s-1EOF\s0
1933.IP "[rm:name]" 4
1934.IX Item "[rm:name]"
1935remove named menuBar(s)
1936.IP "[rm] [rm:]" 4
1937.IX Item "[rm] [rm:]"
1938remove current menuBar
1939.IP "[rm*] [rm:*]" 4
1940.IX Item "[rm*] [rm:*]"
1941remove all menuBar(s)
1942.IP "[swap]" 4
1943.IX Item "[swap]"
1944swap top two menuBars
1945.IP "[prev]" 4
1946.IX Item "[prev]"
1947access the previous menuBar
1948.IP "[next]" 4
1949.IX Item "[next]"
1950access the next menuBar
1951.IP "[show]" 4
1952.IX Item "[show]"
1953map menuBar
1954.IP "[hide]" 4
1955.IX Item "[hide]"
1956unmap menuBar
1957.IP "[pixmap;file]" 4
1958.IX Item "[pixmap;file]"
1959.PD 0
1960.IP "[pixmap;file;scaling]" 4
1961.IX Item "[pixmap;file;scaling]"
1962.PD
1963set a background pixmap
1964.IP "[read:file]" 4
1965.IX Item "[read:file]"
1966.PD 0
1967.IP "[read:file;name]" 4
1968.IX Item "[read:file;name]"
1969.PD
1970read in a menu from a file
1971.IP "[dump]" 4
1972.IX Item "[dump]"
1973dump out all menuBars to /tmp/rxvt\-PID
1974.IP "/" 4
1975access menuBar top level
1976.IP "./" 4
1977.PD 0
1978.IP "../" 4
1979.IP "../../" 4
1980.PD
1981access current or parent menu level
1982.IP "/path/menu" 4
1983.IX Item "/path/menu"
1984add/access menu
1985.IP "/path/{\-}" 4
1986.IX Item "/path/{-}"
1987add separator
1988.IP "/path/{item}{rtext} action" 4
1989.IX Item "/path/{item}{rtext} action"
1990add/alter menu item
1991.IP "\-/*" 4
1992remove all menus from the menuBar
1993.IP "\-/path/menu" 4
1994.IX Item "-/path/menu"
1995remove menu items, separators and submenus from menu
1996.IP "\-/path/menu" 4
1997.IX Item "-/path/menu"
1998remove menu
1999.IP "\-/path/{item}" 4
2000.IX Item "-/path/{item}"
2001remove item
2002.IP "\-/path/{\-}" 4
2003.IX Item "-/path/{-}"
2004remove separator
2005.IP "<b>Begin<r>Right<l>Left<u>Up<d>Down<e>End" 4
2006.IX Item "<b>Begin<r>Right<l>Left<u>Up<d>Down<e>End"
2007menu quick arrows
2008.SH "XPM" 1938.SH "XPM"
2009.IX Header "XPM" 1939.IX Header "XPM"
2010For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value 1940For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value
2011of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a 1941of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a
2012sequence of scaling/positioning commands separated by semi\-colons. The 1942sequence of scaling/positioning commands separated by semi\-colons. The
2162.TE 2092.TE
2163 2093
2164.SH "CONFIGURE OPTIONS" 2094.SH "CONFIGURE OPTIONS"
2165.IX Header "CONFIGURE OPTIONS" 2095.IX Header "CONFIGURE OPTIONS"
2166General hint: if you get compile errors, then likely your configuration 2096General hint: if you get compile errors, then likely your configuration
2167hasn't been tested well. Either try with \-\-enable\-everything or use the 2097hasn't been tested well. Either try with \f(CW\*(C`\-\-enable\-everything\*(C'\fR or use
2168\&./reconf script as a base for experiments. ./reconf is used by myself, 2098the \fI./reconf\fR script as a base for experiments. \fI./reconf\fR is used by
2169so it should generally be a working config. Of course, you should always 2099myself, so it should generally be a working config. Of course, you should
2170report when a combination doesn't work, so it can be fixed. Marc Lehmann 2100always report when a combination doesn't work, so it can be fixed. Marc
2171<rxvt@schmorp.de>. 2101Lehmann <rxvt@schmorp.de>.
2102.PP
2103All
2172.IP "\-\-enable\-everything" 4 2104.IP "\-\-enable\-everything" 4
2173.IX Item "--enable-everything" 2105.IX Item "--enable-everything"
2174Add support for all non-multichoice options listed in \*(L"./configure 2106Add (or remove) support for all non-multichoice options listed in \*(L"./configure
2175\&\-\-help\*(R". Note that unlike other enable options this is order dependant. 2107\&\-\-help\*(R".
2108.Sp
2176You can specify this and then disable options which this enables by 2109You can specify this and then disable options you do not like by
2177\&\fIfollowing\fR this with the appropriate commands. 2110\&\fIfollowing\fR this with the appropriate \f(CW\*(C`\-\-disable\-...\*(C'\fR arguments,
2178.IP "\-\-enable\-xft" 4 2111or you can start with a minimal configuration by specifying
2179.IX Item "--enable-xft" 2112\&\f(CW\*(C`\-\-disable\-everything\*(C'\fR and than adding just the \f(CW\*(C`\-\-enable\-...\*(C'\fR arguments
2113you want.
2114.IP "\-\-enable\-xft (default: enabled)" 4
2115.IX Item "--enable-xft (default: enabled)"
2180Add support for Xft (anti\-aliases, among others) fonts. Xft fonts are 2116Add support for Xft (anti\-aliases, among others) fonts. Xft fonts are
2181slower and require lots of memory, but as long as you don't use them, you 2117slower and require lots of memory, but as long as you don't use them, you
2182don't pay for them. 2118don't pay for them.
2183.IP "\-\-enable\-font\-styles" 4 2119.IP "\-\-enable\-font\-styles (default: on)" 4
2184.IX Item "--enable-font-styles" 2120.IX Item "--enable-font-styles (default: on)"
2185Add support for \fBbold\fR, \fIitalic\fR and \fB\f(BIbold italic\fB\fR font 2121Add support for \fBbold\fR, \fIitalic\fR and \fB\f(BIbold italic\fB\fR font
2186styles. The fonts can be set manually or automatically. 2122styles. The fonts can be set manually or automatically.
2187.IP "\-\-with\-codesets=NAME,..." 4 2123.IP "\-\-with\-codesets=NAME,... (default: all)" 4
2188.IX Item "--with-codesets=NAME,..." 2124.IX Item "--with-codesets=NAME,... (default: all)"
2189Compile in support for additional codeset (encoding) groups (eu, vn are 2125Compile in support for additional codeset (encoding) groups (\f(CW\*(C`eu\*(C'\fR, \f(CW\*(C`vn\*(C'\fR
2190always compiled in, which includes most 8\-bit character sets). These 2126are always compiled in, which includes most 8\-bit character sets). These
2191codeset tables are currently only used for driving X11 core fonts, they 2127codeset tables are used for driving X11 core fonts, they are not required
2192are not required for Xft fonts. Compiling them in will make your binary 2128for Xft fonts, although having them compiled in lets rxvt-unicode choose
2193bigger (together about 700kB), but it doesn't increase memory usage unless 2129replacement fonts more intelligently. Compiling them in will make your
2130binary bigger (all of together cost about 700kB), but it doesn't increase
2194you use an X11 font requiring one of these encodings. 2131memory usage unless you use a font requiring one of these encodings.
2195.TS 2132.TS
2196l l . 2133l l .
2197all all available codeset groups 2134all all available codeset groups
2198zh common chinese encodings 2135zh common chinese encodings
2199zh_ext rarely used but very big chinese encodigs 2136zh_ext rarely used but very big chinese encodigs
2200jp common japanese encodings 2137jp common japanese encodings
2201jp_ext rarely used but big japanese encodings 2138jp_ext rarely used but big japanese encodings
2202kr korean encodings 2139kr korean encodings
2203.TE 2140.TE
2204 2141
2205.IP "\-\-enable\-xim" 4 2142.IP "\-\-enable\-xim (default: on)" 4
2206.IX Item "--enable-xim" 2143.IX Item "--enable-xim (default: on)"
2207Add support for \s-1XIM\s0 (X Input Method) protocol. This allows using 2144Add support for \s-1XIM\s0 (X Input Method) protocol. This allows using
2208alternative input methods (e.g. kinput2) and will also correctly 2145alternative input methods (e.g. kinput2) and will also correctly
2209set up the input for people using dead keys or compose keys. 2146set up the input for people using dead keys or compose keys.
2210.IP "\-\-enable\-unicode3" 4 2147.IP "\-\-enable\-unicode3 (default: off)" 4
2211.IX Item "--enable-unicode3" 2148.IX Item "--enable-unicode3 (default: off)"
2149Recommended to stay off unless you really need non-BMP characters.
2150.Sp
2212Enable direct support for displaying unicode codepoints above 2151Enable direct support for displaying unicode codepoints above
221365535 (the basic multilingual page). This increases storage 215265535 (the basic multilingual page). This increases storage
2214requirements per character from 2 to 4 bytes. X11 fonts do not yet 2153requirements per character from 2 to 4 bytes. X11 fonts do not yet
2215support these extra characters, but Xft does. 2154support these extra characters, but Xft does.
2216.Sp 2155.Sp
2217Please note that rxvt-unicode can store unicode code points >65535 2156Please note that rxvt-unicode can store unicode code points >65535
2218even without this flag, but the number of such characters is 2157even without this flag, but the number of such characters is
2219limited to a view thousand (shared with combining characters, 2158limited to a view thousand (shared with combining characters,
2220see next switch), and right now rxvt-unicode cannot display them 2159see next switch), and right now rxvt-unicode cannot display them
2221(input/output and cut&paste still work, though). 2160(input/output and cut&paste still work, though).
2222.IP "\-\-enable\-combining" 4 2161.IP "\-\-enable\-combining (default: on)" 4
2223.IX Item "--enable-combining" 2162.IX Item "--enable-combining (default: on)"
2224Enable automatic composition of combining characters into 2163Enable automatic composition of combining characters into
2225composite characters. This is required for proper viewing of text 2164composite characters. This is required for proper viewing of text
2226where accents are encoded as seperate unicode characters. This is 2165where accents are encoded as seperate unicode characters. This is
2227done by using precomposited characters when available or creating 2166done by using precomposited characters when available or creating
2228new pseudo-characters when no precomposed form exists. 2167new pseudo-characters when no precomposed form exists.
2229.Sp 2168.Sp
2230Without \-\-enable\-unicode3, the number of additional precomposed characters 2169Without \-\-enable\-unicode3, the number of additional precomposed
2231is rather limited (2048, if this is full, rxvt-unicode will use the 2170characters is somewhat limited (the 6400 private use characters will be
2232private use area, extending the number of combinations to 8448). With
2233\&\-\-enable\-unicode3, no practical limit exists. 2171(ab\-)used). With \-\-enable\-unicode3, no practical limit exists.
2234.Sp 2172.Sp
2235This option will also enable storage (but not display) of characters 2173This option will also enable storage (but not display) of characters
2236beyond plane 0 (>65535) when \-\-enable\-unicode3 was not specified. 2174beyond plane 0 (>65535) when \-\-enable\-unicode3 was not specified.
2237.Sp 2175.Sp
2238The combining table also contains entries for arabic presentation forms, 2176The combining table also contains entries for arabic presentation forms,
2239but these are not currently used. Bug me if you want these to be used (and 2177but these are not currently used. Bug me if you want these to be used (and
2240tell me how these are to be used...). 2178tell me how these are to be used...).
2241.IP "\-\-enable\-fallback(=CLASS)" 4 2179.IP "\-\-enable\-fallback(=CLASS) (default: Rxvt)" 4
2242.IX Item "--enable-fallback(=CLASS)" 2180.IX Item "--enable-fallback(=CLASS) (default: Rxvt)"
2243When reading resource settings, also read settings for class \s-1CLASS\s0 2181When reading resource settings, also read settings for class \s-1CLASS\s0. To
2244(default: Rxvt). To disable resource fallback use \-\-disable\-fallback. 2182disable resource fallback use \-\-disable\-fallback.
2245.IP "\-\-with\-res\-name=NAME" 4 2183.IP "\-\-with\-res\-name=NAME (default: urxvt)" 4
2246.IX Item "--with-res-name=NAME" 2184.IX Item "--with-res-name=NAME (default: urxvt)"
2247Use the given name (default: urxvt) as default application name when 2185Use the given name as default application name when
2248reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt. 2186reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt.
2249.IP "\-\-with\-res\-class=CLASS" 4 2187.IP "\-\-with\-res\-class=CLASS /default: URxvt)" 4
2250.IX Item "--with-res-class=CLASS" 2188.IX Item "--with-res-class=CLASS /default: URxvt)"
2251Use the given class (default: URxvt) as default application class 2189Use the given class as default application class
2252when reading resources. Specify \-\-with\-res\-class=Rxvt to replace 2190when reading resources. Specify \-\-with\-res\-class=Rxvt to replace
2253rxvt. 2191rxvt.
2254.IP "\-\-enable\-utmp" 4 2192.IP "\-\-enable\-utmp (default: on)" 4
2255.IX Item "--enable-utmp" 2193.IX Item "--enable-utmp (default: on)"
2256Write user and tty to utmp file (used by programs like \fIw\fR) at 2194Write user and tty to utmp file (used by programs like \fIw\fR) at
2257start of rxvt execution and delete information when rxvt exits. 2195start of rxvt execution and delete information when rxvt exits.
2258.IP "\-\-enable\-wtmp" 4 2196.IP "\-\-enable\-wtmp (default: on)" 4
2259.IX Item "--enable-wtmp" 2197.IX Item "--enable-wtmp (default: on)"
2260Write user and tty to wtmp file (used by programs like \fIlast\fR) at 2198Write user and tty to wtmp file (used by programs like \fIlast\fR) at
2261start of rxvt execution and write logout when rxvt exits. This 2199start of rxvt execution and write logout when rxvt exits. This
2262option requires \-\-enable\-utmp to also be specified. 2200option requires \-\-enable\-utmp to also be specified.
2263.IP "\-\-enable\-lastlog" 4 2201.IP "\-\-enable\-lastlog (default: on)" 4
2264.IX Item "--enable-lastlog" 2202.IX Item "--enable-lastlog (default: on)"
2265Write user and tty to lastlog file (used by programs like 2203Write user and tty to lastlog file (used by programs like
2266\&\fIlastlogin\fR) at start of rxvt execution. This option requires 2204\&\fIlastlogin\fR) at start of rxvt execution. This option requires
2267\&\-\-enable\-utmp to also be specified. 2205\&\-\-enable\-utmp to also be specified.
2268.IP "\-\-enable\-xpm\-background" 4 2206.IP "\-\-enable\-xpm\-background (default: on)" 4
2269.IX Item "--enable-xpm-background" 2207.IX Item "--enable-xpm-background (default: on)"
2270Add support for \s-1XPM\s0 background pixmaps. 2208Add support for \s-1XPM\s0 background pixmaps.
2271.IP "\-\-enable\-transparency" 4 2209.IP "\-\-enable\-transparency (default: on)" 4
2272.IX Item "--enable-transparency" 2210.IX Item "--enable-transparency (default: on)"
2273Add support for inheriting parent backgrounds thus giving a fake 2211Add support for inheriting parent backgrounds thus giving a fake
2274transparency to the term. 2212transparency to the term.
2275.IP "\-\-enable\-fading" 4 2213.IP "\-\-enable\-fading (default: on)" 4
2276.IX Item "--enable-fading" 2214.IX Item "--enable-fading (default: on)"
2277Add support for fading the text when focus is lost. 2215Add support for fading the text when focus is lost (requires \f(CW\*(C`\-\-enable\-transparency\*(C'\fR).
2278.IP "\-\-enable\-tinting" 4 2216.IP "\-\-enable\-tinting (default: on)" 4
2279.IX Item "--enable-tinting" 2217.IX Item "--enable-tinting (default: on)"
2280Add support for tinting of transparent backgrounds. 2218Add support for tinting of transparent backgrounds (requires \f(CW\*(C`\-\-enable\-transparency\*(C'\fR).
2281.IP "\-\-enable\-menubar" 4
2282.IX Item "--enable-menubar"
2283Add support for our menu bar system (this interacts badly with
2284dynamic locale switching currently).
2285.IP "\-\-enable\-rxvt\-scroll" 4 2219.IP "\-\-enable\-rxvt\-scroll (default: on)" 4
2286.IX Item "--enable-rxvt-scroll" 2220.IX Item "--enable-rxvt-scroll (default: on)"
2287Add support for the original rxvt scrollbar. 2221Add support for the original rxvt scrollbar.
2288.IP "\-\-enable\-next\-scroll" 4 2222.IP "\-\-enable\-next\-scroll (default: on)" 4
2289.IX Item "--enable-next-scroll" 2223.IX Item "--enable-next-scroll (default: on)"
2290Add support for a NeXT-like scrollbar. 2224Add support for a NeXT-like scrollbar.
2291.IP "\-\-enable\-xterm\-scroll" 4 2225.IP "\-\-enable\-xterm\-scroll (default: on)" 4
2292.IX Item "--enable-xterm-scroll" 2226.IX Item "--enable-xterm-scroll (default: on)"
2293Add support for an Xterm-like scrollbar. 2227Add support for an Xterm-like scrollbar.
2294.IP "\-\-enable\-plain\-scroll" 4 2228.IP "\-\-enable\-plain\-scroll (default: on)" 4
2295.IX Item "--enable-plain-scroll" 2229.IX Item "--enable-plain-scroll (default: on)"
2296Add support for a very unobtrusive, plain-looking scrollbar that 2230Add support for a very unobtrusive, plain-looking scrollbar that
2297is the favourite of the rxvt-unicode author, having used it for 2231is the favourite of the rxvt-unicode author, having used it for
2298many years. 2232many years.
2299.IP "\-\-enable\-half\-shadow" 4
2300.IX Item "--enable-half-shadow"
2301Make shadows on the scrollbar only half the normal width & height.
2302only applicable to rxvt scrollbars.
2303.IP "\-\-enable\-ttygid" 4 2233.IP "\-\-enable\-ttygid (default: off)" 4
2304.IX Item "--enable-ttygid" 2234.IX Item "--enable-ttygid (default: off)"
2305Change tty device setting to group \*(L"tty\*(R" \- only use this if 2235Change tty device setting to group \*(L"tty\*(R" \- only use this if
2306your system uses this type of security. 2236your system uses this type of security.
2307.IP "\-\-disable\-backspace\-key" 4 2237.IP "\-\-disable\-backspace\-key" 4
2308.IX Item "--disable-backspace-key" 2238.IX Item "--disable-backspace-key"
2309Disable any handling of the backspace key by us \- let the X server 2239Removes any handling of the backspace key by us \- let the X server do it.
2310do it.
2311.IP "\-\-disable\-delete\-key" 4 2240.IP "\-\-disable\-delete\-key" 4
2312.IX Item "--disable-delete-key" 2241.IX Item "--disable-delete-key"
2313Disable any handling of the delete key by us \- let the X server 2242Removes any handling of the delete key by us \- let the X server
2314do it. 2243do it.
2315.IP "\-\-disable\-resources" 4 2244.IP "\-\-disable\-resources" 4
2316.IX Item "--disable-resources" 2245.IX Item "--disable-resources"
2317Remove all resources checking. 2246Removes any support for resource checking.
2318.IP "\-\-enable\-xgetdefault" 4
2319.IX Item "--enable-xgetdefault"
2320Make resources checking via \fIXGetDefault()\fR instead of our small
2321version which only checks ~/.Xdefaults, or if that doesn't exist then
2322~/.Xresources.
2323.Sp
2324Please note that nowadays, things like \s-1XIM\s0 will automatically pull in and
2325use the full X resource manager, so the overhead of using it might be very
2326small, if nonexistant.
2327.IP "\-\-enable\-strings" 4
2328.IX Item "--enable-strings"
2329Add support for our possibly faster \fImemset()\fR function and other
2330various routines, overriding your system's versions which may
2331have been hand-crafted in assembly or may require extra libraries
2332to link in. (this breaks ANSI-C rules and has problems on many
2333GNU/Linux systems).
2334.IP "\-\-disable\-swapscreen" 4 2247.IP "\-\-disable\-swapscreen" 4
2335.IX Item "--disable-swapscreen" 2248.IX Item "--disable-swapscreen"
2336Remove support for swap screen. 2249Remove support for secondary/swap screen.
2337.IP "\-\-enable\-frills" 4 2250.IP "\-\-enable\-frills (default: on)" 4
2338.IX Item "--enable-frills" 2251.IX Item "--enable-frills (default: on)"
2339Add support for many small features that are not essential but nice to 2252Add support for many small features that are not essential but nice to
2340have. Normally you want this, but for very small binaries you may want to 2253have. Normally you want this, but for very small binaries you may want to
2341disable this. 2254disable this.
2342.Sp 2255.Sp
2343A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly 2256A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly
2344in combination with other switches) is: 2257in combination with other switches) is:
2345.Sp 2258.Sp
2259.Vb 15
2260\& MWM-hints
2261\& EWMH-hints (pid, utf8 names) and protocols (ping)
2262\& seperate underline colour (-underlineColor)
2263\& settable border widths and borderless switch (-w, -b, -bl)
2264\& visual depth selection (-depth)
2265\& settable extra linespacing /-lsp)
2266\& iso-14755-2 and -3, and visual feedback
2267\& tripleclickwords (-tcw)
2268\& settable insecure mode (-insecure)
2269\& keysym remapping support
2270\& cursor blinking and underline cursor (-cb, -uc)
2271\& XEmbed support (-embed)
2272\& user-pty (-pty-fd)
2273\& hold on exit (-hold)
2274\& skip builtin block graphics (-sbg)
2275.Ve
2276.Sp
2277It also enabled some non-essential features otherwise disabled, such as:
2278.Sp
2346.Vb 11 2279.Vb 11
2347\& MWM-hints 2280\& some round-trip time optimisations
2348\& seperate underline colour 2281\& nearest color allocation on pseudocolor screens
2349\& settable border widths and borderless switch 2282\& UTF8_STRING supporr for selection
2350\& settable extra linespacing 2283\& sgr modes 90..97 and 100..107
2351\& extra window properties (e.g. UTF-8 window names and PID)
2352\& iso-14755-2 and -3, and visual feedback
2353\& backindex and forwardindex escape sequence 2284\& backindex and forwardindex escape sequences
2285\& view change/zero scorllback esacpe sequences
2286\& locale switching escape sequence
2354\& window op and locale change escape sequences 2287\& window op and some xterm/OSC escape sequences
2355\& tripleclickwords 2288\& rectangular selections
2356\& settable insecure mode 2289\& trailing space removal for selections
2357\& keysym remapping support 2290\& verbose X error handling
2358.Ve 2291.Ve
2359.IP "\-\-enable\-iso14755" 4 2292.IP "\-\-enable\-iso14755 (default: on)" 4
2360.IX Item "--enable-iso14755" 2293.IX Item "--enable-iso14755 (default: on)"
2361Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or 2294Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or
2362\&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by 2295\&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by
2363\&\f(CW\*(C`\-\-enable\-frills\*(C'\fR, while support for 5.2, 5.3 and 5.4 is enabled with 2296\&\f(CW\*(C`\-\-enable\-frills\*(C'\fR, while support for 5.2, 5.3 and 5.4 is enabled with
2364this switch. 2297this switch.
2365.IP "\-\-enable\-keepscrolling" 4 2298.IP "\-\-enable\-keepscrolling (default: on)" 4
2366.IX Item "--enable-keepscrolling" 2299.IX Item "--enable-keepscrolling (default: on)"
2367Add support for continual scrolling of the display when you hold 2300Add support for continual scrolling of the display when you hold
2368the mouse button down on a scrollbar arrow. 2301the mouse button down on a scrollbar arrow.
2369.IP "\-\-enable\-mousewheel" 4 2302.IP "\-\-enable\-mousewheel (default: on)" 4
2370.IX Item "--enable-mousewheel" 2303.IX Item "--enable-mousewheel (default: on)"
2371Add support for scrolling via mouse wheel or buttons 4 & 5. 2304Add support for scrolling via mouse wheel or buttons 4 & 5.
2372.IP "\-\-enable\-slipwheeling" 4 2305.IP "\-\-enable\-slipwheeling (default: on)" 4
2373.IX Item "--enable-slipwheeling" 2306.IX Item "--enable-slipwheeling (default: on)"
2374Add support for continual scrolling (using the mouse wheel as an 2307Add support for continual scrolling (using the mouse wheel as an
2375accelerator) while the control key is held down. This option 2308accelerator) while the control key is held down. This option
2376requires \-\-enable\-mousewheel to also be specified. 2309requires \-\-enable\-mousewheel to also be specified.
2377.IP "\-\-disable\-new\-selection" 4 2310.IP "\-\-disable\-new\-selection" 4
2378.IX Item "--disable-new-selection" 2311.IX Item "--disable-new-selection"
2379Remove support for mouse selection style like that of xterm. 2312Remove support for mouse selection style like that of xterm.
2380.IP "\-\-enable\-dmalloc" 4 2313.IP "\-\-enable\-dmalloc (default: off)" 4
2381.IX Item "--enable-dmalloc" 2314.IX Item "--enable-dmalloc (default: off)"
2382Use Gray Watson's malloc \- which is good for debugging See 2315Use Gray Watson's malloc \- which is good for debugging See
2383http://www.letters.com/dmalloc/ for details If you use either this or the 2316http://www.letters.com/dmalloc/ for details If you use either this or the
2384next option, you may need to edit src/Makefile after compiling to point 2317next option, you may need to edit src/Makefile after compiling to point
2385\&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places. 2318\&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places.
2386.Sp 2319.Sp
2387You can only use either this option and the following (should 2320You can only use either this option and the following (should
2388you use either) . 2321you use either) .
2389.IP "\-\-enable\-dlmalloc" 4 2322.IP "\-\-enable\-dlmalloc (default: off)" 4
2390.IX Item "--enable-dlmalloc" 2323.IX Item "--enable-dlmalloc (default: off)"
2391Use Doug Lea's malloc \- which is good for a production version 2324Use Doug Lea's malloc \- which is good for a production version
2392See <http://g.oswego.edu/dl/html/malloc.html> for details. 2325See <http://g.oswego.edu/dl/html/malloc.html> for details.
2393.IP "\-\-enable\-smart\-resize" 4 2326.IP "\-\-enable\-smart\-resize (default: on)" 4
2394.IX Item "--enable-smart-resize" 2327.IX Item "--enable-smart-resize (default: on)"
2395Add smart growth/shrink behaviour when changing font size via from hot 2328Add smart growth/shrink behaviour when changing font size via hot
2396keys. This should keep in a fixed position the rxvt corner which is 2329keys. This should keep the window corner which is closest to a corner of
2397closest to a corner of the screen. 2330the screen in a fixed position.
2398.IP "\-\-enable\-cursor\-blink" 4
2399.IX Item "--enable-cursor-blink"
2400Add support for a blinking cursor.
2401.IP "\-\-enable\-pointer\-blank" 4 2331.IP "\-\-enable\-pointer\-blank (default: on)" 4
2402.IX Item "--enable-pointer-blank" 2332.IX Item "--enable-pointer-blank (default: on)"
2403Add support to have the pointer disappear when typing or inactive. 2333Add support to have the pointer disappear when typing or inactive.
2334.IP "\-\-enable\-perl (default: on)" 4
2335.IX Item "--enable-perl (default: on)"
2336Enable an embedded perl interpreter. See the \fB@@RXVT_NAME@@\f(BIperl\fB\|(3)\fR
2337manpage (\fIdoc/rxvtperl.txt\fR) for more info on this feature, or the files
2338in \fIsrc/perl\-ext/\fR for the extensions that are installed by default. The
2339perl interpreter that is used can be specified via the \f(CW\*(C`PERL\*(C'\fR environment
2340variable when running configure.
2404.IP "\-\-with\-name=NAME" 4 2341.IP "\-\-with\-name=NAME (default: urxvt)" 4
2405.IX Item "--with-name=NAME" 2342.IX Item "--with-name=NAME (default: urxvt)"
2406Set the basename for the installed binaries (default: \f(CW\*(C`urxvt\*(C'\fR, resulting 2343Set the basename for the installed binaries, resulting
2407in \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 2344in \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
2408\&\f(CW\*(C`rxvt\*(C'\fR. 2345\&\f(CW\*(C`rxvt\*(C'\fR.
2409.IP "\-\-with\-term=NAME" 4 2346.IP "\-\-with\-term=NAME (default: rxvt\-unicode)" 4
2410.IX Item "--with-term=NAME" 2347.IX Item "--with-term=NAME (default: rxvt-unicode)"
2411Change the environmental variable for the terminal to \s-1NAME\s0 (default 2348Change the environmental variable for the terminal to \s-1NAME\s0.
2412\&\f(CW\*(C`rxvt\-unicode\*(C'\fR)
2413.IP "\-\-with\-terminfo=PATH" 4 2349.IP "\-\-with\-terminfo=PATH" 4
2414.IX Item "--with-terminfo=PATH" 2350.IX Item "--with-terminfo=PATH"
2415Change the environmental variable for the path to the terminfo tree to 2351Change the environmental variable for the path to the terminfo tree to
2416\&\s-1PATH\s0. 2352\&\s-1PATH\s0.
2417.IP "\-\-with\-x" 4 2353.IP "\-\-with\-x" 4

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines