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.50 by root, Thu Jan 19 19:26:31 2006 UTC vs.
Revision 1.59 by root, Tue Jan 31 00:57:35 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-19" "7.1" "RXVT-UNICODE" 132.TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE"
133.SH "NAME" 133.SH "NAME"
134RXVT REFERENCE \- FAQ, command sequences and other background information 134RXVT REFERENCE \- FAQ, command sequences and other background information
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137.Vb 2 137.Vb 2
… …
151.SH "DESCRIPTION" 151.SH "DESCRIPTION"
152.IX Header "DESCRIPTION" 152.IX Header "DESCRIPTION"
153This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting 153This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting
154all escape sequences, and other background information. 154all escape sequences, and other background information.
155.PP 155.PP
156The newest version of this document is 156The newest version of this document is also available on the World Wide Web at
157also available on the World Wide Web at
158<http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>. 157<http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>.
159.SH "FREQUENTLY ASKED QUESTIONS" 158.SH "FREQUENTLY ASKED QUESTIONS"
160.IX Header "FREQUENTLY ASKED QUESTIONS" 159.IX Header "FREQUENTLY ASKED QUESTIONS"
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.Sh "The cursor moves when selecting text in the current input line, how do I switch this off?"
205.IX Subsection "The cursor moves when selecting text in the current input line, how do I switch this off?"
206.Sh "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?"
207.IX Subsection "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?"
208These are caused by the \f(CW\*(C`readline\*(C'\fR perl extension. Under normal
209circumstances, it will move your cursor around when you click into the
210line that contains it. It tries hard not to do this at the wrong moment,
211but when running a program that doesn't parse cursor movements or in some
212cases during rlogin sessions, it fails to detect this properly.
213.PP
214You can permamently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR
215extension:
216.PP
217.Vb 1
218\& URxvt.perl-ext-common: default,-readline
219.Ve
220.Sh "Why doesn't rxvt-unicode read my resources?"
221.IX Subsection "Why doesn't rxvt-unicode read my resources?"
222Well, why, indeed? It does, in a way very similar to other X
223applications. Most importantly, this means that if you or your \s-1OS\s0 loads
224resources into the X display (the right way to do it), rxvt-unicode will
225ignore any resource files in your home directory. It will only read
226\&\fI$HOME/.Xdefaults\fR when no resources are attached to the display.
227.PP
228If you have or use an \fI$HOME/.Xresources\fR file, chances are that
229resources are loaded into your X\-server. In this case, you have to
230re-login after every change (or run \fIxrdb \-merge \f(CI$HOME\fI/.Xresources\fR).
231.PP
232Also consider the form resources have to use:
233.PP
234.Vb 1
235\& URxvt.resource: value
236.Ve
237.PP
238If you want to use another form (there are lots of different ways of
239specifying resources), make sure you understand wether and why it
240works. If unsure, use the form above.
241.Sh "I can't get transparency working, what am I doing wrong?"
242.IX Subsection "I can't get transparency working, what am I doing wrong?"
243First of all, transparency isn't officially supported in rxvt\-unicode, so
244you are mostly on your own. Do not bug the author about it (but you may
245bug everybody else). Also, if you can't get it working consider it a rite
246of passage: ... and you failed.
247.PP
248Here are four ways to get transparency. \fBDo\fR read the manpage and option
249descriptions for the programs mentioned and rxvt\-unicode. Really, do it!
250.PP
2511. Use inheritPixmap:
252.PP
253.Vb 2
254\& Esetroot wallpaper.jpg
255\& @@RXVT_NAME@@ -ip -tint red -sh 40
256.Ve
257.PP
258That works. If you think it doesn't, you lack transparency and tinting
259support, or you are unable to read.
260.PP
2612. Use a simple pixmap and emulate pseudo\-transparency. This enables you
262to use effects other than tinting and shading: Just shade/tint/whatever
263your picture with gimp:
264.PP
265.Vb 2
266\& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
267\& @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background
268.Ve
269.PP
270That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you
271are unable to read.
272.PP
2733. Use an \s-1ARGB\s0 visual:
274.PP
275.Vb 1
276\& @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
277.Ve
278.PP
279This requires \s-1XFT\s0 support, and the support of your X\-server. If that
280doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't
281there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
282bugfixes and workarounds for Xft and Xlib to make it work, but that
283doesn't mean that your \s-1WM\s0 has the required kludges in place.
284.PP
2854. Use xcompmgr and let it do the job:
286.PP
287.Vb 2
288\& xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \e
289\& -set _NET_WM_WINDOW_OPACITY 0xc0000000
290.Ve
291.PP
292Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR
293by other values to change the degree of opacity. If it doesn't work and
294your server crashes, you got to keep the pieces.
205.IP "Isn't rxvt supposed to be small? Don't all those features bloat?" 4 295.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?" 296.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 297I 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 298bloat. 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 299that 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 300compiled 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 301with \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 302features unique to urxvt (locale, encoding conversion, iso14755 etc.) are
213already in use in this mode. 303already in use in this mode.
214.Sp 304.PP
215.Vb 3 305.Vb 3
216\& text data bss drs rss filename 306\& text data bss drs rss filename
217\& 98398 1664 24 15695 1824 rxvt --disable-everything 307\& 98398 1664 24 15695 1824 rxvt --disable-everything
218\& 188985 9048 66616 18222 1788 urxvt --disable-everything 308\& 188985 9048 66616 18222 1788 urxvt --disable-everything
219.Ve 309.Ve
220.Sp 310.PP
221When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft 311When 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 312and full locale/XIM support which are quite bloaty inside libX11 and my
223libc), the two diverge, but not unreasnobaly so. 313libc), the two diverge, but not unreasnobaly so.
224.Sp 314.PP
225.Vb 3 315.Vb 3
226\& text data bss drs rss filename 316\& text data bss drs rss filename
227\& 163431 2152 24 20123 2060 rxvt --enable-everything 317\& 163431 2152 24 20123 2060 rxvt --enable-everything
228\& 1035683 49680 66648 29096 3680 urxvt --enable-everything 318\& 1035683 49680 66648 29096 3680 urxvt --enable-everything
229.Ve 319.Ve
230.Sp 320.PP
231The very large size of the text section is explained by the east-asian 321The 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 322encoding 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 323and 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++ 324encodings. 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 325compiler 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 326memory). 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 327few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when
238not used. 328not used.
239.Sp 329.PP
240Of course, due to every character using two or four bytes instead of one, 330Of course, due to every character using two or four bytes instead of one,
241a large scrollback buffer will ultimately make rxvt-unicode use more 331a large scrollback buffer will ultimately make rxvt-unicode use more
242memory. 332memory.
243.Sp 333.PP
244Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this 334Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this
245still fares rather well. And compared to some monsters like gnome-terminal 335still fares rather well. And compared to some monsters like gnome-terminal
246(21152k + extra 4204k in separate processes) or konsole (22200k + extra 336(21152k + extra 4204k in separate processes) or konsole (22200k + extra
24743180k in daemons that stay around after exit, plus half a minute of 33743180k in daemons that stay around after exit, plus half a minute of
248startup time, including the hundreds of warnings it spits out), it fares 338startup time, including the hundreds of warnings it spits out), it fares
249extremely well *g*. 339extremely well *g*.
250.IP "Why \*(C+, isn't that unportable/bloated/uncool?" 4 340.Sh "Why \*(C+, isn't that unportable/bloated/uncool?"
251.IX Item "Why , isn't that unportable/bloated/uncool?" 341.IX Subsection "Why , isn't that unportable/bloated/uncool?"
252Is this a question? :) It comes up very often. The simple answer is: I had 342Is 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 343to 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 344of the time and effort (which is a scarce resource for me). Put even
255shorter: It simply wouldn't exist without \*(C+. 345shorter: It simply wouldn't exist without \*(C+.
256.Sp 346.PP
257My personal stance on this is that \*(C+ is less portable than C, but in 347My 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 348the case of rxvt-unicode this hardly matters, as its portability limits
259are defined by things like X11, pseudo terminals, locale support and unix 349are defined by things like X11, pseudo terminals, locale support and unix
260domain sockets, which are all less portable than \*(C+ itself. 350domain sockets, which are all less portable than \*(C+ itself.
261.Sp 351.PP
262Regarding the bloat, see the above question: It's easy to write programs 352Regarding 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 353in 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 354\&\*(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 355not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my
266system with a minimal config: 356system with a minimal config:
267.Sp 357.PP
268.Vb 4 358.Vb 4
269\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 359\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
270\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) 360\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000)
271\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) 361\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000)
272\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 362\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
273.Ve 363.Ve
274.Sp 364.PP
275And here is rxvt\-unicode: 365And here is rxvt\-unicode:
276.Sp 366.PP
277.Vb 5 367.Vb 5
278\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) 368\& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000)
279\& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) 369\& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000)
280\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) 370\& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000)
281\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) 371\& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000)
282\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 372\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
283.Ve 373.Ve
284.Sp 374.PP
285No large bloated libraries (of course, none were linked in statically), 375No large bloated libraries (of course, none were linked in statically),
286except maybe libX11 :) 376except maybe libX11 :)
287.IP "Does it support tabs, can I have a tabbed rxvt\-unicode?" 4 377.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?" 378.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 379Beginning with version 7.3, there is a perl extension that implements a
290tabbing functionality of many window managers or similar tabbing programs, 380simple tabbed terminal. It is installed by default, so any of these should
291and its embedding-features allow it to be embedded into other programs, 381give you tabs:
292as witnessed by \fIdoc/rxvt\-tabbed\fR or the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl 382.PP
293module, which features a tabbed urxvt (murxvt) terminal as an example 383.Vb 1
294embedding application. 384\& @@RXVT_NAME@@ -pe tabbed
385.Ve
386.PP
387.Vb 1
388\& URxvt.perl-ext-common: default,tabbed
389.Ve
390.PP
391It will also work fine with tabbing functionality of many window managers
392or similar tabbing programs, and its embedding-features allow it to be
393embedded into other programs, as witnessed by \fIdoc/rxvt\-tabbed\fR or
394the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl module, which features a tabbed urxvt
395(murxvt) terminal as an example embedding application.
295.IP "How do I know which rxvt-unicode version I'm using?" 4 396.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?" 397.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 398The 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 399sequence \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 400using the @@RXVT_NAME@@c client, the version displayed is that of the
300daemon. 401daemon.
301.IP "I am using Debian GNU/Linux and have a problem..." 4 402.Sh "I am using Debian GNU/Linux and have a problem..."
302.IX Item "I am using Debian GNU/Linux and have a problem..." 403.IX Subsection "I am using Debian GNU/Linux and have a problem..."
303The Debian GNU/Linux package of rxvt-unicode in sarge contains large 404The Debian GNU/Linux package of rxvt-unicode in sarge contains large
304patches that considerably change the behaviour of rxvt-unicode (but 405patches that considerably change the behaviour of rxvt-unicode (but
305unfortunately this notice has been removed). Before reporting a bug to 406unfortunately this notice has been removed). Before reporting a bug to
306the original rxvt-unicode author please download and install the genuine 407the original rxvt-unicode author please download and install the genuine
307version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce 408version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce
308the problem. If you cannot, chances are that the problems are specific to 409the problem. If you cannot, chances are that the problems are specific to
309Debian GNU/Linux, in which case it should be reported via the Debian Bug 410Debian GNU/Linux, in which case it should be reported via the Debian Bug
310Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug). 411Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug).
311.Sp 412.PP
312For other problems that also affect the Debian package, you can and 413For 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 414probably 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 415bug in the Debian version and it serves as a reminder for other users that
315might encounter the same issue. 416might encounter the same issue.
316.IP "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?" 4 417.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?" 418.IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?"
318You should build one binary with the default options. \fIconfigure\fR 419You should build one binary with the default options. \fIconfigure\fR
319now enables most useful options, and the trend goes to making them 420now enables most useful options, and the trend goes to making them
320runtime\-switchable, too, so there is usually no drawback to enbaling them, 421runtime\-switchable, too, so there is usually no drawback to enbaling them,
321except higher disk and possibly memory usage. The perl interpreter should 422except higher disk and possibly memory usage. The perl interpreter should
322be enabled, as important functionality (menus, selection, likely more in 423be enabled, as important functionality (menus, selection, likely more in
323the future) depends on it. 424the future) depends on it.
324.Sp 425.PP
325You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources 426You 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 427system-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 428behaviour. 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 429\&\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. 430perl interpreter disabled until the user enables it.
330.Sp 431.PP
331If you can/want build more binaries, I recommend building a minimal 432If 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 433one 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 434\&\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). 435encodings 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 436.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?" 437.IX Subsection "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?"
337It should be, starting with release 7.1. You are encouraged to properly 438It should be, starting with release 7.1. You are encouraged to properly
338install urxvt with privileges necessary for your \s-1OS\s0 now. 439install urxvt with privileges necessary for your \s-1OS\s0 now.
339.Sp 440.PP
340When rxvt-unicode detects that it runs setuid or setgid, it will fork 441When rxvt-unicode detects that it runs setuid or setgid, it will fork
341into a helper process for privileged operations (pty handling on some 442into a helper process for privileged operations (pty handling on some
342systems, utmp/wtmp/lastlog handling on others) and drop privileges 443systems, utmp/wtmp/lastlog handling on others) and drop privileges
343immediately. This is much safer than most other terminals that keep 444immediately. This is much safer than most other terminals that keep
344privileges while running (but is more relevant to urxvt, as it contains 445privileges while running (but is more relevant to urxvt, as it contains
345things as perl interpreters, which might be \*(L"helpful\*(R" to attackers). 446things as perl interpreters, which might be \*(L"helpful\*(R" to attackers).
346.Sp 447.PP
347This forking is done as the very first within \fImain()\fR, which is very early 448This forking is done as the very first within \fImain()\fR, which is very early
348and reduces possible bugs to initialisation code run before \fImain()\fR, or 449and reduces possible bugs to initialisation code run before \fImain()\fR, or
349things like the dynamic loader of your system, which should result in very 450things like the dynamic loader of your system, which should result in very
350little risk. 451little risk.
351.IP "When I log-in to another system it tells me about missing terminfo data?" 4 452.Sh "When I log-in to another system it tells me about missing terminfo data?"
352.IX Item "When I log-in to another system it tells me about missing terminfo data?" 453.IX Subsection "When I log-in to another system it tells me about missing terminfo data?"
353The terminal description used by rxvt-unicode is not as widely available 454The terminal description used by rxvt-unicode is not as widely available
354as that for xterm, or even rxvt (for which the same problem often arises). 455as that for xterm, or even rxvt (for which the same problem often arises).
355.Sp 456.PP
356The correct solution for this problem is to install the terminfo, this can 457The correct solution for this problem is to install the terminfo, this can
357be done like this (with ncurses' infocmp): 458be done like this (with ncurses' infocmp):
358.Sp 459.PP
359.Vb 2 460.Vb 2
360\& REMOTE=remotesystem.domain 461\& REMOTE=remotesystem.domain
361\& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" 462\& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti"
362.Ve 463.Ve
363.Sp 464.PP
364\&... or by installing rxvt-unicode normally on the remote system, 465\&... or by installing rxvt-unicode normally on the remote system,
365.Sp 466.PP
366If you cannot or do not want to do this, then you can simply set 467If you cannot or do not want to do this, then you can simply set
367\&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of 468\&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of
368problems arising, which includes wrong keymapping, less and different 469problems arising, which includes wrong keymapping, less and different
369colours and some refresh errors in fullscreen applications. It's a nice 470colours and some refresh errors in fullscreen applications. It's a nice
370quick-and-dirty workaround for rare cases, though. 471quick-and-dirty workaround for rare cases, though.
371.Sp 472.PP
372If you always want to do this (and are fine with the consequences) you 473If you always want to do this (and are fine with the consequences) you
373can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a 474can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a
374resource to set it: 475resource to set it:
375.Sp 476.PP
376.Vb 1 477.Vb 1
377\& URxvt.termName: rxvt 478\& URxvt.termName: rxvt
378.Ve 479.Ve
379.Sp 480.PP
380If you don't plan to use \fBrxvt\fR (quite common...) you could also replace 481If you don't plan to use \fBrxvt\fR (quite common...) you could also replace
381the rxvt terminfo file with the rxvt-unicode one. 482the rxvt terminfo file with the rxvt-unicode one.
382.ie n .IP """tic"" outputs some error when compiling the terminfo entry." 4 483.ie n .Sh """tic"" outputs some error when compiling the terminfo entry."
383.el .IP "\f(CWtic\fR outputs some error when compiling the terminfo entry." 4 484.el .Sh "\f(CWtic\fP outputs some error when compiling the terminfo entry."
384.IX Item "tic outputs some error when compiling the terminfo entry." 485.IX Subsection "tic outputs some error when compiling the terminfo entry."
385Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by 486Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by
386\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. 487\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again.
387.ie n .IP """bash""'s readline does not work correctly under @@RXVT_NAME@@." 4 488.ie n .Sh """bash""'s readline does not work correctly under @@RXVT_NAME@@."
388.el .IP "\f(CWbash\fR's readline does not work correctly under @@RXVT_NAME@@." 4 489.el .Sh "\f(CWbash\fP's readline does not work correctly under @@RXVT_NAME@@."
389.IX Item "bash's readline does not work correctly under @@RXVT_NAME@@." 490.IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@."
390.PD 0
391.IP "I need a termcap file entry." 4 491.Sh "I need a termcap file entry."
392.IX Item "I need a termcap file entry." 492.IX Subsection "I need a termcap file entry."
393.PD
394One reason you might want this is that some distributions or operating 493One reason you might want this is that some distributions or operating
395systems still compile some programs using the long-obsoleted termcap 494systems still compile some programs using the long-obsoleted termcap
396library (Fedora Core's bash is one example) and rely on a termcap entry 495library (Fedora Core's bash is one example) and rely on a termcap entry
397for \f(CW\*(C`rxvt\-unicode\*(C'\fR. 496for \f(CW\*(C`rxvt\-unicode\*(C'\fR.
398.Sp 497.PP
399You could use rxvt's termcap entry with resonable results in many cases. 498You could use rxvt's termcap entry with resonable results in many cases.
400You can also create a termcap entry by using terminfo's infocmp program 499You can also create a termcap entry by using terminfo's infocmp program
401like this: 500like this:
402.Sp 501.PP
403.Vb 1 502.Vb 1
404\& infocmp -C rxvt-unicode 503\& infocmp -C rxvt-unicode
405.Ve 504.Ve
406.Sp 505.PP
407Or you could use this termcap entry, generated by the command above: 506Or you could use this termcap entry, generated by the command above:
408.Sp 507.PP
409.Vb 20 508.Vb 20
410\& rxvt-unicode|rxvt-unicode terminal (X Window System):\e 509\& rxvt-unicode|rxvt-unicode terminal (X Window System):\e
411\& :am:bw:eo:km:mi:ms:xn:xo:\e 510\& :am:bw:eo:km:mi:ms:xn:xo:\e
412\& :co#80:it#8:li#24:lm#0:\e 511\& :co#80:it#8:li#24:lm#0:\e
413\& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e 512\& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e
… …
426\& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e 525\& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e
427\& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e 526\& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e
428\& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e 527\& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e
429\& :vs=\eE[?25h: 528\& :vs=\eE[?25h:
430.Ve 529.Ve
431.ie n .IP "Why does ""ls"" no longer have coloured output?" 4 530.ie n .Sh "Why does ""ls"" no longer have coloured output?"
432.el .IP "Why does \f(CWls\fR no longer have coloured output?" 4 531.el .Sh "Why does \f(CWls\fP no longer have coloured output?"
433.IX Item "Why does ls no longer have coloured output?" 532.IX Subsection "Why does ls no longer have coloured output?"
434The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to 533The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to
435decide wether a terminal has colour, but uses it's own configuration 534decide wether a terminal has colour, but uses it's own configuration
436file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among 535file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among
437with most other terminals supporting colour). Either add: 536with most other terminals supporting colour). Either add:
438.Sp 537.PP
439.Vb 1 538.Vb 1
440\& TERM rxvt-unicode 539\& TERM rxvt-unicode
441.Ve 540.Ve
442.Sp 541.PP
443to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add: 542to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add:
444.Sp 543.PP
445.Vb 1 544.Vb 1
446\& alias ls='ls --color=auto' 545\& alias ls='ls --color=auto'
447.Ve 546.Ve
448.Sp 547.PP
449to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR. 548to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR.
450.IP "Why doesn't vim/emacs etc. use the 88 colour mode?" 4 549.Sh "Why doesn't vim/emacs etc. use the 88 colour mode?"
451.IX Item "Why doesn't vim/emacs etc. use the 88 colour mode?" 550.IX Subsection "Why doesn't vim/emacs etc. use the 88 colour mode?"
452.PD 0
453.IP "Why doesn't vim/emacs etc. make use of italic?" 4 551.Sh "Why doesn't vim/emacs etc. make use of italic?"
454.IX Item "Why doesn't vim/emacs etc. make use of italic?" 552.IX Subsection "Why doesn't vim/emacs etc. make use of italic?"
455.IP "Why are the secondary screen-related options not working properly?" 4 553.Sh "Why are the secondary screen-related options not working properly?"
456.IX Item "Why are the secondary screen-related options not working properly?" 554.IX Subsection "Why are the secondary screen-related options not working properly?"
457.PD
458Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged 555Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged
459distributions (most notably Debian GNU/Linux) break rxvt-unicode 556distributions (most notably Debian GNU/Linux) break rxvt-unicode
460by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra 557by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra
461features. Unfortunately, some of these (most notably, again, Debian 558features. Unfortunately, some of these (most notably, again, Debian
462GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo 559GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
463file, so you will need to install it on your own (See the question \fBWhen 560file, so you will need to install it on your own (See the question \fBWhen
464I log-in to another system it tells me about missing terminfo data?\fR on 561I log-in to another system it tells me about missing terminfo data?\fR on
465how to do this). 562how to do this).
466.IP "My numerical keypad acts weird and generates differing output?" 4 563.Sh "My numerical keypad acts weird and generates differing output?"
467.IX Item "My numerical keypad acts weird and generates differing output?" 564.IX Subsection "My numerical keypad acts weird and generates differing output?"
468Some Debian GNUL/Linux users seem to have this problem, although no 565Some Debian GNUL/Linux users seem to have this problem, although no
469specific details were reported so far. It is possible that this is caused 566specific details were reported so far. It is possible that this is caused
470by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how 567by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how
471this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible 568this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible
472keymap. See the answer to the previous question, and please report if that 569keymap. See the answer to the previous question, and please report if that
473helped. 570helped.
474.IP "Rxvt-unicode does not seem to understand the selected encoding?" 4 571.Sh "Rxvt-unicode does not seem to understand the selected encoding?"
475.IX Item "Rxvt-unicode does not seem to understand the selected encoding?" 572.IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?"
476.PD 0
477.IP "Unicode does not seem to work?" 4 573.Sh "Unicode does not seem to work?"
478.IX Item "Unicode does not seem to work?" 574.IX Subsection "Unicode does not seem to work?"
479.PD
480If you encounter strange problems like typing an accented character but 575If you encounter strange problems like typing an accented character but
481getting two unrelated other characters or similar, or if program output is 576getting two unrelated other characters or similar, or if program output is
482subtly garbled, then you should check your locale settings. 577subtly garbled, then you should check your locale settings.
483.Sp 578.PP
484Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the 579Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the
485programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the 580programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the
486login script running within the rxvt-unicode window changes the locale to 581login script running within the rxvt-unicode window changes the locale to
487something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work. 582something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work.
488.Sp 583.PP
489The best thing is to fix your startup environment, as you will likely run 584The best thing is to fix your startup environment, as you will likely run
490into other problems. If nothing works you can try this in your .profile. 585into other problems. If nothing works you can try this in your .profile.
491.Sp 586.PP
492.Vb 1 587.Vb 1
493\& printf '\ee]701;%s\e007' "$LC_CTYPE" 588\& printf '\ee]701;%s\e007' "$LC_CTYPE"
494.Ve 589.Ve
495.Sp 590.PP
496If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not 591If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not
497supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which 592supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which
498displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as 593displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as
499it will complain loudly if it cannot set the locale). If it displays something 594it will complain loudly if it cannot set the locale). If it displays something
500like: 595like:
501.Sp 596.PP
502.Vb 1 597.Vb 1
503\& locale: Cannot set LC_CTYPE to default locale: ... 598\& locale: Cannot set LC_CTYPE to default locale: ...
504.Ve 599.Ve
505.Sp 600.PP
506Then the locale you specified is not supported on your system. 601Then the locale you specified is not supported on your system.
507.Sp 602.PP
508If nothing works and you are sure that everything is set correctly then 603If nothing works and you are sure that everything is set correctly then
509you will need to remember a little known fact: Some programs just don't 604you will need to remember a little known fact: Some programs just don't
510support locales :( 605support locales :(
511.IP "Why do some characters look so much different than others?" 4 606.Sh "Why do some characters look so much different than others?"
512.IX Item "Why do some characters look so much different than others?" 607.IX Subsection "Why do some characters look so much different than others?"
513.PD 0
514.IP "How does rxvt-unicode choose fonts?" 4 608.Sh "How does rxvt-unicode choose fonts?"
515.IX Item "How does rxvt-unicode choose fonts?" 609.IX Subsection "How does rxvt-unicode choose fonts?"
516.PD
517Most fonts do not contain the full range of Unicode, which is 610Most fonts do not contain the full range of Unicode, which is
518fine. Chances are that the font you (or the admin/package maintainer of 611fine. Chances are that the font you (or the admin/package maintainer of
519your system/os) have specified does not cover all the characters you want 612your system/os) have specified does not cover all the characters you want
520to display. 613to display.
521.Sp 614.PP
522\&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement 615\&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement
523font. Often the result is fine, but sometimes the chosen font looks 616font. Often the result is fine, but sometimes the chosen font looks
524bad/ugly/wrong. Some fonts have totally strange characters that don't 617bad/ugly/wrong. Some fonts have totally strange characters that don't
525resemble the correct glyph at all, and rxvt-unicode lacks the artificial 618resemble the correct glyph at all, and rxvt-unicode lacks the artificial
526intelligence to detect that a specific glyph is wrong: it has to believe 619intelligence to detect that a specific glyph is wrong: it has to believe
527the font that the characters it claims to contain indeed look correct. 620the font that the characters it claims to contain indeed look correct.
528.Sp 621.PP
529In that case, select a font of your taste and add it to the font list, 622In that case, select a font of your taste and add it to the font list,
530e.g.: 623e.g.:
531.Sp 624.PP
532.Vb 1 625.Vb 1
533\& @@RXVT_NAME@@ -fn basefont,font2,font3... 626\& @@RXVT_NAME@@ -fn basefont,font2,font3...
534.Ve 627.Ve
535.Sp 628.PP
536When rxvt-unicode sees a character, it will first look at the base 629When rxvt-unicode sees a character, it will first look at the base
537font. If the base font does not contain the character, it will go to the 630font. If the base font does not contain the character, it will go to the
538next font, and so on. Specifying your own fonts will also speed up this 631next font, and so on. Specifying your own fonts will also speed up this
539search and use less resources within rxvt-unicode and the X\-server. 632search and use less resources within rxvt-unicode and the X\-server.
540.Sp 633.PP
541The only limitation is that none of the fonts may be larger than the base 634The only limitation is that none of the fonts may be larger than the base
542font, as the base font defines the terminal character cell size, which 635font, as the base font defines the terminal character cell size, which
543must be the same due to the way terminals work. 636must be the same due to the way terminals work.
544.IP "Why do some chinese characters look so different than others?" 4 637.Sh "Why do some chinese characters look so different than others?"
545.IX Item "Why do some chinese characters look so different than others?" 638.IX Subsection "Why do some chinese characters look so different than others?"
546This is because there is a difference between script and language \*(-- 639This is because there is a difference between script and language \*(--
547rxvt-unicode does not know which language the text that is output is, 640rxvt-unicode does not know which language the text that is output is,
548as it only knows the unicode character codes. If rxvt-unicode first 641as it only knows the unicode character codes. If rxvt-unicode first
549sees a japanese/chinese character, it might choose a japanese font for 642sees a japanese/chinese character, it might choose a japanese font for
550display. Subsequent japanese characters will use that font. Now, many 643display. Subsequent japanese characters will use that font. Now, many
551chinese characters aren't represented in japanese fonts, so when the first 644chinese characters aren't represented in japanese fonts, so when the first
552non-japanese character comes up, rxvt-unicode will look for a chinese font 645non-japanese character comes up, rxvt-unicode will look for a chinese font
553\&\*(-- unfortunately at this point, it will still use the japanese font for 646\&\*(-- unfortunately at this point, it will still use the japanese font for
554chinese characters that are also in the japanese font. 647chinese characters that are also in the japanese font.
555.Sp 648.PP
556The workaround is easy: just tag a chinese font at the end of your font 649The workaround is easy: just tag a chinese font at the end of your font
557list (see the previous question). The key is to view the font list as 650list (see the previous question). The key is to view the font list as
558a preference list: If you expect more japanese, list a japanese font 651a preference list: If you expect more japanese, list a japanese font
559first. If you expect more chinese, put a chinese font first. 652first. If you expect more chinese, put a chinese font first.
560.Sp 653.PP
561In the future it might be possible to switch language preferences at 654In the future it might be possible to switch language preferences at
562runtime (the internal data structure has no problem with using different 655runtime (the internal data structure has no problem with using different
563fonts for the same character at the same time, but no interface for this 656fonts for the same character at the same time, but no interface for this
564has been designed yet). 657has been designed yet).
565.Sp 658.PP
566Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document). 659Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document).
567.IP "Why does rxvt-unicode sometimes leave pixel droppings?" 4 660.Sh "Why does rxvt-unicode sometimes leave pixel droppings?"
568.IX Item "Why does rxvt-unicode sometimes leave pixel droppings?" 661.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"
569Most fonts were not designed for terminal use, which means that character 662Most fonts were not designed for terminal use, which means that character
570size varies a lot. A font that is otherwise fine for terminal use might 663size varies a lot. A font that is otherwise fine for terminal use might
571contain some characters that are simply too wide. Rxvt-unicode will avoid 664contain some characters that are simply too wide. Rxvt-unicode will avoid
572these characters. For characters that are just \*(L"a bit\*(R" too wide a special 665these characters. For characters that are just \*(L"a bit\*(R" too wide a special
573\&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters. 666\&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters.
574.Sp 667.PP
575All of this requires that fonts do not lie about character sizes, 668All of this requires that fonts do not lie about character sizes,
576however: Xft fonts often draw glyphs larger than their acclaimed bounding 669however: Xft fonts often draw glyphs larger than their acclaimed bounding
577box, and rxvt-unicode has no way of detecting this (the correct way is to 670box, and rxvt-unicode has no way of detecting this (the correct way is to
578ask for the character bounding box, which unfortunately is wrong in these 671ask for the character bounding box, which unfortunately is wrong in these
579cases). 672cases).
580.Sp 673.PP
581It's not clear (to me at least), wether this is a bug in Xft, freetype, 674It's not clear (to me at least), wether this is a bug in Xft, freetype,
582or the respective font. If you encounter this problem you might try using 675or the respective font. If you encounter this problem you might try using
583the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you 676the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you
584might be forced to use a different font. 677might be forced to use a different font.
585.Sp 678.PP
586All of this is not a problem when using X11 core fonts, as their bounding 679All of this is not a problem when using X11 core fonts, as their bounding
587box data is correct. 680box data is correct.
588.IP "On Solaris 9, many line-drawing characters are too wide." 4 681.Sh "On Solaris 9, many line-drawing characters are too wide."
589.IX Item "On Solaris 9, many line-drawing characters are too wide." 682.IX Subsection "On Solaris 9, many line-drawing characters are too wide."
590Seems to be a known bug, read 683Seems to be a known bug, read
591<http://nixdoc.net/files/forum/about34198.html>. Some people use the 684<http://nixdoc.net/files/forum/about34198.html>. Some people use the
592following ugly workaround to get non-double-wide-characters working: 685following ugly workaround to get non-double-wide-characters working:
593.Sp 686.PP
594.Vb 1 687.Vb 1
595\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) 688\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
596.Ve 689.Ve
597.IP "My Compose (Multi_key) key is no longer working." 4 690.Sh "My Compose (Multi_key) key is no longer working."
598.IX Item "My Compose (Multi_key) key is no longer working." 691.IX Subsection "My Compose (Multi_key) key is no longer working."
599The most common causes for this are that either your locale is not set 692The most common causes for this are that either your locale is not set
600correctly, or you specified a \fBpreeditStyle\fR that is not supported by 693correctly, or you specified a \fBpreeditStyle\fR that is not supported by
601your input method. For example, if you specified \fBOverTheSpot\fR and 694your input method. For example, if you specified \fBOverTheSpot\fR and
602your input method (e.g. the default input method handling Compose keys) 695your input method (e.g. the default input method handling Compose keys)
603does not support this (for instance because it is not visual), then 696does not support this (for instance because it is not visual), then
604rxvt-unicode will continue without an input method. 697rxvt-unicode will continue without an input method.
605.Sp 698.PP
606In this case either do not specify a \fBpreeditStyle\fR or specify more than 699In this case either do not specify a \fBpreeditStyle\fR or specify more than
607one pre-edit style, such as \fBOverTheSpot,Root,None\fR. 700one pre-edit style, such as \fBOverTheSpot,Root,None\fR.
608.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 701.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"
609.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 702.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"
610.IX Item "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755" 703.IX Subsection "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755"
611Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on 704Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on
612international keyboards) or simply use \s-1ISO\s0 14755 support to your 705international keyboards) or simply use \s-1ISO\s0 14755 support to your
613advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other 706advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other
614codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape 707codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape
615character and so on. 708character and so on.
616.IP "How can I keep rxvt-unicode from using reverse video so much?" 4 709.Sh "How can I keep rxvt-unicode from using reverse video so much?"
617.IX Item "How can I keep rxvt-unicode from using reverse video so much?" 710.IX Subsection "How can I keep rxvt-unicode from using reverse video so much?"
618First of all, make sure you are running with the right terminal settings 711First of all, make sure you are running with the right terminal settings
619(\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then 712(\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then
620make sure you have specified colours for italic and bold, as otherwise 713make sure you have specified colours for italic and bold, as otherwise
621rxvt-unicode might use reverse video to simulate the effect: 714rxvt-unicode might use reverse video to simulate the effect:
622.Sp 715.PP
623.Vb 2 716.Vb 2
624\& URxvt.colorBD: white 717\& URxvt.colorBD: white
625\& URxvt.colorIT: green 718\& URxvt.colorIT: green
626.Ve 719.Ve
627.IP "Some programs assume totally weird colours (red instead of blue), how can I fix that?" 4 720.Sh "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
628.IX Item "Some programs assume totally weird colours (red instead of blue), how can I fix that?" 721.IX Subsection "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
629For some unexplainable reason, some rare programs assume a very weird 722For some unexplainable reason, some rare programs assume a very weird
630colour palette when confronted with a terminal with more than the standard 723colour palette when confronted with a terminal with more than the standard
6318 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix 7248 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix
632these programs not to assume non-ISO colours without very good reasons. 725these programs not to assume non-ISO colours without very good reasons.
633.Sp 726.PP
634In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo 727In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
635definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will 728definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will
636fix colours but keep you from using other rxvt-unicode features. 729fix colours but keep you from using other rxvt-unicode features.
637.IP "I am on FreeBSD and rxvt-unicode does not seem to work at all." 4 730.Sh "I am on FreeBSD and rxvt-unicode does not seem to work at all."
638.IX Item "I am on FreeBSD and rxvt-unicode does not seem to work at all." 731.IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all."
639Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined 732Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined
640in your compile environment, or an implementation that implements it, 733in your compile environment, or an implementation that implements it,
641wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that 734wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that
642\&\fBwchar_t\fR is represented as unicode. 735\&\fBwchar_t\fR is represented as unicode.
643.Sp 736.PP
644As you might have guessed, FreeBSD does neither define this symobl nor 737As you might have guessed, FreeBSD does neither define this symobl nor
645does it support it. Instead, it uses it's own internal representation of 738does it support it. Instead, it uses it's own internal representation of
646\&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. 739\&\fBwchar_t\fR. This is, of course, completely fine with respect to standards.
647.Sp 740.PP
648However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and 741However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and
649\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. 742\&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR.
650.Sp 743.PP
651\&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language 744\&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language
652apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized) 745apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized)
653representation of \fBwchar_t\fR makes it impossible to convert between 746representation of \fBwchar_t\fR makes it impossible to convert between
654\&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding 747\&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding
655without implementing OS-specific-wrappers for each and every locale. There 748without implementing OS-specific-wrappers for each and every locale. There
656simply are no APIs to convert \fBwchar_t\fR into anything except the current 749simply are no APIs to convert \fBwchar_t\fR into anything except the current
657locale encoding. 750locale encoding.
658.Sp 751.PP
659Some applications (such as the formidable \fBmlterm\fR) work around this 752Some applications (such as the formidable \fBmlterm\fR) work around this
660by carrying their own replacement functions for character set handling 753by carrying their own replacement functions for character set handling
661with them, and either implementing OS-dependent hacks or doing multiple 754with them, and either implementing OS-dependent hacks or doing multiple
662conversions (which is slow and unreliable in case the \s-1OS\s0 implements 755conversions (which is slow and unreliable in case the \s-1OS\s0 implements
663encodings slightly different than the terminal emulator). 756encodings slightly different than the terminal emulator).
664.Sp 757.PP
665The rxvt-unicode author insists that the right way to fix this is in the 758The rxvt-unicode author insists that the right way to fix this is in the
666system libraries once and for all, instead of forcing every app to carry 759system libraries once and for all, instead of forcing every app to carry
667complete replacements for them :) 760complete replacements for them :)
668.IP "I use Solaris 9 and it doesn't compile/work/etc." 4 761.Sh "I use Solaris 9 and it doesn't compile/work/etc."
669.IX Item "I use Solaris 9 and it doesn't compile/work/etc." 762.IX Subsection "I use Solaris 9 and it doesn't compile/work/etc."
670Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst 763Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst
671problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem. 764problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem.
672.IP "How can I use rxvt-unicode under cygwin?" 4 765.Sh "How can I use rxvt-unicode under cygwin?"
673.IX Item "How can I use rxvt-unicode under cygwin?" 766.IX Subsection "How can I use rxvt-unicode under cygwin?"
674rxvt-unicode should compile and run out of the box on cygwin, using 767rxvt-unicode should compile and run out of the box on cygwin, using
675the X11 libraries that come with cygwin. libW11 emulation is no 768the X11 libraries that come with cygwin. libW11 emulation is no
676longer supported (and makes no sense, either, as it only supported a 769longer supported (and makes no sense, either, as it only supported a
677single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or 770single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or
678\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the 771\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the
679old libW11 emulation. 772old libW11 emulation.
680.Sp 773.PP
681At the time of this writing, cygwin didn't seem to support any multi-byte 774At the time of this writing, cygwin didn't seem to support any multi-byte
682encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited 775encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited
683to 8\-bit encodings. 776to 8\-bit encodings.
684.IP "How does rxvt-unicode determine the encoding to use?" 4 777.Sh "How does rxvt-unicode determine the encoding to use?"
685.IX Item "How does rxvt-unicode determine the encoding to use?" 778.IX Subsection "How does rxvt-unicode determine the encoding to use?"
686.PD 0
687.IP "Is there an option to switch encodings?" 4 779.Sh "Is there an option to switch encodings?"
688.IX Item "Is there an option to switch encodings?" 780.IX Subsection "Is there an option to switch encodings?"
689.PD
690Unlike some other terminals, rxvt-unicode has no encoding switch, and no 781Unlike some other terminals, rxvt-unicode has no encoding switch, and no
691specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about 782specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about
692\&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O. 783\&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O.
693.Sp 784.PP
694The reasons is that there exists a perfectly fine mechanism for selecting 785The reasons is that there exists a perfectly fine mechanism for selecting
695the encoding, doing I/O and (most important) communicating this to all 786the encoding, doing I/O and (most important) communicating this to all
696applications so everybody agrees on character properties such as width 787applications so everybody agrees on character properties such as width
697and code number. This mechanism is the \fIlocale\fR. Applications not using 788and code number. This mechanism is the \fIlocale\fR. Applications not using
698that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of 789that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of
699characters wrong as it uses it's own, locale-independent table under all 790characters wrong as it uses it's own, locale-independent table under all
700locales). 791locales).
701.Sp 792.PP
702Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All 793Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All
703programs doing the same (that is, most) will automatically agree in the 794programs doing the same (that is, most) will automatically agree in the
704interpretation of characters. 795interpretation of characters.
705.Sp 796.PP
706Unfortunately, there is no system-independent way to select locales, nor 797Unfortunately, there is no system-independent way to select locales, nor
707is there a standard on how locale specifiers will look like. 798is there a standard on how locale specifiers will look like.
708.Sp 799.PP
709On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable 800On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable
710contains an arbitrary string which corresponds to an already-installed 801contains an arbitrary string which corresponds to an already-installed
711locale. Common names for locales are \f(CW\*(C`en_US.UTF\-8\*(C'\fR, \f(CW\*(C`de_DE.ISO\-8859\-15\*(C'\fR, 802locale. Common names for locales are \f(CW\*(C`en_US.UTF\-8\*(C'\fR, \f(CW\*(C`de_DE.ISO\-8859\-15\*(C'\fR,
712\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms 803\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms
713(i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common. 804(i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common.
714.Sp 805.PP
715Rxvt-unicode ignores all other locale categories, and except for 806Rxvt-unicode ignores all other locale categories, and except for
716the encoding, ignores country or language-specific settings, 807the encoding, ignores country or language-specific settings,
717i.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 808i.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
718rxvt\-unicode. 809rxvt\-unicode.
719.Sp 810.PP
720If you want to use a specific encoding you have to make sure you start 811If you want to use a specific encoding you have to make sure you start
721rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category. 812rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category.
722.IP "Can I switch locales at runtime?" 4 813.Sh "Can I switch locales at runtime?"
723.IX Item "Can I switch locales at runtime?" 814.IX Subsection "Can I switch locales at runtime?"
724Yes, using an escape sequence. Try something like this, which sets 815Yes, using an escape sequence. Try something like this, which sets
725rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR. 816rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR.
726.Sp 817.PP
727.Vb 1 818.Vb 1
728\& printf '\ee]701;%s\e007' ja_JP.SJIS 819\& printf '\ee]701;%s\e007' ja_JP.SJIS
729.Ve 820.Ve
730.Sp 821.PP
731See also the previous answer. 822See also the previous answer.
732.Sp 823.PP
733Sometimes this capability is rather handy when you want to work in 824Sometimes this capability is rather handy when you want to work in
734one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it 825one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it
735(e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which 826(e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which
736first switches to a locale supported by xjdic and back later: 827first switches to a locale supported by xjdic and back later:
737.Sp 828.PP
738.Vb 3 829.Vb 3
739\& printf '\ee]701;%s\e007' ja_JP.SJIS 830\& printf '\ee]701;%s\e007' ja_JP.SJIS
740\& xjdic -js 831\& xjdic -js
741\& printf '\ee]701;%s\e007' de_DE.UTF-8 832\& printf '\ee]701;%s\e007' de_DE.UTF-8
742.Ve 833.Ve
743.Sp 834.PP
744You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except 835You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except
745for some locales where character width differs between program\- and 836for some locales where character width differs between program\- and
746rxvt\-unicode\-locales. 837rxvt\-unicode\-locales.
747.IP "Can I switch the fonts at runtime?" 4 838.Sh "Can I switch the fonts at runtime?"
748.IX Item "Can I switch the fonts at runtime?" 839.IX Subsection "Can I switch the fonts at runtime?"
749Yes, using an escape sequence. Try something like this, which has the same 840Yes, using an escape sequence. Try something like this, which has the same
750effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately: 841effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately:
751.Sp 842.PP
752.Vb 1 843.Vb 1
753\& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic" 844\& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic"
754.Ve 845.Ve
755.Sp 846.PP
756This is useful if you e.g. work primarily with japanese (and prefer a 847This is useful if you e.g. work primarily with japanese (and prefer a
757japanese font), but you have to switch to chinese temporarily, where 848japanese font), but you have to switch to chinese temporarily, where
758japanese fonts would only be in your way. 849japanese fonts would only be in your way.
759.Sp 850.PP
760You can think of this as a kind of manual \s-1ISO\-2022\s0 switching. 851You can think of this as a kind of manual \s-1ISO\-2022\s0 switching.
761.IP "Why do italic characters look as if clipped?" 4 852.Sh "Why do italic characters look as if clipped?"
762.IX Item "Why do italic characters look as if clipped?" 853.IX Subsection "Why do italic characters look as if clipped?"
763Many fonts have difficulties with italic characters and hinting. For 854Many fonts have difficulties with italic characters and hinting. For
764example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans 855example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans
765Mono\*(C'\fR completely fails in it's italic face. A workaround might be to 856Mono\*(C'\fR completely fails in it's italic face. A workaround might be to
766enable freetype autohinting, i.e. like this: 857enable freetype autohinting, i.e. like this:
767.Sp 858.PP
768.Vb 2 859.Vb 2
769\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true 860\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
770\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true 861\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
771.Ve 862.Ve
772.IP "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?" 4 863.Sh "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?"
773.IX Item "My input method wants <some encoding> but I want UTF-8, what can I do?" 864.IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?"
774You can specify separate locales for the input method and the rest of the 865You can specify separate locales for the input method and the rest of the
775terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR: 866terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
776.Sp 867.PP
777.Vb 1 868.Vb 1
778\& URxvt.imlocale: ja_JP.EUC-JP 869\& URxvt.imlocale: ja_JP.EUC-JP
779.Ve 870.Ve
780.Sp 871.PP
781Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still 872Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still
782use your input method. Please note, however, that you will not be able to 873use your input method. Please note, however, that you will not be able to
783input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input 874input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input
784method limits you. 875method limits you.
785.IP "Rxvt-unicode crashes when the X Input Method changes or exits." 4 876.Sh "Rxvt-unicode crashes when the X Input Method changes or exits."
786.IX Item "Rxvt-unicode crashes when the X Input Method changes or exits." 877.IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits."
787Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by 878Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by
788design. Applications can avoid some crashes at the expense of memory 879design. Applications can avoid some crashes at the expense of memory
789leaks, and Input Methods can avoid some crashes by careful ordering at 880leaks, and Input Methods can avoid some crashes by careful ordering at
790exit time. \fBkinput2\fR (and derived input methods) generally succeeds, 881exit time. \fBkinput2\fR (and derived input methods) generally succeeds,
791while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however, 882while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however,
792crashes cannot be completely avoided even if both sides cooperate. 883crashes cannot be completely avoided even if both sides cooperate.
793.Sp 884.PP
794So the only workaround is not to kill your Input Method Servers. 885So the only workaround is not to kill your Input Method Servers.
795.IP "Rxvt-unicode uses gobs of memory, how can I reduce that?" 4 886.Sh "Rxvt-unicode uses gobs of memory, how can I reduce that?"
796.IX Item "Rxvt-unicode uses gobs of memory, how can I reduce that?" 887.IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?"
797Rxvt-unicode tries to obey the rule of not charging you for something you 888Rxvt-unicode tries to obey the rule of not charging you for something you
798don't use. One thing you should try is to configure out all settings that 889don't use. One thing you should try is to configure out all settings that
799you don't need, for example, Xft support is a resource hog by design, 890you don't need, for example, Xft support is a resource hog by design,
800when used. Compiling it out ensures that no Xft font will be loaded 891when used. Compiling it out ensures that no Xft font will be loaded
801accidentally when rxvt-unicode tries to find a font for your characters. 892accidentally when rxvt-unicode tries to find a font for your characters.
802.Sp 893.PP
803Also, many people (me included) like large windows and even larger 894Also, many people (me included) like large windows and even larger
804scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use 895scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use
8056 bytes per screen cell. For a 160x?? window this amounts to almost a 8966 bytes per screen cell. For a 160x?? window this amounts to almost a
806kilobyte per line. A scrollback buffer of 10000 lines will then (if full) 897kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
807use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as 898use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as
808rxvt-unicode then uses 8 bytes per screen cell. 899rxvt-unicode then uses 8 bytes per screen cell.
809.IP "Can I speed up Xft rendering somehow?" 4 900.Sh "Can I speed up Xft rendering somehow?"
810.IX Item "Can I speed up Xft rendering somehow?" 901.IX Subsection "Can I speed up Xft rendering somehow?"
811Yes, the most obvious way to speed it up is to avoid Xft entirely, as 902Yes, the most obvious way to speed it up is to avoid Xft entirely, as
812it is simply slow. If you still want Xft fonts you might try to disable 903it is simply slow. If you still want Xft fonts you might try to disable
813antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of 904antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of
814memory and also speeds up rendering considerably. 905memory and also speeds up rendering considerably.
815.IP "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 4 906.Sh "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
816.IX Item "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 907.IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
817Rxvt-unicode will use whatever you specify as a font. If it needs to 908Rxvt-unicode will use whatever you specify as a font. If it needs to
818fall back to it's default font search list it will prefer X11 core 909fall back to it's default font search list it will prefer X11 core
819fonts, because they are small and fast, and then use Xft fonts. It has 910fonts, because they are small and fast, and then use Xft fonts. It has
820antialiasing disabled for most of them, because the author thinks they 911antialiasing disabled for most of them, because the author thinks they
821look best that way. 912look best that way.
822.Sp 913.PP
823If you want antialiasing, you have to specify the fonts manually. 914If you want antialiasing, you have to specify the fonts manually.
824.IP "Mouse cut/paste suddenly no longer works." 4 915.Sh "Mouse cut/paste suddenly no longer works."
825.IX Item "Mouse cut/paste suddenly no longer works." 916.IX Subsection "Mouse cut/paste suddenly no longer works."
826Make sure that mouse reporting is actually turned off since killing 917Make sure that mouse reporting is actually turned off since killing
827some editors prematurely may leave the mouse in mouse report mode. I've 918some editors prematurely may leave the mouse in mouse report mode. I've
828heard that tcsh may use mouse reporting unless it otherwise specified. A 919heard that tcsh may use mouse reporting unless it otherwise specified. A
829quick check is to see if cut/paste works when the Alt or Shift keys are 920quick check is to see if cut/paste works when the Alt or Shift keys are
830depressed. 921depressed.
831.IP "What's with this bold/blink stuff?" 4 922.Sh "What's with this bold/blink stuff?"
832.IX Item "What's with this bold/blink stuff?" 923.IX Subsection "What's with this bold/blink stuff?"
833If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the 924If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the
834standard foreground colour. 925standard foreground colour.
835.Sp 926.PP
836For the standard background colour, blinking will actually make the 927For the standard background colour, blinking will actually make the
837text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard 928text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard
838colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be 929colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be
839ignored. 930ignored.
840.Sp 931.PP
841On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity 932On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity
842foreground/background colors. 933foreground/background colors.
843.Sp 934.PP
844color0\-7 are the low-intensity colors. 935color0\-7 are the low-intensity colors.
845.Sp 936.PP
846color8\-15 are the corresponding high-intensity colors. 937color8\-15 are the corresponding high-intensity colors.
847.IP "I don't like the screen colors. How do I change them?" 4 938.Sh "I don't like the screen colors. How do I change them?"
848.IX Item "I don't like the screen colors. How do I change them?" 939.IX Subsection "I don't like the screen colors. How do I change them?"
849You can change the screen colors at run-time using \fI~/.Xdefaults\fR 940You can change the screen colors at run-time using \fI~/.Xdefaults\fR
850resources (or as long\-options). 941resources (or as long\-options).
851.Sp 942.PP
852Here are values that are supposed to resemble a \s-1VGA\s0 screen, 943Here are values that are supposed to resemble a \s-1VGA\s0 screen,
853including the murky brown that passes for low-intensity yellow: 944including the murky brown that passes for low-intensity yellow:
854.Sp 945.PP
855.Vb 8 946.Vb 8
856\& URxvt.color0: #000000 947\& URxvt.color0: #000000
857\& URxvt.color1: #A80000 948\& URxvt.color1: #A80000
858\& URxvt.color2: #00A800 949\& URxvt.color2: #00A800
859\& URxvt.color3: #A8A800 950\& URxvt.color3: #A8A800
860\& URxvt.color4: #0000A8 951\& URxvt.color4: #0000A8
861\& URxvt.color5: #A800A8 952\& URxvt.color5: #A800A8
862\& URxvt.color6: #00A8A8 953\& URxvt.color6: #00A8A8
863\& URxvt.color7: #A8A8A8 954\& URxvt.color7: #A8A8A8
864.Ve 955.Ve
865.Sp 956.PP
866.Vb 8 957.Vb 8
867\& URxvt.color8: #000054 958\& URxvt.color8: #000054
868\& URxvt.color9: #FF0054 959\& URxvt.color9: #FF0054
869\& URxvt.color10: #00FF54 960\& URxvt.color10: #00FF54
870\& URxvt.color11: #FFFF54 961\& URxvt.color11: #FFFF54
871\& URxvt.color12: #0000FF 962\& URxvt.color12: #0000FF
872\& URxvt.color13: #FF00FF 963\& URxvt.color13: #FF00FF
873\& URxvt.color14: #00FFFF 964\& URxvt.color14: #00FFFF
874\& URxvt.color15: #FFFFFF 965\& URxvt.color15: #FFFFFF
875.Ve 966.Ve
876.Sp 967.PP
877And here is a more complete set of non-standard colors described (not by 968And here is a more complete set of non-standard colors described (not by
878me) as \*(L"pretty girly\*(R". 969me) as \*(L"pretty girly\*(R".
879.Sp 970.PP
880.Vb 18 971.Vb 18
881\& URxvt.cursorColor: #dc74d1 972\& URxvt.cursorColor: #dc74d1
882\& URxvt.pointerColor: #dc74d1 973\& URxvt.pointerColor: #dc74d1
883\& URxvt.background: #0e0e0e 974\& URxvt.background: #0e0e0e
884\& URxvt.foreground: #4ad5e1 975\& URxvt.foreground: #4ad5e1
… …
895\& URxvt.color6: #73f7ff 986\& URxvt.color6: #73f7ff
896\& URxvt.color14: #73f7ff 987\& URxvt.color14: #73f7ff
897\& URxvt.color7: #e1dddd 988\& URxvt.color7: #e1dddd
898\& URxvt.color15: #e1dddd 989\& URxvt.color15: #e1dddd
899.Ve 990.Ve
900.IP "How can I start @@RXVT_NAME@@d in a race-free way?" 4 991.Sh "How can I start @@RXVT_NAME@@d in a race-free way?"
901.IX Item "How can I start @@RXVT_NAME@@d in a race-free way?" 992.IX Subsection "How can I start @@RXVT_NAME@@d in a race-free way?"
902Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the 993Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the
903display, create the listening socket and then fork. 994display, create the listening socket and then fork.
904.IP "What's with the strange Backspace/Delete key behaviour?" 4 995.Sh "What's with the strange Backspace/Delete key behaviour?"
905.IX Item "What's with the strange Backspace/Delete key behaviour?" 996.IX Subsection "What's with the strange Backspace/Delete key behaviour?"
906Assuming that the physical Backspace key corresponds to the 997Assuming that the physical Backspace key corresponds to the
907BackSpace keysym (not likely for Linux ... see the following 998BackSpace keysym (not likely for Linux ... see the following
908question) there are two standard values that can be used for 999question) there are two standard values that can be used for
909Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR. 1000Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR.
910.Sp 1001.PP
911Historically, either value is correct, but rxvt-unicode adopts the debian 1002Historically, either value is correct, but rxvt-unicode adopts the debian
912policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct 1003policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct
913choice :). 1004choice :).
914.Sp 1005.PP
915Rxvt-unicode tries to inherit the current stty settings and uses the value 1006Rxvt-unicode tries to inherit the current stty settings and uses the value
916of `erase' to guess the value for backspace. If rxvt-unicode wasn't 1007of `erase' to guess the value for backspace. If rxvt-unicode wasn't
917started from a terminal (say, from a menu or by remote shell), then the 1008started from a terminal (say, from a menu or by remote shell), then the
918system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will 1009system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will
919be used (which may not be the same as your stty setting). 1010be used (which may not be the same as your stty setting).
920.Sp 1011.PP
921For starting a new rxvt\-unicode: 1012For starting a new rxvt\-unicode:
922.Sp 1013.PP
923.Vb 3 1014.Vb 3
924\& # use Backspace = ^H 1015\& # use Backspace = ^H
925\& $ stty erase ^H 1016\& $ stty erase ^H
926\& $ @@RXVT_NAME@@ 1017\& $ @@RXVT_NAME@@
927.Ve 1018.Ve
928.Sp 1019.PP
929.Vb 3 1020.Vb 3
930\& # use Backspace = ^? 1021\& # use Backspace = ^?
931\& $ stty erase ^? 1022\& $ stty erase ^?
932\& $ @@RXVT_NAME@@ 1023\& $ @@RXVT_NAME@@
933.Ve 1024.Ve
934.Sp 1025.PP
935Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. 1026Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR.
936.Sp 1027.PP
937For an existing rxvt\-unicode: 1028For an existing rxvt\-unicode:
938.Sp 1029.PP
939.Vb 3 1030.Vb 3
940\& # use Backspace = ^H 1031\& # use Backspace = ^H
941\& $ stty erase ^H 1032\& $ stty erase ^H
942\& $ echo -n "^[[36h" 1033\& $ echo -n "^[[36h"
943.Ve 1034.Ve
944.Sp 1035.PP
945.Vb 3 1036.Vb 3
946\& # use Backspace = ^? 1037\& # use Backspace = ^?
947\& $ stty erase ^? 1038\& $ stty erase ^?
948\& $ echo -n "^[[36l" 1039\& $ echo -n "^[[36l"
949.Ve 1040.Ve
950.Sp 1041.PP
951This helps satisfy some of the Backspace discrepancies that occur, but 1042This helps satisfy some of the Backspace discrepancies that occur, but
952if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value 1043if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value
953properly reflects that. 1044properly reflects that.
954.Sp 1045.PP
955The Delete key is a another casualty of the ill-defined Backspace problem. 1046The Delete key is a another casualty of the ill-defined Backspace problem.
956To avoid confusion between the Backspace and Delete keys, the Delete 1047To avoid confusion between the Backspace and Delete keys, the Delete
957key has been assigned an escape sequence to match the vt100 for Execute 1048key has been assigned an escape sequence to match the vt100 for Execute
958(\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo. 1049(\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo.
959.Sp 1050.PP
960Some other Backspace problems: 1051Some other Backspace problems:
961.Sp 1052.PP
962some editors use termcap/terminfo, 1053some editors use termcap/terminfo,
963some editors (vim I'm told) expect Backspace = ^H, 1054some editors (vim I'm told) expect Backspace = ^H,
964\&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help. 1055\&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help.
965.Sp 1056.PP
966Perhaps someday this will all be resolved in a consistent manner. 1057Perhaps someday this will all be resolved in a consistent manner.
967.IP "I don't like the key\-bindings. How do I change them?" 4 1058.Sh "I don't like the key\-bindings. How do I change them?"
968.IX Item "I don't like the key-bindings. How do I change them?" 1059.IX Subsection "I don't like the key-bindings. How do I change them?"
969There are some compile-time selections available via configure. Unless 1060There are some compile-time selections available via configure. Unless
970you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can 1061you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can
971use the `keysym' resource to alter the keystrings associated with keysyms. 1062use the `keysym' resource to alter the keystrings associated with keysyms.
972.Sp 1063.PP
973Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR 1064Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR
974.Sp 1065.PP
975.Vb 20 1066.Vb 20
976\& URxvt.keysym.Home: \e033[1~ 1067\& URxvt.keysym.Home: \e033[1~
977\& URxvt.keysym.End: \e033[4~ 1068\& URxvt.keysym.End: \e033[4~
978\& URxvt.keysym.C-apostrophe: \e033<C-'> 1069\& URxvt.keysym.C-apostrophe: \e033<C-'>
979\& URxvt.keysym.C-slash: \e033<C-/> 1070\& URxvt.keysym.C-slash: \e033<C-/>
… …
992\& URxvt.keysym.M-Right: \e033<M-Right> 1083\& URxvt.keysym.M-Right: \e033<M-Right>
993\& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 > 1084\& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 >
994\& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz > 1085\& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz >
995\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007 1086\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007
996.Ve 1087.Ve
997.Sp 1088.PP
998See some more examples in the documentation for the \fBkeysym\fR resource. 1089See some more examples in the documentation for the \fBkeysym\fR resource.
999.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 1090.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."
1000.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." 1091.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."
1001.Vb 6 1092.Vb 6
1002\& KP_Insert == Insert 1093\& KP_Insert == Insert
1003\& F22 == Print 1094\& F22 == Print
1004\& F27 == Home 1095\& F27 == Home
1005\& F29 == Prior 1096\& F29 == Prior
1006\& F33 == End 1097\& F33 == End
1007\& F35 == Next 1098\& F35 == Next
1008.Ve 1099.Ve
1009.Sp 1100.PP
1010Rather than have rxvt-unicode try to accommodate all the various possible 1101Rather than have rxvt-unicode try to accommodate all the various possible
1011keyboard mappings, it is better to use `xmodmap' to remap the keys as 1102keyboard mappings, it is better to use `xmodmap' to remap the keys as
1012required for your particular machine. 1103required for your particular machine.
1013.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 1104.Sh "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
1014.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." 1105.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."
1015rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can 1106rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can
1016check and see if that is set. Note that several programs, \s-1JED\s0, slrn, 1107check and see if that is set. Note that several programs, \s-1JED\s0, slrn,
1017Midnight Commander automatically check this variable to decide whether or 1108Midnight Commander automatically check this variable to decide whether or
1018not to use color. 1109not to use color.
1019.IP "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?" 4 1110.Sh "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?"
1020.IX Item "How do I set the correct, full IP address for the DISPLAY variable?" 1111.IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?"
1021If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled 1112If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled
1022insecure mode then it is possible to use the following shell script 1113insecure mode then it is possible to use the following shell script
1023snippets to correctly set the display. If your version of rxvt-unicode 1114snippets to correctly set the display. If your version of rxvt-unicode
1024wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then 1115wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then
1025the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a 1116the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a
1026regular xterm. 1117regular xterm.
1027.Sp 1118.PP
1028Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script 1119Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
1029snippets: 1120snippets:
1030.Sp 1121.PP
1031.Vb 12 1122.Vb 12
1032\& # Bourne/Korn/POSIX family of shells: 1123\& # Bourne/Korn/POSIX family of shells:
1033\& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know 1124\& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
1034\& if [ ${TERM:-foo} = xterm ]; then 1125\& if [ ${TERM:-foo} = xterm ]; then
1035\& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not 1126\& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
… …
1040\& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string 1131\& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
1041\& read DISPLAY # set it in our local shell 1132\& read DISPLAY # set it in our local shell
1042\& fi 1133\& fi
1043\& fi 1134\& fi
1044.Ve 1135.Ve
1045.IP "How do I compile the manual pages for myself?" 4 1136.Sh "How do I compile the manual pages for myself?"
1046.IX Item "How do I compile the manual pages for myself?" 1137.IX Subsection "How do I compile the manual pages for myself?"
1047You need to have a recent version of perl installed as \fI/usr/bin/perl\fR, 1138You need to have a recent version of perl installed as \fI/usr/bin/perl\fR,
1048one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to 1139one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to
1049the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR. 1140the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR.
1050.IP "My question isn't answered here, can I ask a human?" 4 1141.Sh "My question isn't answered here, can I ask a human?"
1051.IX Item "My question isn't answered here, can I ask a human?" 1142.IX Subsection "My question isn't answered here, can I ask a human?"
1052Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR, 1143Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR,
1053channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be 1144channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be
1054interested in learning about new and exciting problems (but not FAQs :). 1145interested in learning about new and exciting problems (but not FAQs :).
1055.SH "RXVT TECHNICAL REFERENCE" 1146.SH "RXVT TECHNICAL REFERENCE"
1056.IX Header "RXVT TECHNICAL REFERENCE" 1147.IX Header "RXVT TECHNICAL REFERENCE"
… …
1816Ps = 46 Change Log File to Pt unimplemented 1907Ps = 46 Change Log File to Pt unimplemented
1817Ps = 49 Change default background colour to Pt. 1908Ps = 49 Change default background colour to Pt.
1818Ps = 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 1909Ps = 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
1819Ps = 55 Log all scrollback buffer and all of screen to Pt 1910Ps = 55 Log all scrollback buffer and all of screen to Pt
1820Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills). 1911Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills).
1912Ps = 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.
1821Ps = 704 Change colour of italic characters to Pt 1913Ps = 704 Change colour of italic characters to Pt
1822Ps = 705 Change background pixmap tint colour to Pt (Compile transparency). 1914Ps = 705 Change background pixmap tint colour to Pt (Compile transparency).
1823Ps = 706 Change colour of bold characters to Pt 1915Ps = 706 Change colour of bold characters to Pt
1824Ps = 707 Change colour of underlined characters to Pt 1916Ps = 707 Change colour of underlined characters to Pt
1825Ps = 710 Set normal fontset to Pt. Same as Ps = 50. 1917Ps = 710 Set normal fontset to Pt. Same as Ps = 50.
… …
2043Add support for \s-1XIM\s0 (X Input Method) protocol. This allows using 2135Add support for \s-1XIM\s0 (X Input Method) protocol. This allows using
2044alternative input methods (e.g. kinput2) and will also correctly 2136alternative input methods (e.g. kinput2) and will also correctly
2045set up the input for people using dead keys or compose keys. 2137set up the input for people using dead keys or compose keys.
2046.IP "\-\-enable\-unicode3 (default: off)" 4 2138.IP "\-\-enable\-unicode3 (default: off)" 4
2047.IX Item "--enable-unicode3 (default: off)" 2139.IX Item "--enable-unicode3 (default: off)"
2140Recommended to stay off unless you really need non-BMP characters.
2141.Sp
2048Enable direct support for displaying unicode codepoints above 2142Enable direct support for displaying unicode codepoints above
204965535 (the basic multilingual page). This increases storage 214365535 (the basic multilingual page). This increases storage
2050requirements per character from 2 to 4 bytes. X11 fonts do not yet 2144requirements per character from 2 to 4 bytes. X11 fonts do not yet
2051support these extra characters, but Xft does. 2145support these extra characters, but Xft does.
2052.Sp 2146.Sp
… …
2061composite characters. This is required for proper viewing of text 2155composite characters. This is required for proper viewing of text
2062where accents are encoded as seperate unicode characters. This is 2156where accents are encoded as seperate unicode characters. This is
2063done by using precomposited characters when available or creating 2157done by using precomposited characters when available or creating
2064new pseudo-characters when no precomposed form exists. 2158new pseudo-characters when no precomposed form exists.
2065.Sp 2159.Sp
2066Without \-\-enable\-unicode3, the number of additional precomposed characters 2160Without \-\-enable\-unicode3, the number of additional precomposed
2067is rather limited (2048, if this is full, rxvt-unicode will use the 2161characters is somewhat limited (the 6400 private use characters will be
2068private use area, extending the number of combinations to 8448). With
2069\&\-\-enable\-unicode3, no practical limit exists. 2162(ab\-)used). With \-\-enable\-unicode3, no practical limit exists.
2070.Sp 2163.Sp
2071This option will also enable storage (but not display) of characters 2164This option will also enable storage (but not display) of characters
2072beyond plane 0 (>65535) when \-\-enable\-unicode3 was not specified. 2165beyond plane 0 (>65535) when \-\-enable\-unicode3 was not specified.
2073.Sp 2166.Sp
2074The combining table also contains entries for arabic presentation forms, 2167The combining table also contains entries for arabic presentation forms,
2075but these are not currently used. Bug me if you want these to be used (and 2168but these are not currently used. Bug me if you want these to be used (and
2076tell me how these are to be used...). 2169tell me how these are to be used...).
2077.IP "\-\-enable\-fallback(=CLASS) (default: Rxvt)" 4 2170.IP "\-\-enable\-fallback(=CLASS) (default: Rxvt)" 4
2078.IX Item "--enable-fallback(=CLASS) (default: Rxvt)" 2171.IX Item "--enable-fallback(=CLASS) (default: Rxvt)"
2079When reading resource settings, also read settings for class \s-1CLASS\s0. To disable resource fallback use \-\-disable\-fallback. 2172When reading resource settings, also read settings for class \s-1CLASS\s0. To
2173disable resource fallback use \-\-disable\-fallback.
2080.IP "\-\-with\-res\-name=NAME (default: urxvt)" 4 2174.IP "\-\-with\-res\-name=NAME (default: urxvt)" 4
2081.IX Item "--with-res-name=NAME (default: urxvt)" 2175.IX Item "--with-res-name=NAME (default: urxvt)"
2082Use the given name as default application name when 2176Use the given name as default application name when
2083reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt. 2177reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt.
2084.IP "\-\-with\-res\-class=CLASS /default: URxvt)" 4 2178.IP "\-\-with\-res\-class=CLASS /default: URxvt)" 4
… …
2151disable this. 2245disable this.
2152.Sp 2246.Sp
2153A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly 2247A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly
2154in combination with other switches) is: 2248in combination with other switches) is:
2155.Sp 2249.Sp
2156.Vb 17 2250.Vb 15
2157\& MWM-hints 2251\& MWM-hints
2158\& EWMH-hints (pid, utf8 names) and protocols (ping) 2252\& EWMH-hints (pid, utf8 names) and protocols (ping)
2159\& seperate underline colour (-underlineColor) 2253\& seperate underline colour (-underlineColor)
2160\& settable border widths and borderless switch (-w, -b, -bl) 2254\& settable border widths and borderless switch (-w, -b, -bl)
2255\& visual depth selection (-depth)
2161\& settable extra linespacing /-lsp) 2256\& settable extra linespacing /-lsp)
2162\& iso-14755-2 and -3, and visual feedback 2257\& iso-14755-2 and -3, and visual feedback
2163\& backindex and forwardindex escape sequence
2164\& window op and some xterm/OSC escape sequences
2165\& tripleclickwords (-tcw) 2258\& tripleclickwords (-tcw)
2166\& settable insecure mode (-insecure) 2259\& settable insecure mode (-insecure)
2167\& keysym remapping support 2260\& keysym remapping support
2168\& cursor blinking and underline cursor (-cb, -uc) 2261\& cursor blinking and underline cursor (-cb, -uc)
2169\& XEmbed support (-embed) 2262\& XEmbed support (-embed)
2170\& user-pty (-pty-fd) 2263\& user-pty (-pty-fd)
2171\& hold on exit (-hold) 2264\& hold on exit (-hold)
2172\& skip builtin block graphics (-sbg) 2265\& skip builtin block graphics (-sbg)
2266.Ve
2267.Sp
2268It also enabled some non-essential features otherwise disabled, such as:
2269.Sp
2270.Vb 11
2271\& some round-trip time optimisations
2272\& nearest color allocation on pseudocolor screens
2273\& UTF8_STRING supporr for selection
2173\& sgr modes 90..97 and 100..107 2274\& sgr modes 90..97 and 100..107
2275\& backindex and forwardindex escape sequences
2276\& view change/zero scorllback esacpe sequences
2277\& locale switching escape sequence
2278\& window op and some xterm/OSC escape sequences
2279\& rectangular selections
2280\& trailing space removal for selections
2281\& verbose X error handling
2174.Ve 2282.Ve
2175.IP "\-\-enable\-iso14755 (default: on)" 4 2283.IP "\-\-enable\-iso14755 (default: on)" 4
2176.IX Item "--enable-iso14755 (default: on)" 2284.IX Item "--enable-iso14755 (default: on)"
2177Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or 2285Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or
2178\&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by 2286\&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by
… …
2212keys. This should keep the window corner which is closest to a corner of 2320keys. This should keep the window corner which is closest to a corner of
2213the screen in a fixed position. 2321the screen in a fixed position.
2214.IP "\-\-enable\-pointer\-blank (default: on)" 4 2322.IP "\-\-enable\-pointer\-blank (default: on)" 4
2215.IX Item "--enable-pointer-blank (default: on)" 2323.IX Item "--enable-pointer-blank (default: on)"
2216Add support to have the pointer disappear when typing or inactive. 2324Add support to have the pointer disappear when typing or inactive.
2217.IP "\-\-enable\-perl (default: off)" 4 2325.IP "\-\-enable\-perl (default: on)" 4
2218.IX Item "--enable-perl (default: off)" 2326.IX Item "--enable-perl (default: on)"
2219Enable an embedded perl interpreter. See the \fB@@RXVT_NAME@@\f(BIperl\fB\|(3)\fR 2327Enable an embedded perl interpreter. See the \fB@@RXVT_NAME@@\f(BIperl\fB\|(3)\fR
2220manpage (\fIdoc/rxvtperl.txt\fR) for more info on this feature, or the files 2328manpage (\fIdoc/rxvtperl.txt\fR) for more info on this feature, or the files
2221in \fIsrc/perl\-ext/\fR for the extensions that are installed by default. The 2329in \fIsrc/perl\-ext/\fR for the extensions that are installed by default. The
2222perl interpreter that is used can be specified via the \f(CW\*(C`PERL\*(C'\fR environment 2330perl interpreter that is used can be specified via the \f(CW\*(C`PERL\*(C'\fR environment
2223variable when running configure. 2331variable when running configure.

Diff Legend

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