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.48 by root, Mon Jan 16 15:12:48 2006 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 "2006-01-16" "7.0" "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"
161.IP "The new selection selects pieces that are too big, how can I select single words?" 4 160.Sh "The new selection selects pieces that are too big, how can I select single words?"
162.IX Item "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?"
163Yes. For example, if you want to select alphanumeric words, you can use 162If you want to select e.g. alphanumeric words, you can use the following
164the following resource: 163setting:
165.Sp 164.PP
166.Vb 1 165.Vb 1
167\& URxvt.selection.pattern-0: ([[:word:]]+) 166\& URxvt.selection.pattern-0: ([[:word:]]+)
168.Ve 167.Ve
169.Sp 168.PP
170If you click more than twice, the selection will be extended 169If you click more than twice, the selection will be extended
171more and more. 170more and more.
172.Sp 171.PP
173To get a selection that is very similar to the old code, try this pattern: 172To get a selection that is very similar to the old code, try this pattern:
174.Sp 173.PP
175.Vb 1 174.Vb 1
176\& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+) 175\& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+)
177.Ve 176.Ve
178.Sp 177.PP
179Please also note that the \fILeftClick Shift-LeftClik\fR combination also 178Please also note that the \fILeftClick Shift-LeftClik\fR combination also
180selects words like the old code. 179selects words like the old code.
181.IP "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" 4 180.Sh "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?"
182.IX Item "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?"
183You can disable the perl extension completely by setting the 182You can disable the perl extension completely by setting the
184\&\fBperl-ext-common\fR resource to the empty string, which also keeps 183\&\fBperl-ext-common\fR resource to the empty string, which also keeps
185rxvt-unicode from initialising perl, saving memory. 184rxvt-unicode from initialising perl, saving memory.
186.Sp 185.PP
187If you only want to disable specific features, you first have to 186If you only want to disable specific features, you first have to
188identify which perl extension is responsible. For this, read the section 187identify which perl extension is responsible. For this, read the section
189\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For 188\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For
190example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify 189example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify
191this \fBperl-ext-common\fR resource: 190this \fBperl-ext-common\fR resource:
192.Sp 191.PP
193.Vb 1 192.Vb 1
194\& URxvt.perl-ext-common: default,-selection-popup,-option-popup 193\& URxvt.perl-ext-common: default,-selection-popup,-option-popup
195.Ve 194.Ve
196.Sp 195.PP
197This will keep the default extensions, but disable the two popup 196This will keep the default extensions, but disable the two popup
198extensions. Some extensions can also be configured, for example, 197extensions. Some extensions can also be configured, for example,
199scrollback search mode is triggered by \fBM\-s\fR. You can move it to any 198scrollback search mode is triggered by \fBM\-s\fR. You can move it to any
200other combination either by setting the \fBsearchable-scrollback\fR resource: 199other combination either by setting the \fBsearchable-scrollback\fR resource:
201.Sp 200.PP
202.Vb 1 201.Vb 1
203\& URxvt.searchable-scrollback: CM-s 202\& URxvt.searchable-scrollback: CM-s
204.Ve 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.
205.IP "Isn't rxvt supposed to be small? Don't all those features bloat?" 4 298.Sh "Isn't rxvt supposed to be small? Don't all those features bloat?"
206.IX Item "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?"
207I often get asked about this, and I think, no, they didn't cause extra 300I often get asked about this, and I think, no, they didn't cause extra
208bloat. If you compare a minimal rxvt and a minimal urxvt, you can see 301bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
209that the urxvt binary is larger (due to some encoding tables always being 302that the urxvt binary is larger (due to some encoding tables always being
210compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even 303compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even
211with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many 304with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many
212features unique to urxvt (locale, encoding conversion, iso14755 etc.) are 305features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
213already in use in this mode. 306already in use in this mode.
214.Sp 307.PP
215.Vb 3 308.Vb 3
216\& text data bss drs rss filename 309\& text data bss drs rss filename
217\& 98398 1664 24 15695 1824 rxvt --disable-everything 310\& 98398 1664 24 15695 1824 rxvt --disable-everything
218\& 188985 9048 66616 18222 1788 urxvt --disable-everything 311\& 188985 9048 66616 18222 1788 urxvt --disable-everything
219.Ve 312.Ve
220.Sp 313.PP
221When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft 314When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft
222and full locale/XIM support which are quite bloaty inside libX11 and my 315and full locale/XIM support which are quite bloaty inside libX11 and my
223libc), the two diverge, but not unreasnobaly so. 316libc), the two diverge, but not unreasnobaly so.
224.Sp 317.PP
225.Vb 3 318.Vb 3
226\& text data bss drs rss filename 319\& text data bss drs rss filename
227\& 163431 2152 24 20123 2060 rxvt --enable-everything 320\& 163431 2152 24 20123 2060 rxvt --enable-everything
228\& 1035683 49680 66648 29096 3680 urxvt --enable-everything 321\& 1035683 49680 66648 29096 3680 urxvt --enable-everything
229.Ve 322.Ve
230.Sp 323.PP
231The very large size of the text section is explained by the east-asian 324The very large size of the text section is explained by the east-asian
232encoding tables, which, if unused, take up disk space but nothing else 325encoding tables, which, if unused, take up disk space but nothing else
233and can be compiled out unless you rely on X11 core fonts that use those 326and can be compiled out unless you rely on X11 core fonts that use those
234encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++ 327encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++
235compiler allocates (but of course doesn't use unless you are out of 328compiler allocates (but of course doesn't use unless you are out of
236memory). Also, using an xft font instead of a core font immediately adds a 329memory). Also, using an xft font instead of a core font immediately adds a
237few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when 330few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when
238not used. 331not used.
239.Sp 332.PP
240Of course, due to every character using two or four bytes instead of one, 333Of course, due to every character using two or four bytes instead of one,
241a large scrollback buffer will ultimately make rxvt-unicode use more 334a large scrollback buffer will ultimately make rxvt-unicode use more
242memory. 335memory.
243.Sp 336.PP
244Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this 337Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
245still fares rather well. And compared to some monsters like gnome-terminal 338still fares rather well. And compared to some monsters like gnome-terminal
246(21152k + extra 4204k in separate processes) or konsole (22200k + extra 339(21152k + extra 4204k in separate processes) or konsole (22200k + extra
24743180k in daemons that stay around after exit, plus half a minute of 34043180k in daemons that stay around after exit, plus half a minute of
248startup time, including the hundreds of warnings it spits out), it fares 341startup time, including the hundreds of warnings it spits out), it fares
249extremely well *g*. 342extremely well *g*.
250.IP "Why \*(C+, isn't that unportable/bloated/uncool?" 4 343.Sh "Why \*(C+, isn't that unportable/bloated/uncool?"
251.IX Item "Why , isn't that unportable/bloated/uncool?" 344.IX Subsection "Why , isn't that unportable/bloated/uncool?"
252Is this a question? :) It comes up very often. The simple answer is: I had 345Is this a question? :) It comes up very often. The simple answer is: I had
253to write it, and \*(C+ allowed me to write and maintain it in a fraction 346to write it, and \*(C+ allowed me to write and maintain it in a fraction
254of the time and effort (which is a scarce resource for me). Put even 347of the time and effort (which is a scarce resource for me). Put even
255shorter: It simply wouldn't exist without \*(C+. 348shorter: It simply wouldn't exist without \*(C+.
256.Sp 349.PP
257My personal stance on this is that \*(C+ is less portable than C, but in 350My personal stance on this is that \*(C+ is less portable than C, but in
258the case of rxvt-unicode this hardly matters, as its portability limits 351the case of rxvt-unicode this hardly matters, as its portability limits
259are defined by things like X11, pseudo terminals, locale support and unix 352are defined by things like X11, pseudo terminals, locale support and unix
260domain sockets, which are all less portable than \*(C+ itself. 353domain sockets, which are all less portable than \*(C+ itself.
261.Sp 354.PP
262Regarding the bloat, see the above question: It's easy to write programs 355Regarding the bloat, see the above question: It's easy to write programs
263in C that use gobs of memory, an certainly possible to write programs in 356in C that use gobs of memory, an certainly possible to write programs in
264\&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is 357\&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is
265not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my 358not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my
266system with a minimal config: 359system with a minimal config:
267.Sp 360.PP
268.Vb 4 361.Vb 4
269\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 362\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
270\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) 363\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
271\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) 364\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
272\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 365\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
273.Ve 366.Ve
274.Sp 367.PP
275And here is rxvt\-unicode: 368And here is rxvt\-unicode:
276.Sp 369.PP
277.Vb 5 370.Vb 5
278\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 371\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
279\& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) 372\& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
280\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) 373\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
281\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) 374\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
282\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 375\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
283.Ve 376.Ve
284.Sp 377.PP
285No large bloated libraries (of course, none were linked in statically), 378No large bloated libraries (of course, none were linked in statically),
286except maybe libX11 :) 379except maybe libX11 :)
287.IP "Does it support tabs, can I have a tabbed rxvt\-unicode?" 4 380.Sh "Does it support tabs, can I have a tabbed rxvt\-unicode?"
288.IX Item "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?"
289rxvt-unicode does not directly support tabs. It will work fine with 382Beginning with version 7.3, there is a perl extension that implements a
290tabbing functionality of many window managers or similar tabbing programs, 383simple tabbed terminal. It is installed by default, so any of these should
291and its embedding-features allow it to be embedded into other programs, 384give you tabs:
292as witnessed by \fIdoc/rxvt\-tabbed\fR or the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl 385.PP
293module, which features a tabbed urxvt (murxvt) terminal as an example 386.Vb 1
294embedding application. 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.
295.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?"
296.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?"
297The version number is displayed with the usage (\-h). Also the escape 401The version number is displayed with the usage (\-h). Also the escape
298sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When 402sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When
299using the @@RXVT_NAME@@c client, the version displayed is that of the 403using the @@RXVT_NAME@@c client, the version displayed is that of the
300daemon. 404daemon.
301.IP "I am using Debian GNU/Linux and have a problem..." 4 405.Sh "I am using Debian GNU/Linux and have a problem..."
302.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..."
303The Debian GNU/Linux package of rxvt-unicode in sarge contains large 407The Debian GNU/Linux package of rxvt-unicode in sarge contains large
304patches that considerably change the behaviour of rxvt\-unicode. Before 408patches that considerably change the behaviour of rxvt-unicode (but
305reporting a bug to the original rxvt-unicode author please download and 409unfortunately this notice has been removed). Before reporting a bug to
306install the genuine version (<http://software.schmorp.de#rxvt\-unicode>) 410the original rxvt-unicode author please download and install the genuine
307and try to reproduce the problem. If you cannot, chances are that the 411version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce
308problems are specific to Debian GNU/Linux, in which case it should be 412the problem. If you cannot, chances are that the problems are specific to
413Debian GNU/Linux, in which case it should be reported via the Debian Bug
309reported via the Debian Bug Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report 414Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug).
310the bug). 415.PP
311.Sp
312For other problems that also affect the Debian package, you can and 416For other problems that also affect the Debian package, you can and
313probably 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
314bug 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
315might encounter the same issue. 419might encounter the same issue.
316.IP "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?" 4 420.Sh "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?"
317.IX Item "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?" 421.IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?"
318You should build one binary with the default options. \fIconfigure\fR 422You should build one binary with the default options. \fIconfigure\fR
319now enables most useful options, and the trend goes to making them 423now enables most useful options, and the trend goes to making them
320runtime\-switchable, too, so there is usually no drawback to enbaling them, 424runtime\-switchable, too, so there is usually no drawback to enbaling them,
321except higher disk and possibly memory usage. The perl interpreter should 425except higher disk and possibly memory usage. The perl interpreter should
322be enabled, as important functionality (menus, selection, likely more in 426be enabled, as important functionality (menus, selection, likely more in
323the future) depends on it. 427the future) depends on it.
324.Sp 428.PP
325You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources 429You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources
326system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful 430system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful
327behaviour. If your distribution aims at low memory, add an empty 431behaviour. If your distribution aims at low memory, add an empty
328\&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the 432\&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the
329perl interpreter disabled until the user enables it. 433perl interpreter disabled until the user enables it.
330.Sp 434.PP
331If you can/want build more binaries, I recommend building a minimal 435If you can/want build more binaries, I recommend building a minimal
332one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with 436one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with
333\&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of 437\&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of
334encodings built-in that increase download times and are rarely used). 438encodings built-in that increase download times and are rarely used).
335.IP "I need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?" 4 439.Sh "I need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?"
336.IX Item "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?" 440.IX Subsection "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?"
337Likely not. While I honestly try to make it secure, and am probably not 441It should be, starting with release 7.1. You are encouraged to properly
338bad at it, I think it is simply unreasonable to expect all of freetype 442install urxvt with privileges necessary for your \s-1OS\s0 now.
339+ fontconfig + xft + xlib + perl + ... + rxvt-unicode itself to all be 443.PP
340secure. Also, rxvt-unicode disables some options when it detects that it 444When rxvt-unicode detects that it runs setuid or setgid, it will fork
341runs setuid or setgid, which is not nice. Besides, with the embedded perl 445into a helper process for privileged operations (pty handling on some
342interpreter the possibility for security problems easily multiplies. 446systems, utmp/wtmp/lastlog handling on others) and drop privileges
343.Sp 447immediately. This is much safer than most other terminals that keep
344Elevated privileges are only required for utmp and pty operations on some 448privileges while running (but is more relevant to urxvt, as it contains
345systems (for example, GNU/Linux doesn't need any extra privileges for 449things as perl interpreters, which might be \*(L"helpful\*(R" to attackers).
346ptys, but some need it for utmp support). It is planned to mvoe this into 450.PP
347a forked handler process, but this is not yet done. 451This forking is done as the very first within \fImain()\fR, which is very early
348.Sp 452and reduces possible bugs to initialisation code run before \fImain()\fR, or
349So, while setuid/setgid operation is supported and not a problem on your 453things like the dynamic loader of your system, which should result in very
350typical single-user-no-other-logins unix desktop, always remember that 454little risk.
351its an awful lot of code, most of which isn't checked for security issues
352regularly.
353.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?"
354.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?"
355The terminal description used by rxvt-unicode is not as widely available 457The terminal description used by rxvt-unicode is not as widely available
356as 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).
357.Sp 459.PP
358The 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
359be done like this (with ncurses' infocmp): 461be done like this (with ncurses' infocmp):
360.Sp 462.PP
361.Vb 2 463.Vb 2
362\& REMOTE=remotesystem.domain 464\& REMOTE=remotesystem.domain
363\& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" 465\& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
364.Ve 466.Ve
365.Sp 467.PP
366\&... or by installing rxvt-unicode normally on the remote system, 468\&... or by installing rxvt-unicode normally on the remote system,
367.Sp 469.PP
368If 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
369\&\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
370problems arising, which includes wrong keymapping, less and different 472problems arising, which includes wrong keymapping, less and different
371colours and some refresh errors in fullscreen applications. It's a nice 473colours and some refresh errors in fullscreen applications. It's a nice
372quick-and-dirty workaround for rare cases, though. 474quick-and-dirty workaround for rare cases, though.
373.Sp 475.PP
374If 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
375can 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
376resource to set it: 478resource to set it:
377.Sp 479.PP
378.Vb 1 480.Vb 1
379\& URxvt.termName: rxvt 481\& URxvt.termName: rxvt
380.Ve 482.Ve
381.Sp 483.PP
382If 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
383the rxvt terminfo file with the rxvt-unicode one. 485the rxvt terminfo file with the rxvt-unicode one.
384.ie n .IP """tic"" outputs some error when compiling the terminfo entry." 4 486.ie n .Sh """tic"" outputs some error when compiling the terminfo entry."
385.el .IP "\f(CWtic\fR outputs some error when compiling the terminfo entry." 4 487.el .Sh "\f(CWtic\fP outputs some error when compiling the terminfo entry."
386.IX Item "tic outputs some error when compiling the terminfo entry." 488.IX Subsection "tic outputs some error when compiling the terminfo entry."
387Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by 489Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by
388\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. 490\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again.
389.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@@."
390.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@@."
391.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@@."
392.PD 0 494See next entry.
393.IP "I need a termcap file entry." 4 495.Sh "I need a termcap file entry."
394.IX Item "I need a termcap file entry." 496.IX Subsection "I need a termcap file entry."
395.PD
396One reason you might want this is that some distributions or operating 497One reason you might want this is that some distributions or operating
397systems still compile some programs using the long-obsoleted termcap 498systems still compile some programs using the long-obsoleted termcap
398library (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
399for \f(CW\*(C`rxvt\-unicode\*(C'\fR. 500for \f(CW\*(C`rxvt\-unicode\*(C'\fR.
400.Sp 501.PP
401You 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.
402You 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
403like this: 504like this:
404.Sp 505.PP
405.Vb 1 506.Vb 1
406\& infocmp -C rxvt-unicode 507\& infocmp -C rxvt-unicode
407.Ve 508.Ve
408.Sp 509.PP
409Or you could use this termcap entry, generated by the command above: 510Or you could use this termcap entry, generated by the command above:
410.Sp 511.PP
411.Vb 20 512.Vb 20
412\& rxvt-unicode|rxvt-unicode terminal (X Window System):\e 513\& rxvt-unicode|rxvt-unicode terminal (X Window System):\e
413\& :am:bw:eo:km:mi:ms:xn:xo:\e 514\& :am:bw:eo:km:mi:ms:xn:xo:\e
414\& :co#80:it#8:li#24:lm#0:\e 515\& :co#80:it#8:li#24:lm#0:\e
415\& :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
… …
428\& :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
429\& :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
430\& :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
431\& :vs=\eE[?25h: 532\& :vs=\eE[?25h:
432.Ve 533.Ve
433.ie n .IP "Why does ""ls"" no longer have coloured output?" 4 534.ie n .Sh "Why does ""ls"" no longer have coloured output?"
434.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?"
435.IX Item "Why does ls no longer have coloured output?" 536.IX Subsection "Why does ls no longer have coloured output?"
436The \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
437decide wether a terminal has colour, but uses it's own configuration 538decide wether a terminal has colour, but uses it's own configuration
438file. 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
439with most other terminals supporting colour). Either add: 540with most other terminals supporting colour). Either add:
440.Sp 541.PP
441.Vb 1 542.Vb 1
442\& TERM rxvt-unicode 543\& TERM rxvt-unicode
443.Ve 544.Ve
444.Sp 545.PP
445to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add: 546to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add:
446.Sp 547.PP
447.Vb 1 548.Vb 1
448\& alias ls='ls --color=auto' 549\& alias ls='ls --color=auto'
449.Ve 550.Ve
450.Sp 551.PP
451to 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.
452.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?"
453.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?"
454.PD 0 555See next entry.
455.IP "Why doesn't vim/emacs etc. make use of italic?" 4 556.Sh "Why doesn't vim/emacs etc. make use of italic?"
456.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.
457.IP "Why are the secondary screen-related options not working properly?" 4 559.Sh "Why are the secondary screen-related options not working properly?"
458.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?"
459.PD
460Make 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
461distributions (most notably Debian GNU/Linux) break rxvt-unicode 562distributions (most notably Debian GNU/Linux) break rxvt-unicode
462by 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
463features. Unfortunately, some of these (most notably, again, Debian 564features. Unfortunately, some of these (most notably, again, Debian
464GNU/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
465file, 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
466I 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
467how to do this). 568how to do this).
468.IP "My numerical keypad acts weird and generates differing output?" 4 569.Sh "My numerical keypad acts weird and generates differing output?"
469.IX Item "My numerical keypad acts weird and generates differing output?" 570.IX Subsection "My numerical keypad acts weird and generates differing output?"
470Some Debian GNUL/Linux users seem to have this problem, although no 571Some Debian GNUL/Linux users seem to have this problem, although no
471specific 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
472by 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
473this 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
474keymap. 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
475helped. 576helped.
476.IP "Rxvt-unicode does not seem to understand the selected encoding?" 4 577.Sh "Rxvt-unicode does not seem to understand the selected encoding?"
477.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?"
478.PD 0 579See next entry.
479.IP "Unicode does not seem to work?" 4 580.Sh "Unicode does not seem to work?"
480.IX Item "Unicode does not seem to work?" 581.IX Subsection "Unicode does not seem to work?"
481.PD
482If you encounter strange problems like typing an accented character but 582If you encounter strange problems like typing an accented character but
483getting two unrelated other characters or similar, or if program output is 583getting two unrelated other characters or similar, or if program output is
484subtly garbled, then you should check your locale settings. 584subtly garbled, then you should check your locale settings.
485.Sp 585.PP
486Rxvt-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
487programs. 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
488login script running within the rxvt-unicode window changes the locale to 588login script running within the rxvt-unicode window changes the locale to
489something 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.
490.Sp 590.PP
491The 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
492into 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.
493.Sp 593.PP
494.Vb 1 594.Vb 1
495\& printf '\ee]701;%s\e007' "$LC_CTYPE" 595\& printf '\ee]701;%s\e007' "$LC_CTYPE"
496.Ve 596.Ve
497.Sp 597.PP
498If 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
499supported 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
500displays 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
501it 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
502like: 602like:
503.Sp 603.PP
504.Vb 1 604.Vb 1
505\& locale: Cannot set LC_CTYPE to default locale: ... 605\& locale: Cannot set LC_CTYPE to default locale: ...
506.Ve 606.Ve
507.Sp 607.PP
508Then the locale you specified is not supported on your system. 608Then the locale you specified is not supported on your system.
509.Sp 609.PP
510If 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
511you 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
512support locales :( 612support locales :(
513.IP "Why do some characters look so much different than others?" 4 613.Sh "Why do some characters look so much different than others?"
514.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?"
515.PD 0 615See next entry.
516.IP "How does rxvt-unicode choose fonts?" 4 616.Sh "How does rxvt-unicode choose fonts?"
517.IX Item "How does rxvt-unicode choose fonts?" 617.IX Subsection "How does rxvt-unicode choose fonts?"
518.PD
519Most fonts do not contain the full range of Unicode, which is 618Most fonts do not contain the full range of Unicode, which is
520fine. 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
521your 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
522to display. 621to display.
523.Sp 622.PP
524\&\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
525font. Often the result is fine, but sometimes the chosen font looks 624font. Often the result is fine, but sometimes the chosen font looks
526bad/ugly/wrong. Some fonts have totally strange characters that don't 625bad/ugly/wrong. Some fonts have totally strange characters that don't
527resemble the correct glyph at all, and rxvt-unicode lacks the artificial 626resemble the correct glyph at all, and rxvt-unicode lacks the artificial
528intelligence 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
529the font that the characters it claims to contain indeed look correct. 628the font that the characters it claims to contain indeed look correct.
530.Sp 629.PP
531In 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,
532e.g.: 631e.g.:
533.Sp 632.PP
534.Vb 1 633.Vb 1
535\& @@RXVT_NAME@@ -fn basefont,font2,font3... 634\& @@RXVT_NAME@@ -fn basefont,font2,font3...
536.Ve 635.Ve
537.Sp 636.PP
538When 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
539font. 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
540next 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
541search and use less resources within rxvt-unicode and the X\-server. 640search and use less resources within rxvt-unicode and the X\-server.
542.Sp 641.PP
543The 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
544font, as the base font defines the terminal character cell size, which 643font, as the base font defines the terminal character cell size, which
545must be the same due to the way terminals work. 644must be the same due to the way terminals work.
546.IP "Why do some chinese characters look so different than others?" 4 645.Sh "Why do some chinese characters look so different than others?"
547.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?"
548This is because there is a difference between script and language \*(-- 647This is because there is a difference between script and language \*(--
549rxvt-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,
550as it only knows the unicode character codes. If rxvt-unicode first 649as it only knows the unicode character codes. If rxvt-unicode first
551sees a japanese/chinese character, it might choose a japanese font for 650sees a japanese/chinese character, it might choose a japanese font for
552display. Subsequent japanese characters will use that font. Now, many 651display. Subsequent japanese characters will use that font. Now, many
553chinese characters aren't represented in japanese fonts, so when the first 652chinese characters aren't represented in japanese fonts, so when the first
554non-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
555\&\*(-- 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
556chinese characters that are also in the japanese font. 655chinese characters that are also in the japanese font.
557.Sp 656.PP
558The 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
559list (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
560a preference list: If you expect more japanese, list a japanese font 659a preference list: If you expect more japanese, list a japanese font
561first. If you expect more chinese, put a chinese font first. 660first. If you expect more chinese, put a chinese font first.
562.Sp 661.PP
563In the future it might be possible to switch language preferences at 662In the future it might be possible to switch language preferences at
564runtime (the internal data structure has no problem with using different 663runtime (the internal data structure has no problem with using different
565fonts 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
566has been designed yet). 665has been designed yet).
567.Sp 666.PP
568Until 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).
569.IP "Why does rxvt-unicode sometimes leave pixel droppings?" 4 668.Sh "Why does rxvt-unicode sometimes leave pixel droppings?"
570.IX Item "Why does rxvt-unicode sometimes leave pixel droppings?" 669.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"
571Most fonts were not designed for terminal use, which means that character 670Most fonts were not designed for terminal use, which means that character
572size 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
573contain some characters that are simply too wide. Rxvt-unicode will avoid 672contain some characters that are simply too wide. Rxvt-unicode will avoid
574these 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
575\&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters. 674\&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters.
576.Sp 675.PP
577All of this requires that fonts do not lie about character sizes, 676All of this requires that fonts do not lie about character sizes,
578however: Xft fonts often draw glyphs larger than their acclaimed bounding 677however: Xft fonts often draw glyphs larger than their acclaimed bounding
579box, 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
580ask for the character bounding box, which unfortunately is wrong in these 679ask for the character bounding box, which unfortunately is wrong in these
581cases). 680cases).
582.Sp 681.PP
583It'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,
584or 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
585the \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
586might be forced to use a different font. 685might be forced to use a different font.
587.Sp 686.PP
588All 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
589box data is correct. 688box data is correct.
590.IP "On Solaris 9, many line-drawing characters are too wide." 4 689.Sh "On Solaris 9, many line-drawing characters are too wide."
591.IX Item "On Solaris 9, many line-drawing characters are too wide." 690.IX Subsection "On Solaris 9, many line-drawing characters are too wide."
592Seems to be a known bug, read 691Seems to be a known bug, read
593<http://nixdoc.net/files/forum/about34198.html>. Some people use the 692<http://nixdoc.net/files/forum/about34198.html>. Some people use the
594following ugly workaround to get non-double-wide-characters working: 693following ugly workaround to get non-double-wide-characters working:
595.Sp 694.PP
596.Vb 1 695.Vb 1
597\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) 696\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
598.Ve 697.Ve
599.IP "My Compose (Multi_key) key is no longer working." 4 698.Sh "My Compose (Multi_key) key is no longer working."
600.IX Item "My Compose (Multi_key) key is no longer working." 699.IX Subsection "My Compose (Multi_key) key is no longer working."
601The 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
602correctly, or you specified a \fBpreeditStyle\fR that is not supported by 701correctly, or you specified a \fBpreeditStyle\fR that is not supported by
603your input method. For example, if you specified \fBOverTheSpot\fR and 702your input method. For example, if you specified \fBOverTheSpot\fR and
604your input method (e.g. the default input method handling Compose keys) 703your input method (e.g. the default input method handling Compose keys)
605does not support this (for instance because it is not visual), then 704does not support this (for instance because it is not visual), then
606rxvt-unicode will continue without an input method. 705rxvt-unicode will continue without an input method.
607.Sp 706.PP
608In 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
609one pre-edit style, such as \fBOverTheSpot,Root,None\fR. 708one pre-edit style, such as \fBOverTheSpot,Root,None\fR.
610.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"
611.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"
612.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"
613Either 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
614international keyboards) or simply use \s-1ISO\s0 14755 support to your 713international keyboards) or simply use \s-1ISO\s0 14755 support to your
615advantage, 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
616codes, 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
617character and so on. 716character and so on.
618.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?"
619.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?"
620First 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
621(\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
622make sure you have specified colours for italic and bold, as otherwise 721make sure you have specified colours for italic and bold, as otherwise
623rxvt-unicode might use reverse video to simulate the effect: 722rxvt-unicode might use reverse video to simulate the effect:
624.Sp 723.PP
625.Vb 2 724.Vb 2
626\& URxvt.colorBD: white 725\& URxvt.colorBD: white
627\& URxvt.colorIT: green 726\& URxvt.colorIT: green
628.Ve 727.Ve
629.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?"
630.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?"
631For some unexplainable reason, some rare programs assume a very weird 730For some unexplainable reason, some rare programs assume a very weird
632colour palette when confronted with a terminal with more than the standard 731colour palette when confronted with a terminal with more than the standard
6338 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
634these programs not to assume non-ISO colours without very good reasons. 733these programs not to assume non-ISO colours without very good reasons.
635.Sp 734.PP
636In 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
637definition 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
638fix colours but keep you from using other rxvt-unicode features. 737fix colours but keep you from using other rxvt-unicode features.
639.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."
640.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."
641Rxvt-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
642in your compile environment, or an implementation that implements it, 741in your compile environment, or an implementation that implements it,
643wether 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
644\&\fBwchar_t\fR is represented as unicode. 743\&\fBwchar_t\fR is represented as unicode.
645.Sp 744.PP
646As you might have guessed, FreeBSD does neither define this symobl nor 745As you might have guessed, FreeBSD does neither define this symobl nor
647does 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
648\&\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.
649.Sp 748.PP
650However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and 749However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and
651\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. 750\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR.
652.Sp 751.PP
653\&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language 752\&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language
654apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized) 753apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized)
655representation of \fBwchar_t\fR makes it impossible to convert between 754representation of \fBwchar_t\fR makes it impossible to convert between
656\&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding 755\&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding
657without implementing OS-specific-wrappers for each and every locale. There 756without implementing OS-specific-wrappers for each and every locale. There
658simply are no APIs to convert \fBwchar_t\fR into anything except the current 757simply are no APIs to convert \fBwchar_t\fR into anything except the current
659locale encoding. 758locale encoding.
660.Sp 759.PP
661Some applications (such as the formidable \fBmlterm\fR) work around this 760Some applications (such as the formidable \fBmlterm\fR) work around this
662by carrying their own replacement functions for character set handling 761by carrying their own replacement functions for character set handling
663with them, and either implementing OS-dependent hacks or doing multiple 762with them, and either implementing OS-dependent hacks or doing multiple
664conversions (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
665encodings slightly different than the terminal emulator). 764encodings slightly different than the terminal emulator).
666.Sp 765.PP
667The 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
668system 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
669complete replacements for them :) 768complete replacements for them :)
670.IP "I use Solaris 9 and it doesn't compile/work/etc." 4 769.Sh "I use Solaris 9 and it doesn't compile/work/etc."
671.IX Item "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."
672Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst 771Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst
673problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem. 772problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem.
674.IP "How can I use rxvt-unicode under cygwin?" 4 773.Sh "How can I use rxvt-unicode under cygwin?"
675.IX Item "How can I use rxvt-unicode under cygwin?" 774.IX Subsection "How can I use rxvt-unicode under cygwin?"
676rxvt-unicode should compile and run out of the box on cygwin, using 775rxvt-unicode should compile and run out of the box on cygwin, using
677the X11 libraries that come with cygwin. libW11 emulation is no 776the X11 libraries that come with cygwin. libW11 emulation is no
678longer supported (and makes no sense, either, as it only supported a 777longer supported (and makes no sense, either, as it only supported a
679single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or 778single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or
680\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the 779\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the
681old libW11 emulation. 780old libW11 emulation.
682.Sp 781.PP
683At the time of this writing, cygwin didn't seem to support any multi-byte 782At the time of this writing, cygwin didn't seem to support any multi-byte
684encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited 783encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited
685to 8\-bit encodings. 784to 8\-bit encodings.
686.IP "How does rxvt-unicode determine the encoding to use?" 4 785.Sh "How does rxvt-unicode determine the encoding to use?"
687.IX Item "How does rxvt-unicode determine the encoding to use?" 786.IX Subsection "How does rxvt-unicode determine the encoding to use?"
688.PD 0 787See next entry.
689.IP "Is there an option to switch encodings?" 4 788.Sh "Is there an option to switch encodings?"
690.IX Item "Is there an option to switch encodings?" 789.IX Subsection "Is there an option to switch encodings?"
691.PD
692Unlike some other terminals, rxvt-unicode has no encoding switch, and no 790Unlike some other terminals, rxvt-unicode has no encoding switch, and no
693specific \*(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
694\&\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.
695.Sp 793.PP
696The reasons is that there exists a perfectly fine mechanism for selecting 794The reasons is that there exists a perfectly fine mechanism for selecting
697the encoding, doing I/O and (most important) communicating this to all 795the encoding, doing I/O and (most important) communicating this to all
698applications so everybody agrees on character properties such as width 796applications so everybody agrees on character properties such as width
699and code number. This mechanism is the \fIlocale\fR. Applications not using 797and code number. This mechanism is the \fIlocale\fR. Applications not using
700that 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
701characters 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
702locales). 800locales).
703.Sp 801.PP
704Rxvt-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
705programs doing the same (that is, most) will automatically agree in the 803programs doing the same (that is, most) will automatically agree in the
706interpretation of characters. 804interpretation of characters.
707.Sp 805.PP
708Unfortunately, there is no system-independent way to select locales, nor 806Unfortunately, there is no system-independent way to select locales, nor
709is there a standard on how locale specifiers will look like. 807is there a standard on how locale specifiers will look like.
710.Sp 808.PP
711On 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
712contains an arbitrary string which corresponds to an already-installed 810contains an arbitrary string which corresponds to an already-installed
713locale. 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,
714\&\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
715(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.
716.Sp 814.PP
717Rxvt-unicode ignores all other locale categories, and except for 815Rxvt-unicode ignores all other locale categories, and except for
718the encoding, ignores country or language-specific settings, 816the encoding, ignores country or language-specific settings,
719i.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
720rxvt\-unicode. 818rxvt\-unicode.
721.Sp 819.PP
722If 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
723rxvt-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.
724.IP "Can I switch locales at runtime?" 4 822.Sh "Can I switch locales at runtime?"
725.IX Item "Can I switch locales at runtime?" 823.IX Subsection "Can I switch locales at runtime?"
726Yes, using an escape sequence. Try something like this, which sets 824Yes, using an escape sequence. Try something like this, which sets
727rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR. 825rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR.
728.Sp 826.PP
729.Vb 1 827.Vb 1
730\& printf '\ee]701;%s\e007' ja_JP.SJIS 828\& printf '\ee]701;%s\e007' ja_JP.SJIS
731.Ve 829.Ve
732.Sp 830.PP
733See also the previous answer. 831See also the previous answer.
734.Sp 832.PP
735Sometimes this capability is rather handy when you want to work in 833Sometimes this capability is rather handy when you want to work in
736one 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
737(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
738first switches to a locale supported by xjdic and back later: 836first switches to a locale supported by xjdic and back later:
739.Sp 837.PP
740.Vb 3 838.Vb 3
741\& printf '\ee]701;%s\e007' ja_JP.SJIS 839\& printf '\ee]701;%s\e007' ja_JP.SJIS
742\& xjdic -js 840\& xjdic -js
743\& printf '\ee]701;%s\e007' de_DE.UTF-8 841\& printf '\ee]701;%s\e007' de_DE.UTF-8
744.Ve 842.Ve
745.Sp 843.PP
746You 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
747for some locales where character width differs between program\- and 845for some locales where character width differs between program\- and
748rxvt\-unicode\-locales. 846rxvt\-unicode\-locales.
749.IP "Can I switch the fonts at runtime?" 4 847.Sh "Can I switch the fonts at runtime?"
750.IX Item "Can I switch the fonts at runtime?" 848.IX Subsection "Can I switch the fonts at runtime?"
751Yes, 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
752effect 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:
753.Sp 851.PP
754.Vb 1 852.Vb 1
755\& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic" 853\& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic"
756.Ve 854.Ve
757.Sp 855.PP
758This 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
759japanese font), but you have to switch to chinese temporarily, where 857japanese font), but you have to switch to chinese temporarily, where
760japanese fonts would only be in your way. 858japanese fonts would only be in your way.
761.Sp 859.PP
762You 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.
763.IP "Why do italic characters look as if clipped?" 4 861.Sh "Why do italic characters look as if clipped?"
764.IX Item "Why do italic characters look as if clipped?" 862.IX Subsection "Why do italic characters look as if clipped?"
765Many fonts have difficulties with italic characters and hinting. For 863Many fonts have difficulties with italic characters and hinting. For
766example, 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
767Mono\*(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
768enable freetype autohinting, i.e. like this: 866enable freetype autohinting, i.e. like this:
769.Sp 867.PP
770.Vb 2 868.Vb 2
771\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 869\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
772\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 870\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
773.Ve 871.Ve
774.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?"
775.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?"
776You 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
777terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR: 875terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
778.Sp 876.PP
779.Vb 1 877.Vb 1
780\& URxvt.imlocale: ja_JP.EUC-JP 878\& URxvt.imlocale: ja_JP.EUC-JP
781.Ve 879.Ve
782.Sp 880.PP
783Now 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
784use 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
785input 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
786method limits you. 884method limits you.
787.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."
788.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."
789Unfortunately, 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
790design. Applications can avoid some crashes at the expense of memory 888design. Applications can avoid some crashes at the expense of memory
791leaks, and Input Methods can avoid some crashes by careful ordering at 889leaks, and Input Methods can avoid some crashes by careful ordering at
792exit time. \fBkinput2\fR (and derived input methods) generally succeeds, 890exit time. \fBkinput2\fR (and derived input methods) generally succeeds,
793while \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,
794crashes cannot be completely avoided even if both sides cooperate. 892crashes cannot be completely avoided even if both sides cooperate.
795.Sp 893.PP
796So the only workaround is not to kill your Input Method Servers. 894So the only workaround is not to kill your Input Method Servers.
797.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?"
798.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?"
799Rxvt-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
800don'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
801you 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,
802when 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
803accidentally when rxvt-unicode tries to find a font for your characters. 901accidentally when rxvt-unicode tries to find a font for your characters.
804.Sp 902.PP
805Also, many people (me included) like large windows and even larger 903Also, many people (me included) like large windows and even larger
806scrollback 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
8076 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
808kilobyte 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)
809use 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
810rxvt-unicode then uses 8 bytes per screen cell. 908rxvt-unicode then uses 8 bytes per screen cell.
811.IP "Can I speed up Xft rendering somehow?" 4 909.Sh "Can I speed up Xft rendering somehow?"
812.IX Item "Can I speed up Xft rendering somehow?" 910.IX Subsection "Can I speed up Xft rendering somehow?"
813Yes, 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
814it 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
815antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of 913antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of
816memory and also speeds up rendering considerably. 914memory and also speeds up rendering considerably.
817.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?"
818.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?"
819Rxvt-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
820fall 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
821fonts, 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
822antialiasing disabled for most of them, because the author thinks they 920antialiasing disabled for most of them, because the author thinks they
823look best that way. 921look best that way.
824.Sp 922.PP
825If you want antialiasing, you have to specify the fonts manually. 923If you want antialiasing, you have to specify the fonts manually.
826.IP "Mouse cut/paste suddenly no longer works." 4 924.Sh "Mouse cut/paste suddenly no longer works."
827.IX Item "Mouse cut/paste suddenly no longer works." 925.IX Subsection "Mouse cut/paste suddenly no longer works."
828Make sure that mouse reporting is actually turned off since killing 926Make sure that mouse reporting is actually turned off since killing
829some 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
830heard that tcsh may use mouse reporting unless it otherwise specified. A 928heard that tcsh may use mouse reporting unless it otherwise specified. A
831quick 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
832depressed. 930depressed.
833.IP "What's with this bold/blink stuff?" 4 931.Sh "What's with this bold/blink stuff?"
834.IX Item "What's with this bold/blink stuff?" 932.IX Subsection "What's with this bold/blink stuff?"
835If 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
836standard foreground colour. 934standard foreground colour.
837.Sp 935.PP
838For the standard background colour, blinking will actually make the 936For the standard background colour, blinking will actually make the
839text 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
840colours. 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
841ignored. 939ignored.
842.Sp 940.PP
843On \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
844foreground/background colors. 942foreground/background colors.
845.Sp 943.PP
846color0\-7 are the low-intensity colors. 944color0\-7 are the low-intensity colors.
847.Sp 945.PP
848color8\-15 are the corresponding high-intensity colors. 946color8\-15 are the corresponding high-intensity colors.
849.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?"
850.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?"
851You 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
852resources (or as long\-options). 950resources (or as long\-options).
853.Sp 951.PP
854Here 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,
855including the murky brown that passes for low-intensity yellow: 953including the murky brown that passes for low-intensity yellow:
856.Sp 954.PP
857.Vb 8 955.Vb 8
858\& URxvt.color0: #000000 956\& URxvt.color0: #000000
859\& URxvt.color1: #A80000 957\& URxvt.color1: #A80000
860\& URxvt.color2: #00A800 958\& URxvt.color2: #00A800
861\& URxvt.color3: #A8A800 959\& URxvt.color3: #A8A800
862\& URxvt.color4: #0000A8 960\& URxvt.color4: #0000A8
863\& URxvt.color5: #A800A8 961\& URxvt.color5: #A800A8
864\& URxvt.color6: #00A8A8 962\& URxvt.color6: #00A8A8
865\& URxvt.color7: #A8A8A8 963\& URxvt.color7: #A8A8A8
866.Ve 964.Ve
867.Sp 965.PP
868.Vb 8 966.Vb 8
869\& URxvt.color8: #000054 967\& URxvt.color8: #000054
870\& URxvt.color9: #FF0054 968\& URxvt.color9: #FF0054
871\& URxvt.color10: #00FF54 969\& URxvt.color10: #00FF54
872\& URxvt.color11: #FFFF54 970\& URxvt.color11: #FFFF54
873\& URxvt.color12: #0000FF 971\& URxvt.color12: #0000FF
874\& URxvt.color13: #FF00FF 972\& URxvt.color13: #FF00FF
875\& URxvt.color14: #00FFFF 973\& URxvt.color14: #00FFFF
876\& URxvt.color15: #FFFFFF 974\& URxvt.color15: #FFFFFF
877.Ve 975.Ve
878.Sp 976.PP
879And 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
880me) as \*(L"pretty girly\*(R". 978me) as \*(L"pretty girly\*(R".
881.Sp 979.PP
882.Vb 18 980.Vb 18
883\& URxvt.cursorColor: #dc74d1 981\& URxvt.cursorColor: #dc74d1
884\& URxvt.pointerColor: #dc74d1 982\& URxvt.pointerColor: #dc74d1
885\& URxvt.background: #0e0e0e 983\& URxvt.background: #0e0e0e
886\& URxvt.foreground: #4ad5e1 984\& URxvt.foreground: #4ad5e1
… …
897\& URxvt.color6: #73f7ff 995\& URxvt.color6: #73f7ff
898\& URxvt.color14: #73f7ff 996\& URxvt.color14: #73f7ff
899\& URxvt.color7: #e1dddd 997\& URxvt.color7: #e1dddd
900\& URxvt.color15: #e1dddd 998\& URxvt.color15: #e1dddd
901.Ve 999.Ve
902.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?"
903.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?"
904Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the 1002Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the
905display, create the listening socket and then fork. 1003display, create the listening socket and then fork.
906.IP "What's with the strange Backspace/Delete key behaviour?" 4 1004.Sh "What's with the strange Backspace/Delete key behaviour?"
907.IX Item "What's with the strange Backspace/Delete key behaviour?" 1005.IX Subsection "What's with the strange Backspace/Delete key behaviour?"
908Assuming that the physical Backspace key corresponds to the 1006Assuming that the physical Backspace key corresponds to the
909BackSpace keysym (not likely for Linux ... see the following 1007BackSpace keysym (not likely for Linux ... see the following
910question) there are two standard values that can be used for 1008question) there are two standard values that can be used for
911Backspace: \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.
912.Sp 1010.PP
913Historically, either value is correct, but rxvt-unicode adopts the debian 1011Historically, either value is correct, but rxvt-unicode adopts the debian
914policy 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
915choice :). 1013choice :).
916.Sp 1014.PP
917Rxvt-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
918of `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
919started 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
920system 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
921be used (which may not be the same as your stty setting). 1019be used (which may not be the same as your stty setting).
922.Sp 1020.PP
923For starting a new rxvt\-unicode: 1021For starting a new rxvt\-unicode:
924.Sp 1022.PP
925.Vb 3 1023.Vb 3
926\& # use Backspace = ^H 1024\& # use Backspace = ^H
927\& $ stty erase ^H 1025\& $ stty erase ^H
928\& $ @@RXVT_NAME@@ 1026\& $ @@RXVT_NAME@@
929.Ve 1027.Ve
930.Sp 1028.PP
931.Vb 3 1029.Vb 3
932\& # use Backspace = ^? 1030\& # use Backspace = ^?
933\& $ stty erase ^? 1031\& $ stty erase ^?
934\& $ @@RXVT_NAME@@ 1032\& $ @@RXVT_NAME@@
935.Ve 1033.Ve
936.Sp 1034.PP
937Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. 1035Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR.
938.Sp 1036.PP
939For an existing rxvt\-unicode: 1037For an existing rxvt\-unicode:
940.Sp 1038.PP
941.Vb 3 1039.Vb 3
942\& # use Backspace = ^H 1040\& # use Backspace = ^H
943\& $ stty erase ^H 1041\& $ stty erase ^H
944\& $ echo -n "^[[36h" 1042\& $ echo -n "^[[36h"
945.Ve 1043.Ve
946.Sp 1044.PP
947.Vb 3 1045.Vb 3
948\& # use Backspace = ^? 1046\& # use Backspace = ^?
949\& $ stty erase ^? 1047\& $ stty erase ^?
950\& $ echo -n "^[[36l" 1048\& $ echo -n "^[[36l"
951.Ve 1049.Ve
952.Sp 1050.PP
953This helps satisfy some of the Backspace discrepancies that occur, but 1051This helps satisfy some of the Backspace discrepancies that occur, but
954if 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
955properly reflects that. 1053properly reflects that.
956.Sp 1054.PP
957The 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.
958To avoid confusion between the Backspace and Delete keys, the Delete 1056To avoid confusion between the Backspace and Delete keys, the Delete
959key 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
960(\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.
961.Sp 1059.PP
962Some other Backspace problems: 1060Some other Backspace problems:
963.Sp 1061.PP
964some editors use termcap/terminfo, 1062some editors use termcap/terminfo,
965some editors (vim I'm told) expect Backspace = ^H, 1063some editors (vim I'm told) expect Backspace = ^H,
966\&\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.
967.Sp 1065.PP
968Perhaps someday this will all be resolved in a consistent manner. 1066Perhaps someday this will all be resolved in a consistent manner.
969.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?"
970.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?"
971There are some compile-time selections available via configure. Unless 1069There are some compile-time selections available via configure. Unless
972you 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
973use the `keysym' resource to alter the keystrings associated with keysyms. 1071use the `keysym' resource to alter the keystrings associated with keysyms.
974.Sp 1072.PP
975Here'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
976.Sp 1074.PP
977.Vb 20 1075.Vb 20
978\& URxvt.keysym.Home: \e033[1~ 1076\& URxvt.keysym.Home: \e033[1~
979\& URxvt.keysym.End: \e033[4~ 1077\& URxvt.keysym.End: \e033[4~
980\& URxvt.keysym.C-apostrophe: \e033<C-'> 1078\& URxvt.keysym.C-apostrophe: \e033<C-'>
981\& URxvt.keysym.C-slash: \e033<C-/> 1079\& URxvt.keysym.C-slash: \e033<C-/>
… …
994\& URxvt.keysym.M-Right: \e033<M-Right> 1092\& URxvt.keysym.M-Right: \e033<M-Right>
995\& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 > 1093\& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 >
996\& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz > 1094\& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz >
997\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007 1095\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007
998.Ve 1096.Ve
999.Sp 1097.PP
1000See some more examples in the documentation for the \fBkeysym\fR resource. 1098See some more examples in the documentation for the \fBkeysym\fR resource.
1001.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."
1002.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."
1003.Vb 6 1101.Vb 6
1004\& KP_Insert == Insert 1102\& KP_Insert == Insert
1005\& F22 == Print 1103\& F22 == Print
1006\& F27 == Home 1104\& F27 == Home
1007\& F29 == Prior 1105\& F29 == Prior
1008\& F33 == End 1106\& F33 == End
1009\& F35 == Next 1107\& F35 == Next
1010.Ve 1108.Ve
1011.Sp 1109.PP
1012Rather than have rxvt-unicode try to accommodate all the various possible 1110Rather than have rxvt-unicode try to accommodate all the various possible
1013keyboard 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
1014required for your particular machine. 1112required for your particular machine.
1015.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."
1016.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."
1017rxvt 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
1018check 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,
1019Midnight Commander automatically check this variable to decide whether or 1117Midnight Commander automatically check this variable to decide whether or
1020not to use color. 1118not to use color.
1021.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?"
1022.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?"
1023If 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
1024insecure mode then it is possible to use the following shell script 1122insecure mode then it is possible to use the following shell script
1025snippets to correctly set the display. If your version of rxvt-unicode 1123snippets to correctly set the display. If your version of rxvt-unicode
1026wasn'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
1027the \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
1028regular xterm. 1126regular xterm.
1029.Sp 1127.PP
1030Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script 1128Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
1031snippets: 1129snippets:
1032.Sp 1130.PP
1033.Vb 12 1131.Vb 12
1034\& # Bourne/Korn/POSIX family of shells: 1132\& # Bourne/Korn/POSIX family of shells:
1035\& [ ${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
1036\& if [ ${TERM:-foo} = xterm ]; then 1134\& if [ ${TERM:-foo} = xterm ]; then
1037\& 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
… …
1042\& 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
1043\& read DISPLAY # set it in our local shell 1141\& read DISPLAY # set it in our local shell
1044\& fi 1142\& fi
1045\& fi 1143\& fi
1046.Ve 1144.Ve
1047.IP "How do I compile the manual pages for myself?" 4 1145.Sh "How do I compile the manual pages for myself?"
1048.IX Item "How do I compile the manual pages for myself?" 1146.IX Subsection "How do I compile the manual pages for myself?"
1049You 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,
1050one 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
1051the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR. 1149the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR.
1052.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?"
1053.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?"
1054Before 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,
1055channel \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
1056interested in learning about new and exciting problems (but not FAQs :). 1154interested in learning about new and exciting problems (but not FAQs :).
1057.SH "RXVT TECHNICAL REFERENCE" 1155.SH "RXVT TECHNICAL REFERENCE"
1058.IX Header "RXVT TECHNICAL REFERENCE" 1156.IX Header "RXVT TECHNICAL REFERENCE"
… …
1811Ps = 12 Change colour of text cursor foreground to Pt 1909Ps = 12 Change colour of text cursor foreground to Pt
1812Ps = 13 Change colour of mouse foreground to Pt 1910Ps = 13 Change colour of mouse foreground to Pt
1813Ps = 17 Change colour of highlight characters to Pt 1911Ps = 17 Change colour of highlight characters to Pt
1814Ps = 18 Change colour of bold characters to Pt [deprecated, see 706] 1912Ps = 18 Change colour of bold characters to Pt [deprecated, see 706]
1815Ps = 19 Change colour of underlined characters to Pt [deprecated, see 707] 1913Ps = 19 Change colour of underlined characters to Pt [deprecated, see 707]
1816Ps = 20 Change default background to Pt 1914Ps = 20 Change background pixmap parameters (see section XPM) (Compile XPM).
1817Ps = 39 Change default foreground colour to Pt. 1915Ps = 39 Change default foreground colour to Pt.
1818Ps = 46 Change Log File to Pt unimplemented 1916Ps = 46 Change Log File to Pt unimplemented
1819Ps = 49 Change default background colour to Pt. 1917Ps = 49 Change default background colour to Pt.
1820Ps = 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
1821Ps = 55 Log all scrollback buffer and all of screen to Pt 1919Ps = 55 Log all scrollback buffer and all of screen to Pt
1822Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills). 1920Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).
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.
1823Ps = 704 Change colour of italic characters to Pt 1922Ps = 704 Change colour of italic characters to Pt
1824Ps = 705 Change background pixmap tint colour to Pt (Compile transparency). 1923Ps = 705 Change background pixmap tint colour to Pt (Compile transparency).
1825Ps = 706 Change colour of bold characters to Pt 1924Ps = 706 Change colour of bold characters to Pt
1826Ps = 707 Change colour of underlined characters to Pt 1925Ps = 707 Change colour of underlined characters to Pt
1827Ps = 710 Set normal fontset to Pt. Same as Ps = 50. 1926Ps = 710 Set normal fontset to Pt. Same as Ps = 50.
… …
2045Add 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
2046alternative input methods (e.g. kinput2) and will also correctly 2145alternative input methods (e.g. kinput2) and will also correctly
2047set up the input for people using dead keys or compose keys. 2146set up the input for people using dead keys or compose keys.
2048.IP "\-\-enable\-unicode3 (default: off)" 4 2147.IP "\-\-enable\-unicode3 (default: off)" 4
2049.IX Item "--enable-unicode3 (default: off)" 2148.IX Item "--enable-unicode3 (default: off)"
2149Recommended to stay off unless you really need non-BMP characters.
2150.Sp
2050Enable direct support for displaying unicode codepoints above 2151Enable direct support for displaying unicode codepoints above
205165535 (the basic multilingual page). This increases storage 215265535 (the basic multilingual page). This increases storage
2052requirements 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
2053support these extra characters, but Xft does. 2154support these extra characters, but Xft does.
2054.Sp 2155.Sp
… …
2063composite characters. This is required for proper viewing of text 2164composite characters. This is required for proper viewing of text
2064where accents are encoded as seperate unicode characters. This is 2165where accents are encoded as seperate unicode characters. This is
2065done by using precomposited characters when available or creating 2166done by using precomposited characters when available or creating
2066new pseudo-characters when no precomposed form exists. 2167new pseudo-characters when no precomposed form exists.
2067.Sp 2168.Sp
2068Without \-\-enable\-unicode3, the number of additional precomposed characters 2169Without \-\-enable\-unicode3, the number of additional precomposed
2069is rather limited (2048, if this is full, rxvt-unicode will use the 2170characters is somewhat limited (the 6400 private use characters will be
2070private use area, extending the number of combinations to 8448). With
2071\&\-\-enable\-unicode3, no practical limit exists. 2171(ab\-)used). With \-\-enable\-unicode3, no practical limit exists.
2072.Sp 2172.Sp
2073This option will also enable storage (but not display) of characters 2173This option will also enable storage (but not display) of characters
2074beyond plane 0 (>65535) when \-\-enable\-unicode3 was not specified. 2174beyond plane 0 (>65535) when \-\-enable\-unicode3 was not specified.
2075.Sp 2175.Sp
2076The combining table also contains entries for arabic presentation forms, 2176The combining table also contains entries for arabic presentation forms,
2077but 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
2078tell me how these are to be used...). 2178tell me how these are to be used...).
2079.IP "\-\-enable\-fallback(=CLASS) (default: Rxvt)" 4 2179.IP "\-\-enable\-fallback(=CLASS) (default: Rxvt)" 4
2080.IX Item "--enable-fallback(=CLASS) (default: Rxvt)" 2180.IX Item "--enable-fallback(=CLASS) (default: Rxvt)"
2081When reading resource settings, also read settings for class \s-1CLASS\s0. To disable resource fallback use \-\-disable\-fallback. 2181When reading resource settings, also read settings for class \s-1CLASS\s0. To
2182disable resource fallback use \-\-disable\-fallback.
2082.IP "\-\-with\-res\-name=NAME (default: urxvt)" 4 2183.IP "\-\-with\-res\-name=NAME (default: urxvt)" 4
2083.IX Item "--with-res-name=NAME (default: urxvt)" 2184.IX Item "--with-res-name=NAME (default: urxvt)"
2084Use the given name as default application name when 2185Use the given name as default application name when
2085reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt. 2186reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt.
2086.IP "\-\-with\-res\-class=CLASS /default: URxvt)" 4 2187.IP "\-\-with\-res\-class=CLASS /default: URxvt)" 4
… …
2127.IP "\-\-enable\-plain\-scroll (default: on)" 4 2228.IP "\-\-enable\-plain\-scroll (default: on)" 4
2128.IX Item "--enable-plain-scroll (default: on)" 2229.IX Item "--enable-plain-scroll (default: on)"
2129Add support for a very unobtrusive, plain-looking scrollbar that 2230Add support for a very unobtrusive, plain-looking scrollbar that
2130is the favourite of the rxvt-unicode author, having used it for 2231is the favourite of the rxvt-unicode author, having used it for
2131many years. 2232many years.
2132.IP "\-\-enable\-half\-shadow (default: off)" 4
2133.IX Item "--enable-half-shadow (default: off)"
2134Make shadows on the scrollbar only half the normal width & height.
2135only applicable to rxvt scrollbars.
2136.IP "\-\-enable\-ttygid (default: off)" 4 2233.IP "\-\-enable\-ttygid (default: off)" 4
2137.IX Item "--enable-ttygid (default: off)" 2234.IX Item "--enable-ttygid (default: off)"
2138Change 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
2139your system uses this type of security. 2236your system uses this type of security.
2140.IP "\-\-disable\-backspace\-key" 4 2237.IP "\-\-disable\-backspace\-key" 4
… …
2157disable this. 2254disable this.
2158.Sp 2255.Sp
2159A 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
2160in combination with other switches) is: 2257in combination with other switches) is:
2161.Sp 2258.Sp
2162.Vb 17 2259.Vb 15
2163\& MWM-hints 2260\& MWM-hints
2164\& EWMH-hints (pid, utf8 names) and protocols (ping) 2261\& EWMH-hints (pid, utf8 names) and protocols (ping)
2165\& seperate underline colour (-underlineColor) 2262\& seperate underline colour (-underlineColor)
2166\& settable border widths and borderless switch (-w, -b, -bl) 2263\& settable border widths and borderless switch (-w, -b, -bl)
2264\& visual depth selection (-depth)
2167\& settable extra linespacing /-lsp) 2265\& settable extra linespacing /-lsp)
2168\& iso-14755-2 and -3, and visual feedback 2266\& iso-14755-2 and -3, and visual feedback
2169\& backindex and forwardindex escape sequence
2170\& window op and some xterm/OSC escape sequences
2171\& tripleclickwords (-tcw) 2267\& tripleclickwords (-tcw)
2172\& settable insecure mode (-insecure) 2268\& settable insecure mode (-insecure)
2173\& keysym remapping support 2269\& keysym remapping support
2174\& cursor blinking and underline cursor (-cb, -uc) 2270\& cursor blinking and underline cursor (-cb, -uc)
2175\& XEmbed support (-embed) 2271\& XEmbed support (-embed)
2176\& user-pty (-pty-fd) 2272\& user-pty (-pty-fd)
2177\& hold on exit (-hold) 2273\& hold on exit (-hold)
2178\& skip builtin block graphics (-sbg) 2274\& skip builtin block graphics (-sbg)
2275.Ve
2276.Sp
2277It also enabled some non-essential features otherwise disabled, such as:
2278.Sp
2279.Vb 11
2280\& some round-trip time optimisations
2281\& nearest color allocation on pseudocolor screens
2282\& UTF8_STRING supporr for selection
2179\& sgr modes 90..97 and 100..107 2283\& sgr modes 90..97 and 100..107
2284\& backindex and forwardindex escape sequences
2285\& view change/zero scorllback esacpe sequences
2286\& locale switching escape sequence
2287\& window op and some xterm/OSC escape sequences
2288\& rectangular selections
2289\& trailing space removal for selections
2290\& verbose X error handling
2180.Ve 2291.Ve
2181.IP "\-\-enable\-iso14755 (default: on)" 4 2292.IP "\-\-enable\-iso14755 (default: on)" 4
2182.IX Item "--enable-iso14755 (default: on)" 2293.IX Item "--enable-iso14755 (default: on)"
2183Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or 2294Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or
2184\&\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
… …
2218keys. This should keep the window corner which is closest to a corner of 2329keys. This should keep the window corner which is closest to a corner of
2219the screen in a fixed position. 2330the screen in a fixed position.
2220.IP "\-\-enable\-pointer\-blank (default: on)" 4 2331.IP "\-\-enable\-pointer\-blank (default: on)" 4
2221.IX Item "--enable-pointer-blank (default: on)" 2332.IX Item "--enable-pointer-blank (default: on)"
2222Add support to have the pointer disappear when typing or inactive. 2333Add support to have the pointer disappear when typing or inactive.
2223.IP "\-\-enable\-perl (default: off)" 4 2334.IP "\-\-enable\-perl (default: on)" 4
2224.IX Item "--enable-perl (default: off)" 2335.IX Item "--enable-perl (default: on)"
2225Enable an embedded perl interpreter. See the \fB@@RXVT_NAME@@\f(BIperl\fB\|(3)\fR 2336Enable an embedded perl interpreter. See the \fB@@RXVT_NAME@@\f(BIperl\fB\|(3)\fR
2226manpage (\fIdoc/rxvtperl.txt\fR) for more info on this feature, or the files 2337manpage (\fIdoc/rxvtperl.txt\fR) for more info on this feature, or the files
2227in \fIsrc/perl\-ext/\fR for the extensions that are installed by default. The 2338in \fIsrc/perl\-ext/\fR for the extensions that are installed by default. The
2228perl interpreter that is used can be specified via the \f(CW\*(C`PERL\*(C'\fR environment 2339perl interpreter that is used can be specified via the \f(CW\*(C`PERL\*(C'\fR environment
2229variable when running configure. 2340variable when running configure.

Diff Legend

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