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