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