… | |
… | |
21 | The newest version of this document is also available on the World Wide Web at |
21 | The newest version of this document is also available on the World Wide Web at |
22 | L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. |
22 | L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. |
23 | |
23 | |
24 | =head1 FREQUENTLY ASKED QUESTIONS |
24 | =head1 FREQUENTLY ASKED QUESTIONS |
25 | |
25 | |
26 | =head2 The new selection selects pieces that are too big, how can I select single words? |
|
|
27 | |
26 | |
28 | If you want to select e.g. alphanumeric words, you can use the following |
27 | =head2 Meta, Features & Commandline Issues |
29 | setting: |
|
|
30 | |
28 | |
31 | URxvt.selection.pattern-0: ([[:word:]]+) |
29 | =head3 My question isn't answered here, can I ask a human? |
32 | |
30 | |
33 | If you click more than twice, the selection will be extended |
31 | Before sending me mail, you could go to IRC: C<irc.freenode.net>, |
34 | more and more. |
32 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
|
|
33 | interested in learning about new and exciting problems (but not FAQs :). |
35 | |
34 | |
36 | To get a selection that is very similar to the old code, try this pattern: |
35 | =head3 Does it support tabs, can I have a tabbed rxvt-unicode? |
37 | |
36 | |
38 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
37 | Beginning with version 7.3, there is a perl extension that implements a |
|
|
38 | simple tabbed terminal. It is installed by default, so any of these should |
|
|
39 | give you tabs: |
39 | |
40 | |
40 | Please also note that the I<LeftClick Shift-LeftClik> combination also |
41 | @@RXVT_NAME@@ -pe tabbed |
41 | selects words like the old code. |
|
|
42 | |
42 | |
43 | =head2 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
|
|
44 | |
|
|
45 | You can disable the perl extension completely by setting the |
|
|
46 | B<perl-ext-common> resource to the empty string, which also keeps |
|
|
47 | rxvt-unicode from initialising perl, saving memory. |
|
|
48 | |
|
|
49 | If you only want to disable specific features, you first have to |
|
|
50 | identify which perl extension is responsible. For this, read the section |
|
|
51 | B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For |
|
|
52 | example, to disable the B<selection-popup> and B<option-popup>, specify |
|
|
53 | this B<perl-ext-common> resource: |
|
|
54 | |
|
|
55 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
|
|
56 | |
|
|
57 | This will keep the default extensions, but disable the two popup |
|
|
58 | extensions. Some extensions can also be configured, for example, |
|
|
59 | scrollback search mode is triggered by B<M-s>. You can move it to any |
|
|
60 | other combination either by setting the B<searchable-scrollback> resource: |
|
|
61 | |
|
|
62 | URxvt.searchable-scrollback: CM-s |
|
|
63 | |
|
|
64 | =head2 The cursor moves when selecting text in the current input line, how do I switch this off? |
|
|
65 | |
|
|
66 | See next entry. |
|
|
67 | |
|
|
68 | =head2 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
|
|
69 | |
|
|
70 | These are caused by the C<readline> perl extension. Under normal |
|
|
71 | circumstances, it will move your cursor around when you click into the |
|
|
72 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
73 | but when running a program that doesn't parse cursor movements or in some |
|
|
74 | cases during rlogin sessions, it fails to detect this properly. |
|
|
75 | |
|
|
76 | You can permamently switch this feature off by disabling the C<readline> |
|
|
77 | extension: |
|
|
78 | |
|
|
79 | URxvt.perl-ext-common: default,-readline |
43 | URxvt.perl-ext-common: default,tabbed |
80 | |
44 | |
81 | =head2 Why doesn't rxvt-unicode read my resources? |
45 | It will also work fine with tabbing functionality of many window managers |
|
|
46 | or similar tabbing programs, and its embedding-features allow it to be |
|
|
47 | embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or |
|
|
48 | the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt |
|
|
49 | (murxvt) terminal as an example embedding application. |
82 | |
50 | |
83 | Well, why, indeed? It does, in a way very similar to other X |
51 | =head3 How do I know which rxvt-unicode version I'm using? |
84 | applications. Most importantly, this means that if you or your OS loads |
|
|
85 | resources into the X display (the right way to do it), rxvt-unicode will |
|
|
86 | ignore any resource files in your home directory. It will only read |
|
|
87 | F<$HOME/.Xdefaults> when no resources are attached to the display. |
|
|
88 | |
52 | |
89 | If you have or use an F<$HOME/.Xresources> file, chances are that |
53 | The version number is displayed with the usage (-h). Also the escape |
90 | resources are loaded into your X-server. In this case, you have to |
54 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
91 | re-login after every change (or run F<xrdb -merge $HOME/.Xresources>). |
55 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
|
|
56 | daemon. |
92 | |
57 | |
93 | Also consider the form resources have to use: |
58 | =head3 Rxvt-unicode uses gobs of memory, how can I reduce that? |
94 | |
59 | |
95 | URxvt.resource: value |
60 | Rxvt-unicode tries to obey the rule of not charging you for something you |
|
|
61 | don't use. One thing you should try is to configure out all settings that |
|
|
62 | you don't need, for example, Xft support is a resource hog by design, |
|
|
63 | when used. Compiling it out ensures that no Xft font will be loaded |
|
|
64 | accidentally when rxvt-unicode tries to find a font for your characters. |
96 | |
65 | |
97 | If you want to use another form (there are lots of different ways of |
66 | Also, many people (me included) like large windows and even larger |
98 | specifying resources), make sure you understand wether and why it |
67 | scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use |
99 | works. If unsure, use the form above. |
68 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
|
|
69 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
|
|
70 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
|
|
71 | rxvt-unicode then uses 8 bytes per screen cell. |
100 | |
72 | |
101 | =head2 I can't get transparency working, what am I doing wrong? |
73 | =head3 How can I start @@RXVT_NAME@@d in a race-free way? |
102 | |
74 | |
103 | First of all, transparency isn't officially supported in rxvt-unicode, so |
75 | Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the |
104 | you are mostly on your own. Do not bug the author about it (but you may |
76 | display, create the listening socket and then fork. |
105 | bug everybody else). Also, if you can't get it working consider it a rite |
|
|
106 | of passage: ... and you failed. |
|
|
107 | |
77 | |
108 | Here are four ways to get transparency. B<Do> read the manpage and option |
78 | =head3 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
109 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
|
|
110 | |
79 | |
111 | 1. Use inheritPixmap: |
80 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
|
|
81 | check and see if that is set. Note that several programs, JED, slrn, |
|
|
82 | Midnight Commander automatically check this variable to decide whether or |
|
|
83 | not to use color. |
112 | |
84 | |
113 | Esetroot wallpaper.jpg |
85 | =head3 How do I set the correct, full IP address for the DISPLAY variable? |
114 | @@RXVT_NAME@@ -ip -tint red -sh 40 |
|
|
115 | |
86 | |
116 | That works. If you think it doesn't, you lack transparency and tinting |
87 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
117 | support, or you are unable to read. |
88 | insecure mode then it is possible to use the following shell script |
|
|
89 | snippets to correctly set the display. If your version of rxvt-unicode |
|
|
90 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
|
|
91 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
|
|
92 | regular xterm. |
118 | |
93 | |
119 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
94 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
120 | to use effects other than tinting and shading: Just shade/tint/whatever |
95 | snippets: |
121 | your picture with gimp: |
|
|
122 | |
96 | |
123 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
97 | # Bourne/Korn/POSIX family of shells: |
124 | @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background |
98 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
|
|
99 | if [ ${TERM:-foo} = xterm ]; then |
|
|
100 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
|
|
101 | echo -n '^[Z' |
|
|
102 | read term_id |
|
|
103 | stty icanon echo |
|
|
104 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
|
|
105 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
|
|
106 | read DISPLAY # set it in our local shell |
|
|
107 | fi |
|
|
108 | fi |
125 | |
109 | |
126 | That works. If you think it doesn't, you lack XPM and Perl support, or you |
110 | =head3 How do I compile the manual pages on my own? |
127 | are unable to read. |
|
|
128 | |
111 | |
129 | 3. Use an ARGB visual: |
112 | You need to have a recent version of perl installed as F</usr/bin/perl>, |
|
|
113 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
|
|
114 | the doc subdirectory and enter C<make alldoc>. |
130 | |
115 | |
131 | @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
|
|
132 | |
|
|
133 | This requires XFT support, and the support of your X-server. If that |
|
|
134 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
|
|
135 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
|
|
136 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
|
|
137 | doesn't mean that your WM has the required kludges in place. |
|
|
138 | |
|
|
139 | 4. Use xcompmgr and let it do the job: |
|
|
140 | |
|
|
141 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
|
|
142 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
|
|
143 | |
|
|
144 | Then click on a window you want to make transparent. Replace C<0xc0000000> |
|
|
145 | by other values to change the degree of opacity. If it doesn't work and |
|
|
146 | your server crashes, you got to keep the pieces. |
|
|
147 | |
|
|
148 | =head2 Isn't rxvt supposed to be small? Don't all those features bloat? |
116 | =head3 Isn't rxvt-unicode supposed to be small? Don't all those features bloat? |
149 | |
117 | |
150 | I often get asked about this, and I think, no, they didn't cause extra |
118 | I often get asked about this, and I think, no, they didn't cause extra |
151 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
119 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
152 | that the urxvt binary is larger (due to some encoding tables always being |
120 | that the urxvt binary is larger (due to some encoding tables always being |
153 | compiled in), but it actually uses less memory (RSS) after startup. Even |
121 | compiled in), but it actually uses less memory (RSS) after startup. Even |
… | |
… | |
185 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
153 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
186 | 43180k in daemons that stay around after exit, plus half a minute of |
154 | 43180k in daemons that stay around after exit, plus half a minute of |
187 | startup time, including the hundreds of warnings it spits out), it fares |
155 | startup time, including the hundreds of warnings it spits out), it fares |
188 | extremely well *g*. |
156 | extremely well *g*. |
189 | |
157 | |
190 | =head2 Why C++, isn't that unportable/bloated/uncool? |
158 | =head3 Why C++, isn't that unportable/bloated/uncool? |
191 | |
159 | |
192 | Is this a question? :) It comes up very often. The simple answer is: I had |
160 | Is this a question? :) It comes up very often. The simple answer is: I had |
193 | to write it, and C++ allowed me to write and maintain it in a fraction |
161 | to write it, and C++ allowed me to write and maintain it in a fraction |
194 | of the time and effort (which is a scarce resource for me). Put even |
162 | of the time and effort (which is a scarce resource for me). Put even |
195 | shorter: It simply wouldn't exist without C++. |
163 | shorter: It simply wouldn't exist without C++. |
… | |
… | |
219 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
187 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
220 | |
188 | |
221 | No large bloated libraries (of course, none were linked in statically), |
189 | No large bloated libraries (of course, none were linked in statically), |
222 | except maybe libX11 :) |
190 | except maybe libX11 :) |
223 | |
191 | |
224 | =head2 Does it support tabs, can I have a tabbed rxvt-unicode? |
|
|
225 | |
192 | |
226 | Beginning with version 7.3, there is a perl extension that implements a |
193 | =head2 Rendering, Font & Look and Feel Issues |
227 | simple tabbed terminal. It is installed by default, so any of these should |
|
|
228 | give you tabs: |
|
|
229 | |
194 | |
230 | @@RXVT_NAME@@ -pe tabbed |
195 | =head3 I can't get transparency working, what am I doing wrong? |
231 | |
196 | |
|
|
197 | First of all, transparency isn't officially supported in rxvt-unicode, so |
|
|
198 | you are mostly on your own. Do not bug the author about it (but you may |
|
|
199 | bug everybody else). Also, if you can't get it working consider it a rite |
|
|
200 | of passage: ... and you failed. |
|
|
201 | |
|
|
202 | Here are four ways to get transparency. B<Do> read the manpage and option |
|
|
203 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
|
|
204 | |
|
|
205 | 1. Use inheritPixmap: |
|
|
206 | |
|
|
207 | Esetroot wallpaper.jpg |
|
|
208 | @@RXVT_NAME@@ -ip -tint red -sh 40 |
|
|
209 | |
|
|
210 | That works. If you think it doesn't, you lack transparency and tinting |
|
|
211 | support, or you are unable to read. |
|
|
212 | |
|
|
213 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
|
|
214 | to use effects other than tinting and shading: Just shade/tint/whatever |
|
|
215 | your picture with gimp or any other tool: |
|
|
216 | |
|
|
217 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
|
|
218 | @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background |
|
|
219 | |
|
|
220 | That works. If you think it doesn't, you lack XPM and Perl support, or you |
|
|
221 | are unable to read. |
|
|
222 | |
|
|
223 | 3. Use an ARGB visual: |
|
|
224 | |
|
|
225 | @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
|
|
226 | |
|
|
227 | This requires XFT support, and the support of your X-server. If that |
|
|
228 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
|
|
229 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
|
|
230 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
|
|
231 | doesn't mean that your WM has the required kludges in place. |
|
|
232 | |
|
|
233 | 4. Use xcompmgr and let it do the job: |
|
|
234 | |
|
|
235 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
|
|
236 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
|
|
237 | |
|
|
238 | Then click on a window you want to make transparent. Replace C<0xc0000000> |
|
|
239 | by other values to change the degree of opacity. If it doesn't work and |
|
|
240 | your server crashes, you got to keep the pieces. |
|
|
241 | |
|
|
242 | =head3 Why do some chinese characters look so different than others? |
|
|
243 | |
|
|
244 | This is because there is a difference between script and language -- |
|
|
245 | rxvt-unicode does not know which language the text that is output is, |
|
|
246 | as it only knows the unicode character codes. If rxvt-unicode first |
|
|
247 | sees a japanese/chinese character, it might choose a japanese font for |
|
|
248 | display. Subsequent japanese characters will use that font. Now, many |
|
|
249 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
250 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
251 | -- unfortunately at this point, it will still use the japanese font for |
|
|
252 | chinese characters that are also in the japanese font. |
|
|
253 | |
|
|
254 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
255 | list (see the previous question). The key is to view the font list as |
|
|
256 | a preference list: If you expect more japanese, list a japanese font |
|
|
257 | first. If you expect more chinese, put a chinese font first. |
|
|
258 | |
|
|
259 | In the future it might be possible to switch language preferences at |
|
|
260 | runtime (the internal data structure has no problem with using different |
|
|
261 | fonts for the same character at the same time, but no interface for this |
|
|
262 | has been designed yet). |
|
|
263 | |
|
|
264 | Until then, you might get away with switching fonts at runtime (see L<Can |
|
|
265 | I switch the fonts at runtime?> later in this document). |
|
|
266 | |
|
|
267 | =head3 Why does rxvt-unicode sometimes leave pixel droppings? |
|
|
268 | |
|
|
269 | Most fonts were not designed for terminal use, which means that character |
|
|
270 | size varies a lot. A font that is otherwise fine for terminal use might |
|
|
271 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
|
|
272 | these characters. For characters that are just "a bit" too wide a special |
|
|
273 | "careful" rendering mode is used that redraws adjacent characters. |
|
|
274 | |
|
|
275 | All of this requires that fonts do not lie about character sizes, |
|
|
276 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
|
|
277 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
|
|
278 | ask for the character bounding box, which unfortunately is wrong in these |
|
|
279 | cases). |
|
|
280 | |
|
|
281 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
|
|
282 | or the respective font. If you encounter this problem you might try using |
|
|
283 | the C<-lsp> option to give the font more height. If that doesn't work, you |
|
|
284 | might be forced to use a different font. |
|
|
285 | |
|
|
286 | All of this is not a problem when using X11 core fonts, as their bounding |
|
|
287 | box data is correct. |
|
|
288 | |
|
|
289 | =head3 How can I keep rxvt-unicode from using reverse video so much? |
|
|
290 | |
|
|
291 | First of all, make sure you are running with the right terminal settings |
|
|
292 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
|
|
293 | make sure you have specified colours for italic and bold, as otherwise |
|
|
294 | rxvt-unicode might use reverse video to simulate the effect: |
|
|
295 | |
|
|
296 | URxvt.colorBD: white |
|
|
297 | URxvt.colorIT: green |
|
|
298 | |
|
|
299 | =head3 Some programs assume totally weird colours (red instead of blue), how can I fix that? |
|
|
300 | |
|
|
301 | For some unexplainable reason, some rare programs assume a very weird |
|
|
302 | colour palette when confronted with a terminal with more than the standard |
|
|
303 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
|
|
304 | these programs not to assume non-ISO colours without very good reasons. |
|
|
305 | |
|
|
306 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
|
|
307 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
|
|
308 | fix colours but keep you from using other rxvt-unicode features. |
|
|
309 | |
|
|
310 | =head3 Can I switch the fonts at runtime? |
|
|
311 | |
|
|
312 | Yes, using an escape sequence. Try something like this, which has the same |
|
|
313 | effect as using the C<-fn> switch, and takes effect immediately: |
|
|
314 | |
|
|
315 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
|
|
316 | |
|
|
317 | This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
318 | japanese font), but you have to switch to chinese temporarily, where |
|
|
319 | japanese fonts would only be in your way. |
|
|
320 | |
|
|
321 | You can think of this as a kind of manual ISO-2022 switching. |
|
|
322 | |
|
|
323 | =head3 Why do italic characters look as if clipped? |
|
|
324 | |
|
|
325 | Many fonts have difficulties with italic characters and hinting. For |
|
|
326 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
|
|
327 | Mono> completely fails in it's italic face. A workaround might be to |
|
|
328 | enable freetype autohinting, i.e. like this: |
|
|
329 | |
|
|
330 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
331 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
332 | |
|
|
333 | =head3 Can I speed up Xft rendering somehow? |
|
|
334 | |
|
|
335 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
336 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
337 | antialiasing (by appending C<:antialias=false>), which saves lots of |
|
|
338 | memory and also speeds up rendering considerably. |
|
|
339 | |
|
|
340 | =head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
|
|
341 | |
|
|
342 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
343 | fall back to it's default font search list it will prefer X11 core |
|
|
344 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
345 | antialiasing disabled for most of them, because the author thinks they |
|
|
346 | look best that way. |
|
|
347 | |
|
|
348 | If you want antialiasing, you have to specify the fonts manually. |
|
|
349 | |
|
|
350 | =head3 What's with this bold/blink stuff? |
|
|
351 | |
|
|
352 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
|
|
353 | standard foreground colour. |
|
|
354 | |
|
|
355 | For the standard background colour, blinking will actually make the |
|
|
356 | text blink when compiled with C<--enable-blinking>. with standard |
|
|
357 | colours. Without C<--enable-blinking>, the blink attribute will be |
|
|
358 | ignored. |
|
|
359 | |
|
|
360 | On ANSI colours, bold/blink attributes are used to set high-intensity |
|
|
361 | foreground/background colors. |
|
|
362 | |
|
|
363 | color0-7 are the low-intensity colors. |
|
|
364 | |
|
|
365 | color8-15 are the corresponding high-intensity colors. |
|
|
366 | |
|
|
367 | =head3 I don't like the screen colors. How do I change them? |
|
|
368 | |
|
|
369 | You can change the screen colors at run-time using F<~/.Xdefaults> |
|
|
370 | resources (or as long-options). |
|
|
371 | |
|
|
372 | Here are values that are supposed to resemble a VGA screen, |
|
|
373 | including the murky brown that passes for low-intensity yellow: |
|
|
374 | |
|
|
375 | URxvt.color0: #000000 |
|
|
376 | URxvt.color1: #A80000 |
|
|
377 | URxvt.color2: #00A800 |
|
|
378 | URxvt.color3: #A8A800 |
|
|
379 | URxvt.color4: #0000A8 |
|
|
380 | URxvt.color5: #A800A8 |
|
|
381 | URxvt.color6: #00A8A8 |
|
|
382 | URxvt.color7: #A8A8A8 |
|
|
383 | |
|
|
384 | URxvt.color8: #000054 |
|
|
385 | URxvt.color9: #FF0054 |
|
|
386 | URxvt.color10: #00FF54 |
|
|
387 | URxvt.color11: #FFFF54 |
|
|
388 | URxvt.color12: #0000FF |
|
|
389 | URxvt.color13: #FF00FF |
|
|
390 | URxvt.color14: #00FFFF |
|
|
391 | URxvt.color15: #FFFFFF |
|
|
392 | |
|
|
393 | And here is a more complete set of non-standard colors described (not by |
|
|
394 | me) as "pretty girly". |
|
|
395 | |
|
|
396 | URxvt.cursorColor: #dc74d1 |
|
|
397 | URxvt.pointerColor: #dc74d1 |
|
|
398 | URxvt.background: #0e0e0e |
|
|
399 | URxvt.foreground: #4ad5e1 |
|
|
400 | URxvt.color0: #000000 |
|
|
401 | URxvt.color8: #8b8f93 |
|
|
402 | URxvt.color1: #dc74d1 |
|
|
403 | URxvt.color9: #dc74d1 |
|
|
404 | URxvt.color2: #0eb8c7 |
|
|
405 | URxvt.color10: #0eb8c7 |
|
|
406 | URxvt.color3: #dfe37e |
|
|
407 | URxvt.color11: #dfe37e |
|
|
408 | URxvt.color5: #9e88f0 |
|
|
409 | URxvt.color13: #9e88f0 |
|
|
410 | URxvt.color6: #73f7ff |
|
|
411 | URxvt.color14: #73f7ff |
|
|
412 | URxvt.color7: #e1dddd |
|
|
413 | URxvt.color15: #e1dddd |
|
|
414 | |
|
|
415 | =head3 Why do some characters look so much different than others? |
|
|
416 | |
|
|
417 | See next entry. |
|
|
418 | |
|
|
419 | =head3 How does rxvt-unicode choose fonts? |
|
|
420 | |
|
|
421 | Most fonts do not contain the full range of Unicode, which is |
|
|
422 | fine. Chances are that the font you (or the admin/package maintainer of |
|
|
423 | your system/os) have specified does not cover all the characters you want |
|
|
424 | to display. |
|
|
425 | |
|
|
426 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
|
|
427 | font. Often the result is fine, but sometimes the chosen font looks |
|
|
428 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
|
|
429 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
|
|
430 | intelligence to detect that a specific glyph is wrong: it has to believe |
|
|
431 | the font that the characters it claims to contain indeed look correct. |
|
|
432 | |
|
|
433 | In that case, select a font of your taste and add it to the font list, |
|
|
434 | e.g.: |
|
|
435 | |
|
|
436 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
|
|
437 | |
|
|
438 | When rxvt-unicode sees a character, it will first look at the base |
|
|
439 | font. If the base font does not contain the character, it will go to the |
|
|
440 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
441 | search and use less resources within rxvt-unicode and the X-server. |
|
|
442 | |
|
|
443 | The only limitation is that none of the fonts may be larger than the base |
|
|
444 | font, as the base font defines the terminal character cell size, which |
|
|
445 | must be the same due to the way terminals work. |
|
|
446 | |
|
|
447 | |
|
|
448 | =head2 Keyboard, Mouse & User Interaction |
|
|
449 | |
|
|
450 | =head3 The new selection selects pieces that are too big, how can I select single words? |
|
|
451 | |
|
|
452 | If you want to select e.g. alphanumeric words, you can use the following |
|
|
453 | setting: |
|
|
454 | |
|
|
455 | URxvt.selection.pattern-0: ([[:word:]]+) |
|
|
456 | |
|
|
457 | If you click more than twice, the selection will be extended |
|
|
458 | more and more. |
|
|
459 | |
|
|
460 | To get a selection that is very similar to the old code, try this pattern: |
|
|
461 | |
|
|
462 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
|
|
463 | |
|
|
464 | Please also note that the I<LeftClick Shift-LeftClik> combination also |
|
|
465 | selects words like the old code. |
|
|
466 | |
|
|
467 | =head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
|
|
468 | |
|
|
469 | You can disable the perl extension completely by setting the |
|
|
470 | B<perl-ext-common> resource to the empty string, which also keeps |
|
|
471 | rxvt-unicode from initialising perl, saving memory. |
|
|
472 | |
|
|
473 | If you only want to disable specific features, you first have to |
|
|
474 | identify which perl extension is responsible. For this, read the section |
|
|
475 | B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For |
|
|
476 | example, to disable the B<selection-popup> and B<option-popup>, specify |
|
|
477 | this B<perl-ext-common> resource: |
|
|
478 | |
|
|
479 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
|
|
480 | |
|
|
481 | This will keep the default extensions, but disable the two popup |
|
|
482 | extensions. Some extensions can also be configured, for example, |
|
|
483 | scrollback search mode is triggered by B<M-s>. You can move it to any |
|
|
484 | other combination either by setting the B<searchable-scrollback> resource: |
|
|
485 | |
|
|
486 | URxvt.searchable-scrollback: CM-s |
|
|
487 | |
|
|
488 | =head3 The cursor moves when selecting text in the current input line, how do I switch this off? |
|
|
489 | |
|
|
490 | See next entry. |
|
|
491 | |
|
|
492 | =head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
|
|
493 | |
|
|
494 | These are caused by the C<readline> perl extension. Under normal |
|
|
495 | circumstances, it will move your cursor around when you click into the |
|
|
496 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
497 | but when running a program that doesn't parse cursor movements or in some |
|
|
498 | cases during rlogin sessions, it fails to detect this properly. |
|
|
499 | |
|
|
500 | You can permamently switch this feature off by disabling the C<readline> |
|
|
501 | extension: |
|
|
502 | |
232 | URxvt.perl-ext-common: default,tabbed |
503 | URxvt.perl-ext-common: default,-readline |
233 | |
504 | |
234 | It will also work fine with tabbing functionality of many window managers |
505 | =head3 My numerical keypad acts weird and generates differing output? |
235 | or similar tabbing programs, and its embedding-features allow it to be |
|
|
236 | embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or |
|
|
237 | the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt |
|
|
238 | (murxvt) terminal as an example embedding application. |
|
|
239 | |
506 | |
240 | =head2 How do I know which rxvt-unicode version I'm using? |
507 | Some Debian GNUL/Linux users seem to have this problem, although no |
|
|
508 | specific details were reported so far. It is possible that this is caused |
|
|
509 | by the wrong C<TERM> setting, although the details of wether and how |
|
|
510 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
|
|
511 | keymap. See the answer to the previous question, and please report if that |
|
|
512 | helped. |
241 | |
513 | |
242 | The version number is displayed with the usage (-h). Also the escape |
514 | =head3 My Compose (Multi_key) key is no longer working. |
243 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
|
|
244 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
|
|
245 | daemon. |
|
|
246 | |
515 | |
247 | =head2 I am using Debian GNU/Linux and have a problem... |
516 | The most common causes for this are that either your locale is not set |
|
|
517 | correctly, or you specified a B<preeditStyle> that is not supported by |
|
|
518 | your input method. For example, if you specified B<OverTheSpot> and |
|
|
519 | your input method (e.g. the default input method handling Compose keys) |
|
|
520 | does not support this (for instance because it is not visual), then |
|
|
521 | rxvt-unicode will continue without an input method. |
248 | |
522 | |
249 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
523 | In this case either do not specify a B<preeditStyle> or specify more than |
250 | patches that considerably change the behaviour of rxvt-unicode (but |
524 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
251 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
252 | the original rxvt-unicode author please download and install the genuine |
|
|
253 | version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
|
|
254 | the problem. If you cannot, chances are that the problems are specific to |
|
|
255 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
|
|
256 | Tracking System (use C<reportbug> to report the bug). |
|
|
257 | |
525 | |
258 | For other problems that also affect the Debian package, you can and |
526 | =head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
259 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
260 | bug in the Debian version and it serves as a reminder for other users that |
|
|
261 | might encounter the same issue. |
|
|
262 | |
527 | |
263 | =head2 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
528 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
|
|
529 | international keyboards) or simply use ISO 14755 support to your |
|
|
530 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
|
|
531 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
|
|
532 | character and so on. |
264 | |
533 | |
265 | You should build one binary with the default options. F<configure> |
534 | =head3 Mouse cut/paste suddenly no longer works. |
266 | now enables most useful options, and the trend goes to making them |
|
|
267 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
|
|
268 | except higher disk and possibly memory usage. The perl interpreter should |
|
|
269 | be enabled, as important functionality (menus, selection, likely more in |
|
|
270 | the future) depends on it. |
|
|
271 | |
535 | |
272 | You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources |
536 | Make sure that mouse reporting is actually turned off since killing |
273 | system-wide (except maybe with C<defaults>). This will result in useful |
537 | some editors prematurely may leave the mouse in mouse report mode. I've |
274 | behaviour. If your distribution aims at low memory, add an empty |
538 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
275 | C<perl-ext-common> resource to the app-defaults file. This will keep the |
539 | quick check is to see if cut/paste works when the Alt or Shift keys are |
276 | perl interpreter disabled until the user enables it. |
540 | depressed. |
277 | |
541 | |
278 | If you can/want build more binaries, I recommend building a minimal |
542 | =head3 What's with the strange Backspace/Delete key behaviour? |
279 | one with C<--disable-everything> (very useful) and a maximal one with |
|
|
280 | C<--enable-everything> (less useful, it will be very big due to a lot of |
|
|
281 | encodings built-in that increase download times and are rarely used). |
|
|
282 | |
543 | |
283 | =head2 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
544 | Assuming that the physical Backspace key corresponds to the |
|
|
545 | BackSpace keysym (not likely for Linux ... see the following |
|
|
546 | question) there are two standard values that can be used for |
|
|
547 | Backspace: C<^H> and C<^?>. |
284 | |
548 | |
285 | It should be, starting with release 7.1. You are encouraged to properly |
549 | Historically, either value is correct, but rxvt-unicode adopts the debian |
286 | install urxvt with privileges necessary for your OS now. |
550 | policy of using C<^?> when unsure, because it's the one only only correct |
|
|
551 | choice :). |
287 | |
552 | |
288 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
553 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
289 | into a helper process for privileged operations (pty handling on some |
554 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
290 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
555 | started from a terminal (say, from a menu or by remote shell), then the |
291 | immediately. This is much safer than most other terminals that keep |
556 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
292 | privileges while running (but is more relevant to urxvt, as it contains |
557 | be used (which may not be the same as your stty setting). |
293 | things as perl interpreters, which might be "helpful" to attackers). |
|
|
294 | |
558 | |
295 | This forking is done as the very first within main(), which is very early |
559 | For starting a new rxvt-unicode: |
296 | and reduces possible bugs to initialisation code run before main(), or |
|
|
297 | things like the dynamic loader of your system, which should result in very |
|
|
298 | little risk. |
|
|
299 | |
560 | |
|
|
561 | # use Backspace = ^H |
|
|
562 | $ stty erase ^H |
|
|
563 | $ @@RXVT_NAME@@ |
|
|
564 | |
|
|
565 | # use Backspace = ^? |
|
|
566 | $ stty erase ^? |
|
|
567 | $ @@RXVT_NAME@@ |
|
|
568 | |
|
|
569 | Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>. |
|
|
570 | |
|
|
571 | For an existing rxvt-unicode: |
|
|
572 | |
|
|
573 | # use Backspace = ^H |
|
|
574 | $ stty erase ^H |
|
|
575 | $ echo -n "^[[36h" |
|
|
576 | |
|
|
577 | # use Backspace = ^? |
|
|
578 | $ stty erase ^? |
|
|
579 | $ echo -n "^[[36l" |
|
|
580 | |
|
|
581 | This helps satisfy some of the Backspace discrepancies that occur, but |
|
|
582 | if you use Backspace = C<^H>, make sure that the termcap/terminfo value |
|
|
583 | properly reflects that. |
|
|
584 | |
|
|
585 | The Delete key is a another casualty of the ill-defined Backspace problem. |
|
|
586 | To avoid confusion between the Backspace and Delete keys, the Delete |
|
|
587 | key has been assigned an escape sequence to match the vt100 for Execute |
|
|
588 | (C<ESC [ 3 ~>) and is in the supplied termcap/terminfo. |
|
|
589 | |
|
|
590 | Some other Backspace problems: |
|
|
591 | |
|
|
592 | some editors use termcap/terminfo, |
|
|
593 | some editors (vim I'm told) expect Backspace = ^H, |
|
|
594 | GNU Emacs (and Emacs-like editors) use ^H for help. |
|
|
595 | |
|
|
596 | Perhaps someday this will all be resolved in a consistent manner. |
|
|
597 | |
|
|
598 | =head3 I don't like the key-bindings. How do I change them? |
|
|
599 | |
|
|
600 | There are some compile-time selections available via configure. Unless |
|
|
601 | you have run "configure" with the C<--disable-resources> option you can |
|
|
602 | use the `keysym' resource to alter the keystrings associated with keysyms. |
|
|
603 | |
|
|
604 | Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt> |
|
|
605 | |
|
|
606 | URxvt.keysym.Home: \033[1~ |
|
|
607 | URxvt.keysym.End: \033[4~ |
|
|
608 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
609 | URxvt.keysym.C-slash: \033<C-/> |
|
|
610 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
611 | URxvt.keysym.C-grave: \033<C-`> |
|
|
612 | URxvt.keysym.C-comma: \033<C-,> |
|
|
613 | URxvt.keysym.C-period: \033<C-.> |
|
|
614 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
615 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
616 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
617 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
618 | URxvt.keysym.S-space: \033<S-Space> |
|
|
619 | URxvt.keysym.M-Up: \033<M-Up> |
|
|
620 | URxvt.keysym.M-Down: \033<M-Down> |
|
|
621 | URxvt.keysym.M-Left: \033<M-Left> |
|
|
622 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
623 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
624 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
625 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
|
|
626 | |
|
|
627 | See some more examples in the documentation for the B<keysym> resource. |
|
|
628 | |
|
|
629 | =head3 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 |
|
|
630 | |
|
|
631 | KP_Insert == Insert |
|
|
632 | F22 == Print |
|
|
633 | F27 == Home |
|
|
634 | F29 == Prior |
|
|
635 | F33 == End |
|
|
636 | F35 == Next |
|
|
637 | |
|
|
638 | Rather than have rxvt-unicode try to accommodate all the various possible |
|
|
639 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
|
|
640 | required for your particular machine. |
|
|
641 | |
|
|
642 | |
|
|
643 | |
|
|
644 | =head2 Terminal Configuration |
|
|
645 | |
|
|
646 | =head3 Why doesn't rxvt-unicode read my resources? |
|
|
647 | |
|
|
648 | Well, why, indeed? It does, in a way very similar to other X |
|
|
649 | applications. Most importantly, this means that if you or your OS loads |
|
|
650 | resources into the X display (the right way to do it), rxvt-unicode will |
|
|
651 | ignore any resource files in your home directory. It will only read |
|
|
652 | F<$HOME/.Xdefaults> when no resources are attached to the display. |
|
|
653 | |
|
|
654 | If you have or use an F<$HOME/.Xresources> file, chances are that |
|
|
655 | resources are loaded into your X-server. In this case, you have to |
|
|
656 | re-login after every change (or run F<xrdb -merge $HOME/.Xresources>). |
|
|
657 | |
|
|
658 | Also consider the form resources have to use: |
|
|
659 | |
|
|
660 | URxvt.resource: value |
|
|
661 | |
|
|
662 | If you want to use another form (there are lots of different ways of |
|
|
663 | specifying resources), make sure you understand wether and why it |
|
|
664 | works. If unsure, use the form above. |
|
|
665 | |
300 | =head2 When I log-in to another system it tells me about missing terminfo data? |
666 | =head3 When I log-in to another system it tells me about missing terminfo data? |
301 | |
667 | |
302 | The terminal description used by rxvt-unicode is not as widely available |
668 | The terminal description used by rxvt-unicode is not as widely available |
303 | as that for xterm, or even rxvt (for which the same problem often arises). |
669 | as that for xterm, or even rxvt (for which the same problem often arises). |
304 | |
670 | |
305 | The correct solution for this problem is to install the terminfo, this can |
671 | The correct solution for this problem is to install the terminfo, this can |
… | |
… | |
323 | URxvt.termName: rxvt |
689 | URxvt.termName: rxvt |
324 | |
690 | |
325 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
691 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
326 | the rxvt terminfo file with the rxvt-unicode one. |
692 | the rxvt terminfo file with the rxvt-unicode one. |
327 | |
693 | |
328 | =head2 C<tic> outputs some error when compiling the terminfo entry. |
694 | =head3 C<tic> outputs some error when compiling the terminfo entry. |
329 | |
695 | |
330 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
696 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
331 | C<enacs=\E[0@> and try again. |
697 | C<enacs=\E[0@> and try again. |
332 | |
698 | |
333 | =head2 C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
699 | =head3 C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
334 | |
700 | |
335 | See next entry. |
701 | See next entry. |
336 | |
702 | |
337 | =head2 I need a termcap file entry. |
703 | =head3 I need a termcap file entry. |
338 | |
704 | |
339 | One reason you might want this is that some distributions or operating |
705 | One reason you might want this is that some distributions or operating |
340 | systems still compile some programs using the long-obsoleted termcap |
706 | systems still compile some programs using the long-obsoleted termcap |
341 | library (Fedora Core's bash is one example) and rely on a termcap entry |
707 | library (Fedora Core's bash is one example) and rely on a termcap entry |
342 | for C<rxvt-unicode>. |
708 | for C<rxvt-unicode>. |
… | |
… | |
368 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
734 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
369 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
735 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
370 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
736 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
371 | :vs=\E[?25h: |
737 | :vs=\E[?25h: |
372 | |
738 | |
373 | =head2 Why does C<ls> no longer have coloured output? |
739 | =head3 Why does C<ls> no longer have coloured output? |
374 | |
740 | |
375 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
741 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
376 | decide wether a terminal has colour, but uses it's own configuration |
742 | decide wether a terminal has colour, but uses it's own configuration |
377 | file. Needless to say, C<rxvt-unicode> is not in it's default file (among |
743 | file. Needless to say, C<rxvt-unicode> is not in it's default file (among |
378 | with most other terminals supporting colour). Either add: |
744 | with most other terminals supporting colour). Either add: |
… | |
… | |
383 | |
749 | |
384 | alias ls='ls --color=auto' |
750 | alias ls='ls --color=auto' |
385 | |
751 | |
386 | to your C<.profile> or C<.bashrc>. |
752 | to your C<.profile> or C<.bashrc>. |
387 | |
753 | |
388 | =head2 Why doesn't vim/emacs etc. use the 88 colour mode? |
754 | =head3 Why doesn't vim/emacs etc. use the 88 colour mode? |
389 | |
755 | |
390 | See next entry. |
756 | See next entry. |
391 | |
757 | |
392 | =head2 Why doesn't vim/emacs etc. make use of italic? |
758 | =head3 Why doesn't vim/emacs etc. make use of italic? |
393 | |
759 | |
394 | See next entry. |
760 | See next entry. |
395 | |
761 | |
396 | =head2 Why are the secondary screen-related options not working properly? |
762 | =head3 Why are the secondary screen-related options not working properly? |
397 | |
763 | |
398 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
764 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
399 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
765 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
400 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
766 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
401 | features. Unfortunately, some of these (most notably, again, Debian |
767 | features. Unfortunately, some of these (most notably, again, Debian |
402 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
768 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
403 | file, so you will need to install it on your own (See the question B<When |
769 | file, so you will need to install it on your own (See the question B<When |
404 | I log-in to another system it tells me about missing terminfo data?> on |
770 | I log-in to another system it tells me about missing terminfo data?> on |
405 | how to do this). |
771 | how to do this). |
406 | |
772 | |
407 | =head2 My numerical keypad acts weird and generates differing output? |
|
|
408 | |
773 | |
409 | Some Debian GNUL/Linux users seem to have this problem, although no |
774 | =head2 Encoding / Locale / Input Method Issues |
410 | specific details were reported so far. It is possible that this is caused |
|
|
411 | by the wrong C<TERM> setting, although the details of wether and how |
|
|
412 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
|
|
413 | keymap. See the answer to the previous question, and please report if that |
|
|
414 | helped. |
|
|
415 | |
775 | |
416 | =head2 Rxvt-unicode does not seem to understand the selected encoding? |
776 | =head3 Rxvt-unicode does not seem to understand the selected encoding? |
417 | |
777 | |
418 | See next entry. |
778 | See next entry. |
419 | |
779 | |
420 | =head2 Unicode does not seem to work? |
780 | =head3 Unicode does not seem to work? |
421 | |
781 | |
422 | If you encounter strange problems like typing an accented character but |
782 | If you encounter strange problems like typing an accented character but |
423 | getting two unrelated other characters or similar, or if program output is |
783 | getting two unrelated other characters or similar, or if program output is |
424 | subtly garbled, then you should check your locale settings. |
784 | subtly garbled, then you should check your locale settings. |
425 | |
785 | |
… | |
… | |
445 | |
805 | |
446 | If nothing works and you are sure that everything is set correctly then |
806 | If nothing works and you are sure that everything is set correctly then |
447 | you will need to remember a little known fact: Some programs just don't |
807 | you will need to remember a little known fact: Some programs just don't |
448 | support locales :( |
808 | support locales :( |
449 | |
809 | |
450 | =head2 Why do some characters look so much different than others? |
810 | =head3 How does rxvt-unicode determine the encoding to use? |
451 | |
811 | |
452 | See next entry. |
812 | See next entry. |
453 | |
813 | |
454 | =head2 How does rxvt-unicode choose fonts? |
814 | =head3 Is there an option to switch encodings? |
455 | |
815 | |
456 | Most fonts do not contain the full range of Unicode, which is |
816 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
457 | fine. Chances are that the font you (or the admin/package maintainer of |
817 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
458 | your system/os) have specified does not cover all the characters you want |
818 | UTF-8 or any other encodings with respect to terminal I/O. |
459 | to display. |
|
|
460 | |
819 | |
461 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
820 | The reasons is that there exists a perfectly fine mechanism for selecting |
462 | font. Often the result is fine, but sometimes the chosen font looks |
821 | the encoding, doing I/O and (most important) communicating this to all |
463 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
822 | applications so everybody agrees on character properties such as width |
464 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
823 | and code number. This mechanism is the I<locale>. Applications not using |
465 | intelligence to detect that a specific glyph is wrong: it has to believe |
824 | that info will have problems (for example, C<xterm> gets the width of |
466 | the font that the characters it claims to contain indeed look correct. |
825 | characters wrong as it uses it's own, locale-independent table under all |
467 | |
|
|
468 | In that case, select a font of your taste and add it to the font list, |
|
|
469 | e.g.: |
|
|
470 | |
|
|
471 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
|
|
472 | |
|
|
473 | When rxvt-unicode sees a character, it will first look at the base |
|
|
474 | font. If the base font does not contain the character, it will go to the |
|
|
475 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
476 | search and use less resources within rxvt-unicode and the X-server. |
|
|
477 | |
|
|
478 | The only limitation is that none of the fonts may be larger than the base |
|
|
479 | font, as the base font defines the terminal character cell size, which |
|
|
480 | must be the same due to the way terminals work. |
|
|
481 | |
|
|
482 | =head2 Why do some chinese characters look so different than others? |
|
|
483 | |
|
|
484 | This is because there is a difference between script and language -- |
|
|
485 | rxvt-unicode does not know which language the text that is output is, |
|
|
486 | as it only knows the unicode character codes. If rxvt-unicode first |
|
|
487 | sees a japanese/chinese character, it might choose a japanese font for |
|
|
488 | display. Subsequent japanese characters will use that font. Now, many |
|
|
489 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
490 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
491 | -- unfortunately at this point, it will still use the japanese font for |
|
|
492 | chinese characters that are also in the japanese font. |
|
|
493 | |
|
|
494 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
495 | list (see the previous question). The key is to view the font list as |
|
|
496 | a preference list: If you expect more japanese, list a japanese font |
|
|
497 | first. If you expect more chinese, put a chinese font first. |
|
|
498 | |
|
|
499 | In the future it might be possible to switch language preferences at |
|
|
500 | runtime (the internal data structure has no problem with using different |
|
|
501 | fonts for the same character at the same time, but no interface for this |
|
|
502 | has been designed yet). |
|
|
503 | |
|
|
504 | Until then, you might get away with switching fonts at runtime (see L<Can |
|
|
505 | I switch the fonts at runtime?> later in this document). |
|
|
506 | |
|
|
507 | =head2 Why does rxvt-unicode sometimes leave pixel droppings? |
|
|
508 | |
|
|
509 | Most fonts were not designed for terminal use, which means that character |
|
|
510 | size varies a lot. A font that is otherwise fine for terminal use might |
|
|
511 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
|
|
512 | these characters. For characters that are just "a bit" too wide a special |
|
|
513 | "careful" rendering mode is used that redraws adjacent characters. |
|
|
514 | |
|
|
515 | All of this requires that fonts do not lie about character sizes, |
|
|
516 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
|
|
517 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
|
|
518 | ask for the character bounding box, which unfortunately is wrong in these |
|
|
519 | cases). |
826 | locales). |
520 | |
827 | |
521 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
828 | Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
522 | or the respective font. If you encounter this problem you might try using |
829 | programs doing the same (that is, most) will automatically agree in the |
523 | the C<-lsp> option to give the font more height. If that doesn't work, you |
830 | interpretation of characters. |
524 | might be forced to use a different font. |
|
|
525 | |
831 | |
526 | All of this is not a problem when using X11 core fonts, as their bounding |
832 | Unfortunately, there is no system-independent way to select locales, nor |
527 | box data is correct. |
833 | is there a standard on how locale specifiers will look like. |
528 | |
834 | |
|
|
835 | On most systems, the content of the C<LC_CTYPE> environment variable |
|
|
836 | contains an arbitrary string which corresponds to an already-installed |
|
|
837 | locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>, |
|
|
838 | C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
|
|
839 | (i.e. C<de> or C<german>) are also common. |
|
|
840 | |
|
|
841 | Rxvt-unicode ignores all other locale categories, and except for |
|
|
842 | the encoding, ignores country or language-specific settings, |
|
|
843 | i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to |
|
|
844 | rxvt-unicode. |
|
|
845 | |
|
|
846 | If you want to use a specific encoding you have to make sure you start |
|
|
847 | rxvt-unicode with the correct C<LC_CTYPE> category. |
|
|
848 | |
|
|
849 | =head3 Can I switch locales at runtime? |
|
|
850 | |
|
|
851 | Yes, using an escape sequence. Try something like this, which sets |
|
|
852 | rxvt-unicode's idea of C<LC_CTYPE>. |
|
|
853 | |
|
|
854 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
855 | |
|
|
856 | See also the previous answer. |
|
|
857 | |
|
|
858 | Sometimes this capability is rather handy when you want to work in |
|
|
859 | one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it |
|
|
860 | (e.g. UTF-8). For example, I use this script to start C<xjdic>, which |
|
|
861 | first switches to a locale supported by xjdic and back later: |
|
|
862 | |
|
|
863 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
864 | xjdic -js |
|
|
865 | printf '\e]701;%s\007' de_DE.UTF-8 |
|
|
866 | |
|
|
867 | You can also use xterm's C<luit> program, which usually works fine, except |
|
|
868 | for some locales where character width differs between program- and |
|
|
869 | rxvt-unicode-locales. |
|
|
870 | |
|
|
871 | =head3 My input method wants <some encoding> but I want UTF-8, what can I do? |
|
|
872 | |
|
|
873 | You can specify separate locales for the input method and the rest of the |
|
|
874 | terminal, using the resource C<imlocale>: |
|
|
875 | |
|
|
876 | URxvt.imlocale: ja_JP.EUC-JP |
|
|
877 | |
|
|
878 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
|
|
879 | use your input method. Please note, however, that you will not be able to |
|
|
880 | input characters outside C<EUC-JP> in a normal way then, as your input |
|
|
881 | method limits you. |
|
|
882 | |
|
|
883 | =head3 Rxvt-unicode crashes when the X Input Method changes or exits. |
|
|
884 | |
|
|
885 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
|
|
886 | design. Applications can avoid some crashes at the expense of memory |
|
|
887 | leaks, and Input Methods can avoid some crashes by careful ordering at |
|
|
888 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
|
|
889 | while B<SCIM> (or similar input methods) fails. In the end, however, |
|
|
890 | crashes cannot be completely avoided even if both sides cooperate. |
|
|
891 | |
|
|
892 | So the only workaround is not to kill your Input Method Servers. |
|
|
893 | |
|
|
894 | |
|
|
895 | =head2 Operating Systems / Package Maintaining |
|
|
896 | |
|
|
897 | =head3 I am using Debian GNU/Linux and have a problem... |
|
|
898 | |
|
|
899 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
900 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
901 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
902 | the original rxvt-unicode author please download and install the genuine |
|
|
903 | version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
|
|
904 | the problem. If you cannot, chances are that the problems are specific to |
|
|
905 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
|
|
906 | Tracking System (use C<reportbug> to report the bug). |
|
|
907 | |
|
|
908 | For other problems that also affect the Debian package, you can and |
|
|
909 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
910 | bug in the Debian version and it serves as a reminder for other users that |
|
|
911 | might encounter the same issue. |
|
|
912 | |
|
|
913 | =head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
|
|
914 | |
|
|
915 | You should build one binary with the default options. F<configure> |
|
|
916 | now enables most useful options, and the trend goes to making them |
|
|
917 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
|
|
918 | except higher disk and possibly memory usage. The perl interpreter should |
|
|
919 | be enabled, as important functionality (menus, selection, likely more in |
|
|
920 | the future) depends on it. |
|
|
921 | |
|
|
922 | You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources |
|
|
923 | system-wide (except maybe with C<defaults>). This will result in useful |
|
|
924 | behaviour. If your distribution aims at low memory, add an empty |
|
|
925 | C<perl-ext-common> resource to the app-defaults file. This will keep the |
|
|
926 | perl interpreter disabled until the user enables it. |
|
|
927 | |
|
|
928 | If you can/want build more binaries, I recommend building a minimal |
|
|
929 | one with C<--disable-everything> (very useful) and a maximal one with |
|
|
930 | C<--enable-everything> (less useful, it will be very big due to a lot of |
|
|
931 | encodings built-in that increase download times and are rarely used). |
|
|
932 | |
|
|
933 | =head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
|
|
934 | |
|
|
935 | It should be, starting with release 7.1. You are encouraged to properly |
|
|
936 | install urxvt with privileges necessary for your OS now. |
|
|
937 | |
|
|
938 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
|
|
939 | into a helper process for privileged operations (pty handling on some |
|
|
940 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
|
|
941 | immediately. This is much safer than most other terminals that keep |
|
|
942 | privileges while running (but is more relevant to urxvt, as it contains |
|
|
943 | things as perl interpreters, which might be "helpful" to attackers). |
|
|
944 | |
|
|
945 | This forking is done as the very first within main(), which is very early |
|
|
946 | and reduces possible bugs to initialisation code run before main(), or |
|
|
947 | things like the dynamic loader of your system, which should result in very |
|
|
948 | little risk. |
|
|
949 | |
529 | =head2 On Solaris 9, many line-drawing characters are too wide. |
950 | =head3 On Solaris 9, many line-drawing characters are too wide. |
530 | |
951 | |
531 | Seems to be a known bug, read |
952 | Seems to be a known bug, read |
532 | L<http://nixdoc.net/files/forum/about34198.html>. Some people use the |
953 | L<http://nixdoc.net/files/forum/about34198.html>. Some people use the |
533 | following ugly workaround to get non-double-wide-characters working: |
954 | following ugly workaround to get non-double-wide-characters working: |
534 | |
955 | |
535 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
956 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
536 | |
957 | |
537 | =head2 My Compose (Multi_key) key is no longer working. |
|
|
538 | |
|
|
539 | The most common causes for this are that either your locale is not set |
|
|
540 | correctly, or you specified a B<preeditStyle> that is not supported by |
|
|
541 | your input method. For example, if you specified B<OverTheSpot> and |
|
|
542 | your input method (e.g. the default input method handling Compose keys) |
|
|
543 | does not support this (for instance because it is not visual), then |
|
|
544 | rxvt-unicode will continue without an input method. |
|
|
545 | |
|
|
546 | In this case either do not specify a B<preeditStyle> or specify more than |
|
|
547 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
|
|
548 | |
|
|
549 | =head2 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
|
|
550 | |
|
|
551 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
|
|
552 | international keyboards) or simply use ISO 14755 support to your |
|
|
553 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
|
|
554 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
|
|
555 | character and so on. |
|
|
556 | |
|
|
557 | =head2 How can I keep rxvt-unicode from using reverse video so much? |
|
|
558 | |
|
|
559 | First of all, make sure you are running with the right terminal settings |
|
|
560 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
|
|
561 | make sure you have specified colours for italic and bold, as otherwise |
|
|
562 | rxvt-unicode might use reverse video to simulate the effect: |
|
|
563 | |
|
|
564 | URxvt.colorBD: white |
|
|
565 | URxvt.colorIT: green |
|
|
566 | |
|
|
567 | =head2 Some programs assume totally weird colours (red instead of blue), how can I fix that? |
|
|
568 | |
|
|
569 | For some unexplainable reason, some rare programs assume a very weird |
|
|
570 | colour palette when confronted with a terminal with more than the standard |
|
|
571 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
|
|
572 | these programs not to assume non-ISO colours without very good reasons. |
|
|
573 | |
|
|
574 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
|
|
575 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
|
|
576 | fix colours but keep you from using other rxvt-unicode features. |
|
|
577 | |
|
|
578 | =head2 I am on FreeBSD and rxvt-unicode does not seem to work at all. |
958 | =head3 I am on FreeBSD and rxvt-unicode does not seem to work at all. |
579 | |
959 | |
580 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
960 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
581 | in your compile environment, or an implementation that implements it, |
961 | in your compile environment, or an implementation that implements it, |
582 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
962 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
583 | B<wchar_t> is represented as unicode. |
963 | B<wchar_t> is represented as unicode. |
… | |
… | |
605 | |
985 | |
606 | The rxvt-unicode author insists that the right way to fix this is in the |
986 | The rxvt-unicode author insists that the right way to fix this is in the |
607 | system libraries once and for all, instead of forcing every app to carry |
987 | system libraries once and for all, instead of forcing every app to carry |
608 | complete replacements for them :) |
988 | complete replacements for them :) |
609 | |
989 | |
610 | =head2 I use Solaris 9 and it doesn't compile/work/etc. |
990 | =head3 I use Solaris 9 and it doesn't compile/work/etc. |
611 | |
991 | |
612 | Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst |
992 | Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst |
613 | problems with C<wcwidth> and a compile problem. |
993 | problems with C<wcwidth> and a compile problem. |
614 | |
994 | |
615 | =head2 How can I use rxvt-unicode under cygwin? |
995 | =head3 How can I use rxvt-unicode under cygwin? |
616 | |
996 | |
617 | rxvt-unicode should compile and run out of the box on cygwin, using |
997 | rxvt-unicode should compile and run out of the box on cygwin, using |
618 | the X11 libraries that come with cygwin. libW11 emulation is no |
998 | the X11 libraries that come with cygwin. libW11 emulation is no |
619 | longer supported (and makes no sense, either, as it only supported a |
999 | longer supported (and makes no sense, either, as it only supported a |
620 | single font). I recommend starting the X-server in C<-multiwindow> or |
1000 | single font). I recommend starting the X-server in C<-multiwindow> or |
… | |
… | |
622 | old libW11 emulation. |
1002 | old libW11 emulation. |
623 | |
1003 | |
624 | At the time of this writing, cygwin didn't seem to support any multi-byte |
1004 | At the time of this writing, cygwin didn't seem to support any multi-byte |
625 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
1005 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
626 | to 8-bit encodings. |
1006 | to 8-bit encodings. |
627 | |
|
|
628 | =head2 How does rxvt-unicode determine the encoding to use? |
|
|
629 | |
|
|
630 | See next entry. |
|
|
631 | |
|
|
632 | =head2 Is there an option to switch encodings? |
|
|
633 | |
|
|
634 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
|
|
635 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
|
|
636 | UTF-8 or any other encodings with respect to terminal I/O. |
|
|
637 | |
|
|
638 | The reasons is that there exists a perfectly fine mechanism for selecting |
|
|
639 | the encoding, doing I/O and (most important) communicating this to all |
|
|
640 | applications so everybody agrees on character properties such as width |
|
|
641 | and code number. This mechanism is the I<locale>. Applications not using |
|
|
642 | that info will have problems (for example, C<xterm> gets the width of |
|
|
643 | characters wrong as it uses it's own, locale-independent table under all |
|
|
644 | locales). |
|
|
645 | |
|
|
646 | Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
|
|
647 | programs doing the same (that is, most) will automatically agree in the |
|
|
648 | interpretation of characters. |
|
|
649 | |
|
|
650 | Unfortunately, there is no system-independent way to select locales, nor |
|
|
651 | is there a standard on how locale specifiers will look like. |
|
|
652 | |
|
|
653 | On most systems, the content of the C<LC_CTYPE> environment variable |
|
|
654 | contains an arbitrary string which corresponds to an already-installed |
|
|
655 | locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>, |
|
|
656 | C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
|
|
657 | (i.e. C<de> or C<german>) are also common. |
|
|
658 | |
|
|
659 | Rxvt-unicode ignores all other locale categories, and except for |
|
|
660 | the encoding, ignores country or language-specific settings, |
|
|
661 | i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to |
|
|
662 | rxvt-unicode. |
|
|
663 | |
|
|
664 | If you want to use a specific encoding you have to make sure you start |
|
|
665 | rxvt-unicode with the correct C<LC_CTYPE> category. |
|
|
666 | |
|
|
667 | =head2 Can I switch locales at runtime? |
|
|
668 | |
|
|
669 | Yes, using an escape sequence. Try something like this, which sets |
|
|
670 | rxvt-unicode's idea of C<LC_CTYPE>. |
|
|
671 | |
|
|
672 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
673 | |
|
|
674 | See also the previous answer. |
|
|
675 | |
|
|
676 | Sometimes this capability is rather handy when you want to work in |
|
|
677 | one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it |
|
|
678 | (e.g. UTF-8). For example, I use this script to start C<xjdic>, which |
|
|
679 | first switches to a locale supported by xjdic and back later: |
|
|
680 | |
|
|
681 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
682 | xjdic -js |
|
|
683 | printf '\e]701;%s\007' de_DE.UTF-8 |
|
|
684 | |
|
|
685 | You can also use xterm's C<luit> program, which usually works fine, except |
|
|
686 | for some locales where character width differs between program- and |
|
|
687 | rxvt-unicode-locales. |
|
|
688 | |
|
|
689 | =head2 Can I switch the fonts at runtime? |
|
|
690 | |
|
|
691 | Yes, using an escape sequence. Try something like this, which has the same |
|
|
692 | effect as using the C<-fn> switch, and takes effect immediately: |
|
|
693 | |
|
|
694 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
|
|
695 | |
|
|
696 | This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
697 | japanese font), but you have to switch to chinese temporarily, where |
|
|
698 | japanese fonts would only be in your way. |
|
|
699 | |
|
|
700 | You can think of this as a kind of manual ISO-2022 switching. |
|
|
701 | |
|
|
702 | =head2 Why do italic characters look as if clipped? |
|
|
703 | |
|
|
704 | Many fonts have difficulties with italic characters and hinting. For |
|
|
705 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
|
|
706 | Mono> completely fails in it's italic face. A workaround might be to |
|
|
707 | enable freetype autohinting, i.e. like this: |
|
|
708 | |
|
|
709 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
710 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
711 | |
|
|
712 | =head2 My input method wants <some encoding> but I want UTF-8, what can I do? |
|
|
713 | |
|
|
714 | You can specify separate locales for the input method and the rest of the |
|
|
715 | terminal, using the resource C<imlocale>: |
|
|
716 | |
|
|
717 | URxvt.imlocale: ja_JP.EUC-JP |
|
|
718 | |
|
|
719 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
|
|
720 | use your input method. Please note, however, that you will not be able to |
|
|
721 | input characters outside C<EUC-JP> in a normal way then, as your input |
|
|
722 | method limits you. |
|
|
723 | |
|
|
724 | =head2 Rxvt-unicode crashes when the X Input Method changes or exits. |
|
|
725 | |
|
|
726 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
|
|
727 | design. Applications can avoid some crashes at the expense of memory |
|
|
728 | leaks, and Input Methods can avoid some crashes by careful ordering at |
|
|
729 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
|
|
730 | while B<SCIM> (or similar input methods) fails. In the end, however, |
|
|
731 | crashes cannot be completely avoided even if both sides cooperate. |
|
|
732 | |
|
|
733 | So the only workaround is not to kill your Input Method Servers. |
|
|
734 | |
|
|
735 | =head2 Rxvt-unicode uses gobs of memory, how can I reduce that? |
|
|
736 | |
|
|
737 | Rxvt-unicode tries to obey the rule of not charging you for something you |
|
|
738 | don't use. One thing you should try is to configure out all settings that |
|
|
739 | you don't need, for example, Xft support is a resource hog by design, |
|
|
740 | when used. Compiling it out ensures that no Xft font will be loaded |
|
|
741 | accidentally when rxvt-unicode tries to find a font for your characters. |
|
|
742 | |
|
|
743 | Also, many people (me included) like large windows and even larger |
|
|
744 | scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use |
|
|
745 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
|
|
746 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
|
|
747 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
|
|
748 | rxvt-unicode then uses 8 bytes per screen cell. |
|
|
749 | |
|
|
750 | =head2 Can I speed up Xft rendering somehow? |
|
|
751 | |
|
|
752 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
753 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
754 | antialiasing (by appending C<:antialias=false>), which saves lots of |
|
|
755 | memory and also speeds up rendering considerably. |
|
|
756 | |
|
|
757 | =head2 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
|
|
758 | |
|
|
759 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
760 | fall back to it's default font search list it will prefer X11 core |
|
|
761 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
762 | antialiasing disabled for most of them, because the author thinks they |
|
|
763 | look best that way. |
|
|
764 | |
|
|
765 | If you want antialiasing, you have to specify the fonts manually. |
|
|
766 | |
|
|
767 | =head2 Mouse cut/paste suddenly no longer works. |
|
|
768 | |
|
|
769 | Make sure that mouse reporting is actually turned off since killing |
|
|
770 | some editors prematurely may leave the mouse in mouse report mode. I've |
|
|
771 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
|
|
772 | quick check is to see if cut/paste works when the Alt or Shift keys are |
|
|
773 | depressed. |
|
|
774 | |
|
|
775 | =head2 What's with this bold/blink stuff? |
|
|
776 | |
|
|
777 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
|
|
778 | standard foreground colour. |
|
|
779 | |
|
|
780 | For the standard background colour, blinking will actually make the |
|
|
781 | text blink when compiled with C<--enable-blinking>. with standard |
|
|
782 | colours. Without C<--enable-blinking>, the blink attribute will be |
|
|
783 | ignored. |
|
|
784 | |
|
|
785 | On ANSI colours, bold/blink attributes are used to set high-intensity |
|
|
786 | foreground/background colors. |
|
|
787 | |
|
|
788 | color0-7 are the low-intensity colors. |
|
|
789 | |
|
|
790 | color8-15 are the corresponding high-intensity colors. |
|
|
791 | |
|
|
792 | =head2 I don't like the screen colors. How do I change them? |
|
|
793 | |
|
|
794 | You can change the screen colors at run-time using F<~/.Xdefaults> |
|
|
795 | resources (or as long-options). |
|
|
796 | |
|
|
797 | Here are values that are supposed to resemble a VGA screen, |
|
|
798 | including the murky brown that passes for low-intensity yellow: |
|
|
799 | |
|
|
800 | URxvt.color0: #000000 |
|
|
801 | URxvt.color1: #A80000 |
|
|
802 | URxvt.color2: #00A800 |
|
|
803 | URxvt.color3: #A8A800 |
|
|
804 | URxvt.color4: #0000A8 |
|
|
805 | URxvt.color5: #A800A8 |
|
|
806 | URxvt.color6: #00A8A8 |
|
|
807 | URxvt.color7: #A8A8A8 |
|
|
808 | |
|
|
809 | URxvt.color8: #000054 |
|
|
810 | URxvt.color9: #FF0054 |
|
|
811 | URxvt.color10: #00FF54 |
|
|
812 | URxvt.color11: #FFFF54 |
|
|
813 | URxvt.color12: #0000FF |
|
|
814 | URxvt.color13: #FF00FF |
|
|
815 | URxvt.color14: #00FFFF |
|
|
816 | URxvt.color15: #FFFFFF |
|
|
817 | |
|
|
818 | And here is a more complete set of non-standard colors described (not by |
|
|
819 | me) as "pretty girly". |
|
|
820 | |
|
|
821 | URxvt.cursorColor: #dc74d1 |
|
|
822 | URxvt.pointerColor: #dc74d1 |
|
|
823 | URxvt.background: #0e0e0e |
|
|
824 | URxvt.foreground: #4ad5e1 |
|
|
825 | URxvt.color0: #000000 |
|
|
826 | URxvt.color8: #8b8f93 |
|
|
827 | URxvt.color1: #dc74d1 |
|
|
828 | URxvt.color9: #dc74d1 |
|
|
829 | URxvt.color2: #0eb8c7 |
|
|
830 | URxvt.color10: #0eb8c7 |
|
|
831 | URxvt.color3: #dfe37e |
|
|
832 | URxvt.color11: #dfe37e |
|
|
833 | URxvt.color5: #9e88f0 |
|
|
834 | URxvt.color13: #9e88f0 |
|
|
835 | URxvt.color6: #73f7ff |
|
|
836 | URxvt.color14: #73f7ff |
|
|
837 | URxvt.color7: #e1dddd |
|
|
838 | URxvt.color15: #e1dddd |
|
|
839 | |
|
|
840 | =head2 How can I start @@RXVT_NAME@@d in a race-free way? |
|
|
841 | |
|
|
842 | Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the |
|
|
843 | display, create the listening socket and then fork. |
|
|
844 | |
|
|
845 | =head2 What's with the strange Backspace/Delete key behaviour? |
|
|
846 | |
|
|
847 | Assuming that the physical Backspace key corresponds to the |
|
|
848 | BackSpace keysym (not likely for Linux ... see the following |
|
|
849 | question) there are two standard values that can be used for |
|
|
850 | Backspace: C<^H> and C<^?>. |
|
|
851 | |
|
|
852 | Historically, either value is correct, but rxvt-unicode adopts the debian |
|
|
853 | policy of using C<^?> when unsure, because it's the one only only correct |
|
|
854 | choice :). |
|
|
855 | |
|
|
856 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
|
|
857 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
|
|
858 | started from a terminal (say, from a menu or by remote shell), then the |
|
|
859 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
|
|
860 | be used (which may not be the same as your stty setting). |
|
|
861 | |
|
|
862 | For starting a new rxvt-unicode: |
|
|
863 | |
|
|
864 | # use Backspace = ^H |
|
|
865 | $ stty erase ^H |
|
|
866 | $ @@RXVT_NAME@@ |
|
|
867 | |
|
|
868 | # use Backspace = ^? |
|
|
869 | $ stty erase ^? |
|
|
870 | $ @@RXVT_NAME@@ |
|
|
871 | |
|
|
872 | Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>. |
|
|
873 | |
|
|
874 | For an existing rxvt-unicode: |
|
|
875 | |
|
|
876 | # use Backspace = ^H |
|
|
877 | $ stty erase ^H |
|
|
878 | $ echo -n "^[[36h" |
|
|
879 | |
|
|
880 | # use Backspace = ^? |
|
|
881 | $ stty erase ^? |
|
|
882 | $ echo -n "^[[36l" |
|
|
883 | |
|
|
884 | This helps satisfy some of the Backspace discrepancies that occur, but |
|
|
885 | if you use Backspace = C<^H>, make sure that the termcap/terminfo value |
|
|
886 | properly reflects that. |
|
|
887 | |
|
|
888 | The Delete key is a another casualty of the ill-defined Backspace problem. |
|
|
889 | To avoid confusion between the Backspace and Delete keys, the Delete |
|
|
890 | key has been assigned an escape sequence to match the vt100 for Execute |
|
|
891 | (C<ESC [ 3 ~>) and is in the supplied termcap/terminfo. |
|
|
892 | |
|
|
893 | Some other Backspace problems: |
|
|
894 | |
|
|
895 | some editors use termcap/terminfo, |
|
|
896 | some editors (vim I'm told) expect Backspace = ^H, |
|
|
897 | GNU Emacs (and Emacs-like editors) use ^H for help. |
|
|
898 | |
|
|
899 | Perhaps someday this will all be resolved in a consistent manner. |
|
|
900 | |
|
|
901 | =head2 I don't like the key-bindings. How do I change them? |
|
|
902 | |
|
|
903 | There are some compile-time selections available via configure. Unless |
|
|
904 | you have run "configure" with the C<--disable-resources> option you can |
|
|
905 | use the `keysym' resource to alter the keystrings associated with keysyms. |
|
|
906 | |
|
|
907 | Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt> |
|
|
908 | |
|
|
909 | URxvt.keysym.Home: \033[1~ |
|
|
910 | URxvt.keysym.End: \033[4~ |
|
|
911 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
912 | URxvt.keysym.C-slash: \033<C-/> |
|
|
913 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
914 | URxvt.keysym.C-grave: \033<C-`> |
|
|
915 | URxvt.keysym.C-comma: \033<C-,> |
|
|
916 | URxvt.keysym.C-period: \033<C-.> |
|
|
917 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
918 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
919 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
920 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
921 | URxvt.keysym.S-space: \033<S-Space> |
|
|
922 | URxvt.keysym.M-Up: \033<M-Up> |
|
|
923 | URxvt.keysym.M-Down: \033<M-Down> |
|
|
924 | URxvt.keysym.M-Left: \033<M-Left> |
|
|
925 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
926 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
927 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
928 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
|
|
929 | |
|
|
930 | See some more examples in the documentation for the B<keysym> resource. |
|
|
931 | |
|
|
932 | =head2 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. |
|
|
933 | |
|
|
934 | KP_Insert == Insert |
|
|
935 | F22 == Print |
|
|
936 | F27 == Home |
|
|
937 | F29 == Prior |
|
|
938 | F33 == End |
|
|
939 | F35 == Next |
|
|
940 | |
|
|
941 | Rather than have rxvt-unicode try to accommodate all the various possible |
|
|
942 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
|
|
943 | required for your particular machine. |
|
|
944 | |
|
|
945 | =head2 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
|
|
946 | |
|
|
947 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
|
|
948 | check and see if that is set. Note that several programs, JED, slrn, |
|
|
949 | Midnight Commander automatically check this variable to decide whether or |
|
|
950 | not to use color. |
|
|
951 | |
|
|
952 | =head2 How do I set the correct, full IP address for the DISPLAY variable? |
|
|
953 | |
|
|
954 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
|
|
955 | insecure mode then it is possible to use the following shell script |
|
|
956 | snippets to correctly set the display. If your version of rxvt-unicode |
|
|
957 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
|
|
958 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
|
|
959 | regular xterm. |
|
|
960 | |
|
|
961 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
|
|
962 | snippets: |
|
|
963 | |
|
|
964 | # Bourne/Korn/POSIX family of shells: |
|
|
965 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
|
|
966 | if [ ${TERM:-foo} = xterm ]; then |
|
|
967 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
|
|
968 | echo -n '^[Z' |
|
|
969 | read term_id |
|
|
970 | stty icanon echo |
|
|
971 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
|
|
972 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
|
|
973 | read DISPLAY # set it in our local shell |
|
|
974 | fi |
|
|
975 | fi |
|
|
976 | |
|
|
977 | =head2 How do I compile the manual pages for myself? |
|
|
978 | |
|
|
979 | You need to have a recent version of perl installed as F</usr/bin/perl>, |
|
|
980 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
|
|
981 | the doc subdirectory and enter C<make alldoc>. |
|
|
982 | |
|
|
983 | =head2 My question isn't answered here, can I ask a human? |
|
|
984 | |
|
|
985 | Before sending me mail, you could go to IRC: C<irc.freenode.net>, |
|
|
986 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
|
|
987 | interested in learning about new and exciting problems (but not FAQs :). |
|
|
988 | |
1007 | |
989 | =head1 RXVT TECHNICAL REFERENCE |
1008 | =head1 RXVT TECHNICAL REFERENCE |
990 | |
1009 | |
991 | =head1 DESCRIPTION |
1010 | =head1 DESCRIPTION |
992 | |
1011 | |