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