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.56 by root, Tue Jan 31 00:25:16 2006 UTC vs.
Revision 1.60 by root, Tue Jan 31 01:00:49 2006 UTC

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

Diff Legend

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