… | |
… | |
127 | .\} |
127 | .\} |
128 | .rm #[ #] #H #V #F C |
128 | .rm #[ #] #H #V #F C |
129 | .\" ======================================================================== |
129 | .\" ======================================================================== |
130 | .\" |
130 | .\" |
131 | .IX Title "rxvt 7" |
131 | .IX Title "rxvt 7" |
132 | .TH rxvt 7 "2006-01-11" "7.0" "RXVT-UNICODE" |
132 | .TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE" |
133 | .SH "NAME" |
133 | .SH "NAME" |
134 | RXVT REFERENCE \- FAQ, command sequences and other background information |
134 | RXVT REFERENCE \- FAQ, command sequences and other background information |
135 | .SH "SYNOPSIS" |
135 | .SH "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
137 | .Vb 2 |
137 | .Vb 2 |
… | |
… | |
151 | .SH "DESCRIPTION" |
151 | .SH "DESCRIPTION" |
152 | .IX Header "DESCRIPTION" |
152 | .IX Header "DESCRIPTION" |
153 | This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting |
153 | This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting |
154 | all escape sequences, and other background information. |
154 | all escape sequences, and other background information. |
155 | .PP |
155 | .PP |
156 | The newest version of this document is |
156 | The newest version of this document is also available on the World Wide Web at |
157 | also available on the World Wide Web at |
|
|
158 | <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>. |
159 | .SH "FREQUENTLY ASKED QUESTIONS" |
158 | .SH "FREQUENTLY ASKED QUESTIONS" |
160 | .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?" |
|
|
161 | .IX Subsection "The new selection selects pieces that are too big, how can I select single words?" |
|
|
162 | If you want to select e.g. alphanumeric words, you can use the following |
|
|
163 | setting: |
|
|
164 | .PP |
|
|
165 | .Vb 1 |
|
|
166 | \& URxvt.selection.pattern-0: ([[:word:]]+) |
|
|
167 | .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 |
|
|
174 | .Vb 1 |
|
|
175 | \& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+) |
|
|
176 | .Ve |
|
|
177 | .PP |
|
|
178 | Please also note that the \fILeftClick Shift-LeftClik\fR combination also |
|
|
179 | selects words like the old code. |
|
|
180 | .Sh "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" |
|
|
181 | .IX Subsection "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" |
|
|
182 | You can disable the perl extension completely by setting the |
|
|
183 | \&\fBperl-ext-common\fR resource to the empty string, which also keeps |
|
|
184 | rxvt-unicode from initialising perl, saving memory. |
|
|
185 | .PP |
|
|
186 | If you only want to disable specific features, you first have to |
|
|
187 | identify which perl extension is responsible. For this, read the section |
|
|
188 | \&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For |
|
|
189 | example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify |
|
|
190 | this \fBperl-ext-common\fR resource: |
|
|
191 | .PP |
|
|
192 | .Vb 1 |
|
|
193 | \& URxvt.perl-ext-common: default,-selection-popup,-option-popup |
|
|
194 | .Ve |
|
|
195 | .PP |
|
|
196 | This will keep the default extensions, but disable the two popup |
|
|
197 | extensions. Some extensions can also be configured, for example, |
|
|
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 |
|
|
201 | .Vb 1 |
|
|
202 | \& URxvt.searchable-scrollback: CM-s |
|
|
203 | .Ve |
|
|
204 | .PP |
|
|
205 | \fIThe cursor moves when selecting text in the current input line, how do I switch this off?\fR |
|
|
206 | .IX Subsection "The cursor moves when selecting text in the current input line, how do I switch this off?" |
|
|
207 | .PP |
|
|
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. |
161 | .IP "Isn't rxvt supposed to be small? Don't all those features bloat?" 4 |
298 | .Sh "Isn't rxvt supposed to be small? Don't all those features bloat?" |
162 | .IX Item "Isn't rxvt supposed to be small? Don't all those features bloat?" |
299 | .IX Subsection "Isn't rxvt supposed to be small? Don't all those features bloat?" |
163 | I often get asked about this, and I think, no, they didn't cause extra |
300 | I often get asked about this, and I think, no, they didn't cause extra |
164 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
301 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
165 | that the urxvt binary is larger (due to some encoding tables always being |
302 | that the urxvt binary is larger (due to some encoding tables always being |
166 | compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even |
303 | compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even |
167 | with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many |
304 | with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many |
168 | features unique to urxvt (locale, encoding conversion, iso14755 etc.) are |
305 | features unique to urxvt (locale, encoding conversion, iso14755 etc.) are |
169 | already in use in this mode. |
306 | already in use in this mode. |
170 | .Sp |
307 | .PP |
171 | .Vb 3 |
308 | .Vb 3 |
172 | \& text data bss drs rss filename |
309 | \& text data bss drs rss filename |
173 | \& 98398 1664 24 15695 1824 rxvt --disable-everything |
310 | \& 98398 1664 24 15695 1824 rxvt --disable-everything |
174 | \& 188985 9048 66616 18222 1788 urxvt --disable-everything |
311 | \& 188985 9048 66616 18222 1788 urxvt --disable-everything |
175 | .Ve |
312 | .Ve |
176 | .Sp |
313 | .PP |
177 | When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft |
314 | When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft |
178 | and full locale/XIM support which are quite bloaty inside libX11 and my |
315 | and full locale/XIM support which are quite bloaty inside libX11 and my |
179 | libc), the two diverge, but not unreasnobaly so. |
316 | libc), the two diverge, but not unreasnobaly so. |
180 | .Sp |
317 | .PP |
181 | .Vb 3 |
318 | .Vb 3 |
182 | \& text data bss drs rss filename |
319 | \& text data bss drs rss filename |
183 | \& 163431 2152 24 20123 2060 rxvt --enable-everything |
320 | \& 163431 2152 24 20123 2060 rxvt --enable-everything |
184 | \& 1035683 49680 66648 29096 3680 urxvt --enable-everything |
321 | \& 1035683 49680 66648 29096 3680 urxvt --enable-everything |
185 | .Ve |
322 | .Ve |
186 | .Sp |
323 | .PP |
187 | The very large size of the text section is explained by the east-asian |
324 | The very large size of the text section is explained by the east-asian |
188 | encoding tables, which, if unused, take up disk space but nothing else |
325 | encoding tables, which, if unused, take up disk space but nothing else |
189 | and can be compiled out unless you rely on X11 core fonts that use those |
326 | and can be compiled out unless you rely on X11 core fonts that use those |
190 | encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++ |
327 | encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++ |
191 | compiler allocates (but of course doesn't use unless you are out of |
328 | compiler allocates (but of course doesn't use unless you are out of |
192 | memory). Also, using an xft font instead of a core font immediately adds a |
329 | memory). Also, using an xft font instead of a core font immediately adds a |
193 | few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when |
330 | few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when |
194 | not used. |
331 | not used. |
195 | .Sp |
332 | .PP |
196 | Of course, due to every character using two or four bytes instead of one, |
333 | Of course, due to every character using two or four bytes instead of one, |
197 | a large scrollback buffer will ultimately make rxvt-unicode use more |
334 | a large scrollback buffer will ultimately make rxvt-unicode use more |
198 | memory. |
335 | memory. |
199 | .Sp |
336 | .PP |
200 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this |
337 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this |
201 | still fares rather well. And compared to some monsters like gnome-terminal |
338 | still fares rather well. And compared to some monsters like gnome-terminal |
202 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
339 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
203 | 43180k in daemons that stay around after exit, plus half a minute of |
340 | 43180k in daemons that stay around after exit, plus half a minute of |
204 | startup time, including the hundreds of warnings it spits out), it fares |
341 | startup time, including the hundreds of warnings it spits out), it fares |
205 | extremely well *g*. |
342 | extremely well *g*. |
206 | .IP "Why \*(C+, isn't that unportable/bloated/uncool?" 4 |
343 | .Sh "Why \*(C+, isn't that unportable/bloated/uncool?" |
207 | .IX Item "Why , isn't that unportable/bloated/uncool?" |
344 | .IX Subsection "Why , isn't that unportable/bloated/uncool?" |
208 | Is this a question? :) It comes up very often. The simple answer is: I had |
345 | Is this a question? :) It comes up very often. The simple answer is: I had |
209 | to write it, and \*(C+ allowed me to write and maintain it in a fraction |
346 | to write it, and \*(C+ allowed me to write and maintain it in a fraction |
210 | of the time and effort (which is a scarce resource for me). Put even |
347 | of the time and effort (which is a scarce resource for me). Put even |
211 | shorter: It simply wouldn't exist without \*(C+. |
348 | shorter: It simply wouldn't exist without \*(C+. |
212 | .Sp |
349 | .PP |
213 | My personal stance on this is that \*(C+ is less portable than C, but in |
350 | My personal stance on this is that \*(C+ is less portable than C, but in |
214 | the case of rxvt-unicode this hardly matters, as its portability limits |
351 | the case of rxvt-unicode this hardly matters, as its portability limits |
215 | are defined by things like X11, pseudo terminals, locale support and unix |
352 | are defined by things like X11, pseudo terminals, locale support and unix |
216 | domain sockets, which are all less portable than \*(C+ itself. |
353 | domain sockets, which are all less portable than \*(C+ itself. |
217 | .Sp |
354 | .PP |
218 | Regarding the bloat, see the above question: It's easy to write programs |
355 | Regarding the bloat, see the above question: It's easy to write programs |
219 | in C that use gobs of memory, an certainly possible to write programs in |
356 | in C that use gobs of memory, an certainly possible to write programs in |
220 | \&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is |
357 | \&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is |
221 | not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my |
358 | not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my |
222 | system with a minimal config: |
359 | system with a minimal config: |
223 | .Sp |
360 | .PP |
224 | .Vb 4 |
361 | .Vb 4 |
225 | \& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
362 | \& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
226 | \& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
363 | \& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
227 | \& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
364 | \& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
228 | \& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
365 | \& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
229 | .Ve |
366 | .Ve |
230 | .Sp |
367 | .PP |
231 | And here is rxvt\-unicode: |
368 | And here is rxvt\-unicode: |
232 | .Sp |
369 | .PP |
233 | .Vb 5 |
370 | .Vb 5 |
234 | \& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
371 | \& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
235 | \& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
372 | \& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
236 | \& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
373 | \& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
237 | \& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
374 | \& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
238 | \& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
375 | \& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
239 | .Ve |
376 | .Ve |
240 | .Sp |
377 | .PP |
241 | No large bloated libraries (of course, none were linked in statically), |
378 | No large bloated libraries (of course, none were linked in statically), |
242 | except maybe libX11 :) |
379 | except maybe libX11 :) |
243 | .IP "Does it support tabs, can I have a tabbed rxvt\-unicode?" 4 |
380 | .Sh "Does it support tabs, can I have a tabbed rxvt\-unicode?" |
244 | .IX Item "Does it support tabs, can I have a tabbed rxvt-unicode?" |
381 | .IX Subsection "Does it support tabs, can I have a tabbed rxvt-unicode?" |
245 | rxvt-unicode does not directly support tabs. It will work fine with |
382 | Beginning with version 7.3, there is a perl extension that implements a |
246 | tabbing functionality of many window managers or similar tabbing programs, |
383 | simple tabbed terminal. It is installed by default, so any of these should |
247 | and its embedding-features allow it to be embedded into other programs, |
384 | give you tabs: |
248 | as witnessed by \fIdoc/rxvt\-tabbed\fR or the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl |
385 | .PP |
249 | module, which features a tabbed urxvt (murxvt) terminal as an example |
386 | .Vb 1 |
250 | embedding application. |
387 | \& @@RXVT_NAME@@ -pe tabbed |
|
|
388 | .Ve |
|
|
389 | .PP |
|
|
390 | .Vb 1 |
|
|
391 | \& URxvt.perl-ext-common: default,tabbed |
|
|
392 | .Ve |
|
|
393 | .PP |
|
|
394 | It will also work fine with tabbing functionality of many window managers |
|
|
395 | or similar tabbing programs, and its embedding-features allow it to be |
|
|
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. |
251 | .IP "How do I know which rxvt-unicode version I'm using?" 4 |
399 | .Sh "How do I know which rxvt-unicode version I'm using?" |
252 | .IX Item "How do I know which rxvt-unicode version I'm using?" |
400 | .IX Subsection "How do I know which rxvt-unicode version I'm using?" |
253 | The version number is displayed with the usage (\-h). Also the escape |
401 | The version number is displayed with the usage (\-h). Also the escape |
254 | sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When |
402 | sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When |
255 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
403 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
256 | daemon. |
404 | daemon. |
257 | .IP "I am using Debian GNU/Linux and have a problem..." 4 |
405 | .Sh "I am using Debian GNU/Linux and have a problem..." |
258 | .IX Item "I am using Debian GNU/Linux and have a problem..." |
406 | .IX Subsection "I am using Debian GNU/Linux and have a problem..." |
259 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
407 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
260 | patches that considerably change the behaviour of rxvt\-unicode. Before |
408 | patches that considerably change the behaviour of rxvt-unicode (but |
261 | reporting a bug to the original rxvt-unicode author please download and |
409 | unfortunately this notice has been removed). Before reporting a bug to |
262 | install the genuine version (<http://software.schmorp.de#rxvt\-unicode>) |
410 | the original rxvt-unicode author please download and install the genuine |
263 | and try to reproduce the problem. If you cannot, chances are that the |
411 | version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce |
264 | problems are specific to Debian GNU/Linux, in which case it should be |
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 |
265 | reported via the Debian Bug Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report |
414 | Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug). |
266 | the bug). |
415 | .PP |
267 | .Sp |
|
|
268 | For other problems that also affect the Debian package, you can and |
416 | For other problems that also affect the Debian package, you can and |
269 | probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a |
417 | probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a |
270 | bug in the Debian version and it serves as a reminder for other users that |
418 | bug in the Debian version and it serves as a reminder for other users that |
271 | might encounter the same issue. |
419 | might encounter the same issue. |
272 | .IP "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?" 4 |
420 | .Sh "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?" |
273 | .IX Item "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?" |
421 | .IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?" |
274 | You should build one binary with the default options. \fIconfigure\fR |
422 | You should build one binary with the default options. \fIconfigure\fR |
275 | now enables most useful options, and the trend goes to making them |
423 | now enables most useful options, and the trend goes to making them |
276 | runtime\-switchable, too, so there is usually no drawback to enbaling them, |
424 | runtime\-switchable, too, so there is usually no drawback to enbaling them, |
277 | except higher disk and possibly memory usage. The perl interpreter should |
425 | except higher disk and possibly memory usage. The perl interpreter should |
278 | be enabled, as important functionality (menus, selection, likely more in |
426 | be enabled, as important functionality (menus, selection, likely more in |
279 | the future) depends on it. |
427 | the future) depends on it. |
280 | .Sp |
428 | .PP |
281 | You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources |
429 | You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources |
282 | system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful |
430 | system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful |
283 | behaviour. If your distribution aims at low memory, add an empty |
431 | behaviour. If your distribution aims at low memory, add an empty |
284 | \&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the |
432 | \&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the |
285 | perl interpreter disabled until the user enables it. |
433 | perl interpreter disabled until the user enables it. |
286 | .Sp |
434 | .PP |
287 | If you can/want build more binaries, I recommend building a minimal |
435 | If you can/want build more binaries, I recommend building a minimal |
288 | one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with |
436 | one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with |
289 | \&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of |
437 | \&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of |
290 | encodings built-in that increase download times and are rarely used). |
438 | encodings built-in that increase download times and are rarely used). |
291 | .IP "I need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?" 4 |
439 | .Sh "I need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?" |
292 | .IX Item "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?" |
440 | .IX Subsection "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?" |
293 | Likely not. While I honestly try to make it secure, and am probably not |
441 | It should be, starting with release 7.1. You are encouraged to properly |
294 | bad at it, I think it is simply unreasonable to expect all of freetype |
442 | install urxvt with privileges necessary for your \s-1OS\s0 now. |
295 | + fontconfig + xft + xlib + perl + ... + rxvt-unicode itself to all be |
443 | .PP |
296 | secure. Also, rxvt-unicode disables some options when it detects that it |
444 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
297 | runs setuid or setgid, which is not nice. Besides, with the embedded perl |
445 | into a helper process for privileged operations (pty handling on some |
298 | interpreter the possibility for security problems easily multiplies. |
446 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
299 | .Sp |
447 | immediately. This is much safer than most other terminals that keep |
300 | Elevated privileges are only required for utmp and pty operations on some |
448 | privileges while running (but is more relevant to urxvt, as it contains |
301 | systems (for example, GNU/Linux doesn't need any extra privileges for |
449 | things as perl interpreters, which might be \*(L"helpful\*(R" to attackers). |
302 | ptys, but some need it for utmp support). It is planned to mvoe this into |
450 | .PP |
303 | a forked handler process, but this is not yet done. |
451 | This forking is done as the very first within \fImain()\fR, which is very early |
304 | .Sp |
452 | and reduces possible bugs to initialisation code run before \fImain()\fR, or |
305 | So, while setuid/setgid operation is supported and not a problem on your |
453 | things like the dynamic loader of your system, which should result in very |
306 | typical single-user-no-other-logins unix desktop, always remember that |
454 | little risk. |
307 | its an awful lot of code, most of which isn't checked for security issues |
|
|
308 | regularly. |
|
|
309 | .IP "When I log-in to another system it tells me about missing terminfo data?" 4 |
455 | .Sh "When I log-in to another system it tells me about missing terminfo data?" |
310 | .IX Item "When I log-in to another system it tells me about missing terminfo data?" |
456 | .IX Subsection "When I log-in to another system it tells me about missing terminfo data?" |
311 | The terminal description used by rxvt-unicode is not as widely available |
457 | The terminal description used by rxvt-unicode is not as widely available |
312 | as that for xterm, or even rxvt (for which the same problem often arises). |
458 | as that for xterm, or even rxvt (for which the same problem often arises). |
313 | .Sp |
459 | .PP |
314 | The correct solution for this problem is to install the terminfo, this can |
460 | The correct solution for this problem is to install the terminfo, this can |
315 | be done like this (with ncurses' infocmp): |
461 | be done like this (with ncurses' infocmp): |
316 | .Sp |
462 | .PP |
317 | .Vb 2 |
463 | .Vb 2 |
318 | \& REMOTE=remotesystem.domain |
464 | \& REMOTE=remotesystem.domain |
319 | \& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
465 | \& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
320 | .Ve |
466 | .Ve |
321 | .Sp |
467 | .PP |
322 | \&... or by installing rxvt-unicode normally on the remote system, |
468 | \&... or by installing rxvt-unicode normally on the remote system, |
323 | .Sp |
469 | .PP |
324 | If you cannot or do not want to do this, then you can simply set |
470 | If you cannot or do not want to do this, then you can simply set |
325 | \&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of |
471 | \&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of |
326 | problems arising, which includes wrong keymapping, less and different |
472 | problems arising, which includes wrong keymapping, less and different |
327 | colours and some refresh errors in fullscreen applications. It's a nice |
473 | colours and some refresh errors in fullscreen applications. It's a nice |
328 | quick-and-dirty workaround for rare cases, though. |
474 | quick-and-dirty workaround for rare cases, though. |
329 | .Sp |
475 | .PP |
330 | If you always want to do this (and are fine with the consequences) you |
476 | If you always want to do this (and are fine with the consequences) you |
331 | can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a |
477 | can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a |
332 | resource to set it: |
478 | resource to set it: |
333 | .Sp |
479 | .PP |
334 | .Vb 1 |
480 | .Vb 1 |
335 | \& URxvt.termName: rxvt |
481 | \& URxvt.termName: rxvt |
336 | .Ve |
482 | .Ve |
337 | .Sp |
483 | .PP |
338 | If you don't plan to use \fBrxvt\fR (quite common...) you could also replace |
484 | If you don't plan to use \fBrxvt\fR (quite common...) you could also replace |
339 | the rxvt terminfo file with the rxvt-unicode one. |
485 | the rxvt terminfo file with the rxvt-unicode one. |
340 | .ie n .IP """tic"" outputs some error when compiling the terminfo entry." 4 |
486 | .ie n .Sh """tic"" outputs some error when compiling the terminfo entry." |
341 | .el .IP "\f(CWtic\fR outputs some error when compiling the terminfo entry." 4 |
487 | .el .Sh "\f(CWtic\fP outputs some error when compiling the terminfo entry." |
342 | .IX Item "tic outputs some error when compiling the terminfo entry." |
488 | .IX Subsection "tic outputs some error when compiling the terminfo entry." |
343 | Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by |
489 | Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by |
344 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
490 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
345 | .ie n .IP """bash""'s readline does not work correctly under @@RXVT_NAME@@." 4 |
491 | .ie n .Sh """bash""'s readline does not work correctly under @@RXVT_NAME@@." |
346 | .el .IP "\f(CWbash\fR's readline does not work correctly under @@RXVT_NAME@@." 4 |
492 | .el .Sh "\f(CWbash\fP's readline does not work correctly under @@RXVT_NAME@@." |
347 | .IX Item "bash's readline does not work correctly under @@RXVT_NAME@@." |
493 | .IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@." |
348 | .PD 0 |
494 | See next entry. |
349 | .IP "I need a termcap file entry." 4 |
495 | .Sh "I need a termcap file entry." |
350 | .IX Item "I need a termcap file entry." |
496 | .IX Subsection "I need a termcap file entry." |
351 | .PD |
|
|
352 | One reason you might want this is that some distributions or operating |
497 | One reason you might want this is that some distributions or operating |
353 | systems still compile some programs using the long-obsoleted termcap |
498 | systems still compile some programs using the long-obsoleted termcap |
354 | library (Fedora Core's bash is one example) and rely on a termcap entry |
499 | library (Fedora Core's bash is one example) and rely on a termcap entry |
355 | for \f(CW\*(C`rxvt\-unicode\*(C'\fR. |
500 | for \f(CW\*(C`rxvt\-unicode\*(C'\fR. |
356 | .Sp |
501 | .PP |
357 | You could use rxvt's termcap entry with resonable results in many cases. |
502 | You could use rxvt's termcap entry with resonable results in many cases. |
358 | You can also create a termcap entry by using terminfo's infocmp program |
503 | You can also create a termcap entry by using terminfo's infocmp program |
359 | like this: |
504 | like this: |
360 | .Sp |
505 | .PP |
361 | .Vb 1 |
506 | .Vb 1 |
362 | \& infocmp -C rxvt-unicode |
507 | \& infocmp -C rxvt-unicode |
363 | .Ve |
508 | .Ve |
364 | .Sp |
509 | .PP |
365 | Or you could use this termcap entry, generated by the command above: |
510 | Or you could use this termcap entry, generated by the command above: |
366 | .Sp |
511 | .PP |
367 | .Vb 20 |
512 | .Vb 20 |
368 | \& rxvt-unicode|rxvt-unicode terminal (X Window System):\e |
513 | \& rxvt-unicode|rxvt-unicode terminal (X Window System):\e |
369 | \& :am:bw:eo:km:mi:ms:xn:xo:\e |
514 | \& :am:bw:eo:km:mi:ms:xn:xo:\e |
370 | \& :co#80:it#8:li#24:lm#0:\e |
515 | \& :co#80:it#8:li#24:lm#0:\e |
371 | \& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e |
516 | \& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e |
… | |
… | |
384 | \& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e |
529 | \& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e |
385 | \& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e |
530 | \& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e |
386 | \& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e |
531 | \& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e |
387 | \& :vs=\eE[?25h: |
532 | \& :vs=\eE[?25h: |
388 | .Ve |
533 | .Ve |
389 | .ie n .IP "Why does ""ls"" no longer have coloured output?" 4 |
534 | .ie n .Sh "Why does ""ls"" no longer have coloured output?" |
390 | .el .IP "Why does \f(CWls\fR no longer have coloured output?" 4 |
535 | .el .Sh "Why does \f(CWls\fP no longer have coloured output?" |
391 | .IX Item "Why does ls no longer have coloured output?" |
536 | .IX Subsection "Why does ls no longer have coloured output?" |
392 | The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to |
537 | The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to |
393 | decide wether a terminal has colour, but uses it's own configuration |
538 | decide wether a terminal has colour, but uses it's own configuration |
394 | file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among |
539 | file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among |
395 | with most other terminals supporting colour). Either add: |
540 | with most other terminals supporting colour). Either add: |
396 | .Sp |
541 | .PP |
397 | .Vb 1 |
542 | .Vb 1 |
398 | \& TERM rxvt-unicode |
543 | \& TERM rxvt-unicode |
399 | .Ve |
544 | .Ve |
400 | .Sp |
545 | .PP |
401 | to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add: |
546 | to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add: |
402 | .Sp |
547 | .PP |
403 | .Vb 1 |
548 | .Vb 1 |
404 | \& alias ls='ls --color=auto' |
549 | \& alias ls='ls --color=auto' |
405 | .Ve |
550 | .Ve |
406 | .Sp |
551 | .PP |
407 | to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR. |
552 | to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR. |
408 | .IP "Why doesn't vim/emacs etc. use the 88 colour mode?" 4 |
553 | .Sh "Why doesn't vim/emacs etc. use the 88 colour mode?" |
409 | .IX Item "Why doesn't vim/emacs etc. use the 88 colour mode?" |
554 | .IX Subsection "Why doesn't vim/emacs etc. use the 88 colour mode?" |
410 | .PD 0 |
555 | See next entry. |
411 | .IP "Why doesn't vim/emacs etc. make use of italic?" 4 |
556 | .Sh "Why doesn't vim/emacs etc. make use of italic?" |
412 | .IX Item "Why doesn't vim/emacs etc. make use of italic?" |
557 | .IX Subsection "Why doesn't vim/emacs etc. make use of italic?" |
|
|
558 | See next entry. |
413 | .IP "Why are the secondary screen-related options not working properly?" 4 |
559 | .Sh "Why are the secondary screen-related options not working properly?" |
414 | .IX Item "Why are the secondary screen-related options not working properly?" |
560 | .IX Subsection "Why are the secondary screen-related options not working properly?" |
415 | .PD |
|
|
416 | Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged |
561 | Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged |
417 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
562 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
418 | by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra |
563 | by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra |
419 | features. Unfortunately, some of these (most notably, again, Debian |
564 | features. Unfortunately, some of these (most notably, again, Debian |
420 | GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo |
565 | GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo |
421 | file, so you will need to install it on your own (See the question \fBWhen |
566 | file, so you will need to install it on your own (See the question \fBWhen |
422 | I log-in to another system it tells me about missing terminfo data?\fR on |
567 | I log-in to another system it tells me about missing terminfo data?\fR on |
423 | how to do this). |
568 | how to do this). |
424 | .IP "My numerical keypad acts weird and generates differing output?" 4 |
569 | .Sh "My numerical keypad acts weird and generates differing output?" |
425 | .IX Item "My numerical keypad acts weird and generates differing output?" |
570 | .IX Subsection "My numerical keypad acts weird and generates differing output?" |
426 | Some Debian GNUL/Linux users seem to have this problem, although no |
571 | Some Debian GNUL/Linux users seem to have this problem, although no |
427 | specific details were reported so far. It is possible that this is caused |
572 | specific details were reported so far. It is possible that this is caused |
428 | by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how |
573 | by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how |
429 | this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible |
574 | this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible |
430 | keymap. See the answer to the previous question, and please report if that |
575 | keymap. See the answer to the previous question, and please report if that |
431 | helped. |
576 | helped. |
432 | .IP "Rxvt-unicode does not seem to understand the selected encoding?" 4 |
577 | .Sh "Rxvt-unicode does not seem to understand the selected encoding?" |
433 | .IX Item "Rxvt-unicode does not seem to understand the selected encoding?" |
578 | .IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?" |
434 | .PD 0 |
579 | See next entry. |
435 | .IP "Unicode does not seem to work?" 4 |
580 | .Sh "Unicode does not seem to work?" |
436 | .IX Item "Unicode does not seem to work?" |
581 | .IX Subsection "Unicode does not seem to work?" |
437 | .PD |
|
|
438 | If you encounter strange problems like typing an accented character but |
582 | If you encounter strange problems like typing an accented character but |
439 | getting two unrelated other characters or similar, or if program output is |
583 | getting two unrelated other characters or similar, or if program output is |
440 | subtly garbled, then you should check your locale settings. |
584 | subtly garbled, then you should check your locale settings. |
441 | .Sp |
585 | .PP |
442 | Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the |
586 | Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the |
443 | programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the |
587 | programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the |
444 | login script running within the rxvt-unicode window changes the locale to |
588 | login script running within the rxvt-unicode window changes the locale to |
445 | something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work. |
589 | something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work. |
446 | .Sp |
590 | .PP |
447 | The best thing is to fix your startup environment, as you will likely run |
591 | The best thing is to fix your startup environment, as you will likely run |
448 | into other problems. If nothing works you can try this in your .profile. |
592 | into other problems. If nothing works you can try this in your .profile. |
449 | .Sp |
593 | .PP |
450 | .Vb 1 |
594 | .Vb 1 |
451 | \& printf '\ee]701;%s\e007' "$LC_CTYPE" |
595 | \& printf '\ee]701;%s\e007' "$LC_CTYPE" |
452 | .Ve |
596 | .Ve |
453 | .Sp |
597 | .PP |
454 | If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not |
598 | If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not |
455 | supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which |
599 | supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which |
456 | displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as |
600 | displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as |
457 | it will complain loudly if it cannot set the locale). If it displays something |
601 | it will complain loudly if it cannot set the locale). If it displays something |
458 | like: |
602 | like: |
459 | .Sp |
603 | .PP |
460 | .Vb 1 |
604 | .Vb 1 |
461 | \& locale: Cannot set LC_CTYPE to default locale: ... |
605 | \& locale: Cannot set LC_CTYPE to default locale: ... |
462 | .Ve |
606 | .Ve |
463 | .Sp |
607 | .PP |
464 | Then the locale you specified is not supported on your system. |
608 | Then the locale you specified is not supported on your system. |
465 | .Sp |
609 | .PP |
466 | If nothing works and you are sure that everything is set correctly then |
610 | If nothing works and you are sure that everything is set correctly then |
467 | you will need to remember a little known fact: Some programs just don't |
611 | you will need to remember a little known fact: Some programs just don't |
468 | support locales :( |
612 | support locales :( |
469 | .IP "Why do some characters look so much different than others?" 4 |
613 | .Sh "Why do some characters look so much different than others?" |
470 | .IX Item "Why do some characters look so much different than others?" |
614 | .IX Subsection "Why do some characters look so much different than others?" |
471 | .PD 0 |
615 | See next entry. |
472 | .IP "How does rxvt-unicode choose fonts?" 4 |
616 | .Sh "How does rxvt-unicode choose fonts?" |
473 | .IX Item "How does rxvt-unicode choose fonts?" |
617 | .IX Subsection "How does rxvt-unicode choose fonts?" |
474 | .PD |
|
|
475 | Most fonts do not contain the full range of Unicode, which is |
618 | Most fonts do not contain the full range of Unicode, which is |
476 | fine. Chances are that the font you (or the admin/package maintainer of |
619 | fine. Chances are that the font you (or the admin/package maintainer of |
477 | your system/os) have specified does not cover all the characters you want |
620 | your system/os) have specified does not cover all the characters you want |
478 | to display. |
621 | to display. |
479 | .Sp |
622 | .PP |
480 | \&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement |
623 | \&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement |
481 | font. Often the result is fine, but sometimes the chosen font looks |
624 | font. Often the result is fine, but sometimes the chosen font looks |
482 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
625 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
483 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
626 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
484 | intelligence to detect that a specific glyph is wrong: it has to believe |
627 | intelligence to detect that a specific glyph is wrong: it has to believe |
485 | the font that the characters it claims to contain indeed look correct. |
628 | the font that the characters it claims to contain indeed look correct. |
486 | .Sp |
629 | .PP |
487 | In that case, select a font of your taste and add it to the font list, |
630 | In that case, select a font of your taste and add it to the font list, |
488 | e.g.: |
631 | e.g.: |
489 | .Sp |
632 | .PP |
490 | .Vb 1 |
633 | .Vb 1 |
491 | \& @@RXVT_NAME@@ -fn basefont,font2,font3... |
634 | \& @@RXVT_NAME@@ -fn basefont,font2,font3... |
492 | .Ve |
635 | .Ve |
493 | .Sp |
636 | .PP |
494 | When rxvt-unicode sees a character, it will first look at the base |
637 | When rxvt-unicode sees a character, it will first look at the base |
495 | font. If the base font does not contain the character, it will go to the |
638 | font. If the base font does not contain the character, it will go to the |
496 | next font, and so on. Specifying your own fonts will also speed up this |
639 | next font, and so on. Specifying your own fonts will also speed up this |
497 | search and use less resources within rxvt-unicode and the X\-server. |
640 | search and use less resources within rxvt-unicode and the X\-server. |
498 | .Sp |
641 | .PP |
499 | The only limitation is that none of the fonts may be larger than the base |
642 | The only limitation is that none of the fonts may be larger than the base |
500 | font, as the base font defines the terminal character cell size, which |
643 | font, as the base font defines the terminal character cell size, which |
501 | must be the same due to the way terminals work. |
644 | must be the same due to the way terminals work. |
502 | .IP "Why do some chinese characters look so different than others?" 4 |
645 | .Sh "Why do some chinese characters look so different than others?" |
503 | .IX Item "Why do some chinese characters look so different than others?" |
646 | .IX Subsection "Why do some chinese characters look so different than others?" |
504 | This is because there is a difference between script and language \*(-- |
647 | This is because there is a difference between script and language \*(-- |
505 | rxvt-unicode does not know which language the text that is output is, |
648 | rxvt-unicode does not know which language the text that is output is, |
506 | as it only knows the unicode character codes. If rxvt-unicode first |
649 | as it only knows the unicode character codes. If rxvt-unicode first |
507 | sees a japanese/chinese character, it might choose a japanese font for |
650 | sees a japanese/chinese character, it might choose a japanese font for |
508 | display. Subsequent japanese characters will use that font. Now, many |
651 | display. Subsequent japanese characters will use that font. Now, many |
509 | chinese characters aren't represented in japanese fonts, so when the first |
652 | chinese characters aren't represented in japanese fonts, so when the first |
510 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
653 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
511 | \&\*(-- unfortunately at this point, it will still use the japanese font for |
654 | \&\*(-- unfortunately at this point, it will still use the japanese font for |
512 | chinese characters that are also in the japanese font. |
655 | chinese characters that are also in the japanese font. |
513 | .Sp |
656 | .PP |
514 | The workaround is easy: just tag a chinese font at the end of your font |
657 | The workaround is easy: just tag a chinese font at the end of your font |
515 | list (see the previous question). The key is to view the font list as |
658 | list (see the previous question). The key is to view the font list as |
516 | a preference list: If you expect more japanese, list a japanese font |
659 | a preference list: If you expect more japanese, list a japanese font |
517 | first. If you expect more chinese, put a chinese font first. |
660 | first. If you expect more chinese, put a chinese font first. |
518 | .Sp |
661 | .PP |
519 | In the future it might be possible to switch language preferences at |
662 | In the future it might be possible to switch language preferences at |
520 | runtime (the internal data structure has no problem with using different |
663 | runtime (the internal data structure has no problem with using different |
521 | fonts for the same character at the same time, but no interface for this |
664 | fonts for the same character at the same time, but no interface for this |
522 | has been designed yet). |
665 | has been designed yet). |
523 | .Sp |
666 | .PP |
524 | 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). |
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). |
525 | .IP "Why does rxvt-unicode sometimes leave pixel droppings?" 4 |
668 | .Sh "Why does rxvt-unicode sometimes leave pixel droppings?" |
526 | .IX Item "Why does rxvt-unicode sometimes leave pixel droppings?" |
669 | .IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?" |
527 | Most fonts were not designed for terminal use, which means that character |
670 | Most fonts were not designed for terminal use, which means that character |
528 | size varies a lot. A font that is otherwise fine for terminal use might |
671 | size varies a lot. A font that is otherwise fine for terminal use might |
529 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
672 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
530 | these characters. For characters that are just \*(L"a bit\*(R" too wide a special |
673 | these characters. For characters that are just \*(L"a bit\*(R" too wide a special |
531 | \&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters. |
674 | \&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters. |
532 | .Sp |
675 | .PP |
533 | All of this requires that fonts do not lie about character sizes, |
676 | All of this requires that fonts do not lie about character sizes, |
534 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
677 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
535 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
678 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
536 | ask for the character bounding box, which unfortunately is wrong in these |
679 | ask for the character bounding box, which unfortunately is wrong in these |
537 | cases). |
680 | cases). |
538 | .Sp |
681 | .PP |
539 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
682 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
540 | or the respective font. If you encounter this problem you might try using |
683 | or the respective font. If you encounter this problem you might try using |
541 | the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you |
684 | the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you |
542 | might be forced to use a different font. |
685 | might be forced to use a different font. |
543 | .Sp |
686 | .PP |
544 | All of this is not a problem when using X11 core fonts, as their bounding |
687 | All of this is not a problem when using X11 core fonts, as their bounding |
545 | box data is correct. |
688 | box data is correct. |
546 | .IP "On Solaris 9, many line-drawing characters are too wide." 4 |
689 | .Sh "On Solaris 9, many line-drawing characters are too wide." |
547 | .IX Item "On Solaris 9, many line-drawing characters are too wide." |
690 | .IX Subsection "On Solaris 9, many line-drawing characters are too wide." |
548 | Seems to be a known bug, read |
691 | Seems to be a known bug, read |
549 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
692 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
550 | following ugly workaround to get non-double-wide-characters working: |
693 | following ugly workaround to get non-double-wide-characters working: |
551 | .Sp |
694 | .PP |
552 | .Vb 1 |
695 | .Vb 1 |
553 | \& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
696 | \& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
554 | .Ve |
697 | .Ve |
555 | .IP "My Compose (Multi_key) key is no longer working." 4 |
698 | .Sh "My Compose (Multi_key) key is no longer working." |
556 | .IX Item "My Compose (Multi_key) key is no longer working." |
699 | .IX Subsection "My Compose (Multi_key) key is no longer working." |
557 | The most common causes for this are that either your locale is not set |
700 | The most common causes for this are that either your locale is not set |
558 | correctly, or you specified a \fBpreeditStyle\fR that is not supported by |
701 | correctly, or you specified a \fBpreeditStyle\fR that is not supported by |
559 | your input method. For example, if you specified \fBOverTheSpot\fR and |
702 | your input method. For example, if you specified \fBOverTheSpot\fR and |
560 | your input method (e.g. the default input method handling Compose keys) |
703 | your input method (e.g. the default input method handling Compose keys) |
561 | does not support this (for instance because it is not visual), then |
704 | does not support this (for instance because it is not visual), then |
562 | rxvt-unicode will continue without an input method. |
705 | rxvt-unicode will continue without an input method. |
563 | .Sp |
706 | .PP |
564 | In this case either do not specify a \fBpreeditStyle\fR or specify more than |
707 | In this case either do not specify a \fBpreeditStyle\fR or specify more than |
565 | one pre-edit style, such as \fBOverTheSpot,Root,None\fR. |
708 | one pre-edit style, such as \fBOverTheSpot,Root,None\fR. |
566 | .ie n .IP "I cannot type ""Ctrl\-Shift\-2"" to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" 4 |
709 | .ie n .Sh "I cannot type ""Ctrl\-Shift\-2"" to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" |
567 | .el .IP "I cannot type \f(CWCtrl\-Shift\-2\fR to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" 4 |
710 | .el .Sh "I cannot type \f(CWCtrl\-Shift\-2\fP to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" |
568 | .IX Item "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755" |
711 | .IX Subsection "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755" |
569 | Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on |
712 | Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on |
570 | international keyboards) or simply use \s-1ISO\s0 14755 support to your |
713 | international keyboards) or simply use \s-1ISO\s0 14755 support to your |
571 | advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other |
714 | advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other |
572 | codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape |
715 | codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape |
573 | character and so on. |
716 | character and so on. |
574 | .IP "How can I keep rxvt-unicode from using reverse video so much?" 4 |
717 | .Sh "How can I keep rxvt-unicode from using reverse video so much?" |
575 | .IX Item "How can I keep rxvt-unicode from using reverse video so much?" |
718 | .IX Subsection "How can I keep rxvt-unicode from using reverse video so much?" |
576 | First of all, make sure you are running with the right terminal settings |
719 | First of all, make sure you are running with the right terminal settings |
577 | (\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then |
720 | (\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then |
578 | make sure you have specified colours for italic and bold, as otherwise |
721 | make sure you have specified colours for italic and bold, as otherwise |
579 | rxvt-unicode might use reverse video to simulate the effect: |
722 | rxvt-unicode might use reverse video to simulate the effect: |
580 | .Sp |
723 | .PP |
581 | .Vb 2 |
724 | .Vb 2 |
582 | \& URxvt.colorBD: white |
725 | \& URxvt.colorBD: white |
583 | \& URxvt.colorIT: green |
726 | \& URxvt.colorIT: green |
584 | .Ve |
727 | .Ve |
585 | .IP "Some programs assume totally weird colours (red instead of blue), how can I fix that?" 4 |
728 | .Sh "Some programs assume totally weird colours (red instead of blue), how can I fix that?" |
586 | .IX Item "Some programs assume totally weird colours (red instead of blue), how can I fix that?" |
729 | .IX Subsection "Some programs assume totally weird colours (red instead of blue), how can I fix that?" |
587 | For some unexplainable reason, some rare programs assume a very weird |
730 | For some unexplainable reason, some rare programs assume a very weird |
588 | colour palette when confronted with a terminal with more than the standard |
731 | colour palette when confronted with a terminal with more than the standard |
589 | 8 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix |
732 | 8 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix |
590 | these programs not to assume non-ISO colours without very good reasons. |
733 | these programs not to assume non-ISO colours without very good reasons. |
591 | .Sp |
734 | .PP |
592 | In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo |
735 | In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo |
593 | definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will |
736 | definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will |
594 | fix colours but keep you from using other rxvt-unicode features. |
737 | fix colours but keep you from using other rxvt-unicode features. |
595 | .IP "I am on FreeBSD and rxvt-unicode does not seem to work at all." 4 |
738 | .Sh "I am on FreeBSD and rxvt-unicode does not seem to work at all." |
596 | .IX Item "I am on FreeBSD and rxvt-unicode does not seem to work at all." |
739 | .IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all." |
597 | Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined |
740 | Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined |
598 | in your compile environment, or an implementation that implements it, |
741 | in your compile environment, or an implementation that implements it, |
599 | wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that |
742 | wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that |
600 | \&\fBwchar_t\fR is represented as unicode. |
743 | \&\fBwchar_t\fR is represented as unicode. |
601 | .Sp |
744 | .PP |
602 | As you might have guessed, FreeBSD does neither define this symobl nor |
745 | As you might have guessed, FreeBSD does neither define this symobl nor |
603 | does it support it. Instead, it uses it's own internal representation of |
746 | does it support it. Instead, it uses it's own internal representation of |
604 | \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. |
747 | \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. |
605 | .Sp |
748 | .PP |
606 | However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and |
749 | However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and |
607 | \&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. |
750 | \&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. |
608 | .Sp |
751 | .PP |
609 | \&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language |
752 | \&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language |
610 | apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized) |
753 | apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized) |
611 | representation of \fBwchar_t\fR makes it impossible to convert between |
754 | representation of \fBwchar_t\fR makes it impossible to convert between |
612 | \&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding |
755 | \&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding |
613 | without implementing OS-specific-wrappers for each and every locale. There |
756 | without implementing OS-specific-wrappers for each and every locale. There |
614 | simply are no APIs to convert \fBwchar_t\fR into anything except the current |
757 | simply are no APIs to convert \fBwchar_t\fR into anything except the current |
615 | locale encoding. |
758 | locale encoding. |
616 | .Sp |
759 | .PP |
617 | Some applications (such as the formidable \fBmlterm\fR) work around this |
760 | Some applications (such as the formidable \fBmlterm\fR) work around this |
618 | by carrying their own replacement functions for character set handling |
761 | by carrying their own replacement functions for character set handling |
619 | with them, and either implementing OS-dependent hacks or doing multiple |
762 | with them, and either implementing OS-dependent hacks or doing multiple |
620 | conversions (which is slow and unreliable in case the \s-1OS\s0 implements |
763 | conversions (which is slow and unreliable in case the \s-1OS\s0 implements |
621 | encodings slightly different than the terminal emulator). |
764 | encodings slightly different than the terminal emulator). |
622 | .Sp |
765 | .PP |
623 | The rxvt-unicode author insists that the right way to fix this is in the |
766 | The rxvt-unicode author insists that the right way to fix this is in the |
624 | system libraries once and for all, instead of forcing every app to carry |
767 | system libraries once and for all, instead of forcing every app to carry |
625 | complete replacements for them :) |
768 | complete replacements for them :) |
626 | .IP "I use Solaris 9 and it doesn't compile/work/etc." 4 |
769 | .Sh "I use Solaris 9 and it doesn't compile/work/etc." |
627 | .IX Item "I use Solaris 9 and it doesn't compile/work/etc." |
770 | .IX Subsection "I use Solaris 9 and it doesn't compile/work/etc." |
628 | Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst |
771 | Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst |
629 | problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem. |
772 | problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem. |
630 | .IP "How can I use rxvt-unicode under cygwin?" 4 |
773 | .Sh "How can I use rxvt-unicode under cygwin?" |
631 | .IX Item "How can I use rxvt-unicode under cygwin?" |
774 | .IX Subsection "How can I use rxvt-unicode under cygwin?" |
632 | rxvt-unicode should compile and run out of the box on cygwin, using |
775 | rxvt-unicode should compile and run out of the box on cygwin, using |
633 | the X11 libraries that come with cygwin. libW11 emulation is no |
776 | the X11 libraries that come with cygwin. libW11 emulation is no |
634 | longer supported (and makes no sense, either, as it only supported a |
777 | longer supported (and makes no sense, either, as it only supported a |
635 | single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or |
778 | single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or |
636 | \&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the |
779 | \&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the |
637 | old libW11 emulation. |
780 | old libW11 emulation. |
638 | .Sp |
781 | .PP |
639 | At the time of this writing, cygwin didn't seem to support any multi-byte |
782 | At the time of this writing, cygwin didn't seem to support any multi-byte |
640 | encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited |
783 | encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited |
641 | to 8\-bit encodings. |
784 | to 8\-bit encodings. |
642 | .IP "How does rxvt-unicode determine the encoding to use?" 4 |
785 | .Sh "How does rxvt-unicode determine the encoding to use?" |
643 | .IX Item "How does rxvt-unicode determine the encoding to use?" |
786 | .IX Subsection "How does rxvt-unicode determine the encoding to use?" |
644 | .PD 0 |
787 | See next entry. |
645 | .IP "Is there an option to switch encodings?" 4 |
788 | .Sh "Is there an option to switch encodings?" |
646 | .IX Item "Is there an option to switch encodings?" |
789 | .IX Subsection "Is there an option to switch encodings?" |
647 | .PD |
|
|
648 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
790 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
649 | specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about |
791 | specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about |
650 | \&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O. |
792 | \&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O. |
651 | .Sp |
793 | .PP |
652 | The reasons is that there exists a perfectly fine mechanism for selecting |
794 | The reasons is that there exists a perfectly fine mechanism for selecting |
653 | the encoding, doing I/O and (most important) communicating this to all |
795 | the encoding, doing I/O and (most important) communicating this to all |
654 | applications so everybody agrees on character properties such as width |
796 | applications so everybody agrees on character properties such as width |
655 | and code number. This mechanism is the \fIlocale\fR. Applications not using |
797 | and code number. This mechanism is the \fIlocale\fR. Applications not using |
656 | that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of |
798 | that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of |
657 | characters wrong as it uses it's own, locale-independent table under all |
799 | characters wrong as it uses it's own, locale-independent table under all |
658 | locales). |
800 | locales). |
659 | .Sp |
801 | .PP |
660 | Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All |
802 | Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All |
661 | programs doing the same (that is, most) will automatically agree in the |
803 | programs doing the same (that is, most) will automatically agree in the |
662 | interpretation of characters. |
804 | interpretation of characters. |
663 | .Sp |
805 | .PP |
664 | Unfortunately, there is no system-independent way to select locales, nor |
806 | Unfortunately, there is no system-independent way to select locales, nor |
665 | is there a standard on how locale specifiers will look like. |
807 | is there a standard on how locale specifiers will look like. |
666 | .Sp |
808 | .PP |
667 | On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable |
809 | On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable |
668 | contains an arbitrary string which corresponds to an already-installed |
810 | contains an arbitrary string which corresponds to an already-installed |
669 | 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, |
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, |
670 | \&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms |
812 | \&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms |
671 | (i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common. |
813 | (i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common. |
672 | .Sp |
814 | .PP |
673 | Rxvt-unicode ignores all other locale categories, and except for |
815 | Rxvt-unicode ignores all other locale categories, and except for |
674 | the encoding, ignores country or language-specific settings, |
816 | the encoding, ignores country or language-specific settings, |
675 | 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 |
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 |
676 | rxvt\-unicode. |
818 | rxvt\-unicode. |
677 | .Sp |
819 | .PP |
678 | If you want to use a specific encoding you have to make sure you start |
820 | If you want to use a specific encoding you have to make sure you start |
679 | rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category. |
821 | rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category. |
680 | .IP "Can I switch locales at runtime?" 4 |
822 | .Sh "Can I switch locales at runtime?" |
681 | .IX Item "Can I switch locales at runtime?" |
823 | .IX Subsection "Can I switch locales at runtime?" |
682 | Yes, using an escape sequence. Try something like this, which sets |
824 | Yes, using an escape sequence. Try something like this, which sets |
683 | rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR. |
825 | rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR. |
684 | .Sp |
826 | .PP |
685 | .Vb 1 |
827 | .Vb 1 |
686 | \& printf '\ee]701;%s\e007' ja_JP.SJIS |
828 | \& printf '\ee]701;%s\e007' ja_JP.SJIS |
687 | .Ve |
829 | .Ve |
688 | .Sp |
830 | .PP |
689 | See also the previous answer. |
831 | See also the previous answer. |
690 | .Sp |
832 | .PP |
691 | Sometimes this capability is rather handy when you want to work in |
833 | Sometimes this capability is rather handy when you want to work in |
692 | one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it |
834 | one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it |
693 | (e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which |
835 | (e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which |
694 | first switches to a locale supported by xjdic and back later: |
836 | first switches to a locale supported by xjdic and back later: |
695 | .Sp |
837 | .PP |
696 | .Vb 3 |
838 | .Vb 3 |
697 | \& printf '\ee]701;%s\e007' ja_JP.SJIS |
839 | \& printf '\ee]701;%s\e007' ja_JP.SJIS |
698 | \& xjdic -js |
840 | \& xjdic -js |
699 | \& printf '\ee]701;%s\e007' de_DE.UTF-8 |
841 | \& printf '\ee]701;%s\e007' de_DE.UTF-8 |
700 | .Ve |
842 | .Ve |
701 | .Sp |
843 | .PP |
702 | You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except |
844 | You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except |
703 | for some locales where character width differs between program\- and |
845 | for some locales where character width differs between program\- and |
704 | rxvt\-unicode\-locales. |
846 | rxvt\-unicode\-locales. |
705 | .IP "Can I switch the fonts at runtime?" 4 |
847 | .Sh "Can I switch the fonts at runtime?" |
706 | .IX Item "Can I switch the fonts at runtime?" |
848 | .IX Subsection "Can I switch the fonts at runtime?" |
707 | Yes, using an escape sequence. Try something like this, which has the same |
849 | Yes, using an escape sequence. Try something like this, which has the same |
708 | effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately: |
850 | effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately: |
709 | .Sp |
851 | .PP |
710 | .Vb 1 |
852 | .Vb 1 |
711 | \& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic" |
853 | \& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic" |
712 | .Ve |
854 | .Ve |
713 | .Sp |
855 | .PP |
714 | This is useful if you e.g. work primarily with japanese (and prefer a |
856 | This is useful if you e.g. work primarily with japanese (and prefer a |
715 | japanese font), but you have to switch to chinese temporarily, where |
857 | japanese font), but you have to switch to chinese temporarily, where |
716 | japanese fonts would only be in your way. |
858 | japanese fonts would only be in your way. |
717 | .Sp |
859 | .PP |
718 | You can think of this as a kind of manual \s-1ISO\-2022\s0 switching. |
860 | You can think of this as a kind of manual \s-1ISO\-2022\s0 switching. |
719 | .IP "Why do italic characters look as if clipped?" 4 |
861 | .Sh "Why do italic characters look as if clipped?" |
720 | .IX Item "Why do italic characters look as if clipped?" |
862 | .IX Subsection "Why do italic characters look as if clipped?" |
721 | Many fonts have difficulties with italic characters and hinting. For |
863 | Many fonts have difficulties with italic characters and hinting. For |
722 | example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans |
864 | example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans |
723 | Mono\*(C'\fR completely fails in it's italic face. A workaround might be to |
865 | Mono\*(C'\fR completely fails in it's italic face. A workaround might be to |
724 | enable freetype autohinting, i.e. like this: |
866 | enable freetype autohinting, i.e. like this: |
725 | .Sp |
867 | .PP |
726 | .Vb 2 |
868 | .Vb 2 |
727 | \& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
869 | \& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
728 | \& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
870 | \& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
729 | .Ve |
871 | .Ve |
730 | .IP "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?" 4 |
872 | .Sh "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?" |
731 | .IX Item "My input method wants <some encoding> but I want UTF-8, what can I do?" |
873 | .IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?" |
732 | You can specify separate locales for the input method and the rest of the |
874 | You can specify separate locales for the input method and the rest of the |
733 | terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR: |
875 | terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR: |
734 | .Sp |
876 | .PP |
735 | .Vb 1 |
877 | .Vb 1 |
736 | \& URxvt*imlocale: ja_JP.EUC-JP |
878 | \& URxvt.imlocale: ja_JP.EUC-JP |
737 | .Ve |
879 | .Ve |
738 | .Sp |
880 | .PP |
739 | Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still |
881 | Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still |
740 | use your input method. Please note, however, that you will not be able to |
882 | use your input method. Please note, however, that you will not be able to |
741 | input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input |
883 | input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input |
742 | method limits you. |
884 | method limits you. |
743 | .IP "Rxvt-unicode crashes when the X Input Method changes or exits." 4 |
885 | .Sh "Rxvt-unicode crashes when the X Input Method changes or exits." |
744 | .IX Item "Rxvt-unicode crashes when the X Input Method changes or exits." |
886 | .IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits." |
745 | Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by |
887 | Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by |
746 | design. Applications can avoid some crashes at the expense of memory |
888 | design. Applications can avoid some crashes at the expense of memory |
747 | leaks, and Input Methods can avoid some crashes by careful ordering at |
889 | leaks, and Input Methods can avoid some crashes by careful ordering at |
748 | exit time. \fBkinput2\fR (and derived input methods) generally succeeds, |
890 | exit time. \fBkinput2\fR (and derived input methods) generally succeeds, |
749 | while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however, |
891 | while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however, |
750 | crashes cannot be completely avoided even if both sides cooperate. |
892 | crashes cannot be completely avoided even if both sides cooperate. |
751 | .Sp |
893 | .PP |
752 | So the only workaround is not to kill your Input Method Servers. |
894 | So the only workaround is not to kill your Input Method Servers. |
753 | .IP "Rxvt-unicode uses gobs of memory, how can I reduce that?" 4 |
895 | .Sh "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
754 | .IX Item "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
896 | .IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
755 | Rxvt-unicode tries to obey the rule of not charging you for something you |
897 | Rxvt-unicode tries to obey the rule of not charging you for something you |
756 | don't use. One thing you should try is to configure out all settings that |
898 | don't use. One thing you should try is to configure out all settings that |
757 | you don't need, for example, Xft support is a resource hog by design, |
899 | you don't need, for example, Xft support is a resource hog by design, |
758 | when used. Compiling it out ensures that no Xft font will be loaded |
900 | when used. Compiling it out ensures that no Xft font will be loaded |
759 | accidentally when rxvt-unicode tries to find a font for your characters. |
901 | accidentally when rxvt-unicode tries to find a font for your characters. |
760 | .Sp |
902 | .PP |
761 | Also, many people (me included) like large windows and even larger |
903 | Also, many people (me included) like large windows and even larger |
762 | scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use |
904 | scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use |
763 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
905 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
764 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
906 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
765 | use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as |
907 | use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as |
766 | rxvt-unicode then uses 8 bytes per screen cell. |
908 | rxvt-unicode then uses 8 bytes per screen cell. |
767 | .IP "Can I speed up Xft rendering somehow?" 4 |
909 | .Sh "Can I speed up Xft rendering somehow?" |
768 | .IX Item "Can I speed up Xft rendering somehow?" |
910 | .IX Subsection "Can I speed up Xft rendering somehow?" |
769 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
911 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
770 | it is simply slow. If you still want Xft fonts you might try to disable |
912 | it is simply slow. If you still want Xft fonts you might try to disable |
771 | antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of |
913 | antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of |
772 | memory and also speeds up rendering considerably. |
914 | memory and also speeds up rendering considerably. |
773 | .IP "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 4 |
915 | .Sh "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" |
774 | .IX Item "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" |
916 | .IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" |
775 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
917 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
776 | fall back to it's default font search list it will prefer X11 core |
918 | fall back to it's default font search list it will prefer X11 core |
777 | fonts, because they are small and fast, and then use Xft fonts. It has |
919 | fonts, because they are small and fast, and then use Xft fonts. It has |
778 | antialiasing disabled for most of them, because the author thinks they |
920 | antialiasing disabled for most of them, because the author thinks they |
779 | look best that way. |
921 | look best that way. |
780 | .Sp |
922 | .PP |
781 | If you want antialiasing, you have to specify the fonts manually. |
923 | If you want antialiasing, you have to specify the fonts manually. |
782 | .IP "Mouse cut/paste suddenly no longer works." 4 |
924 | .Sh "Mouse cut/paste suddenly no longer works." |
783 | .IX Item "Mouse cut/paste suddenly no longer works." |
925 | .IX Subsection "Mouse cut/paste suddenly no longer works." |
784 | Make sure that mouse reporting is actually turned off since killing |
926 | Make sure that mouse reporting is actually turned off since killing |
785 | some editors prematurely may leave the mouse in mouse report mode. I've |
927 | some editors prematurely may leave the mouse in mouse report mode. I've |
786 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
928 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
787 | quick check is to see if cut/paste works when the Alt or Shift keys are |
929 | quick check is to see if cut/paste works when the Alt or Shift keys are |
788 | depressed. See @@RXVT_NAME@@(7) |
930 | depressed. |
789 | .IP "What's with this bold/blink stuff?" 4 |
931 | .Sh "What's with this bold/blink stuff?" |
790 | .IX Item "What's with this bold/blink stuff?" |
932 | .IX Subsection "What's with this bold/blink stuff?" |
791 | If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the |
933 | If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the |
792 | standard foreground colour. |
934 | standard foreground colour. |
793 | .Sp |
935 | .PP |
794 | For the standard background colour, blinking will actually make the |
936 | For the standard background colour, blinking will actually make the |
795 | text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard |
937 | text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard |
796 | colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be |
938 | colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be |
797 | ignored. |
939 | ignored. |
798 | .Sp |
940 | .PP |
799 | On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity |
941 | On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity |
800 | foreground/background colors. |
942 | foreground/background colors. |
801 | .Sp |
943 | .PP |
802 | color0\-7 are the low-intensity colors. |
944 | color0\-7 are the low-intensity colors. |
803 | .Sp |
945 | .PP |
804 | color8\-15 are the corresponding high-intensity colors. |
946 | color8\-15 are the corresponding high-intensity colors. |
805 | .IP "I don't like the screen colors. How do I change them?" 4 |
947 | .Sh "I don't like the screen colors. How do I change them?" |
806 | .IX Item "I don't like the screen colors. How do I change them?" |
948 | .IX Subsection "I don't like the screen colors. How do I change them?" |
807 | You can change the screen colors at run-time using \fI~/.Xdefaults\fR |
949 | You can change the screen colors at run-time using \fI~/.Xdefaults\fR |
808 | resources (or as long\-options). |
950 | resources (or as long\-options). |
809 | .Sp |
951 | .PP |
810 | Here are values that are supposed to resemble a \s-1VGA\s0 screen, |
952 | Here are values that are supposed to resemble a \s-1VGA\s0 screen, |
811 | including the murky brown that passes for low-intensity yellow: |
953 | including the murky brown that passes for low-intensity yellow: |
812 | .Sp |
954 | .PP |
813 | .Vb 8 |
955 | .Vb 8 |
814 | \& URxvt.color0: #000000 |
956 | \& URxvt.color0: #000000 |
815 | \& URxvt.color1: #A80000 |
957 | \& URxvt.color1: #A80000 |
816 | \& URxvt.color2: #00A800 |
958 | \& URxvt.color2: #00A800 |
817 | \& URxvt.color3: #A8A800 |
959 | \& URxvt.color3: #A8A800 |
818 | \& URxvt.color4: #0000A8 |
960 | \& URxvt.color4: #0000A8 |
819 | \& URxvt.color5: #A800A8 |
961 | \& URxvt.color5: #A800A8 |
820 | \& URxvt.color6: #00A8A8 |
962 | \& URxvt.color6: #00A8A8 |
821 | \& URxvt.color7: #A8A8A8 |
963 | \& URxvt.color7: #A8A8A8 |
822 | .Ve |
964 | .Ve |
823 | .Sp |
965 | .PP |
824 | .Vb 8 |
966 | .Vb 8 |
825 | \& URxvt.color8: #000054 |
967 | \& URxvt.color8: #000054 |
826 | \& URxvt.color9: #FF0054 |
968 | \& URxvt.color9: #FF0054 |
827 | \& URxvt.color10: #00FF54 |
969 | \& URxvt.color10: #00FF54 |
828 | \& URxvt.color11: #FFFF54 |
970 | \& URxvt.color11: #FFFF54 |
829 | \& URxvt.color12: #0000FF |
971 | \& URxvt.color12: #0000FF |
830 | \& URxvt.color13: #FF00FF |
972 | \& URxvt.color13: #FF00FF |
831 | \& URxvt.color14: #00FFFF |
973 | \& URxvt.color14: #00FFFF |
832 | \& URxvt.color15: #FFFFFF |
974 | \& URxvt.color15: #FFFFFF |
833 | .Ve |
975 | .Ve |
834 | .Sp |
976 | .PP |
835 | And here is a more complete set of non-standard colors described (not by |
977 | And here is a more complete set of non-standard colors described (not by |
836 | me) as \*(L"pretty girly\*(R". |
978 | me) as \*(L"pretty girly\*(R". |
837 | .Sp |
979 | .PP |
838 | .Vb 18 |
980 | .Vb 18 |
839 | \& URxvt.cursorColor: #dc74d1 |
981 | \& URxvt.cursorColor: #dc74d1 |
840 | \& URxvt.pointerColor: #dc74d1 |
982 | \& URxvt.pointerColor: #dc74d1 |
841 | \& URxvt.background: #0e0e0e |
983 | \& URxvt.background: #0e0e0e |
842 | \& URxvt.foreground: #4ad5e1 |
984 | \& URxvt.foreground: #4ad5e1 |
… | |
… | |
853 | \& URxvt.color6: #73f7ff |
995 | \& URxvt.color6: #73f7ff |
854 | \& URxvt.color14: #73f7ff |
996 | \& URxvt.color14: #73f7ff |
855 | \& URxvt.color7: #e1dddd |
997 | \& URxvt.color7: #e1dddd |
856 | \& URxvt.color15: #e1dddd |
998 | \& URxvt.color15: #e1dddd |
857 | .Ve |
999 | .Ve |
858 | .IP "How can I start @@RXVT_NAME@@d in a race-free way?" 4 |
1000 | .Sh "How can I start @@RXVT_NAME@@d in a race-free way?" |
859 | .IX Item "How can I start @@RXVT_NAME@@d in a race-free way?" |
1001 | .IX Subsection "How can I start @@RXVT_NAME@@d in a race-free way?" |
860 | Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the |
1002 | Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the |
861 | display, create the listening socket and then fork. |
1003 | display, create the listening socket and then fork. |
862 | .IP "What's with the strange Backspace/Delete key behaviour?" 4 |
1004 | .Sh "What's with the strange Backspace/Delete key behaviour?" |
863 | .IX Item "What's with the strange Backspace/Delete key behaviour?" |
1005 | .IX Subsection "What's with the strange Backspace/Delete key behaviour?" |
864 | Assuming that the physical Backspace key corresponds to the |
1006 | Assuming that the physical Backspace key corresponds to the |
865 | BackSpace keysym (not likely for Linux ... see the following |
1007 | BackSpace keysym (not likely for Linux ... see the following |
866 | question) there are two standard values that can be used for |
1008 | question) there are two standard values that can be used for |
867 | Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR. |
1009 | Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR. |
868 | .Sp |
1010 | .PP |
869 | Historically, either value is correct, but rxvt-unicode adopts the debian |
1011 | Historically, either value is correct, but rxvt-unicode adopts the debian |
870 | policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct |
1012 | policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct |
871 | choice :). |
1013 | choice :). |
872 | .Sp |
1014 | .PP |
873 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
1015 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
874 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
1016 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
875 | started from a terminal (say, from a menu or by remote shell), then the |
1017 | started from a terminal (say, from a menu or by remote shell), then the |
876 | system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will |
1018 | system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will |
877 | be used (which may not be the same as your stty setting). |
1019 | be used (which may not be the same as your stty setting). |
878 | .Sp |
1020 | .PP |
879 | For starting a new rxvt\-unicode: |
1021 | For starting a new rxvt\-unicode: |
880 | .Sp |
1022 | .PP |
881 | .Vb 3 |
1023 | .Vb 3 |
882 | \& # use Backspace = ^H |
1024 | \& # use Backspace = ^H |
883 | \& $ stty erase ^H |
1025 | \& $ stty erase ^H |
884 | \& $ @@RXVT_NAME@@ |
1026 | \& $ @@RXVT_NAME@@ |
885 | .Ve |
1027 | .Ve |
886 | .Sp |
1028 | .PP |
887 | .Vb 3 |
1029 | .Vb 3 |
888 | \& # use Backspace = ^? |
1030 | \& # use Backspace = ^? |
889 | \& $ stty erase ^? |
1031 | \& $ stty erase ^? |
890 | \& $ @@RXVT_NAME@@ |
1032 | \& $ @@RXVT_NAME@@ |
891 | .Ve |
1033 | .Ve |
892 | .Sp |
1034 | .PP |
893 | Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR as documented in @@RXVT_NAME@@(7). |
1035 | Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. |
894 | .Sp |
1036 | .PP |
895 | For an existing rxvt\-unicode: |
1037 | For an existing rxvt\-unicode: |
896 | .Sp |
1038 | .PP |
897 | .Vb 3 |
1039 | .Vb 3 |
898 | \& # use Backspace = ^H |
1040 | \& # use Backspace = ^H |
899 | \& $ stty erase ^H |
1041 | \& $ stty erase ^H |
900 | \& $ echo -n "^[[36h" |
1042 | \& $ echo -n "^[[36h" |
901 | .Ve |
1043 | .Ve |
902 | .Sp |
1044 | .PP |
903 | .Vb 3 |
1045 | .Vb 3 |
904 | \& # use Backspace = ^? |
1046 | \& # use Backspace = ^? |
905 | \& $ stty erase ^? |
1047 | \& $ stty erase ^? |
906 | \& $ echo -n "^[[36l" |
1048 | \& $ echo -n "^[[36l" |
907 | .Ve |
1049 | .Ve |
908 | .Sp |
1050 | .PP |
909 | This helps satisfy some of the Backspace discrepancies that occur, but |
1051 | This helps satisfy some of the Backspace discrepancies that occur, but |
910 | if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value |
1052 | if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value |
911 | properly reflects that. |
1053 | properly reflects that. |
912 | .Sp |
1054 | .PP |
913 | The Delete key is a another casualty of the ill-defined Backspace problem. |
1055 | The Delete key is a another casualty of the ill-defined Backspace problem. |
914 | To avoid confusion between the Backspace and Delete keys, the Delete |
1056 | To avoid confusion between the Backspace and Delete keys, the Delete |
915 | key has been assigned an escape sequence to match the vt100 for Execute |
1057 | key has been assigned an escape sequence to match the vt100 for Execute |
916 | (\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo. |
1058 | (\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo. |
917 | .Sp |
1059 | .PP |
918 | Some other Backspace problems: |
1060 | Some other Backspace problems: |
919 | .Sp |
1061 | .PP |
920 | some editors use termcap/terminfo, |
1062 | some editors use termcap/terminfo, |
921 | some editors (vim I'm told) expect Backspace = ^H, |
1063 | some editors (vim I'm told) expect Backspace = ^H, |
922 | \&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help. |
1064 | \&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help. |
923 | .Sp |
1065 | .PP |
924 | Perhaps someday this will all be resolved in a consistent manner. |
1066 | Perhaps someday this will all be resolved in a consistent manner. |
925 | .IP "I don't like the key\-bindings. How do I change them?" 4 |
1067 | .Sh "I don't like the key\-bindings. How do I change them?" |
926 | .IX Item "I don't like the key-bindings. How do I change them?" |
1068 | .IX Subsection "I don't like the key-bindings. How do I change them?" |
927 | There are some compile-time selections available via configure. Unless |
1069 | There are some compile-time selections available via configure. Unless |
928 | you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can |
1070 | you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can |
929 | use the `keysym' resource to alter the keystrings associated with keysyms. |
1071 | use the `keysym' resource to alter the keystrings associated with keysyms. |
930 | .Sp |
1072 | .PP |
931 | Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR |
1073 | Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR |
932 | .Sp |
1074 | .PP |
933 | .Vb 20 |
1075 | .Vb 20 |
934 | \& URxvt.keysym.Home: \e033[1~ |
1076 | \& URxvt.keysym.Home: \e033[1~ |
935 | \& URxvt.keysym.End: \e033[4~ |
1077 | \& URxvt.keysym.End: \e033[4~ |
936 | \& URxvt.keysym.C-apostrophe: \e033<C-'> |
1078 | \& URxvt.keysym.C-apostrophe: \e033<C-'> |
937 | \& URxvt.keysym.C-slash: \e033<C-/> |
1079 | \& URxvt.keysym.C-slash: \e033<C-/> |
… | |
… | |
950 | \& URxvt.keysym.M-Right: \e033<M-Right> |
1092 | \& URxvt.keysym.M-Right: \e033<M-Right> |
951 | \& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 > |
1093 | \& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 > |
952 | \& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz > |
1094 | \& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz > |
953 | \& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007 |
1095 | \& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007 |
954 | .Ve |
1096 | .Ve |
955 | .Sp |
1097 | .PP |
956 | See some more examples in the documentation for the \fBkeysym\fR resource. |
1098 | See some more examples in the documentation for the \fBkeysym\fR resource. |
957 | .IP "I'm using keyboard model \s-1XXX\s0 that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize." 4 |
1099 | .Sh "I'm using keyboard model \s-1XXX\s0 that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize." |
958 | .IX Item "I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize." |
1100 | .IX Subsection "I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize." |
959 | .Vb 6 |
1101 | .Vb 6 |
960 | \& KP_Insert == Insert |
1102 | \& KP_Insert == Insert |
961 | \& F22 == Print |
1103 | \& F22 == Print |
962 | \& F27 == Home |
1104 | \& F27 == Home |
963 | \& F29 == Prior |
1105 | \& F29 == Prior |
964 | \& F33 == End |
1106 | \& F33 == End |
965 | \& F35 == Next |
1107 | \& F35 == Next |
966 | .Ve |
1108 | .Ve |
967 | .Sp |
1109 | .PP |
968 | Rather than have rxvt-unicode try to accommodate all the various possible |
1110 | Rather than have rxvt-unicode try to accommodate all the various possible |
969 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
1111 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
970 | required for your particular machine. |
1112 | required for your particular machine. |
971 | .IP "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." 4 |
1113 | .Sh "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
972 | .IX Item "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
1114 | .IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
973 | rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can |
1115 | rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can |
974 | check and see if that is set. Note that several programs, \s-1JED\s0, slrn, |
1116 | check and see if that is set. Note that several programs, \s-1JED\s0, slrn, |
975 | Midnight Commander automatically check this variable to decide whether or |
1117 | Midnight Commander automatically check this variable to decide whether or |
976 | not to use color. |
1118 | not to use color. |
977 | .IP "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?" 4 |
1119 | .Sh "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?" |
978 | .IX Item "How do I set the correct, full IP address for the DISPLAY variable?" |
1120 | .IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?" |
979 | If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled |
1121 | If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled |
980 | insecure mode then it is possible to use the following shell script |
1122 | insecure mode then it is possible to use the following shell script |
981 | snippets to correctly set the display. If your version of rxvt-unicode |
1123 | snippets to correctly set the display. If your version of rxvt-unicode |
982 | wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then |
1124 | wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then |
983 | the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a |
1125 | the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a |
984 | regular xterm. |
1126 | regular xterm. |
985 | .Sp |
1127 | .PP |
986 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
1128 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
987 | snippets: |
1129 | snippets: |
988 | .Sp |
1130 | .PP |
989 | .Vb 12 |
1131 | .Vb 12 |
990 | \& # Bourne/Korn/POSIX family of shells: |
1132 | \& # Bourne/Korn/POSIX family of shells: |
991 | \& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
1133 | \& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
992 | \& if [ ${TERM:-foo} = xterm ]; then |
1134 | \& if [ ${TERM:-foo} = xterm ]; then |
993 | \& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
1135 | \& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
… | |
… | |
998 | \& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
1140 | \& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
999 | \& read DISPLAY # set it in our local shell |
1141 | \& read DISPLAY # set it in our local shell |
1000 | \& fi |
1142 | \& fi |
1001 | \& fi |
1143 | \& fi |
1002 | .Ve |
1144 | .Ve |
1003 | .IP "How do I compile the manual pages for myself?" 4 |
1145 | .Sh "How do I compile the manual pages for myself?" |
1004 | .IX Item "How do I compile the manual pages for myself?" |
1146 | .IX Subsection "How do I compile the manual pages for myself?" |
1005 | You need to have a recent version of perl installed as \fI/usr/bin/perl\fR, |
1147 | You need to have a recent version of perl installed as \fI/usr/bin/perl\fR, |
1006 | one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to |
1148 | one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to |
1007 | the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR. |
1149 | the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR. |
1008 | .IP "My question isn't answered here, can I ask a human?" 4 |
1150 | .Sh "My question isn't answered here, can I ask a human?" |
1009 | .IX Item "My question isn't answered here, can I ask a human?" |
1151 | .IX Subsection "My question isn't answered here, can I ask a human?" |
1010 | Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR, |
1152 | Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR, |
1011 | channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be |
1153 | channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be |
1012 | interested in learning about new and exciting problems (but not FAQs :). |
1154 | interested in learning about new and exciting problems (but not FAQs :). |
1013 | .SH "RXVT TECHNICAL REFERENCE" |
1155 | .SH "RXVT TECHNICAL REFERENCE" |
1014 | .IX Header "RXVT TECHNICAL REFERENCE" |
1156 | .IX Header "RXVT TECHNICAL REFERENCE" |
1015 | .SH "DESCRIPTION" |
1157 | .SH "DESCRIPTION" |
1016 | .IX Header "DESCRIPTION" |
1158 | .IX Header "DESCRIPTION" |
1017 | The rest of this document describes various technical aspects of |
1159 | The rest of this document describes various technical aspects of |
1018 | \&\fBrxvt-unicode\fR. First the description of supported command sequences, |
1160 | \&\fBrxvt-unicode\fR. First the description of supported command sequences, |
1019 | followed by menu and pixmap support and last by a description of all |
1161 | followed by pixmap support and last by a description of all features |
1020 | features selectable at \f(CW\*(C`configure\*(C'\fR time. |
1162 | selectable at \f(CW\*(C`configure\*(C'\fR time. |
1021 | .SH "Definitions" |
1163 | .SH "Definitions" |
1022 | .IX Header "Definitions" |
1164 | .IX Header "Definitions" |
1023 | .ie n .IP "\fB\fB""c""\fB\fR" 4 |
1165 | .ie n .IP "\fB\fB""c""\fB\fR" 4 |
1024 | .el .IP "\fB\f(CBc\fB\fR" 4 |
1166 | .el .IP "\fB\f(CBc\fB\fR" 4 |
1025 | .IX Item "c" |
1167 | .IX Item "c" |
… | |
… | |
1572 | l l . |
1714 | l l . |
1573 | h Send Mouse X & Y on button press. |
1715 | h Send Mouse X & Y on button press. |
1574 | l No mouse reporting. |
1716 | l No mouse reporting. |
1575 | .TE |
1717 | .TE |
1576 | |
1718 | |
1577 | .ie n .IP "\fB\fB""Ps = 10""\fB\fR (\fBrxvt\fR)" 4 |
|
|
1578 | .el .IP "\fB\f(CBPs = 10\fB\fR (\fBrxvt\fR)" 4 |
|
|
1579 | .IX Item "Ps = 10 (rxvt)" |
|
|
1580 | .TS |
|
|
1581 | l l . |
|
|
1582 | h menuBar visible |
|
|
1583 | l menuBar invisible |
|
|
1584 | .TE |
|
|
1585 | |
|
|
1586 | .ie n .IP "\fB\fB""Ps = 25""\fB\fR" 4 |
1719 | .ie n .IP "\fB\fB""Ps = 25""\fB\fR" 4 |
1587 | .el .IP "\fB\f(CBPs = 25\fB\fR" 4 |
1720 | .el .IP "\fB\f(CBPs = 25\fB\fR" 4 |
1588 | .IX Item "Ps = 25" |
1721 | .IX Item "Ps = 25" |
1589 | .TS |
1722 | .TS |
1590 | l l . |
1723 | l l . |
… | |
… | |
1776 | Ps = 12 Change colour of text cursor foreground to Pt |
1909 | Ps = 12 Change colour of text cursor foreground to Pt |
1777 | Ps = 13 Change colour of mouse foreground to Pt |
1910 | Ps = 13 Change colour of mouse foreground to Pt |
1778 | Ps = 17 Change colour of highlight characters to Pt |
1911 | Ps = 17 Change colour of highlight characters to Pt |
1779 | Ps = 18 Change colour of bold characters to Pt [deprecated, see 706] |
1912 | Ps = 18 Change colour of bold characters to Pt [deprecated, see 706] |
1780 | Ps = 19 Change colour of underlined characters to Pt [deprecated, see 707] |
1913 | Ps = 19 Change colour of underlined characters to Pt [deprecated, see 707] |
1781 | Ps = 20 Change default background to Pt |
1914 | Ps = 20 Change background pixmap parameters (see section XPM) (Compile XPM). |
1782 | Ps = 39 Change default foreground colour to Pt. |
1915 | Ps = 39 Change default foreground colour to Pt. |
1783 | Ps = 46 Change Log File to Pt unimplemented |
1916 | Ps = 46 Change Log File to Pt unimplemented |
1784 | Ps = 49 Change default background colour to Pt. |
1917 | Ps = 49 Change default background colour to Pt. |
1785 | Ps = 50 Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n |
1918 | Ps = 50 Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n |
1786 | Ps = 55 Log all scrollback buffer and all of screen to Pt |
1919 | Ps = 55 Log all scrollback buffer and all of screen to Pt |
1787 | Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills). |
1920 | Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills). |
1788 | Ps = 703 Menubar command Pt (Compile menubar). |
1921 | Ps = 702 Request version if Pt is ?, returning rxvt-unicode, the resource name, the major and minor version numbers, e.g. ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST. |
1789 | Ps = 704 Change colour of italic characters to Pt |
1922 | Ps = 704 Change colour of italic characters to Pt |
1790 | Ps = 705 Change background pixmap tint colour to Pt (Compile transparency). |
1923 | Ps = 705 Change background pixmap tint colour to Pt (Compile transparency). |
1791 | Ps = 706 Change colour of bold characters to Pt |
1924 | Ps = 706 Change colour of bold characters to Pt |
1792 | Ps = 707 Change colour of underlined characters to Pt |
1925 | Ps = 707 Change colour of underlined characters to Pt |
1793 | Ps = 710 Set normal fontset to Pt. Same as Ps = 50. |
1926 | Ps = 710 Set normal fontset to Pt. Same as Ps = 50. |
… | |
… | |
1799 | Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl). |
1932 | Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl). |
1800 | .TE |
1933 | .TE |
1801 | |
1934 | |
1802 | .PP |
1935 | .PP |
1803 | |
1936 | |
1804 | .IX Xref "menuBar" |
1937 | .IX Xref "XPM" |
1805 | .SH "menuBar" |
|
|
1806 | .IX Header "menuBar" |
|
|
1807 | \&\fBThe exact syntax used is \f(BIalmost\fB solidified.\fR |
|
|
1808 | In the menus, \fB\s-1DON\s0'T\fR try to use menuBar commands that add or remove a |
|
|
1809 | menuBar. |
|
|
1810 | .PP |
|
|
1811 | Note that in all of the commands, the \fB\f(BI/path/\fB\fR \fIcannot\fR be |
|
|
1812 | omitted: use \fB./\fR to specify a menu relative to the current menu. |
|
|
1813 | .Sh "Overview of menuBar operation" |
|
|
1814 | .IX Subsection "Overview of menuBar operation" |
|
|
1815 | For the menuBar XTerm escape sequence \f(CW\*(C`ESC ] 703 ; Pt ST\*(C'\fR, the syntax |
|
|
1816 | of \f(CW\*(C`Pt\*(C'\fR can be used for a variety of tasks: |
|
|
1817 | .PP |
|
|
1818 | At the top level is the current menuBar which is a member of a circular |
|
|
1819 | linked-list of other such menuBars. |
|
|
1820 | .PP |
|
|
1821 | The menuBar acts as a parent for the various drop-down menus, which in |
|
|
1822 | turn, may have labels, separator lines, menuItems and subMenus. |
|
|
1823 | .PP |
|
|
1824 | The menuItems are the useful bits: you can use them to mimic keyboard |
|
|
1825 | input or even to send text or escape sequences back to rxvt. |
|
|
1826 | .PP |
|
|
1827 | The menuBar syntax is intended to provide a simple yet robust method of |
|
|
1828 | constructing and manipulating menus and navigating through the |
|
|
1829 | menuBars. |
|
|
1830 | .PP |
|
|
1831 | The first step is to use the tag \fB[menu:\f(BIname\fB]\fR which creates |
|
|
1832 | the menuBar called \fIname\fR and allows access. You may now or menus, |
|
|
1833 | subMenus, and menuItems. Finally, use the tag \fB[done]\fR to set the |
|
|
1834 | menuBar access as \fBreadonly\fR to prevent accidental corruption of the |
|
|
1835 | menus. To re-access the current menuBar for alterations, use the tag |
|
|
1836 | \&\fB[menu]\fR, make the alterations and then use \fB[done]\fR |
|
|
1837 | .PP |
|
|
1838 | |
|
|
1839 | .IX Xref "menuBarCommands" |
|
|
1840 | .Sh "Commands" |
|
|
1841 | .IX Subsection "Commands" |
|
|
1842 | .IP "\fB[menu:+\f(BIname\fB]\fR" 4 |
|
|
1843 | .IX Item "[menu:+name]" |
|
|
1844 | access the named menuBar for creation or alteration. If a new menuBar |
|
|
1845 | is created, it is called \fIname\fR (max of 15 chars) and the current |
|
|
1846 | menuBar is pushed onto the stack |
|
|
1847 | .IP "\fB[menu]\fR" 4 |
|
|
1848 | .IX Item "[menu]" |
|
|
1849 | access the current menuBar for alteration |
|
|
1850 | .IP "\fB[title:+\f(BIstring\fB]\fR" 4 |
|
|
1851 | .IX Item "[title:+string]" |
|
|
1852 | set the current menuBar's title to \fIstring\fR, which may contain the |
|
|
1853 | following format specifiers: |
|
|
1854 | .Sp |
|
|
1855 | .Vb 3 |
|
|
1856 | \& B<%n> rxvt name (as per the B<-name> command-line option) |
|
|
1857 | \& B<%v> rxvt version |
|
|
1858 | \& B<%%> literal B<%> character |
|
|
1859 | .Ve |
|
|
1860 | .IP "\fB[done]\fR" 4 |
|
|
1861 | .IX Item "[done]" |
|
|
1862 | set menuBar access as \fBreadonly\fR. |
|
|
1863 | End-of-file tag for \fB[read:+\f(BIfile\fB]\fR operations. |
|
|
1864 | .IP "\fB[read:+\f(BIfile\fB]\fR" 4 |
|
|
1865 | .IX Item "[read:+file]" |
|
|
1866 | read menu commands directly from \fIfile\fR (extension \*(L".menu\*(R" will be |
|
|
1867 | appended if required.) Start reading at a line with \fB[menu]\fR or \fB[menu:+\f(BIname\fB\fR and continuing until \fB[done]\fR is encountered. |
|
|
1868 | .Sp |
|
|
1869 | Blank and comment lines (starting with \fB#\fR) are ignored. Actually, |
|
|
1870 | since any invalid menu commands are also ignored, almost anything could |
|
|
1871 | be construed as a comment line, but this may be tightened up in the |
|
|
1872 | future ... so don't count on it!. |
|
|
1873 | .IP "\fB[read:+\f(BIfile\fB;+\f(BIname\fB]\fR" 4 |
|
|
1874 | .IX Item "[read:+file;+name]" |
|
|
1875 | The same as \fB[read:+\f(BIfile\fB]\fR, but start reading at a line with |
|
|
1876 | \&\fB[menu:+\f(BIname\fB]\fR and continuing until \fB[done:+\f(BIname\fB]\fR or |
|
|
1877 | \&\fB[done]\fR is encountered. |
|
|
1878 | .IP "\fB[dump]\fR" 4 |
|
|
1879 | .IX Item "[dump]" |
|
|
1880 | dump all menuBars to the file \fB/tmp/rxvt\-PID\fR in a format suitable for |
|
|
1881 | later rereading. |
|
|
1882 | .IP "\fB[rm:name]\fR" 4 |
|
|
1883 | .IX Item "[rm:name]" |
|
|
1884 | remove the named menuBar |
|
|
1885 | .IP "\fB[rm] [rm:]\fR" 4 |
|
|
1886 | .IX Item "[rm] [rm:]" |
|
|
1887 | remove the current menuBar |
|
|
1888 | .IP "\fB[rm*] [rm:*]\fR" 4 |
|
|
1889 | .IX Item "[rm*] [rm:*]" |
|
|
1890 | remove all menuBars |
|
|
1891 | .IP "\fB[swap]\fR" 4 |
|
|
1892 | .IX Item "[swap]" |
|
|
1893 | swap the top two menuBars |
|
|
1894 | .IP "\fB[prev]\fR" 4 |
|
|
1895 | .IX Item "[prev]" |
|
|
1896 | access the previous menuBar |
|
|
1897 | .IP "\fB[next]\fR" 4 |
|
|
1898 | .IX Item "[next]" |
|
|
1899 | access the next menuBar |
|
|
1900 | .IP "\fB[show]\fR" 4 |
|
|
1901 | .IX Item "[show]" |
|
|
1902 | Enable display of the menuBar |
|
|
1903 | .IP "\fB[hide]\fR" 4 |
|
|
1904 | .IX Item "[hide]" |
|
|
1905 | Disable display of the menuBar |
|
|
1906 | .IP "\fB[pixmap:+\f(BIname\fB]\fR" 4 |
|
|
1907 | .IX Item "[pixmap:+name]" |
|
|
1908 | .PD 0 |
|
|
1909 | .IP "\fB[pixmap:+\f(BIname\fB;\f(BIscaling\fB]\fR" 4 |
|
|
1910 | .IX Item "[pixmap:+name;scaling]" |
|
|
1911 | .PD |
|
|
1912 | (set the background pixmap globally |
|
|
1913 | .Sp |
|
|
1914 | \&\fBA Future implementation \f(BImay\fB make this local to the menubar\fR) |
|
|
1915 | .IP "\fB[:+\f(BIcommand\fB:]\fR" 4 |
|
|
1916 | .IX Item "[:+command:]" |
|
|
1917 | ignore the menu readonly status and issue a \fIcommand\fR to or a menu or |
|
|
1918 | menuitem or change the ; a useful shortcut for setting the quick arrows |
|
|
1919 | from a menuBar. |
|
|
1920 | .PP |
|
|
1921 | |
|
|
1922 | .IX Xref "menuBarAdd" |
|
|
1923 | .Sh "Adding and accessing menus" |
|
|
1924 | .IX Subsection "Adding and accessing menus" |
|
|
1925 | The following commands may also be \fB+\fR prefixed. |
|
|
1926 | .IP "\fB/+\fR" 4 |
|
|
1927 | .IX Item "/+" |
|
|
1928 | access menuBar top level |
|
|
1929 | .IP "\fB./+\fR" 4 |
|
|
1930 | .IX Item "./+" |
|
|
1931 | access current menu level |
|
|
1932 | .IP "\fB../+\fR" 4 |
|
|
1933 | .IX Item "../+" |
|
|
1934 | access parent menu (1 level up) |
|
|
1935 | .IP "\fB../../\fR" 4 |
|
|
1936 | .IX Item "../../" |
|
|
1937 | access parent menu (multiple levels up) |
|
|
1938 | .IP "\fB\f(BI/path/\fBmenu\fR" 4 |
|
|
1939 | .IX Item "/path/menu" |
|
|
1940 | add/access menu |
|
|
1941 | .IP "\fB\f(BI/path/\fBmenu/*\fR" 4 |
|
|
1942 | .IX Item "/path/menu/*" |
|
|
1943 | add/access menu and clear it if it exists |
|
|
1944 | .IP "\fB\f(BI/path/\fB{\-}\fR" 4 |
|
|
1945 | .IX Item "/path/{-}" |
|
|
1946 | add separator |
|
|
1947 | .IP "\fB\f(BI/path/\fB{item}\fR" 4 |
|
|
1948 | .IX Item "/path/{item}" |
|
|
1949 | add \fBitem\fR as a label |
|
|
1950 | .IP "\fB\f(BI/path/\fB{item} action\fR" 4 |
|
|
1951 | .IX Item "/path/{item} action" |
|
|
1952 | add/alter \fImenuitem\fR with an associated \fIaction\fR |
|
|
1953 | .IP "\fB\f(BI/path/\fB{item}{right\-text}\fR" 4 |
|
|
1954 | .IX Item "/path/{item}{right-text}" |
|
|
1955 | add/alter \fImenuitem\fR with \fBright-text\fR as the right-justified text |
|
|
1956 | and as the associated \fIaction\fR |
|
|
1957 | .IP "\fB\f(BI/path/\fB{item}{rtext} action\fR" 4 |
|
|
1958 | .IX Item "/path/{item}{rtext} action" |
|
|
1959 | add/alter \fImenuitem\fR with an associated \fIaction\fR and with \fBrtext\fR as |
|
|
1960 | the right-justified text. |
|
|
1961 | .IP "Special characters in \fIaction\fR must be backslash\-escaped:" 4 |
|
|
1962 | .IX Item "Special characters in action must be backslash-escaped:" |
|
|
1963 | \&\fB\ea \eb \eE \ee \en \er \et \eoctal\fR |
|
|
1964 | .IP "or in control-character notation:" 4 |
|
|
1965 | .IX Item "or in control-character notation:" |
|
|
1966 | \&\fB^@, ^A .. ^Z .. ^_, ^?\fR |
|
|
1967 | .PP |
|
|
1968 | To send a string starting with a \fB\s-1NUL\s0\fR (\fB^@\fR) character to the |
|
|
1969 | program, start \fIaction\fR with a pair of \fB\s-1NUL\s0\fR characters (\fB^@^@\fR), |
|
|
1970 | the first of which will be stripped off and the balance directed to the |
|
|
1971 | program. Otherwise if \fIaction\fR begins with \fB\s-1NUL\s0\fR followed by |
|
|
1972 | non\-+\fB\s-1NUL\s0\fR characters, the leading \fB\s-1NUL\s0\fR is stripped off and the |
|
|
1973 | balance is sent back to rxvt. |
|
|
1974 | .PP |
|
|
1975 | As a convenience for the many Emacs-type editors, \fIaction\fR may start |
|
|
1976 | with \fBM\-\fR (eg, \fBM\-$\fR is equivalent to \fB\eE$\fR) and a \fB\s-1CR\s0\fR will be |
|
|
1977 | appended if missed from \fBM\-x\fR commands. |
|
|
1978 | .PP |
|
|
1979 | As a convenience for issuing XTerm \fB\s-1ESC\s0 ]\fR sequences from a menubar (or |
|
|
1980 | quick arrow), a \fB\s-1BEL\s0\fR (\fB^G\fR) will be appended if needed. |
|
|
1981 | .IP "For example," 4 |
|
|
1982 | .IX Item "For example," |
|
|
1983 | \&\fBM\-xapropos\fR is equivalent to \fB\eExapropos\er\fR |
|
|
1984 | .IP "and" 4 |
|
|
1985 | .IX Item "and" |
|
|
1986 | \&\fB\eE]703;mona;100\fR is equivalent to \fB\eE]703;mona;100\ea\fR |
|
|
1987 | .PP |
|
|
1988 | The option \fB{\f(BIright-rtext\fB}\fR will be right\-justified. In the |
|
|
1989 | absence of a specified action, this text will be used as the \fIaction\fR |
|
|
1990 | as well. |
|
|
1991 | .IP "For example," 4 |
|
|
1992 | .IX Item "For example," |
|
|
1993 | \&\fB/File/{Open}{^X^F}\fR is equivalent to \fB/File/{Open}{^X^F} ^X^F\fR |
|
|
1994 | .PP |
|
|
1995 | The left label \fIis\fR necessary, since it's used for matching, but |
|
|
1996 | implicitly hiding the left label (by using same name for both left and |
|
|
1997 | right labels), or explicitly hiding the left label (by preceeding it |
|
|
1998 | with a dot), makes it possible to have right-justified text only. |
|
|
1999 | .IP "For example," 4 |
|
|
2000 | .IX Item "For example," |
|
|
2001 | \&\fB/File/{Open}{Open} Open-File-Action\fR |
|
|
2002 | .IP "or hiding it" 4 |
|
|
2003 | .IX Item "or hiding it" |
|
|
2004 | \&\fB/File/{.anylabel}{Open} Open-File-Action\fR |
|
|
2005 | .PP |
|
|
2006 | |
|
|
2007 | .IX Xref "menuBarRemove" |
|
|
2008 | .Sh "Removing menus" |
|
|
2009 | .IX Subsection "Removing menus" |
|
|
2010 | .IP "\fB\-/*+\fR" 4 |
|
|
2011 | .IX Item "-/*+" |
|
|
2012 | remove all menus from the menuBar, the same as \fB[clear]\fR |
|
|
2013 | .IP "\fB\-+\f(BI/path\fBmenu+\fR" 4 |
|
|
2014 | .IX Item "-+/pathmenu+" |
|
|
2015 | remove menu |
|
|
2016 | .IP "\fB\-+\f(BI/path\fB{item}+\fR" 4 |
|
|
2017 | .IX Item "-+/path{item}+" |
|
|
2018 | remove item |
|
|
2019 | .IP "\fB\-+\f(BI/path\fB{\-}\fR" 4 |
|
|
2020 | .IX Item "-+/path{-}" |
|
|
2021 | remove separator) |
|
|
2022 | .IP "\fB\-/path/menu/*\fR" 4 |
|
|
2023 | .IX Item "-/path/menu/*" |
|
|
2024 | remove all items, separators and submenus from menu |
|
|
2025 | .PP |
|
|
2026 | |
|
|
2027 | .IX Xref "menuBarArrows" |
|
|
2028 | .Sh "Quick Arrows" |
|
|
2029 | .IX Subsection "Quick Arrows" |
|
|
2030 | The menus also provide a hook for \fIquick arrows\fR to provide easier |
|
|
2031 | user access. If nothing has been explicitly set, the default is to |
|
|
2032 | emulate the curror keys. The syntax permits each arrow to be altered |
|
|
2033 | individually or all four at once without re-entering their common |
|
|
2034 | beginning/end text. For example, to explicitly associate cursor actions |
|
|
2035 | with the arrows, any of the following forms could be used: |
|
|
2036 | .IP "\fB<r>+\f(BIRight\fB\fR" 4 |
|
|
2037 | .IX Item "<r>+Right" |
|
|
2038 | .PD 0 |
|
|
2039 | .IP "\fB<l>+\f(BILeft\fB\fR" 4 |
|
|
2040 | .IX Item "<l>+Left" |
|
|
2041 | .IP "\fB<u>+\f(BIUp\fB\fR" 4 |
|
|
2042 | .IX Item "<u>+Up" |
|
|
2043 | .IP "\fB<d>+\f(BIDown\fB\fR" 4 |
|
|
2044 | .IX Item "<d>+Down" |
|
|
2045 | .PD |
|
|
2046 | Define actions for the respective arrow buttons |
|
|
2047 | .IP "\fB<b>+\f(BIBegin\fB\fR" 4 |
|
|
2048 | .IX Item "<b>+Begin" |
|
|
2049 | .PD 0 |
|
|
2050 | .IP "\fB<e>+\f(BIEnd\fB\fR" 4 |
|
|
2051 | .IX Item "<e>+End" |
|
|
2052 | .PD |
|
|
2053 | Define common beginning/end parts for \fIquick arrows\fR which used in |
|
|
2054 | conjunction with the above <r> <l> <u> <d> constructs |
|
|
2055 | .IP "For example, define arrows individually," 4 |
|
|
2056 | .IX Item "For example, define arrows individually," |
|
|
2057 | .Vb 1 |
|
|
2058 | \& <u>\eE[A |
|
|
2059 | .Ve |
|
|
2060 | .Sp |
|
|
2061 | .Vb 1 |
|
|
2062 | \& <d>\eE[B |
|
|
2063 | .Ve |
|
|
2064 | .Sp |
|
|
2065 | .Vb 1 |
|
|
2066 | \& <r>\eE[C |
|
|
2067 | .Ve |
|
|
2068 | .Sp |
|
|
2069 | .Vb 1 |
|
|
2070 | \& <l>\eE[D |
|
|
2071 | .Ve |
|
|
2072 | .IP "or all at once" 4 |
|
|
2073 | .IX Item "or all at once" |
|
|
2074 | .Vb 1 |
|
|
2075 | \& <u>\eE[AZ<><d>\eE[BZ<><r>\eE[CZ<><l>\eE[D |
|
|
2076 | .Ve |
|
|
2077 | .IP "or more compactly (factoring out common parts)" 4 |
|
|
2078 | .IX Item "or more compactly (factoring out common parts)" |
|
|
2079 | .Vb 1 |
|
|
2080 | \& <b>\eE[<u>AZ<><d>BZ<><r>CZ<><l>D |
|
|
2081 | .Ve |
|
|
2082 | .PP |
|
|
2083 | |
|
|
2084 | .IX Xref "menuBarSummary" |
|
|
2085 | .Sh "Command Summary" |
|
|
2086 | .IX Subsection "Command Summary" |
|
|
2087 | A short summary of the most \fIcommon\fR commands: |
|
|
2088 | .IP "[menu:name]" 4 |
|
|
2089 | .IX Item "[menu:name]" |
|
|
2090 | use an existing named menuBar or start a new one |
|
|
2091 | .IP "[menu]" 4 |
|
|
2092 | .IX Item "[menu]" |
|
|
2093 | use the current menuBar |
|
|
2094 | .IP "[title:string]" 4 |
|
|
2095 | .IX Item "[title:string]" |
|
|
2096 | set menuBar title |
|
|
2097 | .IP "[done]" 4 |
|
|
2098 | .IX Item "[done]" |
|
|
2099 | set menu access to readonly and, if reading from a file, signal \s-1EOF\s0 |
|
|
2100 | .IP "[done:name]" 4 |
|
|
2101 | .IX Item "[done:name]" |
|
|
2102 | if reading from a file using [read:file;name] signal \s-1EOF\s0 |
|
|
2103 | .IP "[rm:name]" 4 |
|
|
2104 | .IX Item "[rm:name]" |
|
|
2105 | remove named menuBar(s) |
|
|
2106 | .IP "[rm] [rm:]" 4 |
|
|
2107 | .IX Item "[rm] [rm:]" |
|
|
2108 | remove current menuBar |
|
|
2109 | .IP "[rm*] [rm:*]" 4 |
|
|
2110 | .IX Item "[rm*] [rm:*]" |
|
|
2111 | remove all menuBar(s) |
|
|
2112 | .IP "[swap]" 4 |
|
|
2113 | .IX Item "[swap]" |
|
|
2114 | swap top two menuBars |
|
|
2115 | .IP "[prev]" 4 |
|
|
2116 | .IX Item "[prev]" |
|
|
2117 | access the previous menuBar |
|
|
2118 | .IP "[next]" 4 |
|
|
2119 | .IX Item "[next]" |
|
|
2120 | access the next menuBar |
|
|
2121 | .IP "[show]" 4 |
|
|
2122 | .IX Item "[show]" |
|
|
2123 | map menuBar |
|
|
2124 | .IP "[hide]" 4 |
|
|
2125 | .IX Item "[hide]" |
|
|
2126 | unmap menuBar |
|
|
2127 | .IP "[pixmap;file]" 4 |
|
|
2128 | .IX Item "[pixmap;file]" |
|
|
2129 | .PD 0 |
|
|
2130 | .IP "[pixmap;file;scaling]" 4 |
|
|
2131 | .IX Item "[pixmap;file;scaling]" |
|
|
2132 | .PD |
|
|
2133 | set a background pixmap |
|
|
2134 | .IP "[read:file]" 4 |
|
|
2135 | .IX Item "[read:file]" |
|
|
2136 | .PD 0 |
|
|
2137 | .IP "[read:file;name]" 4 |
|
|
2138 | .IX Item "[read:file;name]" |
|
|
2139 | .PD |
|
|
2140 | read in a menu from a file |
|
|
2141 | .IP "[dump]" 4 |
|
|
2142 | .IX Item "[dump]" |
|
|
2143 | dump out all menuBars to /tmp/rxvt\-PID |
|
|
2144 | .IP "/" 4 |
|
|
2145 | access menuBar top level |
|
|
2146 | .IP "./" 4 |
|
|
2147 | .PD 0 |
|
|
2148 | .IP "../" 4 |
|
|
2149 | .IP "../../" 4 |
|
|
2150 | .PD |
|
|
2151 | access current or parent menu level |
|
|
2152 | .IP "/path/menu" 4 |
|
|
2153 | .IX Item "/path/menu" |
|
|
2154 | add/access menu |
|
|
2155 | .IP "/path/{\-}" 4 |
|
|
2156 | .IX Item "/path/{-}" |
|
|
2157 | add separator |
|
|
2158 | .IP "/path/{item}{rtext} action" 4 |
|
|
2159 | .IX Item "/path/{item}{rtext} action" |
|
|
2160 | add/alter menu item |
|
|
2161 | .IP "\-/*" 4 |
|
|
2162 | remove all menus from the menuBar |
|
|
2163 | .IP "\-/path/menu" 4 |
|
|
2164 | .IX Item "-/path/menu" |
|
|
2165 | remove menu items, separators and submenus from menu |
|
|
2166 | .IP "\-/path/menu" 4 |
|
|
2167 | .IX Item "-/path/menu" |
|
|
2168 | remove menu |
|
|
2169 | .IP "\-/path/{item}" 4 |
|
|
2170 | .IX Item "-/path/{item}" |
|
|
2171 | remove item |
|
|
2172 | .IP "\-/path/{\-}" 4 |
|
|
2173 | .IX Item "-/path/{-}" |
|
|
2174 | remove separator |
|
|
2175 | .IP "<b>Begin<r>Right<l>Left<u>Up<d>Down<e>End" 4 |
|
|
2176 | .IX Item "<b>Begin<r>Right<l>Left<u>Up<d>Down<e>End" |
|
|
2177 | menu quick arrows |
|
|
2178 | .SH "XPM" |
1938 | .SH "XPM" |
2179 | .IX Header "XPM" |
1939 | .IX Header "XPM" |
2180 | For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value |
1940 | For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value |
2181 | of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a |
1941 | of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a |
2182 | sequence of scaling/positioning commands separated by semi\-colons. The |
1942 | sequence of scaling/positioning commands separated by semi\-colons. The |
… | |
… | |
2384 | Add support for \s-1XIM\s0 (X Input Method) protocol. This allows using |
2144 | Add support for \s-1XIM\s0 (X Input Method) protocol. This allows using |
2385 | alternative input methods (e.g. kinput2) and will also correctly |
2145 | alternative input methods (e.g. kinput2) and will also correctly |
2386 | set up the input for people using dead keys or compose keys. |
2146 | set up the input for people using dead keys or compose keys. |
2387 | .IP "\-\-enable\-unicode3 (default: off)" 4 |
2147 | .IP "\-\-enable\-unicode3 (default: off)" 4 |
2388 | .IX Item "--enable-unicode3 (default: off)" |
2148 | .IX Item "--enable-unicode3 (default: off)" |
|
|
2149 | Recommended to stay off unless you really need non-BMP characters. |
|
|
2150 | .Sp |
2389 | Enable direct support for displaying unicode codepoints above |
2151 | Enable direct support for displaying unicode codepoints above |
2390 | 65535 (the basic multilingual page). This increases storage |
2152 | 65535 (the basic multilingual page). This increases storage |
2391 | requirements per character from 2 to 4 bytes. X11 fonts do not yet |
2153 | requirements per character from 2 to 4 bytes. X11 fonts do not yet |
2392 | support these extra characters, but Xft does. |
2154 | support these extra characters, but Xft does. |
2393 | .Sp |
2155 | .Sp |
… | |
… | |
2402 | composite characters. This is required for proper viewing of text |
2164 | composite characters. This is required for proper viewing of text |
2403 | where accents are encoded as seperate unicode characters. This is |
2165 | where accents are encoded as seperate unicode characters. This is |
2404 | done by using precomposited characters when available or creating |
2166 | done by using precomposited characters when available or creating |
2405 | new pseudo-characters when no precomposed form exists. |
2167 | new pseudo-characters when no precomposed form exists. |
2406 | .Sp |
2168 | .Sp |
2407 | Without \-\-enable\-unicode3, the number of additional precomposed characters |
2169 | Without \-\-enable\-unicode3, the number of additional precomposed |
2408 | is rather limited (2048, if this is full, rxvt-unicode will use the |
2170 | characters is somewhat limited (the 6400 private use characters will be |
2409 | private use area, extending the number of combinations to 8448). With |
|
|
2410 | \&\-\-enable\-unicode3, no practical limit exists. |
2171 | (ab\-)used). With \-\-enable\-unicode3, no practical limit exists. |
2411 | .Sp |
2172 | .Sp |
2412 | This option will also enable storage (but not display) of characters |
2173 | This option will also enable storage (but not display) of characters |
2413 | beyond plane 0 (>65535) when \-\-enable\-unicode3 was not specified. |
2174 | beyond plane 0 (>65535) when \-\-enable\-unicode3 was not specified. |
2414 | .Sp |
2175 | .Sp |
2415 | The combining table also contains entries for arabic presentation forms, |
2176 | The combining table also contains entries for arabic presentation forms, |
2416 | but these are not currently used. Bug me if you want these to be used (and |
2177 | but these are not currently used. Bug me if you want these to be used (and |
2417 | tell me how these are to be used...). |
2178 | tell me how these are to be used...). |
2418 | .IP "\-\-enable\-fallback(=CLASS) (default: Rxvt)" 4 |
2179 | .IP "\-\-enable\-fallback(=CLASS) (default: Rxvt)" 4 |
2419 | .IX Item "--enable-fallback(=CLASS) (default: Rxvt)" |
2180 | .IX Item "--enable-fallback(=CLASS) (default: Rxvt)" |
2420 | When reading resource settings, also read settings for class \s-1CLASS\s0. To disable resource fallback use \-\-disable\-fallback. |
2181 | When reading resource settings, also read settings for class \s-1CLASS\s0. To |
|
|
2182 | disable resource fallback use \-\-disable\-fallback. |
2421 | .IP "\-\-with\-res\-name=NAME (default: urxvt)" 4 |
2183 | .IP "\-\-with\-res\-name=NAME (default: urxvt)" 4 |
2422 | .IX Item "--with-res-name=NAME (default: urxvt)" |
2184 | .IX Item "--with-res-name=NAME (default: urxvt)" |
2423 | Use the given name as default application name when |
2185 | Use the given name as default application name when |
2424 | reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt. |
2186 | reading resources. Specify \-\-with\-res\-name=rxvt to replace rxvt. |
2425 | .IP "\-\-with\-res\-class=CLASS /default: URxvt)" 4 |
2187 | .IP "\-\-with\-res\-class=CLASS /default: URxvt)" 4 |
… | |
… | |
2452 | .IX Item "--enable-fading (default: on)" |
2214 | .IX Item "--enable-fading (default: on)" |
2453 | Add support for fading the text when focus is lost (requires \f(CW\*(C`\-\-enable\-transparency\*(C'\fR). |
2215 | Add support for fading the text when focus is lost (requires \f(CW\*(C`\-\-enable\-transparency\*(C'\fR). |
2454 | .IP "\-\-enable\-tinting (default: on)" 4 |
2216 | .IP "\-\-enable\-tinting (default: on)" 4 |
2455 | .IX Item "--enable-tinting (default: on)" |
2217 | .IX Item "--enable-tinting (default: on)" |
2456 | Add support for tinting of transparent backgrounds (requires \f(CW\*(C`\-\-enable\-transparency\*(C'\fR). |
2218 | Add support for tinting of transparent backgrounds (requires \f(CW\*(C`\-\-enable\-transparency\*(C'\fR). |
2457 | .IP "\-\-enable\-menubar (default: off) [\s-1DEPRECATED\s0]" 4 |
|
|
2458 | .IX Item "--enable-menubar (default: off) [DEPRECATED]" |
|
|
2459 | Add support for our menu bar system (this interacts badly with dynamic |
|
|
2460 | locale switching currently). This option is \s-1DEPRECATED\s0 and will be removed |
|
|
2461 | in the future. |
|
|
2462 | .IP "\-\-enable\-rxvt\-scroll (default: on)" 4 |
2219 | .IP "\-\-enable\-rxvt\-scroll (default: on)" 4 |
2463 | .IX Item "--enable-rxvt-scroll (default: on)" |
2220 | .IX Item "--enable-rxvt-scroll (default: on)" |
2464 | Add support for the original rxvt scrollbar. |
2221 | Add support for the original rxvt scrollbar. |
2465 | .IP "\-\-enable\-next\-scroll (default: on)" 4 |
2222 | .IP "\-\-enable\-next\-scroll (default: on)" 4 |
2466 | .IX Item "--enable-next-scroll (default: on)" |
2223 | .IX Item "--enable-next-scroll (default: on)" |
… | |
… | |
2471 | .IP "\-\-enable\-plain\-scroll (default: on)" 4 |
2228 | .IP "\-\-enable\-plain\-scroll (default: on)" 4 |
2472 | .IX Item "--enable-plain-scroll (default: on)" |
2229 | .IX Item "--enable-plain-scroll (default: on)" |
2473 | Add support for a very unobtrusive, plain-looking scrollbar that |
2230 | Add support for a very unobtrusive, plain-looking scrollbar that |
2474 | is the favourite of the rxvt-unicode author, having used it for |
2231 | is the favourite of the rxvt-unicode author, having used it for |
2475 | many years. |
2232 | many years. |
2476 | .IP "\-\-enable\-half\-shadow (default: off)" 4 |
|
|
2477 | .IX Item "--enable-half-shadow (default: off)" |
|
|
2478 | Make shadows on the scrollbar only half the normal width & height. |
|
|
2479 | only applicable to rxvt scrollbars. |
|
|
2480 | .IP "\-\-enable\-ttygid (default: off)" 4 |
2233 | .IP "\-\-enable\-ttygid (default: off)" 4 |
2481 | .IX Item "--enable-ttygid (default: off)" |
2234 | .IX Item "--enable-ttygid (default: off)" |
2482 | Change tty device setting to group \*(L"tty\*(R" \- only use this if |
2235 | Change tty device setting to group \*(L"tty\*(R" \- only use this if |
2483 | your system uses this type of security. |
2236 | your system uses this type of security. |
2484 | .IP "\-\-disable\-backspace\-key" 4 |
2237 | .IP "\-\-disable\-backspace\-key" 4 |
… | |
… | |
2489 | Removes any handling of the delete key by us \- let the X server |
2242 | Removes any handling of the delete key by us \- let the X server |
2490 | do it. |
2243 | do it. |
2491 | .IP "\-\-disable\-resources" 4 |
2244 | .IP "\-\-disable\-resources" 4 |
2492 | .IX Item "--disable-resources" |
2245 | .IX Item "--disable-resources" |
2493 | Removes any support for resource checking. |
2246 | Removes any support for resource checking. |
2494 | .IP "\-\-enable\-strings (default: off)" 4 |
|
|
2495 | .IX Item "--enable-strings (default: off)" |
|
|
2496 | Add support for our possibly faster \fImemset()\fR function and other |
|
|
2497 | various routines, overriding your system's versions which may |
|
|
2498 | have been hand-crafted in assembly or may require extra libraries |
|
|
2499 | to link in. (this breaks ANSI-C rules and has problems on many |
|
|
2500 | GNU/Linux systems). |
|
|
2501 | .IP "\-\-disable\-swapscreen" 4 |
2247 | .IP "\-\-disable\-swapscreen" 4 |
2502 | .IX Item "--disable-swapscreen" |
2248 | .IX Item "--disable-swapscreen" |
2503 | Remove support for secondary/swap screen. |
2249 | Remove support for secondary/swap screen. |
2504 | .IP "\-\-enable\-frills (default: on)" 4 |
2250 | .IP "\-\-enable\-frills (default: on)" 4 |
2505 | .IX Item "--enable-frills (default: on)" |
2251 | .IX Item "--enable-frills (default: on)" |
… | |
… | |
2508 | disable this. |
2254 | disable this. |
2509 | .Sp |
2255 | .Sp |
2510 | A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly |
2256 | A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly |
2511 | in combination with other switches) is: |
2257 | in combination with other switches) is: |
2512 | .Sp |
2258 | .Sp |
2513 | .Vb 17 |
2259 | .Vb 15 |
2514 | \& MWM-hints |
2260 | \& MWM-hints |
2515 | \& EWMH-hints (pid, utf8 names) and protocols (ping) |
2261 | \& EWMH-hints (pid, utf8 names) and protocols (ping) |
2516 | \& seperate underline colour (-underlineColor) |
2262 | \& seperate underline colour (-underlineColor) |
2517 | \& settable border widths and borderless switch (-w, -b, -bl) |
2263 | \& settable border widths and borderless switch (-w, -b, -bl) |
|
|
2264 | \& visual depth selection (-depth) |
2518 | \& settable extra linespacing /-lsp) |
2265 | \& settable extra linespacing /-lsp) |
2519 | \& iso-14755-2 and -3, and visual feedback |
2266 | \& iso-14755-2 and -3, and visual feedback |
2520 | \& backindex and forwardindex escape sequence |
|
|
2521 | \& window op and some xterm/OSC escape sequences |
|
|
2522 | \& tripleclickwords (-tcw) |
2267 | \& tripleclickwords (-tcw) |
2523 | \& settable insecure mode (-insecure) |
2268 | \& settable insecure mode (-insecure) |
2524 | \& keysym remapping support |
2269 | \& keysym remapping support |
2525 | \& cursor blinking and underline cursor (-cb, -uc) |
2270 | \& cursor blinking and underline cursor (-cb, -uc) |
2526 | \& XEmbed support (-embed) |
2271 | \& XEmbed support (-embed) |
2527 | \& user-pty (-pty-fd) |
2272 | \& user-pty (-pty-fd) |
2528 | \& hold on exit (-hold) |
2273 | \& hold on exit (-hold) |
2529 | \& skip builtin block graphics (-sbg) |
2274 | \& skip builtin block graphics (-sbg) |
|
|
2275 | .Ve |
|
|
2276 | .Sp |
|
|
2277 | It also enabled some non-essential features otherwise disabled, such as: |
|
|
2278 | .Sp |
|
|
2279 | .Vb 11 |
|
|
2280 | \& some round-trip time optimisations |
|
|
2281 | \& nearest color allocation on pseudocolor screens |
|
|
2282 | \& UTF8_STRING supporr for selection |
2530 | \& sgr modes 90..97 and 100..107 |
2283 | \& sgr modes 90..97 and 100..107 |
|
|
2284 | \& backindex and forwardindex escape sequences |
|
|
2285 | \& view change/zero scorllback esacpe sequences |
|
|
2286 | \& locale switching escape sequence |
|
|
2287 | \& window op and some xterm/OSC escape sequences |
|
|
2288 | \& rectangular selections |
|
|
2289 | \& trailing space removal for selections |
|
|
2290 | \& verbose X error handling |
2531 | .Ve |
2291 | .Ve |
2532 | .IP "\-\-enable\-iso14755 (default: on)" 4 |
2292 | .IP "\-\-enable\-iso14755 (default: on)" 4 |
2533 | .IX Item "--enable-iso14755 (default: on)" |
2293 | .IX Item "--enable-iso14755 (default: on)" |
2534 | Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or |
2294 | Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or |
2535 | \&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by |
2295 | \&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by |
… | |
… | |
2569 | keys. This should keep the window corner which is closest to a corner of |
2329 | keys. This should keep the window corner which is closest to a corner of |
2570 | the screen in a fixed position. |
2330 | the screen in a fixed position. |
2571 | .IP "\-\-enable\-pointer\-blank (default: on)" 4 |
2331 | .IP "\-\-enable\-pointer\-blank (default: on)" 4 |
2572 | .IX Item "--enable-pointer-blank (default: on)" |
2332 | .IX Item "--enable-pointer-blank (default: on)" |
2573 | Add support to have the pointer disappear when typing or inactive. |
2333 | Add support to have the pointer disappear when typing or inactive. |
2574 | .IP "\-\-enable\-perl (default: off)" 4 |
2334 | .IP "\-\-enable\-perl (default: on)" 4 |
2575 | .IX Item "--enable-perl (default: off)" |
2335 | .IX Item "--enable-perl (default: on)" |
2576 | Enable an embedded perl interpreter. See the \fB@@RXVT_NAME@@\f(BIperl\fB\|(3)\fR |
2336 | Enable an embedded perl interpreter. See the \fB@@RXVT_NAME@@\f(BIperl\fB\|(3)\fR |
2577 | manpage (\fIdoc/rxvtperl.txt\fR) for more info on this feature, or the files |
2337 | manpage (\fIdoc/rxvtperl.txt\fR) for more info on this feature, or the files |
2578 | in \fIsrc/perl\-ext/\fR for the extensions that are installed by default. The |
2338 | in \fIsrc/perl\-ext/\fR for the extensions that are installed by default. The |
2579 | perl interpreter that is used can be specified via the \f(CW\*(C`PERL\*(C'\fR environment |
2339 | perl interpreter that is used can be specified via the \f(CW\*(C`PERL\*(C'\fR environment |
2580 | variable when running configure. |
2340 | variable when running configure. |