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.59 by root, Tue Jan 31 00:57:35 2006 UTC vs.
Revision 1.75 by root, Wed Feb 22 10:42:49 2006 UTC

… …
127.\} 127.\}
128.rm #[ #] #H #V #F C 128.rm #[ #] #H #V #F C
129.\" ======================================================================== 129.\" ========================================================================
130.\" 130.\"
131.IX Title "rxvt 7" 131.IX Title "rxvt 7"
132.TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE" 132.TH rxvt 7 "2006-02-22" "7.7" "RXVT-UNICODE"
133.SH "NAME" 133.SH "NAME"
134RXVT REFERENCE \- FAQ, command sequences and other background information 134RXVT REFERENCE \- FAQ, command sequences and other background information
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137.Vb 2 137.Vb 2
… …
153This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting 153This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting
154all escape sequences, and other background information. 154all escape sequences, and other background information.
155.PP 155.PP
156The newest version of this document is 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 "RXVT\-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS"
159.IX Header "FREQUENTLY ASKED QUESTIONS" 159.IX Header "RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS"
160.Sh "The new selection selects pieces that are too big, how can I select single words?" 160.Sh "Meta, Features & Commandline Issues"
161.IX Subsection "The new selection selects pieces that are too big, how can I select single words?" 161.IX Subsection "Meta, Features & Commandline Issues"
162If you want to select e.g. alphanumeric words, you can use the following 162\fIMy question isn't answered here, can I ask a human?\fR
163setting: 163.IX Subsection "My question isn't answered here, can I ask a human?"
164.PP
165Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR,
166channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be
167interested in learning about new and exciting problems (but not FAQs :).
168.PP
169\fIDoes it support tabs, can I have a tabbed rxvt\-unicode?\fR
170.IX Subsection "Does it support tabs, can I have a tabbed rxvt-unicode?"
171.PP
172Beginning with version 7.3, there is a perl extension that implements a
173simple tabbed terminal. It is installed by default, so any of these should
174give you tabs:
164.PP 175.PP
165.Vb 1 176.Vb 1
166\& URxvt.selection.pattern-0: ([[:word:]]+) 177\& @@URXVT_NAME@@ -pe tabbed
167.Ve 178.Ve
168.PP
169If you click more than twice, the selection will be extended
170more and more.
171.PP
172To get a selection that is very similar to the old code, try this pattern:
173.PP 179.PP
174.Vb 1 180.Vb 1
175\& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+) 181\& URxvt.perl-ext-common: default,tabbed
176.Ve 182.Ve
177.PP 183.PP
178Please also note that the \fILeftClick Shift-LeftClik\fR combination also 184It will also work fine with tabbing functionality of many window managers
179selects words like the old code. 185or similar tabbing programs, and its embedding-features allow it to be
180.Sh "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" 186embedded into other programs, as witnessed by \fIdoc/rxvt\-tabbed\fR or
181.IX Subsection "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" 187the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl module, which features a tabbed urxvt
182You can disable the perl extension completely by setting the 188(murxvt) terminal as an example embedding application.
183\&\fBperl-ext-common\fR resource to the empty string, which also keeps
184rxvt-unicode from initialising perl, saving memory.
185.PP 189.PP
186If you only want to disable specific features, you first have to 190\fIHow do I know which rxvt-unicode version I'm using?\fR
187identify which perl extension is responsible. For this, read the section 191.IX Subsection "How do I know which rxvt-unicode version I'm using?"
188\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For
189example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify
190this \fBperl-ext-common\fR resource:
191.PP 192.PP
193The version number is displayed with the usage (\-h). Also the escape
194sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When
195using the @@URXVT_NAME@@c client, the version displayed is that of the
196daemon.
197.PP
198\fIRxvt-unicode uses gobs of memory, how can I reduce that?\fR
199.IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?"
200.PP
201Rxvt-unicode tries to obey the rule of not charging you for something you
202don't use. One thing you should try is to configure out all settings that
203you don't need, for example, Xft support is a resource hog by design,
204when used. Compiling it out ensures that no Xft font will be loaded
205accidentally when rxvt-unicode tries to find a font for your characters.
206.PP
207Also, many people (me included) like large windows and even larger
208scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use
2096 bytes per screen cell. For a 160x?? window this amounts to almost a
210kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
211use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as
212rxvt-unicode then uses 8 bytes per screen cell.
213.PP
214\fIHow can I start @@URXVT_NAME@@d in a race-free way?\fR
215.IX Subsection "How can I start @@URXVT_NAME@@d in a race-free way?"
216.PP
217Try \f(CW\*(C`@@URXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@URXVT_NAME@@d to open the
218display, create the listening socket and then fork.
219.PP
220\fIHow can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?\fR
221.IX Subsection "How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?"
222.PP
223If you want to start @@URXVT_NAME@@d automatically whenever you run
224@@URXVT_NAME@@c and the daemon isn't running yet, use this script:
225.PP
226.Vb 6
227\& #!/bin/sh
228\& @@URXVT_NAME@@c "$@"
229\& if [ $? -eq 2 ]; then
230\& @@URXVT_NAME@@d -q -o -f
231\& @@URXVT_NAME@@c "$@"
232\& fi
233.Ve
234.PP
235This tries to create a new terminal, and if fails with exit status 2,
236meaning it couldn't connect to the daemon, it will start the daemon and
237re-run the command. Subsequent invocations of the script will re-use the
238existing daemon.
239.PP
240\fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR
241.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."
242.PP
243The original rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R",
244so you can check and see if that is set. Note that several programs, \s-1JED\s0,
245slrn, Midnight Commander automatically check this variable to decide
246whether or not to use color.
247.PP
248\fIHow do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?\fR
249.IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?"
250.PP
251If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled
252insecure mode then it is possible to use the following shell script
253snippets to correctly set the display. If your version of rxvt-unicode
254wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then
255the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a
256regular xterm.
257.PP
258Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
259snippets:
260.PP
192.Vb 1 261.Vb 12
193\& URxvt.perl-ext-common: default,-selection-popup,-option-popup 262\& # Bourne/Korn/POSIX family of shells:
263\& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
264\& if [ ${TERM:-foo} = xterm ]; then
265\& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
266\& echo -n '^[Z'
267\& read term_id
268\& stty icanon echo
269\& if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
270\& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
271\& read DISPLAY # set it in our local shell
272\& fi
273\& fi
194.Ve 274.Ve
195.PP 275.PP
196This will keep the default extensions, but disable the two popup 276\fIHow do I compile the manual pages on my own?\fR
197extensions. Some extensions can also be configured, for example, 277.IX Subsection "How do I compile the manual pages on my own?"
198scrollback search mode is triggered by \fBM\-s\fR. You can move it to any
199other combination either by setting the \fBsearchable-scrollback\fR resource:
200.PP 278.PP
201.Vb 1 279You need to have a recent version of perl installed as \fI/usr/bin/perl\fR,
202\& URxvt.searchable-scrollback: CM-s 280one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to
203.Ve 281the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR.
204.Sh "The cursor moves when selecting text in the current input line, how do I switch this off?"
205.IX Subsection "The cursor moves when selecting text in the current input line, how do I switch this off?"
206.Sh "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?"
207.IX Subsection "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?"
208These are caused by the \f(CW\*(C`readline\*(C'\fR perl extension. Under normal
209circumstances, it will move your cursor around when you click into the
210line that contains it. It tries hard not to do this at the wrong moment,
211but when running a program that doesn't parse cursor movements or in some
212cases during rlogin sessions, it fails to detect this properly.
213.PP 282.PP
214You can permamently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR
215extension:
216.PP
217.Vb 1
218\& URxvt.perl-ext-common: default,-readline
219.Ve
220.Sh "Why doesn't rxvt-unicode read my resources?"
221.IX Subsection "Why doesn't rxvt-unicode read my resources?"
222Well, why, indeed? It does, in a way very similar to other X
223applications. Most importantly, this means that if you or your \s-1OS\s0 loads
224resources into the X display (the right way to do it), rxvt-unicode will
225ignore any resource files in your home directory. It will only read
226\&\fI$HOME/.Xdefaults\fR when no resources are attached to the display.
227.PP
228If you have or use an \fI$HOME/.Xresources\fR file, chances are that
229resources are loaded into your X\-server. In this case, you have to
230re-login after every change (or run \fIxrdb \-merge \f(CI$HOME\fI/.Xresources\fR).
231.PP
232Also consider the form resources have to use:
233.PP
234.Vb 1
235\& URxvt.resource: value
236.Ve
237.PP
238If you want to use another form (there are lots of different ways of
239specifying resources), make sure you understand wether and why it
240works. If unsure, use the form above.
241.Sh "I can't get transparency working, what am I doing wrong?"
242.IX Subsection "I can't get transparency working, what am I doing wrong?"
243First of all, transparency isn't officially supported in rxvt\-unicode, so
244you are mostly on your own. Do not bug the author about it (but you may
245bug everybody else). Also, if you can't get it working consider it a rite
246of passage: ... and you failed.
247.PP
248Here are four ways to get transparency. \fBDo\fR read the manpage and option
249descriptions for the programs mentioned and rxvt\-unicode. Really, do it!
250.PP
2511. Use inheritPixmap:
252.PP
253.Vb 2
254\& Esetroot wallpaper.jpg
255\& @@RXVT_NAME@@ -ip -tint red -sh 40
256.Ve
257.PP
258That works. If you think it doesn't, you lack transparency and tinting
259support, or you are unable to read.
260.PP
2612. Use a simple pixmap and emulate pseudo\-transparency. This enables you
262to use effects other than tinting and shading: Just shade/tint/whatever
263your picture with gimp:
264.PP
265.Vb 2
266\& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
267\& @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background
268.Ve
269.PP
270That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you
271are unable to read.
272.PP
2733. Use an \s-1ARGB\s0 visual:
274.PP
275.Vb 1
276\& @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
277.Ve
278.PP
279This requires \s-1XFT\s0 support, and the support of your X\-server. If that
280doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't
281there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
282bugfixes and workarounds for Xft and Xlib to make it work, but that
283doesn't mean that your \s-1WM\s0 has the required kludges in place.
284.PP
2854. Use xcompmgr and let it do the job:
286.PP
287.Vb 2
288\& xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \e
289\& -set _NET_WM_WINDOW_OPACITY 0xc0000000
290.Ve
291.PP
292Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR
293by other values to change the degree of opacity. If it doesn't work and
294your server crashes, you got to keep the pieces.
295.Sh "Isn't rxvt supposed to be small? Don't all those features bloat?" 283\fIIsn't rxvt-unicode supposed to be small? Don't all those features bloat?\fR
296.IX Subsection "Isn't rxvt supposed to be small? Don't all those features bloat?" 284.IX Subsection "Isn't rxvt-unicode supposed to be small? Don't all those features bloat?"
285.PP
297I often get asked about this, and I think, no, they didn't cause extra 286I often get asked about this, and I think, no, they didn't cause extra
298bloat. If you compare a minimal rxvt and a minimal urxvt, you can see 287bloat. If you compare a minimal rxvt and a minimal urxvt, you can see
299that the urxvt binary is larger (due to some encoding tables always being 288that the urxvt binary is larger (due to some encoding tables always being
300compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even 289compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even
301with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many 290with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many
… …
306\& text data bss drs rss filename 295\& text data bss drs rss filename
307\& 98398 1664 24 15695 1824 rxvt --disable-everything 296\& 98398 1664 24 15695 1824 rxvt --disable-everything
308\& 188985 9048 66616 18222 1788 urxvt --disable-everything 297\& 188985 9048 66616 18222 1788 urxvt --disable-everything
309.Ve 298.Ve
310.PP 299.PP
311When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft 300When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which \fIis\fR unfair, as this involves xft
312and full locale/XIM support which are quite bloaty inside libX11 and my 301and full locale/XIM support which are quite bloaty inside libX11 and my
313libc), the two diverge, but not unreasnobaly so. 302libc), the two diverge, but not unreasnobaly so.
314.PP 303.PP
315.Vb 3 304.Vb 3
316\& text data bss drs rss filename 305\& text data bss drs rss filename
… …
335still fares rather well. And compared to some monsters like gnome-terminal 324still fares rather well. And compared to some monsters like gnome-terminal
336(21152k + extra 4204k in separate processes) or konsole (22200k + extra 325(21152k + extra 4204k in separate processes) or konsole (22200k + extra
33743180k in daemons that stay around after exit, plus half a minute of 32643180k in daemons that stay around after exit, plus half a minute of
338startup time, including the hundreds of warnings it spits out), it fares 327startup time, including the hundreds of warnings it spits out), it fares
339extremely well *g*. 328extremely well *g*.
329.PP
340.Sh "Why \*(C+, isn't that unportable/bloated/uncool?" 330\fIWhy \*(C+, isn't that unportable/bloated/uncool?\fR
341.IX Subsection "Why , isn't that unportable/bloated/uncool?" 331.IX Subsection "Why , isn't that unportable/bloated/uncool?"
332.PP
342Is this a question? :) It comes up very often. The simple answer is: I had 333Is this a question? :) It comes up very often. The simple answer is: I had
343to write it, and \*(C+ allowed me to write and maintain it in a fraction 334to write it, and \*(C+ allowed me to write and maintain it in a fraction
344of the time and effort (which is a scarce resource for me). Put even 335of the time and effort (which is a scarce resource for me). Put even
345shorter: It simply wouldn't exist without \*(C+. 336shorter: It simply wouldn't exist without \*(C+.
346.PP 337.PP
… …
372\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) 363\& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000)
373.Ve 364.Ve
374.PP 365.PP
375No large bloated libraries (of course, none were linked in statically), 366No large bloated libraries (of course, none were linked in statically),
376except maybe libX11 :) 367except maybe libX11 :)
377.Sh "Does it support tabs, can I have a tabbed rxvt\-unicode?" 368.Sh "Rendering, Font & Look and Feel Issues"
378.IX Subsection "Does it support tabs, can I have a tabbed rxvt-unicode?" 369.IX Subsection "Rendering, Font & Look and Feel Issues"
379Beginning with version 7.3, there is a perl extension that implements a 370\fII can't get transparency working, what am I doing wrong?\fR
380simple tabbed terminal. It is installed by default, so any of these should 371.IX Subsection "I can't get transparency working, what am I doing wrong?"
381give you tabs: 372.PP
373First of all, transparency isn't officially supported in rxvt\-unicode, so
374you are mostly on your own. Do not bug the author about it (but you may
375bug everybody else). Also, if you can't get it working consider it a rite
376of passage: ... and you failed.
377.PP
378Here are four ways to get transparency. \fBDo\fR read the manpage and option
379descriptions for the programs mentioned and rxvt\-unicode. Really, do it!
380.PP
3811. Use inheritPixmap:
382.PP
383.Vb 2
384\& Esetroot wallpaper.jpg
385\& @@URXVT_NAME@@ -ip -tint red -sh 40
386.Ve
387.PP
388That works. If you think it doesn't, you lack transparency and tinting
389support, or you are unable to read.
390.PP
3912. Use a simple pixmap and emulate pseudo\-transparency. This enables you
392to use effects other than tinting and shading: Just shade/tint/whatever
393your picture with gimp or any other tool:
394.PP
395.Vb 2
396\& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm
397\& @@URXVT_NAME@@ -pixmap background.xpm -pe automove-background
398.Ve
399.PP
400That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you
401are unable to read.
402.PP
4033. Use an \s-1ARGB\s0 visual:
382.PP 404.PP
383.Vb 1 405.Vb 1
384\& @@RXVT_NAME@@ -pe tabbed 406\& @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc
385.Ve 407.Ve
408.PP
409This requires \s-1XFT\s0 support, and the support of your X\-server. If that
410doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't
411there yet, no matter what they claim. Rxvt-Unicode contains the neccessary
412bugfixes and workarounds for Xft and Xlib to make it work, but that
413doesn't mean that your \s-1WM\s0 has the required kludges in place.
414.PP
4154. Use xcompmgr and let it do the job:
416.PP
417.Vb 2
418\& xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \e
419\& -set _NET_WM_WINDOW_OPACITY 0xc0000000
420.Ve
421.PP
422Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR
423by other values to change the degree of opacity. If it doesn't work and
424your server crashes, you got to keep the pieces.
425.PP
426\fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR
427.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"
428.PP
429Most fonts were not designed for terminal use, which means that character
430size varies a lot. A font that is otherwise fine for terminal use might
431contain some characters that are simply too wide. Rxvt-unicode will avoid
432these characters. For characters that are just \*(L"a bit\*(R" too wide a special
433\&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters.
434.PP
435All of this requires that fonts do not lie about character sizes,
436however: Xft fonts often draw glyphs larger than their acclaimed bounding
437box, and rxvt-unicode has no way of detecting this (the correct way is to
438ask for the character bounding box, which unfortunately is wrong in these
439cases).
440.PP
441It's not clear (to me at least), wether this is a bug in Xft, freetype,
442or the respective font. If you encounter this problem you might try using
443the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you
444might be forced to use a different font.
445.PP
446All of this is not a problem when using X11 core fonts, as their bounding
447box data is correct.
448.PP
449\fIHow can I keep rxvt-unicode from using reverse video so much?\fR
450.IX Subsection "How can I keep rxvt-unicode from using reverse video so much?"
451.PP
452First of all, make sure you are running with the right terminal settings
453(\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then
454make sure you have specified colours for italic and bold, as otherwise
455rxvt-unicode might use reverse video to simulate the effect:
456.PP
457.Vb 2
458\& URxvt.colorBD: white
459\& URxvt.colorIT: green
460.Ve
461.PP
462\fISome programs assume totally weird colours (red instead of blue), how can I fix that?\fR
463.IX Subsection "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
464.PP
465For some unexplainable reason, some rare programs assume a very weird
466colour palette when confronted with a terminal with more than the standard
4678 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix
468these programs not to assume non-ISO colours without very good reasons.
469.PP
470In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
471definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will
472fix colours but keep you from using other rxvt-unicode features.
473.PP
474\fICan I switch the fonts at runtime?\fR
475.IX Subsection "Can I switch the fonts at runtime?"
476.PP
477Yes, using an escape sequence. Try something like this, which has the same
478effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately:
386.PP 479.PP
387.Vb 1 480.Vb 1
481\& printf '\e33]50;%s\e007' "9x15bold,xft:Kochi Gothic"
482.Ve
483.PP
484This is useful if you e.g. work primarily with japanese (and prefer a
485japanese font), but you have to switch to chinese temporarily, where
486japanese fonts would only be in your way.
487.PP
488You can think of this as a kind of manual \s-1ISO\-2022\s0 switching.
489.PP
490\fIWhy do italic characters look as if clipped?\fR
491.IX Subsection "Why do italic characters look as if clipped?"
492.PP
493Many fonts have difficulties with italic characters and hinting. For
494example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans
495Mono\*(C'\fR completely fails in it's italic face. A workaround might be to
496enable freetype autohinting, i.e. like this:
497.PP
498.Vb 2
499\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
500\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
501.Ve
502.PP
503\fICan I speed up Xft rendering somehow?\fR
504.IX Subsection "Can I speed up Xft rendering somehow?"
505.PP
506Yes, the most obvious way to speed it up is to avoid Xft entirely, as
507it is simply slow. If you still want Xft fonts you might try to disable
508antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of
509memory and also speeds up rendering considerably.
510.PP
511\fIRxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?\fR
512.IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
513.PP
514Rxvt-unicode will use whatever you specify as a font. If it needs to
515fall back to it's default font search list it will prefer X11 core
516fonts, because they are small and fast, and then use Xft fonts. It has
517antialiasing disabled for most of them, because the author thinks they
518look best that way.
519.PP
520If you want antialiasing, you have to specify the fonts manually.
521.PP
522\fIWhat's with this bold/blink stuff?\fR
523.IX Subsection "What's with this bold/blink stuff?"
524.PP
525If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the
526standard foreground colour.
527.PP
528For the standard background colour, blinking will actually make the
529text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard
530colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be
531ignored.
532.PP
533On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity
534foreground/background colors.
535.PP
536color0\-7 are the low-intensity colors.
537.PP
538color8\-15 are the corresponding high-intensity colors.
539.PP
540\fII don't like the screen colors. How do I change them?\fR
541.IX Subsection "I don't like the screen colors. How do I change them?"
542.PP
543You can change the screen colors at run-time using \fI~/.Xdefaults\fR
544resources (or as long\-options).
545.PP
546Here are values that are supposed to resemble a \s-1VGA\s0 screen,
547including the murky brown that passes for low-intensity yellow:
548.PP
549.Vb 8
550\& URxvt.color0: #000000
551\& URxvt.color1: #A80000
552\& URxvt.color2: #00A800
553\& URxvt.color3: #A8A800
554\& URxvt.color4: #0000A8
555\& URxvt.color5: #A800A8
556\& URxvt.color6: #00A8A8
557\& URxvt.color7: #A8A8A8
558.Ve
559.PP
560.Vb 8
561\& URxvt.color8: #000054
562\& URxvt.color9: #FF0054
563\& URxvt.color10: #00FF54
564\& URxvt.color11: #FFFF54
565\& URxvt.color12: #0000FF
566\& URxvt.color13: #FF00FF
567\& URxvt.color14: #00FFFF
568\& URxvt.color15: #FFFFFF
569.Ve
570.PP
571And here is a more complete set of non-standard colors.
572.PP
573.Vb 18
574\& URxvt.cursorColor: #dc74d1
575\& URxvt.pointerColor: #dc74d1
576\& URxvt.background: #0e0e0e
577\& URxvt.foreground: #4ad5e1
578\& URxvt.color0: #000000
579\& URxvt.color8: #8b8f93
580\& URxvt.color1: #dc74d1
581\& URxvt.color9: #dc74d1
582\& URxvt.color2: #0eb8c7
583\& URxvt.color10: #0eb8c7
584\& URxvt.color3: #dfe37e
585\& URxvt.color11: #dfe37e
586\& URxvt.color5: #9e88f0
587\& URxvt.color13: #9e88f0
588\& URxvt.color6: #73f7ff
589\& URxvt.color14: #73f7ff
590\& URxvt.color7: #e1dddd
591\& URxvt.color15: #e1dddd
592.Ve
593.PP
594They have been described (not by me) as \*(L"pretty girly\*(R".
595.PP
596\fIWhy do some characters look so much different than others?\fR
597.IX Subsection "Why do some characters look so much different than others?"
598.PP
599See next entry.
600.PP
601\fIHow does rxvt-unicode choose fonts?\fR
602.IX Subsection "How does rxvt-unicode choose fonts?"
603.PP
604Most fonts do not contain the full range of Unicode, which is
605fine. Chances are that the font you (or the admin/package maintainer of
606your system/os) have specified does not cover all the characters you want
607to display.
608.PP
609\&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement
610font. Often the result is fine, but sometimes the chosen font looks
611bad/ugly/wrong. Some fonts have totally strange characters that don't
612resemble the correct glyph at all, and rxvt-unicode lacks the artificial
613intelligence to detect that a specific glyph is wrong: it has to believe
614the font that the characters it claims to contain indeed look correct.
615.PP
616In that case, select a font of your taste and add it to the font list,
617e.g.:
618.PP
619.Vb 1
620\& @@URXVT_NAME@@ -fn basefont,font2,font3...
621.Ve
622.PP
623When rxvt-unicode sees a character, it will first look at the base
624font. If the base font does not contain the character, it will go to the
625next font, and so on. Specifying your own fonts will also speed up this
626search and use less resources within rxvt-unicode and the X\-server.
627.PP
628The only limitation is that none of the fonts may be larger than the base
629font, as the base font defines the terminal character cell size, which
630must be the same due to the way terminals work.
631.PP
632\fIWhy do some chinese characters look so different than others?\fR
633.IX Subsection "Why do some chinese characters look so different than others?"
634.PP
635This is because there is a difference between script and language \*(--
636rxvt-unicode does not know which language the text that is output is,
637as it only knows the unicode character codes. If rxvt-unicode first
638sees a japanese/chinese character, it might choose a japanese font for
639display. Subsequent japanese characters will use that font. Now, many
640chinese characters aren't represented in japanese fonts, so when the first
641non-japanese character comes up, rxvt-unicode will look for a chinese font
642\&\*(-- unfortunately at this point, it will still use the japanese font for
643chinese characters that are also in the japanese font.
644.PP
645The workaround is easy: just tag a chinese font at the end of your font
646list (see the previous question). The key is to view the font list as
647a preference list: If you expect more japanese, list a japanese font
648first. If you expect more chinese, put a chinese font first.
649.PP
650In the future it might be possible to switch language preferences at
651runtime (the internal data structure has no problem with using different
652fonts for the same character at the same time, but no interface for this
653has been designed yet).
654.PP
655Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document).
656.Sh "Keyboard, Mouse & User Interaction"
657.IX Subsection "Keyboard, Mouse & User Interaction"
658\fIThe new selection selects pieces that are too big, how can I select single words?\fR
659.IX Subsection "The new selection selects pieces that are too big, how can I select single words?"
660.PP
661If you want to select e.g. alphanumeric words, you can use the following
662setting:
663.PP
664.Vb 1
665\& URxvt.selection.pattern-0: ([[:word:]]+)
666.Ve
667.PP
668If you click more than twice, the selection will be extended
669more and more.
670.PP
671To get a selection that is very similar to the old code, try this pattern:
672.PP
673.Vb 1
674\& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+)
675.Ve
676.PP
677Please also note that the \fILeftClick Shift-LeftClik\fR combination also
678selects words like the old code.
679.PP
680\fII don't like the new selection/popups/hotkeys/perl, how do I change/disable it?\fR
681.IX Subsection "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?"
682.PP
683You can disable the perl extension completely by setting the
684\&\fBperl-ext-common\fR resource to the empty string, which also keeps
685rxvt-unicode from initialising perl, saving memory.
686.PP
687If you only want to disable specific features, you first have to
688identify which perl extension is responsible. For this, read the section
689\&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@URXVT_NAME@@\fIperl\fR\|(3) manpage. For
690example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify
691this \fBperl-ext-common\fR resource:
692.PP
693.Vb 1
694\& URxvt.perl-ext-common: default,-selection-popup,-option-popup
695.Ve
696.PP
697This will keep the default extensions, but disable the two popup
698extensions. Some extensions can also be configured, for example,
699scrollback search mode is triggered by \fBM\-s\fR. You can move it to any
700other combination either by setting the \fBsearchable-scrollback\fR resource:
701.PP
702.Vb 1
703\& URxvt.searchable-scrollback: CM-s
704.Ve
705.PP
706\fIThe cursor moves when selecting text in the current input line, how do I switch this off?\fR
707.IX Subsection "The cursor moves when selecting text in the current input line, how do I switch this off?"
708.PP
709See next entry.
710.PP
711\fIDuring rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?\fR
712.IX Subsection "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?"
713.PP
714These are caused by the \f(CW\*(C`readline\*(C'\fR perl extension. Under normal
715circumstances, it will move your cursor around when you click into the
716line that contains it. It tries hard not to do this at the wrong moment,
717but when running a program that doesn't parse cursor movements or in some
718cases during rlogin sessions, it fails to detect this properly.
719.PP
720You can permamently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR
721extension:
722.PP
723.Vb 1
388\& URxvt.perl-ext-common: default,tabbed 724\& URxvt.perl-ext-common: default,-readline
389.Ve 725.Ve
390.PP 726.PP
391It will also work fine with tabbing functionality of many window managers 727\fIMy numerical keypad acts weird and generates differing output?\fR
392or similar tabbing programs, and its embedding-features allow it to be 728.IX Subsection "My numerical keypad acts weird and generates differing output?"
393embedded into other programs, as witnessed by \fIdoc/rxvt\-tabbed\fR or
394the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl module, which features a tabbed urxvt
395(murxvt) terminal as an example embedding application.
396.Sh "How do I know which rxvt-unicode version I'm using?"
397.IX Subsection "How do I know which rxvt-unicode version I'm using?"
398The version number is displayed with the usage (\-h). Also the escape
399sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When
400using the @@RXVT_NAME@@c client, the version displayed is that of the
401daemon.
402.Sh "I am using Debian GNU/Linux and have a problem..."
403.IX Subsection "I am using Debian GNU/Linux and have a problem..."
404The Debian GNU/Linux package of rxvt-unicode in sarge contains large
405patches that considerably change the behaviour of rxvt-unicode (but
406unfortunately this notice has been removed). Before reporting a bug to
407the original rxvt-unicode author please download and install the genuine
408version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce
409the problem. If you cannot, chances are that the problems are specific to
410Debian GNU/Linux, in which case it should be reported via the Debian Bug
411Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug).
412.PP 729.PP
413For other problems that also affect the Debian package, you can and 730Some Debian GNUL/Linux users seem to have this problem, although no
414probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a 731specific details were reported so far. It is possible that this is caused
415bug in the Debian version and it serves as a reminder for other users that 732by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how
416might encounter the same issue. 733this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible
417.Sh "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?" 734keymap. See the answer to the previous question, and please report if that
418.IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?" 735helped.
419You should build one binary with the default options. \fIconfigure\fR
420now enables most useful options, and the trend goes to making them
421runtime\-switchable, too, so there is usually no drawback to enbaling them,
422except higher disk and possibly memory usage. The perl interpreter should
423be enabled, as important functionality (menus, selection, likely more in
424the future) depends on it.
425.PP 736.PP
426You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources 737\fIMy Compose (Multi_key) key is no longer working.\fR
427system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful 738.IX Subsection "My Compose (Multi_key) key is no longer working."
428behaviour. If your distribution aims at low memory, add an empty
429\&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the
430perl interpreter disabled until the user enables it.
431.PP 739.PP
432If you can/want build more binaries, I recommend building a minimal 740The most common causes for this are that either your locale is not set
433one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with 741correctly, or you specified a \fBpreeditStyle\fR that is not supported by
434\&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of 742your input method. For example, if you specified \fBOverTheSpot\fR and
435encodings built-in that increase download times and are rarely used). 743your input method (e.g. the default input method handling Compose keys)
436.Sh "I need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?" 744does not support this (for instance because it is not visual), then
437.IX Subsection "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?" 745rxvt-unicode will continue without an input method.
438It should be, starting with release 7.1. You are encouraged to properly
439install urxvt with privileges necessary for your \s-1OS\s0 now.
440.PP 746.PP
441When rxvt-unicode detects that it runs setuid or setgid, it will fork 747In this case either do not specify a \fBpreeditStyle\fR or specify more than
442into a helper process for privileged operations (pty handling on some 748one pre-edit style, such as \fBOverTheSpot,Root,None\fR.
443systems, utmp/wtmp/lastlog handling on others) and drop privileges
444immediately. This is much safer than most other terminals that keep
445privileges while running (but is more relevant to urxvt, as it contains
446things as perl interpreters, which might be \*(L"helpful\*(R" to attackers).
447.PP 749.PP
448This forking is done as the very first within \fImain()\fR, which is very early 750\fII cannot type \f(CI\*(C`Ctrl\-Shift\-2\*(C'\fI to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755\fR
449and reduces possible bugs to initialisation code run before \fImain()\fR, or 751.IX Subsection "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755"
450things like the dynamic loader of your system, which should result in very 752.PP
451little risk. 753Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on
754international keyboards) or simply use \s-1ISO\s0 14755 support to your
755advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other
756codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape
757character and so on.
758.PP
759\fIMouse cut/paste suddenly no longer works.\fR
760.IX Subsection "Mouse cut/paste suddenly no longer works."
761.PP
762Make sure that mouse reporting is actually turned off since killing
763some editors prematurely may leave the mouse in mouse report mode. I've
764heard that tcsh may use mouse reporting unless it otherwise specified. A
765quick check is to see if cut/paste works when the Alt or Shift keys are
766depressed.
767.PP
768\fIWhat's with the strange Backspace/Delete key behaviour?\fR
769.IX Subsection "What's with the strange Backspace/Delete key behaviour?"
770.PP
771Assuming that the physical Backspace key corresponds to the
772BackSpace keysym (not likely for Linux ... see the following
773question) there are two standard values that can be used for
774Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR.
775.PP
776Historically, either value is correct, but rxvt-unicode adopts the debian
777policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct
778choice :).
779.PP
780Rxvt-unicode tries to inherit the current stty settings and uses the value
781of `erase' to guess the value for backspace. If rxvt-unicode wasn't
782started from a terminal (say, from a menu or by remote shell), then the
783system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will
784be used (which may not be the same as your stty setting).
785.PP
786For starting a new rxvt\-unicode:
787.PP
788.Vb 3
789\& # use Backspace = ^H
790\& $ stty erase ^H
791\& $ @@URXVT_NAME@@
792.Ve
793.PP
794.Vb 3
795\& # use Backspace = ^?
796\& $ stty erase ^?
797\& $ @@URXVT_NAME@@
798.Ve
799.PP
800Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR.
801.PP
802For an existing rxvt\-unicode:
803.PP
804.Vb 3
805\& # use Backspace = ^H
806\& $ stty erase ^H
807\& $ echo -n "^[[36h"
808.Ve
809.PP
810.Vb 3
811\& # use Backspace = ^?
812\& $ stty erase ^?
813\& $ echo -n "^[[36l"
814.Ve
815.PP
816This helps satisfy some of the Backspace discrepancies that occur, but
817if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value
818properly reflects that.
819.PP
820The Delete key is a another casualty of the ill-defined Backspace problem.
821To avoid confusion between the Backspace and Delete keys, the Delete
822key has been assigned an escape sequence to match the vt100 for Execute
823(\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo.
824.PP
825Some other Backspace problems:
826.PP
827some editors use termcap/terminfo,
828some editors (vim I'm told) expect Backspace = ^H,
829\&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help.
830.PP
831Perhaps someday this will all be resolved in a consistent manner.
832.PP
833\fII don't like the key\-bindings. How do I change them?\fR
834.IX Subsection "I don't like the key-bindings. How do I change them?"
835.PP
836There are some compile-time selections available via configure. Unless
837you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can
838use the `keysym' resource to alter the keystrings associated with keysyms.
839.PP
840Here's an example for a URxvt session started using \f(CW\*(C`@@URXVT_NAME@@ \-name URxvt\*(C'\fR
841.PP
842.Vb 20
843\& URxvt.keysym.Home: \e033[1~
844\& URxvt.keysym.End: \e033[4~
845\& URxvt.keysym.C-apostrophe: \e033<C-'>
846\& URxvt.keysym.C-slash: \e033<C-/>
847\& URxvt.keysym.C-semicolon: \e033<C-;>
848\& URxvt.keysym.C-grave: \e033<C-`>
849\& URxvt.keysym.C-comma: \e033<C-,>
850\& URxvt.keysym.C-period: \e033<C-.>
851\& URxvt.keysym.C-0x60: \e033<C-`>
852\& URxvt.keysym.C-Tab: \e033<C-Tab>
853\& URxvt.keysym.C-Return: \e033<C-Return>
854\& URxvt.keysym.S-Return: \e033<S-Return>
855\& URxvt.keysym.S-space: \e033<S-Space>
856\& URxvt.keysym.M-Up: \e033<M-Up>
857\& URxvt.keysym.M-Down: \e033<M-Down>
858\& URxvt.keysym.M-Left: \e033<M-Left>
859\& URxvt.keysym.M-Right: \e033<M-Right>
860\& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 >
861\& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz >
862\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007
863.Ve
864.PP
865See some more examples in the documentation for the \fBkeysym\fR resource.
866.PP
867\fII'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 map\fR
868.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 map"
869.PP
870.Vb 6
871\& KP_Insert == Insert
872\& F22 == Print
873\& F27 == Home
874\& F29 == Prior
875\& F33 == End
876\& F35 == Next
877.Ve
878.PP
879Rather than have rxvt-unicode try to accommodate all the various possible
880keyboard mappings, it is better to use `xmodmap' to remap the keys as
881required for your particular machine.
882.Sh "Terminal Configuration"
883.IX Subsection "Terminal Configuration"
884\fICan I see a typical configuration?\fR
885.IX Subsection "Can I see a typical configuration?"
886.PP
887The default configuration tries to be xterm\-like, which I don't like that
888much, but it's least surprise to regular users.
889.PP
890As a rxvt or rxvt-unicode user, you are practically supposed to invest
891time into customising your terminal. To get you started, here is the
892author's .Xdefaults entries, with comments on what they do. It's certainly
893not \fItypical\fR, but what's typical...
894.PP
895.Vb 2
896\& URxvt.cutchars: "()*,<>[]{}|'
897\& URxvt.print-pipe: cat >/tmp/xxx
898.Ve
899.PP
900These are just for testing stuff.
901.PP
902.Vb 2
903\& URxvt.imLocale: ja_JP.UTF-8
904\& URxvt.preeditType: OnTheSpot,None
905.Ve
906.PP
907This tells rxvt-unicode to use a special locale when communicating with
908the X Input Method, and also tells it to only use the OnTheSpot pre-edit
909type, which requires the \f(CW\*(C`xim\-onthespot\*(C'\fR perl extension but rewards me
910with correct-looking fonts.
911.PP
912.Vb 6
913\& URxvt.perl-lib: /root/lib/urxvt
914\& URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard
915\& URxvt.selection.pattern-0: ( at .*? line \e\ed+)
916\& URxvt.selection.pattern-1: ^(/[^:]+):\e
917\& URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\e\ed+):?$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/
918\& URxvt.selection-autotransform.1: s/^ at (.*?) line (\e\ed+)$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/
919.Ve
920.PP
921This is my perl configuration. The first two set the perl library
922directory and also tells urxvt to use a large number of extensions. I
923develop for myself mostly, so I actually use most of the extensions I
924write.
925.PP
926The selection stuff mainly makes the selection perl-error-message aware
927and tells it to convert pelr error mssages into vi-commands to load the
928relevant file and go tot he error line number.
929.PP
930.Vb 2
931\& URxvt.scrollstyle: plain
932\& URxvt.secondaryScroll: true
933.Ve
934.PP
935As the documentation says: plain is the preferred scrollbar for the
936author. The \f(CW\*(C`secondaryScroll\*(C'\fR confgiures urxvt to scroll in full-screen
937apps, like screen, so lines scorlled out of screen end up in urxvt's
938scrollback buffer.
939.PP
940.Vb 7
941\& URxvt.background: #000000
942\& URxvt.foreground: gray90
943\& URxvt.color7: gray90
944\& URxvt.colorBD: #ffffff
945\& URxvt.cursorColor: #e0e080
946\& URxvt.throughColor: #8080f0
947\& URxvt.highlightColor: #f0f0f0
948.Ve
949.PP
950Some colours. Not sure which ones are being used or even non\-defaults, but
951these are in my .Xdefaults. Most notably, they set foreground/background
952to light gray/black, and also make sure that the colour 7 matches the
953default foreground colour.
954.PP
955.Vb 1
956\& URxvt.underlineColor: yellow
957.Ve
958.PP
959Another colour, makes underline lines look different. Sometimes hurts, but
960is mostly a nice effect.
961.PP
962.Vb 4
963\& URxvt.geometry: 154x36
964\& URxvt.loginShell: false
965\& URxvt.meta: ignore
966\& URxvt.utmpInhibit: true
967.Ve
968.PP
969Uh, well, should be mostly self\-explanatory. By specifying some defaults
970manually, I can quickly switch them for testing.
971.PP
972.Vb 1
973\& URxvt.saveLines: 8192
974.Ve
975.PP
976A large scrollback buffer is essential. Really.
977.PP
978.Vb 1
979\& URxvt.mapAlert: true
980.Ve
981.PP
982The only case I use it is for my \s-1IRC\s0 window, which I like to keep
983iconified till people msg me (which beeps).
984.PP
985.Vb 1
986\& URxvt.visualBell: true
987.Ve
988.PP
989The audible bell is often annoying, especially when in a crowd.
990.PP
991.Vb 1
992\& URxvt.insecure: true
993.Ve
994.PP
995Please don't hack my mutt! Ooops...
996.PP
997.Vb 1
998\& URxvt.pastableTabs: false
999.Ve
1000.PP
1001I once thought this is a great idea.
1002.PP
1003.Vb 9
1004\& urxvt.font: 9x15bold,\e
1005\& -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\e
1006\& -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \e
1007\& [codeset=JISX0208]xft:Kochi Gothic, \e
1008\& xft:Bitstream Vera Sans Mono:autohint=true, \e
1009\& xft:Code2000:antialias=false
1010\& urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15
1011\& urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
1012\& urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
1013.Ve
1014.PP
1015I wrote rxvt-unicode to be able to specify fonts exactly. So don't be
1016overwhelmed. A special note: the \f(CW\*(C`9x15bold\*(C'\fR mentioend above is actually
1017the version from XFree\-3.3, as XFree\-4 replaced it by a totally different
1018font (different glyphs for \f(CW\*(C`;\*(C'\fR and many other harmless characters),
1019while the second font is actually the \f(CW\*(C`9x15bold\*(C'\fR from XFree4/XOrg. The
1020bold version has less chars than the medium version, so I use it for rare
1021characters, too. Whene ditign sources with vim, I use italic for comments
1022and other stuff, which looks quite good with Bitstream Vera anti\-aliased.
1023.PP
1024Terminus is a quite bad font (many very wrong glyphs), but for most of my
1025purposes, it works, and gives a different look, as my normal (Non\-bold)
1026font is already bold, and I want to see a difference between bold and
1027normal fonts.
1028.PP
1029Please note that I used the \f(CW\*(C`urxvt\*(C'\fR instance name and not the \f(CW\*(C`URxvt\*(C'\fR
1030class name. Thats because I use different configs for different purposes,
1031for example, my \s-1IRC\s0 window is started with \f(CW\*(C`\-name IRC\*(C'\fR, and uses these
1032defaults:
1033.PP
1034.Vb 9
1035\& IRC*title: IRC
1036\& IRC*geometry: 87x12+535+542
1037\& IRC*saveLines: 0
1038\& IRC*mapAlert: true
1039\& IRC*font: suxuseuro
1040\& IRC*boldFont: suxuseuro
1041\& IRC*colorBD: white
1042\& IRC*keysym.M-C-1: command:\e033]710;suxuseuro\e007\e033]711;suxuseuro\e007
1043\& IRC*keysym.M-C-2: command:\e033]710;9x15bold\e007\e033]711;9x15bold\e007
1044.Ve
1045.PP
1046\&\f(CW\*(C`Alt\-Shift\-1\*(C'\fR and \f(CW\*(C`Alt\-Shift\-2\*(C'\fR switch between two different font
1047sizes. \f(CW\*(C`suxuseuro\*(C'\fR allows me to keep an eye (and actually read)
1048stuff while keeping a very small window. If somebody pastes something
1049complicated (e.g. japanese), I temporarily switch to a larger font.
1050.PP
1051The above is all in my \f(CW\*(C`.Xdefaults\*(C'\fR (I don't use \f(CW\*(C`.Xresources\*(C'\fR nor
1052\&\f(CW\*(C`xrdb\*(C'\fR). I also have some resources in a separate \f(CW\*(C`.Xdefaults\-hostname\*(C'\fR
1053file for different hosts, for example, on ym main desktop, I use:
1054.PP
1055.Vb 5
1056\& URxvt.keysym.C-M-q: command:\e033[3;5;5t
1057\& URxvt.keysym.C-M-y: command:\e033[3;5;606t
1058\& URxvt.keysym.C-M-e: command:\e033[3;1605;5t
1059\& URxvt.keysym.C-M-c: command:\e033[3;1605;606t
1060\& URxvt.keysym.C-M-p: perl:test
1061.Ve
1062.PP
1063The first for keysym definitions allow me to quickly bring some windows
1064in the layout I like most. Ion users might start laughing but will stop
1065immediately when I tell them that I use my own Fvwm2 module for much the
1066same effect as Ion provides, and I only very rarely use the above key
1067combinations :\->
1068.PP
1069\fIWhy doesn't rxvt-unicode read my resources?\fR
1070.IX Subsection "Why doesn't rxvt-unicode read my resources?"
1071.PP
1072Well, why, indeed? It does, in a way very similar to other X
1073applications. Most importantly, this means that if you or your \s-1OS\s0 loads
1074resources into the X display (the right way to do it), rxvt-unicode will
1075ignore any resource files in your home directory. It will only read
1076\&\fI$HOME/.Xdefaults\fR when no resources are attached to the display.
1077.PP
1078If you have or use an \fI$HOME/.Xresources\fR file, chances are that
1079resources are loaded into your X\-server. In this case, you have to
1080re-login after every change (or run \fIxrdb \-merge \f(CI$HOME\fI/.Xresources\fR).
1081.PP
1082Also consider the form resources have to use:
1083.PP
1084.Vb 1
1085\& URxvt.resource: value
1086.Ve
1087.PP
1088If you want to use another form (there are lots of different ways of
1089specifying resources), make sure you understand wether and why it
1090works. If unsure, use the form above.
1091.PP
452.Sh "When I log-in to another system it tells me about missing terminfo data?" 1092\fIWhen I log-in to another system it tells me about missing terminfo data?\fR
453.IX Subsection "When I log-in to another system it tells me about missing terminfo data?" 1093.IX Subsection "When I log-in to another system it tells me about missing terminfo data?"
1094.PP
454The terminal description used by rxvt-unicode is not as widely available 1095The terminal description used by rxvt-unicode is not as widely available
455as that for xterm, or even rxvt (for which the same problem often arises). 1096as that for xterm, or even rxvt (for which the same problem often arises).
456.PP 1097.PP
457The correct solution for this problem is to install the terminfo, this can 1098The correct solution for this problem is to install the terminfo, this can
458be done like this (with ncurses' infocmp): 1099be done like this (with ncurses' infocmp):
… …
477.Vb 1 1118.Vb 1
478\& URxvt.termName: rxvt 1119\& URxvt.termName: rxvt
479.Ve 1120.Ve
480.PP 1121.PP
481If you don't plan to use \fBrxvt\fR (quite common...) you could also replace 1122If you don't plan to use \fBrxvt\fR (quite common...) you could also replace
482the rxvt terminfo file with the rxvt-unicode one. 1123the rxvt terminfo file with the rxvt-unicode one and use \f(CW\*(C`TERM=rxvt\*(C'\fR.
483.ie n .Sh """tic"" outputs some error when compiling the terminfo entry." 1124.PP
484.el .Sh "\f(CWtic\fP outputs some error when compiling the terminfo entry." 1125\fI\f(CI\*(C`tic\*(C'\fI outputs some error when compiling the terminfo entry.\fR
485.IX Subsection "tic outputs some error when compiling the terminfo entry." 1126.IX Subsection "tic outputs some error when compiling the terminfo entry."
1127.PP
486Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by 1128Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by
487\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. 1129\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again.
488.ie n .Sh """bash""'s readline does not work correctly under @@RXVT_NAME@@." 1130.PP
489.el .Sh "\f(CWbash\fP's readline does not work correctly under @@RXVT_NAME@@." 1131\fI\f(CI\*(C`bash\*(C'\fI's readline does not work correctly under @@URXVT_NAME@@.\fR
490.IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@." 1132.IX Subsection "bash's readline does not work correctly under @@URXVT_NAME@@."
1133.PP
1134See next entry.
1135.PP
491.Sh "I need a termcap file entry." 1136\fII need a termcap file entry.\fR
492.IX Subsection "I need a termcap file entry." 1137.IX Subsection "I need a termcap file entry."
1138.PP
493One reason you might want this is that some distributions or operating 1139One reason you might want this is that some distributions or operating
494systems still compile some programs using the long-obsoleted termcap 1140systems still compile some programs using the long-obsoleted termcap
495library (Fedora Core's bash is one example) and rely on a termcap entry 1141library (Fedora Core's bash is one example) and rely on a termcap entry
496for \f(CW\*(C`rxvt\-unicode\*(C'\fR. 1142for \f(CW\*(C`rxvt\-unicode\*(C'\fR.
497.PP 1143.PP
… …
525\& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e 1171\& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e
526\& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e 1172\& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e
527\& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e 1173\& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e
528\& :vs=\eE[?25h: 1174\& :vs=\eE[?25h:
529.Ve 1175.Ve
530.ie n .Sh "Why does ""ls"" no longer have coloured output?" 1176.PP
531.el .Sh "Why does \f(CWls\fP no longer have coloured output?" 1177\fIWhy does \f(CI\*(C`ls\*(C'\fI no longer have coloured output?\fR
532.IX Subsection "Why does ls no longer have coloured output?" 1178.IX Subsection "Why does ls no longer have coloured output?"
1179.PP
533The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to 1180The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to
534decide wether a terminal has colour, but uses it's own configuration 1181decide wether a terminal has colour, but uses it's own configuration
535file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among 1182file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among
536with most other terminals supporting colour). Either add: 1183with most other terminals supporting colour). Either add:
537.PP 1184.PP
… …
544.Vb 1 1191.Vb 1
545\& alias ls='ls --color=auto' 1192\& alias ls='ls --color=auto'
546.Ve 1193.Ve
547.PP 1194.PP
548to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR. 1195to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR.
1196.PP
549.Sh "Why doesn't vim/emacs etc. use the 88 colour mode?" 1197\fIWhy doesn't vim/emacs etc. use the 88 colour mode?\fR
550.IX Subsection "Why doesn't vim/emacs etc. use the 88 colour mode?" 1198.IX Subsection "Why doesn't vim/emacs etc. use the 88 colour mode?"
1199.PP
1200See next entry.
1201.PP
551.Sh "Why doesn't vim/emacs etc. make use of italic?" 1202\fIWhy doesn't vim/emacs etc. make use of italic?\fR
552.IX Subsection "Why doesn't vim/emacs etc. make use of italic?" 1203.IX Subsection "Why doesn't vim/emacs etc. make use of italic?"
1204.PP
1205See next entry.
1206.PP
553.Sh "Why are the secondary screen-related options not working properly?" 1207\fIWhy are the secondary screen-related options not working properly?\fR
554.IX Subsection "Why are the secondary screen-related options not working properly?" 1208.IX Subsection "Why are the secondary screen-related options not working properly?"
1209.PP
555Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged 1210Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged
556distributions (most notably Debian GNU/Linux) break rxvt-unicode 1211distributions (most notably Debian GNU/Linux) break rxvt-unicode
557by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra 1212by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra
558features. Unfortunately, some of these (most notably, again, Debian 1213features. Unfortunately, some of these (most notably, again, Debian
559GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo 1214GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
560file, so you will need to install it on your own (See the question \fBWhen 1215file, so you will need to install it on your own (See the question \fBWhen
561I log-in to another system it tells me about missing terminfo data?\fR on 1216I log-in to another system it tells me about missing terminfo data?\fR on
562how to do this). 1217how to do this).
563.Sh "My numerical keypad acts weird and generates differing output?" 1218.Sh "Encoding / Locale / Input Method Issues"
564.IX Subsection "My numerical keypad acts weird and generates differing output?" 1219.IX Subsection "Encoding / Locale / Input Method Issues"
565Some Debian GNUL/Linux users seem to have this problem, although no
566specific details were reported so far. It is possible that this is caused
567by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how
568this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible
569keymap. See the answer to the previous question, and please report if that
570helped.
571.Sh "Rxvt-unicode does not seem to understand the selected encoding?" 1220\fIRxvt-unicode does not seem to understand the selected encoding?\fR
572.IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?" 1221.IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?"
1222.PP
1223See next entry.
1224.PP
573.Sh "Unicode does not seem to work?" 1225\fIUnicode does not seem to work?\fR
574.IX Subsection "Unicode does not seem to work?" 1226.IX Subsection "Unicode does not seem to work?"
1227.PP
575If you encounter strange problems like typing an accented character but 1228If you encounter strange problems like typing an accented character but
576getting two unrelated other characters or similar, or if program output is 1229getting two unrelated other characters or similar, or if program output is
577subtly garbled, then you should check your locale settings. 1230subtly garbled, then you should check your locale settings.
578.PP 1231.PP
579Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the 1232Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the
… …
583.PP 1236.PP
584The best thing is to fix your startup environment, as you will likely run 1237The best thing is to fix your startup environment, as you will likely run
585into other problems. If nothing works you can try this in your .profile. 1238into other problems. If nothing works you can try this in your .profile.
586.PP 1239.PP
587.Vb 1 1240.Vb 1
588\& printf '\ee]701;%s\e007' "$LC_CTYPE" 1241\& printf '\e33]701;%s\e007' "$LC_CTYPE"
589.Ve 1242.Ve
590.PP 1243.PP
591If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not 1244If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not
592supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which 1245supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which
593displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as 1246displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as
… …
601Then the locale you specified is not supported on your system. 1254Then the locale you specified is not supported on your system.
602.PP 1255.PP
603If nothing works and you are sure that everything is set correctly then 1256If nothing works and you are sure that everything is set correctly then
604you will need to remember a little known fact: Some programs just don't 1257you will need to remember a little known fact: Some programs just don't
605support locales :( 1258support locales :(
606.Sh "Why do some characters look so much different than others?"
607.IX Subsection "Why do some characters look so much different than others?"
608.Sh "How does rxvt-unicode choose fonts?"
609.IX Subsection "How does rxvt-unicode choose fonts?"
610Most fonts do not contain the full range of Unicode, which is
611fine. Chances are that the font you (or the admin/package maintainer of
612your system/os) have specified does not cover all the characters you want
613to display.
614.PP 1259.PP
615\&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement 1260\fIHow does rxvt-unicode determine the encoding to use?\fR
616font. Often the result is fine, but sometimes the chosen font looks 1261.IX Subsection "How does rxvt-unicode determine the encoding to use?"
617bad/ugly/wrong. Some fonts have totally strange characters that don't
618resemble the correct glyph at all, and rxvt-unicode lacks the artificial
619intelligence to detect that a specific glyph is wrong: it has to believe
620the font that the characters it claims to contain indeed look correct.
621.PP 1262.PP
622In that case, select a font of your taste and add it to the font list, 1263See next entry.
623e.g.: 1264.PP
1265\fIIs there an option to switch encodings?\fR
1266.IX Subsection "Is there an option to switch encodings?"
1267.PP
1268Unlike some other terminals, rxvt-unicode has no encoding switch, and no
1269specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about
1270\&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O.
1271.PP
1272The reasons is that there exists a perfectly fine mechanism for selecting
1273the encoding, doing I/O and (most important) communicating this to all
1274applications so everybody agrees on character properties such as width
1275and code number. This mechanism is the \fIlocale\fR. Applications not using
1276that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of
1277characters wrong as it uses it's own, locale-independent table under all
1278locales).
1279.PP
1280Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All
1281programs doing the same (that is, most) will automatically agree in the
1282interpretation of characters.
1283.PP
1284Unfortunately, there is no system-independent way to select locales, nor
1285is there a standard on how locale specifiers will look like.
1286.PP
1287On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable
1288contains an arbitrary string which corresponds to an already-installed
1289locale. Common names for locales are \f(CW\*(C`en_US.UTF\-8\*(C'\fR, \f(CW\*(C`de_DE.ISO\-8859\-15\*(C'\fR,
1290\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms
1291(i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common.
1292.PP
1293Rxvt-unicode ignores all other locale categories, and except for
1294the encoding, ignores country or language-specific settings,
1295i.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
1296rxvt\-unicode.
1297.PP
1298If you want to use a specific encoding you have to make sure you start
1299rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category.
1300.PP
1301\fICan I switch locales at runtime?\fR
1302.IX Subsection "Can I switch locales at runtime?"
1303.PP
1304Yes, using an escape sequence. Try something like this, which sets
1305rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR.
624.PP 1306.PP
625.Vb 1 1307.Vb 1
626\& @@RXVT_NAME@@ -fn basefont,font2,font3... 1308\& printf '\e33]701;%s\e007' ja_JP.SJIS
627.Ve 1309.Ve
628.PP 1310.PP
629When rxvt-unicode sees a character, it will first look at the base 1311See also the previous answer.
630font. If the base font does not contain the character, it will go to the
631next font, and so on. Specifying your own fonts will also speed up this
632search and use less resources within rxvt-unicode and the X\-server.
633.PP 1312.PP
634The only limitation is that none of the fonts may be larger than the base 1313Sometimes this capability is rather handy when you want to work in
635font, as the base font defines the terminal character cell size, which 1314one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it
636must be the same due to the way terminals work. 1315(e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which
637.Sh "Why do some chinese characters look so different than others?" 1316first switches to a locale supported by xjdic and back later:
638.IX Subsection "Why do some chinese characters look so different than others?"
639This is because there is a difference between script and language \*(--
640rxvt-unicode does not know which language the text that is output is,
641as it only knows the unicode character codes. If rxvt-unicode first
642sees a japanese/chinese character, it might choose a japanese font for
643display. Subsequent japanese characters will use that font. Now, many
644chinese characters aren't represented in japanese fonts, so when the first
645non-japanese character comes up, rxvt-unicode will look for a chinese font
646\&\*(-- unfortunately at this point, it will still use the japanese font for
647chinese characters that are also in the japanese font.
648.PP 1317.PP
649The workaround is easy: just tag a chinese font at the end of your font 1318.Vb 3
650list (see the previous question). The key is to view the font list as 1319\& printf '\e33]701;%s\e007' ja_JP.SJIS
651a preference list: If you expect more japanese, list a japanese font 1320\& xjdic -js
652first. If you expect more chinese, put a chinese font first. 1321\& printf '\e33]701;%s\e007' de_DE.UTF-8
1322.Ve
653.PP 1323.PP
654In the future it might be possible to switch language preferences at 1324You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except
655runtime (the internal data structure has no problem with using different 1325for some locales where character width differs between program\- and
656fonts for the same character at the same time, but no interface for this 1326rxvt\-unicode\-locales.
657has been designed yet).
658.PP 1327.PP
659Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document). 1328\fII have problems getting my input method working.\fR
660.Sh "Why does rxvt-unicode sometimes leave pixel droppings?" 1329.IX Subsection "I have problems getting my input method working."
661.IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?"
662Most fonts were not designed for terminal use, which means that character
663size varies a lot. A font that is otherwise fine for terminal use might
664contain some characters that are simply too wide. Rxvt-unicode will avoid
665these characters. For characters that are just \*(L"a bit\*(R" too wide a special
666\&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters.
667.PP 1330.PP
668All of this requires that fonts do not lie about character sizes, 1331Try a search engine, as this is slightly different for every input method server.
669however: Xft fonts often draw glyphs larger than their acclaimed bounding
670box, and rxvt-unicode has no way of detecting this (the correct way is to
671ask for the character bounding box, which unfortunately is wrong in these
672cases).
673.PP 1332.PP
674It's not clear (to me at least), wether this is a bug in Xft, freetype, 1333Here is a checklist:
675or the respective font. If you encounter this problem you might try using 1334.IP "\- Make sure your locale \fIand\fR the imLocale are supported on your \s-1OS\s0." 4
676the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you 1335.IX Item "- Make sure your locale and the imLocale are supported on your OS."
677might be forced to use a different font. 1336Try \f(CW\*(C`locale \-a\*(C'\fR or check the documentation for your \s-1OS\s0.
1337.IP "\- Make sure your locale or imLocale matches a locale supported by your \s-1XIM\s0." 4
1338.IX Item "- Make sure your locale or imLocale matches a locale supported by your XIM."
1339For example, \fBkinput2\fR does not support \s-1UTF\-8\s0 locales, you should use
1340\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR or equivalent.
1341.IP "\- Make sure your \s-1XIM\s0 server is actually running." 4
1342.IX Item "- Make sure your XIM server is actually running."
1343.PD 0
1344.ie n .IP "\- Make sure the ""XMODIFIERS""\fR environment variable is set correctly when \fIstarting rxvt\-unicode." 4
1345.el .IP "\- Make sure the \f(CWXMODIFIERS\fR environment variable is set correctly when \fIstarting\fR rxvt\-unicode." 4
1346.IX Item "- Make sure the XMODIFIERS environment variable is set correctly when starting rxvt-unicode."
1347.PD
1348When you want to use e.g. \fBkinput2\fR, it must be set to
1349\&\f(CW\*(C`@im=kinput2\*(C'\fR. For \fBscim\fR, use \f(CW\*(C`@im=SCIM\*(C'\fR. Youc an see what input
1350method servers are running with this command:
1351.Sp
1352.Vb 1
1353\& xprop -root XIM_SERVERS
1354.Ve
1355.IP "*" 4
678.PP 1356.PP
679All of this is not a problem when using X11 core fonts, as their bounding 1357\fIMy input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?\fR
680box data is correct. 1358.IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?"
1359.PP
1360You can specify separate locales for the input method and the rest of the
1361terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
1362.PP
1363.Vb 1
1364\& URxvt.imlocale: ja_JP.EUC-JP
1365.Ve
1366.PP
1367Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still
1368use your input method. Please note, however, that, depending on your Xlib
1369version, you may not be able to input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a
1370normal way then, as your input method limits you.
1371.PP
1372\fIRxvt-unicode crashes when the X Input Method changes or exits.\fR
1373.IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits."
1374.PP
1375Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by
1376design. Applications can avoid some crashes at the expense of memory
1377leaks, and Input Methods can avoid some crashes by careful ordering at
1378exit time. \fBkinput2\fR (and derived input methods) generally succeeds,
1379while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however,
1380crashes cannot be completely avoided even if both sides cooperate.
1381.PP
1382So the only workaround is not to kill your Input Method Servers.
1383.Sh "Operating Systems / Package Maintaining"
1384.IX Subsection "Operating Systems / Package Maintaining"
1385\fII am using Debian GNU/Linux and have a problem...\fR
1386.IX Subsection "I am using Debian GNU/Linux and have a problem..."
1387.PP
1388The Debian GNU/Linux package of rxvt-unicode in sarge contains large
1389patches that considerably change the behaviour of rxvt-unicode (but
1390unfortunately this notice has been removed). Before reporting a bug to
1391the original rxvt-unicode author please download and install the genuine
1392version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce
1393the problem. If you cannot, chances are that the problems are specific to
1394Debian GNU/Linux, in which case it should be reported via the Debian Bug
1395Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug).
1396.PP
1397For other problems that also affect the Debian package, you can and
1398probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a
1399bug in the Debian version and it serves as a reminder for other users that
1400might encounter the same issue.
1401.PP
1402\fII am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?\fR
1403.IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?"
1404.PP
1405You should build one binary with the default options. \fIconfigure\fR
1406now enables most useful options, and the trend goes to making them
1407runtime\-switchable, too, so there is usually no drawback to enbaling them,
1408except higher disk and possibly memory usage. The perl interpreter should
1409be enabled, as important functionality (menus, selection, likely more in
1410the future) depends on it.
1411.PP
1412You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources
1413system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful
1414behaviour. If your distribution aims at low memory, add an empty
1415\&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the
1416perl interpreter disabled until the user enables it.
1417.PP
1418If you can/want build more binaries, I recommend building a minimal
1419one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with
1420\&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of
1421encodings built-in that increase download times and are rarely used).
1422.PP
1423\fII need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?\fR
1424.IX Subsection "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?"
1425.PP
1426It should be, starting with release 7.1. You are encouraged to properly
1427install urxvt with privileges necessary for your \s-1OS\s0 now.
1428.PP
1429When rxvt-unicode detects that it runs setuid or setgid, it will fork
1430into a helper process for privileged operations (pty handling on some
1431systems, utmp/wtmp/lastlog handling on others) and drop privileges
1432immediately. This is much safer than most other terminals that keep
1433privileges while running (but is more relevant to urxvt, as it contains
1434things as perl interpreters, which might be \*(L"helpful\*(R" to attackers).
1435.PP
1436This forking is done as the very first within \fImain()\fR, which is very early
1437and reduces possible bugs to initialisation code run before \fImain()\fR, or
1438things like the dynamic loader of your system, which should result in very
1439little risk.
1440.PP
681.Sh "On Solaris 9, many line-drawing characters are too wide." 1441\fIOn Solaris 9, many line-drawing characters are too wide.\fR
682.IX Subsection "On Solaris 9, many line-drawing characters are too wide." 1442.IX Subsection "On Solaris 9, many line-drawing characters are too wide."
1443.PP
683Seems to be a known bug, read 1444Seems to be a known bug, read
684<http://nixdoc.net/files/forum/about34198.html>. Some people use the 1445<http://nixdoc.net/files/forum/about34198.html>. Some people use the
685following ugly workaround to get non-double-wide-characters working: 1446following ugly workaround to get non-double-wide-characters working:
686.PP 1447.PP
687.Vb 1 1448.Vb 1
688\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) 1449\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
689.Ve 1450.Ve
690.Sh "My Compose (Multi_key) key is no longer working."
691.IX Subsection "My Compose (Multi_key) key is no longer working."
692The most common causes for this are that either your locale is not set
693correctly, or you specified a \fBpreeditStyle\fR that is not supported by
694your input method. For example, if you specified \fBOverTheSpot\fR and
695your input method (e.g. the default input method handling Compose keys)
696does not support this (for instance because it is not visual), then
697rxvt-unicode will continue without an input method.
698.PP 1451.PP
699In this case either do not specify a \fBpreeditStyle\fR or specify more than
700one pre-edit style, such as \fBOverTheSpot,Root,None\fR.
701.ie n .Sh "I cannot type ""Ctrl\-Shift\-2"" to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755"
702.el .Sh "I cannot type \f(CWCtrl\-Shift\-2\fP to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755"
703.IX Subsection "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755"
704Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on
705international keyboards) or simply use \s-1ISO\s0 14755 support to your
706advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other
707codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape
708character and so on.
709.Sh "How can I keep rxvt-unicode from using reverse video so much?"
710.IX Subsection "How can I keep rxvt-unicode from using reverse video so much?"
711First of all, make sure you are running with the right terminal settings
712(\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then
713make sure you have specified colours for italic and bold, as otherwise
714rxvt-unicode might use reverse video to simulate the effect:
715.PP
716.Vb 2
717\& URxvt.colorBD: white
718\& URxvt.colorIT: green
719.Ve
720.Sh "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
721.IX Subsection "Some programs assume totally weird colours (red instead of blue), how can I fix that?"
722For some unexplainable reason, some rare programs assume a very weird
723colour palette when confronted with a terminal with more than the standard
7248 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix
725these programs not to assume non-ISO colours without very good reasons.
726.PP
727In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo
728definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will
729fix colours but keep you from using other rxvt-unicode features.
730.Sh "I am on FreeBSD and rxvt-unicode does not seem to work at all." 1452\fII am on FreeBSD and rxvt-unicode does not seem to work at all.\fR
731.IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all." 1453.IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all."
1454.PP
732Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined 1455Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined
733in your compile environment, or an implementation that implements it, 1456in your compile environment, or an implementation that implements it,
734wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that 1457wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that
735\&\fBwchar_t\fR is represented as unicode. 1458\&\fBwchar_t\fR is represented as unicode.
736.PP 1459.PP
… …
756encodings slightly different than the terminal emulator). 1479encodings slightly different than the terminal emulator).
757.PP 1480.PP
758The rxvt-unicode author insists that the right way to fix this is in the 1481The rxvt-unicode author insists that the right way to fix this is in the
759system libraries once and for all, instead of forcing every app to carry 1482system libraries once and for all, instead of forcing every app to carry
760complete replacements for them :) 1483complete replacements for them :)
1484.PP
761.Sh "I use Solaris 9 and it doesn't compile/work/etc." 1485\fII use Solaris 9 and it doesn't compile/work/etc.\fR
762.IX Subsection "I use Solaris 9 and it doesn't compile/work/etc." 1486.IX Subsection "I use Solaris 9 and it doesn't compile/work/etc."
1487.PP
763Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst 1488Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst
764problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem. 1489problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem.
1490.PP
765.Sh "How can I use rxvt-unicode under cygwin?" 1491\fIHow can I use rxvt-unicode under cygwin?\fR
766.IX Subsection "How can I use rxvt-unicode under cygwin?" 1492.IX Subsection "How can I use rxvt-unicode under cygwin?"
1493.PP
767rxvt-unicode should compile and run out of the box on cygwin, using 1494rxvt-unicode should compile and run out of the box on cygwin, using
768the X11 libraries that come with cygwin. libW11 emulation is no 1495the X11 libraries that come with cygwin. libW11 emulation is no
769longer supported (and makes no sense, either, as it only supported a 1496longer supported (and makes no sense, either, as it only supported a
770single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or 1497single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or
771\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the 1498\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the
772old libW11 emulation. 1499old libW11 emulation.
773.PP 1500.PP
774At the time of this writing, cygwin didn't seem to support any multi-byte 1501At the time of this writing, cygwin didn't seem to support any multi-byte
775encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited 1502encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited
776to 8\-bit encodings. 1503to 8\-bit encodings.
777.Sh "How does rxvt-unicode determine the encoding to use?"
778.IX Subsection "How does rxvt-unicode determine the encoding to use?"
779.Sh "Is there an option to switch encodings?"
780.IX Subsection "Is there an option to switch encodings?"
781Unlike some other terminals, rxvt-unicode has no encoding switch, and no
782specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about
783\&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O.
784.PP
785The reasons is that there exists a perfectly fine mechanism for selecting
786the encoding, doing I/O and (most important) communicating this to all
787applications so everybody agrees on character properties such as width
788and code number. This mechanism is the \fIlocale\fR. Applications not using
789that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of
790characters wrong as it uses it's own, locale-independent table under all
791locales).
792.PP
793Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All
794programs doing the same (that is, most) will automatically agree in the
795interpretation of characters.
796.PP
797Unfortunately, there is no system-independent way to select locales, nor
798is there a standard on how locale specifiers will look like.
799.PP
800On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable
801contains an arbitrary string which corresponds to an already-installed
802locale. Common names for locales are \f(CW\*(C`en_US.UTF\-8\*(C'\fR, \f(CW\*(C`de_DE.ISO\-8859\-15\*(C'\fR,
803\&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms
804(i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common.
805.PP
806Rxvt-unicode ignores all other locale categories, and except for
807the encoding, ignores country or language-specific settings,
808i.e. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR and \f(CW\*(C`ja_JP.UTF\-8\*(C'\fR are the normally same to
809rxvt\-unicode.
810.PP
811If you want to use a specific encoding you have to make sure you start
812rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category.
813.Sh "Can I switch locales at runtime?"
814.IX Subsection "Can I switch locales at runtime?"
815Yes, using an escape sequence. Try something like this, which sets
816rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR.
817.PP
818.Vb 1
819\& printf '\ee]701;%s\e007' ja_JP.SJIS
820.Ve
821.PP
822See also the previous answer.
823.PP
824Sometimes this capability is rather handy when you want to work in
825one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it
826(e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which
827first switches to a locale supported by xjdic and back later:
828.PP
829.Vb 3
830\& printf '\ee]701;%s\e007' ja_JP.SJIS
831\& xjdic -js
832\& printf '\ee]701;%s\e007' de_DE.UTF-8
833.Ve
834.PP
835You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except
836for some locales where character width differs between program\- and
837rxvt\-unicode\-locales.
838.Sh "Can I switch the fonts at runtime?"
839.IX Subsection "Can I switch the fonts at runtime?"
840Yes, using an escape sequence. Try something like this, which has the same
841effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately:
842.PP
843.Vb 1
844\& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic"
845.Ve
846.PP
847This is useful if you e.g. work primarily with japanese (and prefer a
848japanese font), but you have to switch to chinese temporarily, where
849japanese fonts would only be in your way.
850.PP
851You can think of this as a kind of manual \s-1ISO\-2022\s0 switching.
852.Sh "Why do italic characters look as if clipped?"
853.IX Subsection "Why do italic characters look as if clipped?"
854Many fonts have difficulties with italic characters and hinting. For
855example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans
856Mono\*(C'\fR completely fails in it's italic face. A workaround might be to
857enable freetype autohinting, i.e. like this:
858.PP
859.Vb 2
860\& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true
861\& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true
862.Ve
863.Sh "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?"
864.IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?"
865You can specify separate locales for the input method and the rest of the
866terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR:
867.PP
868.Vb 1
869\& URxvt.imlocale: ja_JP.EUC-JP
870.Ve
871.PP
872Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still
873use your input method. Please note, however, that you will not be able to
874input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input
875method limits you.
876.Sh "Rxvt-unicode crashes when the X Input Method changes or exits."
877.IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits."
878Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by
879design. Applications can avoid some crashes at the expense of memory
880leaks, and Input Methods can avoid some crashes by careful ordering at
881exit time. \fBkinput2\fR (and derived input methods) generally succeeds,
882while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however,
883crashes cannot be completely avoided even if both sides cooperate.
884.PP
885So the only workaround is not to kill your Input Method Servers.
886.Sh "Rxvt-unicode uses gobs of memory, how can I reduce that?"
887.IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?"
888Rxvt-unicode tries to obey the rule of not charging you for something you
889don't use. One thing you should try is to configure out all settings that
890you don't need, for example, Xft support is a resource hog by design,
891when used. Compiling it out ensures that no Xft font will be loaded
892accidentally when rxvt-unicode tries to find a font for your characters.
893.PP
894Also, many people (me included) like large windows and even larger
895scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use
8966 bytes per screen cell. For a 160x?? window this amounts to almost a
897kilobyte per line. A scrollback buffer of 10000 lines will then (if full)
898use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as
899rxvt-unicode then uses 8 bytes per screen cell.
900.Sh "Can I speed up Xft rendering somehow?"
901.IX Subsection "Can I speed up Xft rendering somehow?"
902Yes, the most obvious way to speed it up is to avoid Xft entirely, as
903it is simply slow. If you still want Xft fonts you might try to disable
904antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of
905memory and also speeds up rendering considerably.
906.Sh "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
907.IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
908Rxvt-unicode will use whatever you specify as a font. If it needs to
909fall back to it's default font search list it will prefer X11 core
910fonts, because they are small and fast, and then use Xft fonts. It has
911antialiasing disabled for most of them, because the author thinks they
912look best that way.
913.PP
914If you want antialiasing, you have to specify the fonts manually.
915.Sh "Mouse cut/paste suddenly no longer works."
916.IX Subsection "Mouse cut/paste suddenly no longer works."
917Make sure that mouse reporting is actually turned off since killing
918some editors prematurely may leave the mouse in mouse report mode. I've
919heard that tcsh may use mouse reporting unless it otherwise specified. A
920quick check is to see if cut/paste works when the Alt or Shift keys are
921depressed.
922.Sh "What's with this bold/blink stuff?"
923.IX Subsection "What's with this bold/blink stuff?"
924If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the
925standard foreground colour.
926.PP
927For the standard background colour, blinking will actually make the
928text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard
929colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be
930ignored.
931.PP
932On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity
933foreground/background colors.
934.PP
935color0\-7 are the low-intensity colors.
936.PP
937color8\-15 are the corresponding high-intensity colors.
938.Sh "I don't like the screen colors. How do I change them?"
939.IX Subsection "I don't like the screen colors. How do I change them?"
940You can change the screen colors at run-time using \fI~/.Xdefaults\fR
941resources (or as long\-options).
942.PP
943Here are values that are supposed to resemble a \s-1VGA\s0 screen,
944including the murky brown that passes for low-intensity yellow:
945.PP
946.Vb 8
947\& URxvt.color0: #000000
948\& URxvt.color1: #A80000
949\& URxvt.color2: #00A800
950\& URxvt.color3: #A8A800
951\& URxvt.color4: #0000A8
952\& URxvt.color5: #A800A8
953\& URxvt.color6: #00A8A8
954\& URxvt.color7: #A8A8A8
955.Ve
956.PP
957.Vb 8
958\& URxvt.color8: #000054
959\& URxvt.color9: #FF0054
960\& URxvt.color10: #00FF54
961\& URxvt.color11: #FFFF54
962\& URxvt.color12: #0000FF
963\& URxvt.color13: #FF00FF
964\& URxvt.color14: #00FFFF
965\& URxvt.color15: #FFFFFF
966.Ve
967.PP
968And here is a more complete set of non-standard colors described (not by
969me) as \*(L"pretty girly\*(R".
970.PP
971.Vb 18
972\& URxvt.cursorColor: #dc74d1
973\& URxvt.pointerColor: #dc74d1
974\& URxvt.background: #0e0e0e
975\& URxvt.foreground: #4ad5e1
976\& URxvt.color0: #000000
977\& URxvt.color8: #8b8f93
978\& URxvt.color1: #dc74d1
979\& URxvt.color9: #dc74d1
980\& URxvt.color2: #0eb8c7
981\& URxvt.color10: #0eb8c7
982\& URxvt.color3: #dfe37e
983\& URxvt.color11: #dfe37e
984\& URxvt.color5: #9e88f0
985\& URxvt.color13: #9e88f0
986\& URxvt.color6: #73f7ff
987\& URxvt.color14: #73f7ff
988\& URxvt.color7: #e1dddd
989\& URxvt.color15: #e1dddd
990.Ve
991.Sh "How can I start @@RXVT_NAME@@d in a race-free way?"
992.IX Subsection "How can I start @@RXVT_NAME@@d in a race-free way?"
993Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the
994display, create the listening socket and then fork.
995.Sh "What's with the strange Backspace/Delete key behaviour?"
996.IX Subsection "What's with the strange Backspace/Delete key behaviour?"
997Assuming that the physical Backspace key corresponds to the
998BackSpace keysym (not likely for Linux ... see the following
999question) there are two standard values that can be used for
1000Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR.
1001.PP
1002Historically, either value is correct, but rxvt-unicode adopts the debian
1003policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct
1004choice :).
1005.PP
1006Rxvt-unicode tries to inherit the current stty settings and uses the value
1007of `erase' to guess the value for backspace. If rxvt-unicode wasn't
1008started from a terminal (say, from a menu or by remote shell), then the
1009system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will
1010be used (which may not be the same as your stty setting).
1011.PP
1012For starting a new rxvt\-unicode:
1013.PP
1014.Vb 3
1015\& # use Backspace = ^H
1016\& $ stty erase ^H
1017\& $ @@RXVT_NAME@@
1018.Ve
1019.PP
1020.Vb 3
1021\& # use Backspace = ^?
1022\& $ stty erase ^?
1023\& $ @@RXVT_NAME@@
1024.Ve
1025.PP
1026Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR.
1027.PP
1028For an existing rxvt\-unicode:
1029.PP
1030.Vb 3
1031\& # use Backspace = ^H
1032\& $ stty erase ^H
1033\& $ echo -n "^[[36h"
1034.Ve
1035.PP
1036.Vb 3
1037\& # use Backspace = ^?
1038\& $ stty erase ^?
1039\& $ echo -n "^[[36l"
1040.Ve
1041.PP
1042This helps satisfy some of the Backspace discrepancies that occur, but
1043if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value
1044properly reflects that.
1045.PP
1046The Delete key is a another casualty of the ill-defined Backspace problem.
1047To avoid confusion between the Backspace and Delete keys, the Delete
1048key has been assigned an escape sequence to match the vt100 for Execute
1049(\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo.
1050.PP
1051Some other Backspace problems:
1052.PP
1053some editors use termcap/terminfo,
1054some editors (vim I'm told) expect Backspace = ^H,
1055\&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help.
1056.PP
1057Perhaps someday this will all be resolved in a consistent manner.
1058.Sh "I don't like the key\-bindings. How do I change them?"
1059.IX Subsection "I don't like the key-bindings. How do I change them?"
1060There are some compile-time selections available via configure. Unless
1061you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can
1062use the `keysym' resource to alter the keystrings associated with keysyms.
1063.PP
1064Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR
1065.PP
1066.Vb 20
1067\& URxvt.keysym.Home: \e033[1~
1068\& URxvt.keysym.End: \e033[4~
1069\& URxvt.keysym.C-apostrophe: \e033<C-'>
1070\& URxvt.keysym.C-slash: \e033<C-/>
1071\& URxvt.keysym.C-semicolon: \e033<C-;>
1072\& URxvt.keysym.C-grave: \e033<C-`>
1073\& URxvt.keysym.C-comma: \e033<C-,>
1074\& URxvt.keysym.C-period: \e033<C-.>
1075\& URxvt.keysym.C-0x60: \e033<C-`>
1076\& URxvt.keysym.C-Tab: \e033<C-Tab>
1077\& URxvt.keysym.C-Return: \e033<C-Return>
1078\& URxvt.keysym.S-Return: \e033<S-Return>
1079\& URxvt.keysym.S-space: \e033<S-Space>
1080\& URxvt.keysym.M-Up: \e033<M-Up>
1081\& URxvt.keysym.M-Down: \e033<M-Down>
1082\& URxvt.keysym.M-Left: \e033<M-Left>
1083\& URxvt.keysym.M-Right: \e033<M-Right>
1084\& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 >
1085\& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz >
1086\& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007
1087.Ve
1088.PP
1089See some more examples in the documentation for the \fBkeysym\fR resource.
1090.Sh "I'm using keyboard model \s-1XXX\s0 that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize."
1091.IX Subsection "I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize."
1092.Vb 6
1093\& KP_Insert == Insert
1094\& F22 == Print
1095\& F27 == Home
1096\& F29 == Prior
1097\& F33 == End
1098\& F35 == Next
1099.Ve
1100.PP
1101Rather than have rxvt-unicode try to accommodate all the various possible
1102keyboard mappings, it is better to use `xmodmap' to remap the keys as
1103required for your particular machine.
1104.Sh "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
1105.IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc."
1106rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can
1107check and see if that is set. Note that several programs, \s-1JED\s0, slrn,
1108Midnight Commander automatically check this variable to decide whether or
1109not to use color.
1110.Sh "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?"
1111.IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?"
1112If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled
1113insecure mode then it is possible to use the following shell script
1114snippets to correctly set the display. If your version of rxvt-unicode
1115wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then
1116the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a
1117regular xterm.
1118.PP
1119Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script
1120snippets:
1121.PP
1122.Vb 12
1123\& # Bourne/Korn/POSIX family of shells:
1124\& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know
1125\& if [ ${TERM:-foo} = xterm ]; then
1126\& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not
1127\& echo -n '^[Z'
1128\& read term_id
1129\& stty icanon echo
1130\& if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then
1131\& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string
1132\& read DISPLAY # set it in our local shell
1133\& fi
1134\& fi
1135.Ve
1136.Sh "How do I compile the manual pages for myself?"
1137.IX Subsection "How do I compile the manual pages for myself?"
1138You need to have a recent version of perl installed as \fI/usr/bin/perl\fR,
1139one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to
1140the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR.
1141.Sh "My question isn't answered here, can I ask a human?"
1142.IX Subsection "My question isn't answered here, can I ask a human?"
1143Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR,
1144channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be
1145interested in learning about new and exciting problems (but not FAQs :).
1146.SH "RXVT TECHNICAL REFERENCE" 1504.SH "RXVT-UNICODE TECHNICAL REFERENCE"
1147.IX Header "RXVT TECHNICAL REFERENCE" 1505.IX Header "RXVT-UNICODE TECHNICAL REFERENCE"
1148.SH "DESCRIPTION"
1149.IX Header "DESCRIPTION"
1150The rest of this document describes various technical aspects of 1506The rest of this document describes various technical aspects of
1151\&\fBrxvt-unicode\fR. First the description of supported command sequences, 1507\&\fBrxvt-unicode\fR. First the description of supported command sequences,
1152followed by pixmap support and last by a description of all features 1508followed by pixmap support and last by a description of all features
1153selectable at \f(CW\*(C`configure\*(C'\fR time. 1509selectable at \f(CW\*(C`configure\*(C'\fR time.
1154.SH "Definitions" 1510.Sh "Definitions"
1155.IX Header "Definitions" 1511.IX Subsection "Definitions"
1156.ie n .IP "\fB\fB""c""\fB\fR" 4 1512.ie n .IP "\fB\fB""c""\fB\fR" 4
1157.el .IP "\fB\f(CBc\fB\fR" 4 1513.el .IP "\fB\f(CBc\fB\fR" 4
1158.IX Item "c" 1514.IX Item "c"
1159The literal character c. 1515The literal character c.
1160.ie n .IP "\fB\fB""C""\fB\fR" 4 1516.ie n .IP "\fB\fB""C""\fB\fR" 4
… …
1173parameters, separated by \f(CW\*(C`;\*(C'\fR character(s). 1529parameters, separated by \f(CW\*(C`;\*(C'\fR character(s).
1174.ie n .IP "\fB\fB""Pt""\fB\fR" 4 1530.ie n .IP "\fB\fB""Pt""\fB\fR" 4
1175.el .IP "\fB\f(CBPt\fB\fR" 4 1531.el .IP "\fB\f(CBPt\fB\fR" 4
1176.IX Item "Pt" 1532.IX Item "Pt"
1177A text parameter composed of printable characters. 1533A text parameter composed of printable characters.
1178.SH "Values" 1534.Sh "Values"
1179.IX Header "Values" 1535.IX Subsection "Values"
1180.ie n .IP "\fB\fB""ENQ""\fB\fR" 4 1536.ie n .IP "\fB\fB""ENQ""\fB\fR" 4
1181.el .IP "\fB\f(CBENQ\fB\fR" 4 1537.el .IP "\fB\f(CBENQ\fB\fR" 4
1182.IX Item "ENQ" 1538.IX Item "ENQ"
1183Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0) 1539Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0)
1184request attributes from terminal. See \fB\f(CB\*(C`ESC [ Ps c\*(C'\fB\fR. 1540request attributes from terminal. See \fB\f(CB\*(C`ESC [ Ps c\*(C'\fB\fR.
… …
1222Switch to Standard Character Set 1578Switch to Standard Character Set
1223.ie n .IP "\fB\fB""SPC""\fB\fR" 4 1579.ie n .IP "\fB\fB""SPC""\fB\fR" 4
1224.el .IP "\fB\f(CBSPC\fB\fR" 4 1580.el .IP "\fB\f(CBSPC\fB\fR" 4
1225.IX Item "SPC" 1581.IX Item "SPC"
1226Space Character 1582Space Character
1227.SH "Escape Sequences" 1583.Sh "Escape Sequences"
1228.IX Header "Escape Sequences" 1584.IX Subsection "Escape Sequences"
1229.ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4 1585.ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4
1230.el .IP "\fB\f(CBESC # 8\fB\fR" 4 1586.el .IP "\fB\f(CBESC # 8\fB\fR" 4
1231.IX Item "ESC # 8" 1587.IX Item "ESC # 8"
1232\&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0) 1588\&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0)
1233.ie n .IP "\fB\fB""ESC 7""\fB\fR" 4 1589.ie n .IP "\fB\fB""ESC 7""\fB\fR" 4
… …
1326.TE 1682.TE
1327 1683
1328.PP 1684.PP
1329 1685
1330.IX Xref "CSI" 1686.IX Xref "CSI"
1331.SH "CSI (Command Sequence Introducer) Sequences" 1687.Sh "\s-1CSI\s0 (Command Sequence Introducer) Sequences"
1332.IX Header "CSI (Command Sequence Introducer) Sequences" 1688.IX Subsection "CSI (Command Sequence Introducer) Sequences"
1333.ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4 1689.ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4
1334.el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4 1690.el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4
1335.IX Item "ESC [ Ps @" 1691.IX Item "ESC [ Ps @"
1336Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR (Blank) Character(s) [default: 1] (\s-1ICH\s0) 1692Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR (Blank) Character(s) [default: 1] (\s-1ICH\s0)
1337.IX Xref "ESCOBPsA" 1693.IX Xref "ESCOBPsA"
… …
1600.IX Item "ESC [ Ps x" 1956.IX Item "ESC [ Ps x"
1601Request Terminal Parameters (\s-1DECREQTPARM\s0) 1957Request Terminal Parameters (\s-1DECREQTPARM\s0)
1602.PP 1958.PP
1603 1959
1604.IX Xref "PrivateModes" 1960.IX Xref "PrivateModes"
1605.SH "DEC Private Modes" 1961.Sh "\s-1DEC\s0 Private Modes"
1606.IX Header "DEC Private Modes" 1962.IX Subsection "DEC Private Modes"
1607.ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4 1963.ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4
1608.el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4 1964.el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4
1609.IX Item "ESC [ ? Pm h" 1965.IX Item "ESC [ ? Pm h"
1610\&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0) 1966\&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0)
1611.ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4 1967.ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4
… …
1878.RE 2234.RE
1879.PD 2235.PD
1880.PP 2236.PP
1881 2237
1882.IX Xref "XTerm" 2238.IX Xref "XTerm"
1883.SH "XTerm Operating System Commands" 2239.Sh "XTerm Operating System Commands"
1884.IX Header "XTerm Operating System Commands" 2240.IX Subsection "XTerm Operating System Commands"
1885.ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4 2241.ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4
1886.el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4 2242.el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4
1887.IX Item "ESC ] Ps;Pt ST" 2243.IX Item "ESC ] Ps;Pt ST"
1888Set XTerm Parameters. 8\-bit \s-1ST:\s0 0x9c, 7\-bit \s-1ST\s0 sequence: \s-1ESC\s0 \e (0x1b, 2244Set XTerm Parameters. 8\-bit \s-1ST:\s0 0x9c, 7\-bit \s-1ST\s0 sequence: \s-1ESC\s0 \e (0x1b,
18890x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any 22450x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any
… …
1921Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). 2277Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1922Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). 2278Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills).
1923Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl). 2279Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl).
1924.TE 2280.TE
1925 2281
1926.PP
1927
1928.IX Xref "XPM"
1929.SH "XPM" 2282.SH "XPM"
1930.IX Header "XPM" 2283.IX Header "XPM"
1931For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value 2284For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value
1932of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a 2285of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a
1933sequence of scaling/positioning commands separated by semi\-colons. The 2286sequence of scaling/positioning commands separated by semi\-colons. The
… …
2003.TS 2356.TS
2004l l . 2357l l .
20054 Shift 23584 Shift
20068 Meta 23598 Meta
200716 Control 236016 Control
200832 Double Click (Rxvt extension) 236132 Double Click (rxvt extension)
2009.TE 2362.TE
2010 2363
2011Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR 2364Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR
2012.Sp 2365.Sp
2013Row = \fB\f(CB\*(C`<y> \- SPACE\*(C'\fB\fR 2366Row = \fB\f(CB\*(C`<y> \- SPACE\*(C'\fB\fR
… …
2302.IX Item "--disable-new-selection" 2655.IX Item "--disable-new-selection"
2303Remove support for mouse selection style like that of xterm. 2656Remove support for mouse selection style like that of xterm.
2304.IP "\-\-enable\-dmalloc (default: off)" 4 2657.IP "\-\-enable\-dmalloc (default: off)" 4
2305.IX Item "--enable-dmalloc (default: off)" 2658.IX Item "--enable-dmalloc (default: off)"
2306Use Gray Watson's malloc \- which is good for debugging See 2659Use Gray Watson's malloc \- which is good for debugging See
2307http://www.letters.com/dmalloc/ for details If you use either this or the 2660<http://www.letters.com/dmalloc/> for details If you use either this or the
2308next option, you may need to edit src/Makefile after compiling to point 2661next option, you may need to edit src/Makefile after compiling to point
2309\&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places. 2662\&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places.
2310.Sp 2663.Sp
2311You can only use either this option and the following (should 2664You can only use either this option and the following (should
2312you use either) . 2665you use either) .

Diff Legend

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