1 | .\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14 |
1 | .\" Automatically generated by Pod::Man 2.09 (Pod::Simple 3.04) |
2 | .\" |
2 | .\" |
3 | .\" Standard preamble: |
3 | .\" Standard preamble: |
4 | .\" ======================================================================== |
4 | .\" ======================================================================== |
5 | .de Sh \" Subsection heading |
5 | .de Sh \" Subsection heading |
6 | .br |
6 | .br |
… | |
… | |
126 | . ds Ae AE |
126 | . ds Ae AE |
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_NAME@@ 7" |
132 | .TH rxvt 7 "2006-01-30" "7.4" "RXVT-UNICODE" |
132 | .TH @@RXVT_NAME@@ 7 "2006-07-17" "7.8" "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 |
138 | \& # set a new font set |
138 | \& # set a new font set |
139 | \& printf '\e33]50;%s\e007' 9x15,xft:Kochi" Mincho" |
139 | \& printf '\e33]50;%s\e007' 9x15,xft:Kochi" Mincho" |
140 | .Ve |
140 | \& |
141 | .PP |
|
|
142 | .Vb 2 |
|
|
143 | \& # change the locale and tell rxvt-unicode about it |
141 | \& # change the locale and tell rxvt\-unicode about it |
144 | \& export LC_CTYPE=ja_JP.EUC-JP; printf "\e33]701;$LC_CTYPE\e007" |
142 | \& export LC_CTYPE=ja_JP.EUC\-JP; printf "\e33]701;$LC_CTYPE\e007" |
145 | .Ve |
143 | \& |
146 | .PP |
|
|
147 | .Vb 2 |
|
|
148 | \& # set window title |
144 | \& # set window title |
149 | \& printf '\e33]2;%s\e007' "new window title" |
145 | \& printf '\e33]2;%s\e007' "new window title" |
150 | .Ve |
146 | .Ve |
151 | .SH "DESCRIPTION" |
147 | .SH "DESCRIPTION" |
152 | .IX Header "DESCRIPTION" |
148 | .IX Header "DESCRIPTION" |
153 | This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting |
149 | 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. |
150 | all escape sequences, and other background information. |
155 | .PP |
151 | .PP |
156 | The newest version of this document is |
152 | The newest version of this document is also available on the World Wide Web at |
157 | also available on the World Wide Web at |
|
|
158 | <http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>. |
153 | <http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>. |
159 | .SH "FREQUENTLY ASKED QUESTIONS" |
154 | .SH "RXVT\-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS" |
160 | .IX Header "FREQUENTLY ASKED QUESTIONS" |
155 | .IX Header "RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS" |
161 | .IP "The new selection selects pieces that are too big, how can I select single words?" 4 |
156 | .Sh "Meta, Features & Commandline Issues" |
162 | .IX Item "The new selection selects pieces that are too big, how can I select single words?" |
157 | .IX Subsection "Meta, Features & Commandline Issues" |
163 | Yes. For example, if you want to select alphanumeric words, you can use |
158 | \fIMy question isn't answered here, can I ask a human?\fR |
164 | the following resource: |
159 | .IX Subsection "My question isn't answered here, can I ask a human?" |
165 | .Sp |
160 | .PP |
|
|
161 | Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR, |
|
|
162 | channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be |
|
|
163 | interested in learning about new and exciting problems (but not FAQs :). |
|
|
164 | .PP |
|
|
165 | \fIDoes it support tabs, can I have a tabbed rxvt\-unicode?\fR |
|
|
166 | .IX Subsection "Does it support tabs, can I have a tabbed rxvt-unicode?" |
|
|
167 | .PP |
|
|
168 | Beginning with version 7.3, there is a perl extension that implements a |
|
|
169 | simple tabbed terminal. It is installed by default, so any of these should |
|
|
170 | give you tabs: |
|
|
171 | .PP |
166 | .Vb 1 |
172 | .Vb 1 |
167 | \& URxvt.selection.pattern-0: ([[:word:]]+) |
173 | \& @@URXVT_NAME@@ \-pe tabbed |
|
|
174 | \& |
|
|
175 | \& URxvt.perl\-ext\-common: default,tabbed |
168 | .Ve |
176 | .Ve |
169 | .Sp |
177 | .PP |
170 | If you click more than twice, the selection will be extended |
178 | It will also work fine with tabbing functionality of many window managers |
171 | more and more. |
179 | or similar tabbing programs, and its embedding-features allow it to be |
172 | .Sp |
180 | embedded into other programs, as witnessed by \fIdoc/rxvt\-tabbed\fR or |
173 | To get a selection that is very similar to the old code, try this pattern: |
181 | the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl module, which features a tabbed urxvt |
174 | .Sp |
182 | (murxvt) terminal as an example embedding application. |
|
|
183 | .PP |
|
|
184 | \fIHow do I know which rxvt-unicode version I'm using?\fR |
|
|
185 | .IX Subsection "How do I know which rxvt-unicode version I'm using?" |
|
|
186 | .PP |
|
|
187 | The version number is displayed with the usage (\-h). Also the escape |
|
|
188 | sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When |
|
|
189 | using the @@URXVT_NAME@@c client, the version displayed is that of the |
|
|
190 | daemon. |
|
|
191 | .PP |
|
|
192 | \fIRxvt-unicode uses gobs of memory, how can I reduce that?\fR |
|
|
193 | .IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
|
|
194 | .PP |
|
|
195 | Rxvt-unicode tries to obey the rule of not charging you for something you |
|
|
196 | don't use. One thing you should try is to configure out all settings that |
|
|
197 | you don't need, for example, Xft support is a resource hog by design, |
|
|
198 | when used. Compiling it out ensures that no Xft font will be loaded |
|
|
199 | accidentally when rxvt-unicode tries to find a font for your characters. |
|
|
200 | .PP |
|
|
201 | Also, many people (me included) like large windows and even larger |
|
|
202 | scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use |
|
|
203 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
|
|
204 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
|
|
205 | use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as |
|
|
206 | rxvt-unicode then uses 8 bytes per screen cell. |
|
|
207 | .PP |
|
|
208 | \fIHow can I start @@URXVT_NAME@@d in a race-free way?\fR |
|
|
209 | .IX Subsection "How can I start @@URXVT_NAME@@d in a race-free way?" |
|
|
210 | .PP |
|
|
211 | Try \f(CW\*(C`@@URXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@URXVT_NAME@@d to open the |
|
|
212 | display, create the listening socket and then fork. |
|
|
213 | .PP |
|
|
214 | \fIHow can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?\fR |
|
|
215 | .IX Subsection "How can I start @@URXVT_NAME@@d automatically when I run URXVT_NAME@@c?" |
|
|
216 | .PP |
|
|
217 | If you want to start @@URXVT_NAME@@d automatically whenever you run |
|
|
218 | @@URXVT_NAME@@c and the daemon isn't running yet, use this script: |
|
|
219 | .PP |
|
|
220 | .Vb 6 |
|
|
221 | \& #!/bin/sh |
|
|
222 | \& @@URXVT_NAME@@c "$@" |
|
|
223 | \& if [ $? \-eq 2 ]; then |
|
|
224 | \& @@URXVT_NAME@@d \-q \-o \-f |
|
|
225 | \& @@URXVT_NAME@@c "$@" |
|
|
226 | \& fi |
|
|
227 | .Ve |
|
|
228 | .PP |
|
|
229 | This tries to create a new terminal, and if fails with exit status 2, |
|
|
230 | meaning it couldn't connect to the daemon, it will start the daemon and |
|
|
231 | re-run the command. Subsequent invocations of the script will re-use the |
|
|
232 | existing daemon. |
|
|
233 | .PP |
|
|
234 | \fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR |
|
|
235 | .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." |
|
|
236 | .PP |
|
|
237 | The original rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", |
|
|
238 | so you can check and see if that is set. Note that several programs, \s-1JED\s0, |
|
|
239 | slrn, Midnight Commander automatically check this variable to decide |
|
|
240 | whether or not to use color. |
|
|
241 | .PP |
|
|
242 | \fIHow do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?\fR |
|
|
243 | .IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?" |
|
|
244 | .PP |
|
|
245 | If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled |
|
|
246 | insecure mode then it is possible to use the following shell script |
|
|
247 | snippets to correctly set the display. If your version of rxvt-unicode |
|
|
248 | wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then |
|
|
249 | the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a |
|
|
250 | regular xterm. |
|
|
251 | .PP |
|
|
252 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
|
|
253 | snippets: |
|
|
254 | .PP |
175 | .Vb 1 |
255 | .Vb 12 |
176 | \& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+) |
256 | \& # Bourne/Korn/POSIX family of shells: |
|
|
257 | \& [ ${TERM:\-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
|
|
258 | \& if [ ${TERM:\-foo} = xterm ]; then |
|
|
259 | \& stty \-icanon \-echo min 0 time 15 # see if enhanced rxvt or not |
|
|
260 | \& echo \-n '^[Z' |
|
|
261 | \& read term_id |
|
|
262 | \& stty icanon echo |
|
|
263 | \& if [ ""${term_id} = '^[[?1;2C' \-a ${DISPLAY:\-foo} = foo ]; then |
|
|
264 | \& echo \-n '^[[7n' # query the rxvt we are in for the DISPLAY string |
|
|
265 | \& read DISPLAY # set it in our local shell |
|
|
266 | \& fi |
|
|
267 | \& fi |
177 | .Ve |
268 | .Ve |
178 | .Sp |
269 | .PP |
179 | Please also note that the \fILeftClick Shift-LeftClik\fR combination also |
270 | \fIHow do I compile the manual pages on my own?\fR |
180 | selects words like the old code. |
271 | .IX Subsection "How do I compile the manual pages on my own?" |
181 | .IP "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" 4 |
272 | .PP |
182 | .IX Item "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" |
273 | You need to have a recent version of perl installed as \fI/usr/bin/perl\fR, |
183 | You can disable the perl extension completely by setting the |
274 | one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to |
184 | \&\fBperl-ext-common\fR resource to the empty string, which also keeps |
275 | the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR. |
185 | rxvt-unicode from initialising perl, saving memory. |
276 | .PP |
186 | .Sp |
|
|
187 | If you only want to disable specific features, you first have to |
|
|
188 | identify which perl extension is responsible. For this, read the section |
|
|
189 | \&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For |
|
|
190 | example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify |
|
|
191 | this \fBperl-ext-common\fR resource: |
|
|
192 | .Sp |
|
|
193 | .Vb 1 |
|
|
194 | \& URxvt.perl-ext-common: default,-selection-popup,-option-popup |
|
|
195 | .Ve |
|
|
196 | .Sp |
|
|
197 | This will keep the default extensions, but disable the two popup |
|
|
198 | extensions. Some extensions can also be configured, for example, |
|
|
199 | scrollback search mode is triggered by \fBM\-s\fR. You can move it to any |
|
|
200 | other combination either by setting the \fBsearchable-scrollback\fR resource: |
|
|
201 | .Sp |
|
|
202 | .Vb 1 |
|
|
203 | \& URxvt.searchable-scrollback: CM-s |
|
|
204 | .Ve |
|
|
205 | .IP "Why doesn't rxvt-unicode read my resources?" 4 |
|
|
206 | .IX Item "Why doesn't rxvt-unicode read my resources?" |
|
|
207 | Well, why, indeed? It does, in a way very similar to other X |
|
|
208 | applications. Most importantly, this means that if you or your \s-1OS\s0 loads |
|
|
209 | resources into the X display (the right way to do it), rxvt-unicode will |
|
|
210 | ignore any resource files in your home directory. It will only read |
|
|
211 | \&\fI$HOME/.Xdefaults\fR when no resources are attached to the display. |
|
|
212 | .Sp |
|
|
213 | If you have or use an \fI$HOME/.Xresources\fR file, chances are that |
|
|
214 | resources are loaded into your X\-server. In this case, you have to |
|
|
215 | re-login after every change (or run \fIxrdb \-merge \f(CI$HOME\fI/.Xresources\fR). |
|
|
216 | .Sp |
|
|
217 | Also consider the form resources have to use: |
|
|
218 | .Sp |
|
|
219 | .Vb 1 |
|
|
220 | \& URxvt.resource: value |
|
|
221 | .Ve |
|
|
222 | .Sp |
|
|
223 | If you want to use another form (there are lots of different ways of |
|
|
224 | specifying resources), make sure you understand wether and why it |
|
|
225 | works. If unsure, use the form above. |
|
|
226 | .IP "I can't get transparency working, what am I doing wrong?" 4 |
|
|
227 | .IX Item "I can't get transparency working, what am I doing wrong?" |
|
|
228 | First of all, transparency isn't officially supported in rxvt\-unicode, so |
|
|
229 | you are mostly on your own. Do not bug the author about it (but you may |
|
|
230 | bug everybody else). Also, if you can't get it working consider it a rite |
|
|
231 | of passage, and you failed. |
|
|
232 | .Sp |
|
|
233 | Here are three ways to get transparency. \fBDo\fR read the manpage and option |
|
|
234 | descriptions for the programs mentioned and rxvt\-unicode. Really, do it! |
|
|
235 | .Sp |
|
|
236 | 1. Use inheritPixmap: |
|
|
237 | .Sp |
|
|
238 | .Vb 2 |
|
|
239 | \& Esetroot wallpaper.jpg |
|
|
240 | \& @@RXVT_NAME@@ -ip -tint red -sh 40 |
|
|
241 | .Ve |
|
|
242 | .Sp |
|
|
243 | That works. If you think it doesn't, you lack transparency and tinting |
|
|
244 | support, or you are unable to read. |
|
|
245 | .Sp |
|
|
246 | 2. Use a simple pixmap and emulate pseudo\-transparency. This enables you |
|
|
247 | to use effects other than tinting and shading: Just shade/tint/whatever |
|
|
248 | your picture with gimp: |
|
|
249 | .Sp |
|
|
250 | .Vb 2 |
|
|
251 | \& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
|
|
252 | \& @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background |
|
|
253 | .Ve |
|
|
254 | .Sp |
|
|
255 | That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you |
|
|
256 | are unable to read. |
|
|
257 | .Sp |
|
|
258 | 3. Use an \s-1ARGB\s0 visual: |
|
|
259 | .Sp |
|
|
260 | .Vb 1 |
|
|
261 | \& @@RXVT_NAME@@ -depth 432 -fg grey90 -bg rgba:0000/0000/0000/c000 |
|
|
262 | .Ve |
|
|
263 | .Sp |
|
|
264 | This requires \s-1XFT\s0 support, and support form your X\-server. If that doesn't |
|
|
265 | work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't there yet, |
|
|
266 | no matter what they claim. Rxvt-Unicode contains the neccessary bugfixes |
|
|
267 | and workarounds for Xft and Xlib to make it work. |
|
|
268 | .IP "Isn't rxvt supposed to be small? Don't all those features bloat?" 4 |
277 | \fIIsn't rxvt-unicode supposed to be small? Don't all those features bloat?\fR |
269 | .IX Item "Isn't rxvt supposed to be small? Don't all those features bloat?" |
278 | .IX Subsection "Isn't rxvt-unicode supposed to be small? Don't all those features bloat?" |
|
|
279 | .PP |
270 | I often get asked about this, and I think, no, they didn't cause extra |
280 | I often get asked about this, and I think, no, they didn't cause extra |
271 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
281 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
272 | that the urxvt binary is larger (due to some encoding tables always being |
282 | that the urxvt binary is larger (due to some encoding tables always being |
273 | compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even |
283 | compiled in), but it actually uses less memory (\s-1RSS\s0) after startup. Even |
274 | with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many |
284 | with \f(CW\*(C`\-\-disable\-everything\*(C'\fR, this comparison is a bit unfair, as many |
275 | features unique to urxvt (locale, encoding conversion, iso14755 etc.) are |
285 | features unique to urxvt (locale, encoding conversion, iso14755 etc.) are |
276 | already in use in this mode. |
286 | already in use in this mode. |
277 | .Sp |
287 | .PP |
278 | .Vb 3 |
288 | .Vb 3 |
279 | \& text data bss drs rss filename |
289 | \& text data bss drs rss filename |
280 | \& 98398 1664 24 15695 1824 rxvt --disable-everything |
290 | \& 98398 1664 24 15695 1824 rxvt \-\-disable\-everything |
281 | \& 188985 9048 66616 18222 1788 urxvt --disable-everything |
291 | \& 188985 9048 66616 18222 1788 urxvt \-\-disable\-everything |
282 | .Ve |
292 | .Ve |
283 | .Sp |
293 | .PP |
284 | When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which _is_ unfair, as this involves xft |
294 | When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which \fIis\fR unfair, as this involves xft |
285 | and full locale/XIM support which are quite bloaty inside libX11 and my |
295 | and full locale/XIM support which are quite bloaty inside libX11 and my |
286 | libc), the two diverge, but not unreasnobaly so. |
296 | libc), the two diverge, but not unreasnobaly so. |
287 | .Sp |
297 | .PP |
288 | .Vb 3 |
298 | .Vb 3 |
289 | \& text data bss drs rss filename |
299 | \& text data bss drs rss filename |
290 | \& 163431 2152 24 20123 2060 rxvt --enable-everything |
300 | \& 163431 2152 24 20123 2060 rxvt \-\-enable\-everything |
291 | \& 1035683 49680 66648 29096 3680 urxvt --enable-everything |
301 | \& 1035683 49680 66648 29096 3680 urxvt \-\-enable\-everything |
292 | .Ve |
302 | .Ve |
293 | .Sp |
303 | .PP |
294 | The very large size of the text section is explained by the east-asian |
304 | The very large size of the text section is explained by the east-asian |
295 | encoding tables, which, if unused, take up disk space but nothing else |
305 | encoding tables, which, if unused, take up disk space but nothing else |
296 | and can be compiled out unless you rely on X11 core fonts that use those |
306 | and can be compiled out unless you rely on X11 core fonts that use those |
297 | encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++ |
307 | encodings. The \s-1BSS\s0 size comes from the 64k emergency buffer that my c++ |
298 | compiler allocates (but of course doesn't use unless you are out of |
308 | compiler allocates (but of course doesn't use unless you are out of |
299 | memory). Also, using an xft font instead of a core font immediately adds a |
309 | memory). Also, using an xft font instead of a core font immediately adds a |
300 | few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when |
310 | few megabytes of \s-1RSS\s0. Xft indeed is responsible for a lot of \s-1RSS\s0 even when |
301 | not used. |
311 | not used. |
302 | .Sp |
312 | .PP |
303 | Of course, due to every character using two or four bytes instead of one, |
313 | Of course, due to every character using two or four bytes instead of one, |
304 | a large scrollback buffer will ultimately make rxvt-unicode use more |
314 | a large scrollback buffer will ultimately make rxvt-unicode use more |
305 | memory. |
315 | memory. |
306 | .Sp |
316 | .PP |
307 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this |
317 | Compared to e.g. Eterm (5112k), aterm (3132k) and xterm (4680k), this |
308 | still fares rather well. And compared to some monsters like gnome-terminal |
318 | still fares rather well. And compared to some monsters like gnome-terminal |
309 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
319 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
310 | 43180k in daemons that stay around after exit, plus half a minute of |
320 | 43180k in daemons that stay around after exit, plus half a minute of |
311 | startup time, including the hundreds of warnings it spits out), it fares |
321 | startup time, including the hundreds of warnings it spits out), it fares |
312 | extremely well *g*. |
322 | extremely well *g*. |
|
|
323 | .PP |
313 | .IP "Why \*(C+, isn't that unportable/bloated/uncool?" 4 |
324 | \fIWhy \*(C+, isn't that unportable/bloated/uncool?\fR |
314 | .IX Item "Why , isn't that unportable/bloated/uncool?" |
325 | .IX Subsection "Why , isn't that unportable/bloated/uncool?" |
|
|
326 | .PP |
315 | Is this a question? :) It comes up very often. The simple answer is: I had |
327 | Is this a question? :) It comes up very often. The simple answer is: I had |
316 | to write it, and \*(C+ allowed me to write and maintain it in a fraction |
328 | to write it, and \*(C+ allowed me to write and maintain it in a fraction |
317 | of the time and effort (which is a scarce resource for me). Put even |
329 | of the time and effort (which is a scarce resource for me). Put even |
318 | shorter: It simply wouldn't exist without \*(C+. |
330 | shorter: It simply wouldn't exist without \*(C+. |
319 | .Sp |
331 | .PP |
320 | My personal stance on this is that \*(C+ is less portable than C, but in |
332 | My personal stance on this is that \*(C+ is less portable than C, but in |
321 | the case of rxvt-unicode this hardly matters, as its portability limits |
333 | the case of rxvt-unicode this hardly matters, as its portability limits |
322 | are defined by things like X11, pseudo terminals, locale support and unix |
334 | are defined by things like X11, pseudo terminals, locale support and unix |
323 | domain sockets, which are all less portable than \*(C+ itself. |
335 | domain sockets, which are all less portable than \*(C+ itself. |
324 | .Sp |
336 | .PP |
325 | Regarding the bloat, see the above question: It's easy to write programs |
337 | Regarding the bloat, see the above question: It's easy to write programs |
326 | in C that use gobs of memory, an certainly possible to write programs in |
338 | in C that use gobs of memory, an certainly possible to write programs in |
327 | \&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is |
339 | \&\*(C+ that don't. \*(C+ also often comes with large libraries, but this is |
328 | not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my |
340 | not necessarily the case with \s-1GCC\s0. Here is what rxvt links against on my |
329 | system with a minimal config: |
341 | system with a minimal config: |
330 | .Sp |
342 | .PP |
331 | .Vb 4 |
343 | .Vb 4 |
332 | \& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
344 | \& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
333 | \& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
345 | \& libc.so.6 => /lib/libc.so.6 (0x00002aaaaadde000) |
334 | \& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
346 | \& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab01d000) |
335 | \& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
347 | \& /lib64/ld\-linux\-x86\-64.so.2 (0x00002aaaaaaab000) |
336 | .Ve |
348 | .Ve |
337 | .Sp |
349 | .PP |
338 | And here is rxvt\-unicode: |
350 | And here is rxvt\-unicode: |
339 | .Sp |
351 | .PP |
340 | .Vb 5 |
352 | .Vb 5 |
341 | \& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
353 | \& libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
342 | \& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
354 | \& libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
343 | \& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
355 | \& libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
344 | \& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
356 | \& libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
345 | \& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
357 | \& /lib64/ld\-linux\-x86\-64.so.2 (0x00002aaaaaaab000) |
346 | .Ve |
358 | .Ve |
347 | .Sp |
359 | .PP |
348 | No large bloated libraries (of course, none were linked in statically), |
360 | No large bloated libraries (of course, none were linked in statically), |
349 | except maybe libX11 :) |
361 | except maybe libX11 :) |
350 | .IP "Does it support tabs, can I have a tabbed rxvt\-unicode?" 4 |
362 | .Sh "Rendering, Font & Look and Feel Issues" |
351 | .IX Item "Does it support tabs, can I have a tabbed rxvt-unicode?" |
363 | .IX Subsection "Rendering, Font & Look and Feel Issues" |
352 | Beginning with version 7.3, there is a perl extension that implements a |
364 | \fII can't get transparency working, what am I doing wrong?\fR |
353 | simple tabbed terminal. It is installed by default, so any of these should |
365 | .IX Subsection "I can't get transparency working, what am I doing wrong?" |
354 | give you tabs: |
366 | .PP |
355 | .Sp |
367 | First of all, transparency isn't officially supported in rxvt\-unicode, so |
|
|
368 | you are mostly on your own. Do not bug the author about it (but you may |
|
|
369 | bug everybody else). Also, if you can't get it working consider it a rite |
|
|
370 | of passage: ... and you failed. |
|
|
371 | .PP |
|
|
372 | Here are four ways to get transparency. \fBDo\fR read the manpage and option |
|
|
373 | descriptions for the programs mentioned and rxvt\-unicode. Really, do it! |
|
|
374 | .PP |
|
|
375 | 1. Use inheritPixmap: |
|
|
376 | .PP |
|
|
377 | .Vb 2 |
|
|
378 | \& Esetroot wallpaper.jpg |
|
|
379 | \& @@URXVT_NAME@@ \-ip \-tint red \-sh 40 |
|
|
380 | .Ve |
|
|
381 | .PP |
|
|
382 | That works. If you think it doesn't, you lack transparency and tinting |
|
|
383 | support, or you are unable to read. |
|
|
384 | .PP |
|
|
385 | 2. Use a simple pixmap and emulate pseudo\-transparency. This enables you |
|
|
386 | to use effects other than tinting and shading: Just shade/tint/whatever |
|
|
387 | your picture with gimp or any other tool: |
|
|
388 | .PP |
|
|
389 | .Vb 2 |
|
|
390 | \& convert wallpaper.jpg \-blur 20x20 \-modulate 30 background.xpm |
|
|
391 | \& @@URXVT_NAME@@ \-pixmap background.xpm \-pe automove\-background |
|
|
392 | .Ve |
|
|
393 | .PP |
|
|
394 | That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you |
|
|
395 | are unable to read. |
|
|
396 | .PP |
|
|
397 | 3. Use an \s-1ARGB\s0 visual: |
|
|
398 | .PP |
356 | .Vb 1 |
399 | .Vb 1 |
357 | \& @@RXVT_NAME@@ -pe tabbed |
400 | \& @@URXVT_NAME@@ \-depth 32 \-fg grey90 \-bg rgba:0000/0000/4444/cccc |
358 | .Ve |
401 | .Ve |
359 | .Sp |
402 | .PP |
|
|
403 | This requires \s-1XFT\s0 support, and the support of your X\-server. If that |
|
|
404 | doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't |
|
|
405 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
|
|
406 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
|
|
407 | doesn't mean that your \s-1WM\s0 has the required kludges in place. |
|
|
408 | .PP |
|
|
409 | 4. Use xcompmgr and let it do the job: |
|
|
410 | .PP |
|
|
411 | .Vb 2 |
|
|
412 | \& xprop \-frame \-f _NET_WM_WINDOW_OPACITY 32c \e |
|
|
413 | \& \-set _NET_WM_WINDOW_OPACITY 0xc0000000 |
|
|
414 | .Ve |
|
|
415 | .PP |
|
|
416 | Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR |
|
|
417 | by other values to change the degree of opacity. If it doesn't work and |
|
|
418 | your server crashes, you got to keep the pieces. |
|
|
419 | .PP |
|
|
420 | \fIWhy does rxvt-unicode sometimes leave pixel droppings?\fR |
|
|
421 | .IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?" |
|
|
422 | .PP |
|
|
423 | Most fonts were not designed for terminal use, which means that character |
|
|
424 | size varies a lot. A font that is otherwise fine for terminal use might |
|
|
425 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
|
|
426 | these characters. For characters that are just \*(L"a bit\*(R" too wide a special |
|
|
427 | \&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters. |
|
|
428 | .PP |
|
|
429 | All of this requires that fonts do not lie about character sizes, |
|
|
430 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
|
|
431 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
|
|
432 | ask for the character bounding box, which unfortunately is wrong in these |
|
|
433 | cases). |
|
|
434 | .PP |
|
|
435 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
|
|
436 | or the respective font. If you encounter this problem you might try using |
|
|
437 | the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you |
|
|
438 | might be forced to use a different font. |
|
|
439 | .PP |
|
|
440 | All of this is not a problem when using X11 core fonts, as their bounding |
|
|
441 | box data is correct. |
|
|
442 | .PP |
|
|
443 | \fIHow can I keep rxvt-unicode from using reverse video so much?\fR |
|
|
444 | .IX Subsection "How can I keep rxvt-unicode from using reverse video so much?" |
|
|
445 | .PP |
|
|
446 | First of all, make sure you are running with the right terminal settings |
|
|
447 | (\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then |
|
|
448 | make sure you have specified colours for italic and bold, as otherwise |
|
|
449 | rxvt-unicode might use reverse video to simulate the effect: |
|
|
450 | .PP |
|
|
451 | .Vb 2 |
|
|
452 | \& URxvt.colorBD: white |
|
|
453 | \& URxvt.colorIT: green |
|
|
454 | .Ve |
|
|
455 | .PP |
|
|
456 | \fISome programs assume totally weird colours (red instead of blue), how can I fix that?\fR |
|
|
457 | .IX Subsection "Some programs assume totally weird colours (red instead of blue), how can I fix that?" |
|
|
458 | .PP |
|
|
459 | For some unexplainable reason, some rare programs assume a very weird |
|
|
460 | colour palette when confronted with a terminal with more than the standard |
|
|
461 | 8 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix |
|
|
462 | these programs not to assume non-ISO colours without very good reasons. |
|
|
463 | .PP |
|
|
464 | In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo |
|
|
465 | definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will |
|
|
466 | fix colours but keep you from using other rxvt-unicode features. |
|
|
467 | .PP |
|
|
468 | \fICan I switch the fonts at runtime?\fR |
|
|
469 | .IX Subsection "Can I switch the fonts at runtime?" |
|
|
470 | .PP |
|
|
471 | Yes, using an escape sequence. Try something like this, which has the same |
|
|
472 | effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately: |
|
|
473 | .PP |
360 | .Vb 1 |
474 | .Vb 1 |
|
|
475 | \& printf '\e33]50;%s\e007' "9x15bold,xft:Kochi Gothic" |
|
|
476 | .Ve |
|
|
477 | .PP |
|
|
478 | This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
479 | japanese font), but you have to switch to chinese temporarily, where |
|
|
480 | japanese fonts would only be in your way. |
|
|
481 | .PP |
|
|
482 | You can think of this as a kind of manual \s-1ISO\-2022\s0 switching. |
|
|
483 | .PP |
|
|
484 | \fIWhy do italic characters look as if clipped?\fR |
|
|
485 | .IX Subsection "Why do italic characters look as if clipped?" |
|
|
486 | .PP |
|
|
487 | Many fonts have difficulties with italic characters and hinting. For |
|
|
488 | example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans |
|
|
489 | Mono\*(C'\fR completely fails in its italic face. A workaround might be to |
|
|
490 | enable freetype autohinting, i.e. like this: |
|
|
491 | .PP |
|
|
492 | .Vb 2 |
|
|
493 | \& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
494 | \& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
495 | .Ve |
|
|
496 | .PP |
|
|
497 | \fICan I speed up Xft rendering somehow?\fR |
|
|
498 | .IX Subsection "Can I speed up Xft rendering somehow?" |
|
|
499 | .PP |
|
|
500 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
501 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
502 | antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of |
|
|
503 | memory and also speeds up rendering considerably. |
|
|
504 | .PP |
|
|
505 | \fIRxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?\fR |
|
|
506 | .IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" |
|
|
507 | .PP |
|
|
508 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
509 | fall back to its default font search list it will prefer X11 core |
|
|
510 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
511 | antialiasing disabled for most of them, because the author thinks they |
|
|
512 | look best that way. |
|
|
513 | .PP |
|
|
514 | If you want antialiasing, you have to specify the fonts manually. |
|
|
515 | .PP |
|
|
516 | \fIWhat's with this bold/blink stuff?\fR |
|
|
517 | .IX Subsection "What's with this bold/blink stuff?" |
|
|
518 | .PP |
|
|
519 | If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the |
|
|
520 | standard foreground colour. |
|
|
521 | .PP |
|
|
522 | For the standard background colour, blinking will actually make the |
|
|
523 | text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard |
|
|
524 | colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be |
|
|
525 | ignored. |
|
|
526 | .PP |
|
|
527 | On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity |
|
|
528 | foreground/background colors. |
|
|
529 | .PP |
|
|
530 | color0\-7 are the low-intensity colors. |
|
|
531 | .PP |
|
|
532 | color8\-15 are the corresponding high-intensity colors. |
|
|
533 | .PP |
|
|
534 | \fII don't like the screen colors. How do I change them?\fR |
|
|
535 | .IX Subsection "I don't like the screen colors. How do I change them?" |
|
|
536 | .PP |
|
|
537 | You can change the screen colors at run-time using \fI~/.Xdefaults\fR |
|
|
538 | resources (or as long\-options). |
|
|
539 | .PP |
|
|
540 | Here are values that are supposed to resemble a \s-1VGA\s0 screen, |
|
|
541 | including the murky brown that passes for low-intensity yellow: |
|
|
542 | .PP |
|
|
543 | .Vb 8 |
|
|
544 | \& URxvt.color0: #000000 |
|
|
545 | \& URxvt.color1: #A80000 |
|
|
546 | \& URxvt.color2: #00A800 |
|
|
547 | \& URxvt.color3: #A8A800 |
|
|
548 | \& URxvt.color4: #0000A8 |
|
|
549 | \& URxvt.color5: #A800A8 |
|
|
550 | \& URxvt.color6: #00A8A8 |
|
|
551 | \& URxvt.color7: #A8A8A8 |
|
|
552 | \& |
|
|
553 | \& URxvt.color8: #000054 |
|
|
554 | \& URxvt.color9: #FF0054 |
|
|
555 | \& URxvt.color10: #00FF54 |
|
|
556 | \& URxvt.color11: #FFFF54 |
|
|
557 | \& URxvt.color12: #0000FF |
|
|
558 | \& URxvt.color13: #FF00FF |
|
|
559 | \& URxvt.color14: #00FFFF |
|
|
560 | \& URxvt.color15: #FFFFFF |
|
|
561 | .Ve |
|
|
562 | .PP |
|
|
563 | And here is a more complete set of non-standard colors. |
|
|
564 | .PP |
|
|
565 | .Vb 10 |
|
|
566 | \& URxvt.cursorColor: #dc74d1 |
|
|
567 | \& URxvt.pointerColor: #dc74d1 |
|
|
568 | \& URxvt.background: #0e0e0e |
|
|
569 | \& URxvt.foreground: #4ad5e1 |
|
|
570 | \& URxvt.color0: #000000 |
|
|
571 | \& URxvt.color8: #8b8f93 |
|
|
572 | \& URxvt.color1: #dc74d1 |
|
|
573 | \& URxvt.color9: #dc74d1 |
|
|
574 | \& URxvt.color2: #0eb8c7 |
|
|
575 | \& URxvt.color10: #0eb8c7 |
|
|
576 | \& URxvt.color3: #dfe37e |
|
|
577 | \& URxvt.color11: #dfe37e |
|
|
578 | \& URxvt.color5: #9e88f0 |
|
|
579 | \& URxvt.color13: #9e88f0 |
|
|
580 | \& URxvt.color6: #73f7ff |
|
|
581 | \& URxvt.color14: #73f7ff |
|
|
582 | \& URxvt.color7: #e1dddd |
|
|
583 | \& URxvt.color15: #e1dddd |
|
|
584 | .Ve |
|
|
585 | .PP |
|
|
586 | They have been described (not by me) as \*(L"pretty girly\*(R". |
|
|
587 | .PP |
|
|
588 | \fIWhy do some characters look so much different than others?\fR |
|
|
589 | .IX Subsection "Why do some characters look so much different than others?" |
|
|
590 | .PP |
|
|
591 | See next entry. |
|
|
592 | .PP |
|
|
593 | \fIHow does rxvt-unicode choose fonts?\fR |
|
|
594 | .IX Subsection "How does rxvt-unicode choose fonts?" |
|
|
595 | .PP |
|
|
596 | Most fonts do not contain the full range of Unicode, which is |
|
|
597 | fine. Chances are that the font you (or the admin/package maintainer of |
|
|
598 | your system/os) have specified does not cover all the characters you want |
|
|
599 | to display. |
|
|
600 | .PP |
|
|
601 | \&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement |
|
|
602 | font. Often the result is fine, but sometimes the chosen font looks |
|
|
603 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
|
|
604 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
|
|
605 | intelligence to detect that a specific glyph is wrong: it has to believe |
|
|
606 | the font that the characters it claims to contain indeed look correct. |
|
|
607 | .PP |
|
|
608 | In that case, select a font of your taste and add it to the font list, |
|
|
609 | e.g.: |
|
|
610 | .PP |
|
|
611 | .Vb 1 |
|
|
612 | \& @@URXVT_NAME@@ \-fn basefont,font2,font3... |
|
|
613 | .Ve |
|
|
614 | .PP |
|
|
615 | When rxvt-unicode sees a character, it will first look at the base |
|
|
616 | font. If the base font does not contain the character, it will go to the |
|
|
617 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
618 | search and use less resources within rxvt-unicode and the X\-server. |
|
|
619 | .PP |
|
|
620 | The only limitation is that none of the fonts may be larger than the base |
|
|
621 | font, as the base font defines the terminal character cell size, which |
|
|
622 | must be the same due to the way terminals work. |
|
|
623 | .PP |
|
|
624 | \fIWhy do some chinese characters look so different than others?\fR |
|
|
625 | .IX Subsection "Why do some chinese characters look so different than others?" |
|
|
626 | .PP |
|
|
627 | This is because there is a difference between script and language \*(-- |
|
|
628 | rxvt-unicode does not know which language the text that is output is, |
|
|
629 | as it only knows the unicode character codes. If rxvt-unicode first |
|
|
630 | sees a japanese/chinese character, it might choose a japanese font for |
|
|
631 | display. Subsequent japanese characters will use that font. Now, many |
|
|
632 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
633 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
634 | \&\*(-- unfortunately at this point, it will still use the japanese font for |
|
|
635 | chinese characters that are also in the japanese font. |
|
|
636 | .PP |
|
|
637 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
638 | list (see the previous question). The key is to view the font list as |
|
|
639 | a preference list: If you expect more japanese, list a japanese font |
|
|
640 | first. If you expect more chinese, put a chinese font first. |
|
|
641 | .PP |
|
|
642 | In the future it might be possible to switch language preferences at |
|
|
643 | runtime (the internal data structure has no problem with using different |
|
|
644 | fonts for the same character at the same time, but no interface for this |
|
|
645 | has been designed yet). |
|
|
646 | .PP |
|
|
647 | Until then, you might get away with switching fonts at runtime (see \*(L"Can |
|
|
648 | I switch the fonts at runtime?\*(R" later in this document). |
|
|
649 | .Sh "Keyboard, Mouse & User Interaction" |
|
|
650 | .IX Subsection "Keyboard, Mouse & User Interaction" |
|
|
651 | \fIThe new selection selects pieces that are too big, how can I select single words?\fR |
|
|
652 | .IX Subsection "The new selection selects pieces that are too big, how can I select single words?" |
|
|
653 | .PP |
|
|
654 | If you want to select e.g. alphanumeric words, you can use the following |
|
|
655 | setting: |
|
|
656 | .PP |
|
|
657 | .Vb 1 |
|
|
658 | \& URxvt.selection.pattern\-0: ([[:word:]]+) |
|
|
659 | .Ve |
|
|
660 | .PP |
|
|
661 | If you click more than twice, the selection will be extended |
|
|
662 | more and more. |
|
|
663 | .PP |
|
|
664 | To get a selection that is very similar to the old code, try this pattern: |
|
|
665 | .PP |
|
|
666 | .Vb 1 |
|
|
667 | \& URxvt.selection.pattern\-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+) |
|
|
668 | .Ve |
|
|
669 | .PP |
|
|
670 | Please also note that the \fILeftClick Shift-LeftClik\fR combination also |
|
|
671 | selects words like the old code. |
|
|
672 | .PP |
|
|
673 | \fII don't like the new selection/popups/hotkeys/perl, how do I change/disable it?\fR |
|
|
674 | .IX Subsection "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" |
|
|
675 | .PP |
|
|
676 | You can disable the perl extension completely by setting the |
|
|
677 | \&\fBperl-ext-common\fR resource to the empty string, which also keeps |
|
|
678 | rxvt-unicode from initialising perl, saving memory. |
|
|
679 | .PP |
|
|
680 | If you only want to disable specific features, you first have to |
|
|
681 | identify which perl extension is responsible. For this, read the section |
|
|
682 | \&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@URXVT_NAME@@\fIperl\fR\|(3) manpage. For |
|
|
683 | example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify |
|
|
684 | this \fBperl-ext-common\fR resource: |
|
|
685 | .PP |
|
|
686 | .Vb 1 |
|
|
687 | \& URxvt.perl\-ext\-common: default,\-selection\-popup,\-option\-popup |
|
|
688 | .Ve |
|
|
689 | .PP |
|
|
690 | This will keep the default extensions, but disable the two popup |
|
|
691 | extensions. Some extensions can also be configured, for example, |
|
|
692 | scrollback search mode is triggered by \fBM\-s\fR. You can move it to any |
|
|
693 | other combination either by setting the \fBsearchable-scrollback\fR resource: |
|
|
694 | .PP |
|
|
695 | .Vb 1 |
|
|
696 | \& URxvt.searchable\-scrollback: CM\-s |
|
|
697 | .Ve |
|
|
698 | .PP |
|
|
699 | \fIThe cursor moves when selecting text in the current input line, how do I switch this off?\fR |
|
|
700 | .IX Subsection "The cursor moves when selecting text in the current input line, how do I switch this off?" |
|
|
701 | .PP |
|
|
702 | See next entry. |
|
|
703 | .PP |
|
|
704 | \fIDuring rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?\fR |
|
|
705 | .IX Subsection "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?" |
|
|
706 | .PP |
|
|
707 | These are caused by the \f(CW\*(C`readline\*(C'\fR perl extension. Under normal |
|
|
708 | circumstances, it will move your cursor around when you click into the |
|
|
709 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
710 | but when running a program that doesn't parse cursor movements or in some |
|
|
711 | cases during rlogin sessions, it fails to detect this properly. |
|
|
712 | .PP |
|
|
713 | You can permamently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR |
|
|
714 | extension: |
|
|
715 | .PP |
|
|
716 | .Vb 1 |
361 | \& URxvt.perl-ext-common: default,tabbed |
717 | \& URxvt.perl\-ext\-common: default,\-readline |
362 | .Ve |
718 | .Ve |
363 | .Sp |
719 | .PP |
364 | It will also work fine with tabbing functionality of many window managers |
720 | \fIMy numerical keypad acts weird and generates differing output?\fR |
365 | or similar tabbing programs, and its embedding-features allow it to be |
721 | .IX Subsection "My numerical keypad acts weird and generates differing output?" |
366 | embedded into other programs, as witnessed by \fIdoc/rxvt\-tabbed\fR or |
722 | .PP |
367 | the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl module, which features a tabbed urxvt |
723 | Some Debian GNUL/Linux users seem to have this problem, although no |
368 | (murxvt) terminal as an example embedding application. |
724 | specific details were reported so far. It is possible that this is caused |
369 | .IP "How do I know which rxvt-unicode version I'm using?" 4 |
725 | by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how |
370 | .IX Item "How do I know which rxvt-unicode version I'm using?" |
726 | this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible |
371 | The version number is displayed with the usage (\-h). Also the escape |
727 | keymap. See the answer to the previous question, and please report if that |
372 | sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When |
728 | helped. |
373 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
729 | .PP |
374 | daemon. |
730 | \fIMy Compose (Multi_key) key is no longer working.\fR |
375 | .IP "I am using Debian GNU/Linux and have a problem..." 4 |
731 | .IX Subsection "My Compose (Multi_key) key is no longer working." |
376 | .IX Item "I am using Debian GNU/Linux and have a problem..." |
732 | .PP |
377 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
733 | The most common causes for this are that either your locale is not set |
378 | patches that considerably change the behaviour of rxvt-unicode (but |
734 | correctly, or you specified a \fBpreeditStyle\fR that is not supported by |
379 | unfortunately this notice has been removed). Before reporting a bug to |
735 | your input method. For example, if you specified \fBOverTheSpot\fR and |
380 | the original rxvt-unicode author please download and install the genuine |
736 | your input method (e.g. the default input method handling Compose keys) |
381 | version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce |
737 | does not support this (for instance because it is not visual), then |
382 | the problem. If you cannot, chances are that the problems are specific to |
738 | rxvt-unicode will continue without an input method. |
383 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
739 | .PP |
384 | Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug). |
740 | In this case either do not specify a \fBpreeditStyle\fR or specify more than |
385 | .Sp |
741 | one pre-edit style, such as \fBOverTheSpot,Root,None\fR. |
386 | For other problems that also affect the Debian package, you can and |
742 | .PP |
387 | probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a |
743 | \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 |
388 | bug in the Debian version and it serves as a reminder for other users that |
744 | .IX Subsection "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755" |
389 | might encounter the same issue. |
745 | .PP |
390 | .IP "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?" 4 |
746 | Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on |
391 | .IX Item "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?" |
747 | international keyboards) or simply use \s-1ISO\s0 14755 support to your |
392 | You should build one binary with the default options. \fIconfigure\fR |
748 | advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other |
393 | now enables most useful options, and the trend goes to making them |
749 | codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape |
394 | runtime\-switchable, too, so there is usually no drawback to enbaling them, |
750 | character and so on. |
395 | except higher disk and possibly memory usage. The perl interpreter should |
751 | .PP |
396 | be enabled, as important functionality (menus, selection, likely more in |
752 | \fIMouse cut/paste suddenly no longer works.\fR |
397 | the future) depends on it. |
753 | .IX Subsection "Mouse cut/paste suddenly no longer works." |
398 | .Sp |
754 | .PP |
399 | You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources |
755 | Make sure that mouse reporting is actually turned off since killing |
400 | system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful |
756 | some editors prematurely may leave the mouse in mouse report mode. I've |
401 | behaviour. If your distribution aims at low memory, add an empty |
757 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
402 | \&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the |
758 | quick check is to see if cut/paste works when the Alt or Shift keys are |
403 | perl interpreter disabled until the user enables it. |
759 | depressed. |
404 | .Sp |
760 | .PP |
405 | If you can/want build more binaries, I recommend building a minimal |
761 | \fIWhat's with the strange Backspace/Delete key behaviour?\fR |
406 | one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with |
762 | .IX Subsection "What's with the strange Backspace/Delete key behaviour?" |
407 | \&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of |
763 | .PP |
408 | encodings built-in that increase download times and are rarely used). |
764 | Assuming that the physical Backspace key corresponds to the |
409 | .IP "I need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?" 4 |
765 | BackSpace keysym (not likely for Linux ... see the following |
410 | .IX Item "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?" |
766 | question) there are two standard values that can be used for |
411 | It should be, starting with release 7.1. You are encouraged to properly |
767 | Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR. |
412 | install urxvt with privileges necessary for your \s-1OS\s0 now. |
768 | .PP |
413 | .Sp |
769 | Historically, either value is correct, but rxvt-unicode adopts the debian |
414 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
770 | policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct |
415 | into a helper process for privileged operations (pty handling on some |
771 | choice :). |
416 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
772 | .PP |
417 | immediately. This is much safer than most other terminals that keep |
773 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
418 | privileges while running (but is more relevant to urxvt, as it contains |
774 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
419 | things as perl interpreters, which might be \*(L"helpful\*(R" to attackers). |
775 | started from a terminal (say, from a menu or by remote shell), then the |
420 | .Sp |
776 | system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will |
421 | This forking is done as the very first within \fImain()\fR, which is very early |
777 | be used (which may not be the same as your stty setting). |
422 | and reduces possible bugs to initialisation code run before \fImain()\fR, or |
778 | .PP |
423 | things like the dynamic loader of your system, which should result in very |
779 | For starting a new rxvt\-unicode: |
424 | little risk. |
780 | .PP |
|
|
781 | .Vb 3 |
|
|
782 | \& # use Backspace = ^H |
|
|
783 | \& $ stty erase ^H |
|
|
784 | \& $ @@URXVT_NAME@@ |
|
|
785 | \& |
|
|
786 | \& # use Backspace = ^? |
|
|
787 | \& $ stty erase ^? |
|
|
788 | \& $ @@URXVT_NAME@@ |
|
|
789 | .Ve |
|
|
790 | .PP |
|
|
791 | Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. |
|
|
792 | .PP |
|
|
793 | For an existing rxvt\-unicode: |
|
|
794 | .PP |
|
|
795 | .Vb 3 |
|
|
796 | \& # use Backspace = ^H |
|
|
797 | \& $ stty erase ^H |
|
|
798 | \& $ echo \-n "^[[36h" |
|
|
799 | \& |
|
|
800 | \& # use Backspace = ^? |
|
|
801 | \& $ stty erase ^? |
|
|
802 | \& $ echo \-n "^[[36l" |
|
|
803 | .Ve |
|
|
804 | .PP |
|
|
805 | This helps satisfy some of the Backspace discrepancies that occur, but |
|
|
806 | if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value |
|
|
807 | properly reflects that. |
|
|
808 | .PP |
|
|
809 | The Delete key is a another casualty of the ill-defined Backspace problem. |
|
|
810 | To avoid confusion between the Backspace and Delete keys, the Delete |
|
|
811 | key has been assigned an escape sequence to match the vt100 for Execute |
|
|
812 | (\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo. |
|
|
813 | .PP |
|
|
814 | Some other Backspace problems: |
|
|
815 | .PP |
|
|
816 | some editors use termcap/terminfo, |
|
|
817 | some editors (vim I'm told) expect Backspace = ^H, |
|
|
818 | \&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help. |
|
|
819 | .PP |
|
|
820 | Perhaps someday this will all be resolved in a consistent manner. |
|
|
821 | .PP |
|
|
822 | \fII don't like the key\-bindings. How do I change them?\fR |
|
|
823 | .IX Subsection "I don't like the key-bindings. How do I change them?" |
|
|
824 | .PP |
|
|
825 | There are some compile-time selections available via configure. Unless |
|
|
826 | you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can |
|
|
827 | use the `keysym' resource to alter the keystrings associated with keysyms. |
|
|
828 | .PP |
|
|
829 | Here's an example for a URxvt session started using \f(CW\*(C`@@URXVT_NAME@@ \-name URxvt\*(C'\fR |
|
|
830 | .PP |
|
|
831 | .Vb 10 |
|
|
832 | \& URxvt.keysym.Home: \e033[1~ |
|
|
833 | \& URxvt.keysym.End: \e033[4~ |
|
|
834 | \& URxvt.keysym.C\-apostrophe: \e033<C\-'> |
|
|
835 | \& URxvt.keysym.C\-slash: \e033<C\-/> |
|
|
836 | \& URxvt.keysym.C\-semicolon: \e033<C\-;> |
|
|
837 | \& URxvt.keysym.C\-grave: \e033<C\-`> |
|
|
838 | \& URxvt.keysym.C\-comma: \e033<C\-,> |
|
|
839 | \& URxvt.keysym.C\-period: \e033<C\-.> |
|
|
840 | \& URxvt.keysym.C\-0x60: \e033<C\-`> |
|
|
841 | \& URxvt.keysym.C\-Tab: \e033<C\-Tab> |
|
|
842 | \& URxvt.keysym.C\-Return: \e033<C\-Return> |
|
|
843 | \& URxvt.keysym.S\-Return: \e033<S\-Return> |
|
|
844 | \& URxvt.keysym.S\-space: \e033<S\-Space> |
|
|
845 | \& URxvt.keysym.M\-Up: \e033<M\-Up> |
|
|
846 | \& URxvt.keysym.M\-Down: \e033<M\-Down> |
|
|
847 | \& URxvt.keysym.M\-Left: \e033<M\-Left> |
|
|
848 | \& URxvt.keysym.M\-Right: \e033<M\-Right> |
|
|
849 | \& URxvt.keysym.M\-C\-0: list \e033<M\-C\- 0123456789 > |
|
|
850 | \& URxvt.keysym.M\-C\-a: list \e033<M\-C\- abcdefghijklmnopqrstuvwxyz > |
|
|
851 | \& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007 |
|
|
852 | .Ve |
|
|
853 | .PP |
|
|
854 | See some more examples in the documentation for the \fBkeysym\fR resource. |
|
|
855 | .PP |
|
|
856 | \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 |
|
|
857 | .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" |
|
|
858 | .PP |
|
|
859 | .Vb 6 |
|
|
860 | \& KP_Insert == Insert |
|
|
861 | \& F22 == Print |
|
|
862 | \& F27 == Home |
|
|
863 | \& F29 == Prior |
|
|
864 | \& F33 == End |
|
|
865 | \& F35 == Next |
|
|
866 | .Ve |
|
|
867 | .PP |
|
|
868 | Rather than have rxvt-unicode try to accommodate all the various possible |
|
|
869 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
|
|
870 | required for your particular machine. |
|
|
871 | .Sh "Terminal Configuration" |
|
|
872 | .IX Subsection "Terminal Configuration" |
|
|
873 | \fICan I see a typical configuration?\fR |
|
|
874 | .IX Subsection "Can I see a typical configuration?" |
|
|
875 | .PP |
|
|
876 | The default configuration tries to be xterm\-like, which I don't like that |
|
|
877 | much, but it's least surprise to regular users. |
|
|
878 | .PP |
|
|
879 | As a rxvt or rxvt-unicode user, you are practically supposed to invest |
|
|
880 | time into customising your terminal. To get you started, here is the |
|
|
881 | author's .Xdefaults entries, with comments on what they do. It's certainly |
|
|
882 | not \fItypical\fR, but what's typical... |
|
|
883 | .PP |
|
|
884 | .Vb 2 |
|
|
885 | \& URxvt.cutchars: "()*,<>[]{}|' |
|
|
886 | \& URxvt.print\-pipe: cat >/tmp/xxx |
|
|
887 | .Ve |
|
|
888 | .PP |
|
|
889 | These are just for testing stuff. |
|
|
890 | .PP |
|
|
891 | .Vb 2 |
|
|
892 | \& URxvt.imLocale: ja_JP.UTF\-8 |
|
|
893 | \& URxvt.preeditType: OnTheSpot,None |
|
|
894 | .Ve |
|
|
895 | .PP |
|
|
896 | This tells rxvt-unicode to use a special locale when communicating with |
|
|
897 | the X Input Method, and also tells it to only use the OnTheSpot pre-edit |
|
|
898 | type, which requires the \f(CW\*(C`xim\-onthespot\*(C'\fR perl extension but rewards me |
|
|
899 | with correct-looking fonts. |
|
|
900 | .PP |
|
|
901 | .Vb 6 |
|
|
902 | \& URxvt.perl\-lib: /root/lib/urxvt |
|
|
903 | \& URxvt.perl\-ext\-common: default,selection\-autotransform,selection\-pastebin,xim\-onthespot,remote\-clipboard |
|
|
904 | \& URxvt.selection.pattern\-0: ( at .*? line \e\ed+) |
|
|
905 | \& URxvt.selection.pattern\-1: ^(/[^:]+):\e |
|
|
906 | \& URxvt.selection\-autotransform.0: s/^([^:[:space:]]+):(\e\ed+):?$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/ |
|
|
907 | \& URxvt.selection\-autotransform.1: s/^ at (.*?) line (\e\ed+)$/:e \e\eQ$1\e\eE\e\ex0d:$2\e\ex0d/ |
|
|
908 | .Ve |
|
|
909 | .PP |
|
|
910 | This is my perl configuration. The first two set the perl library |
|
|
911 | directory and also tells urxvt to use a large number of extensions. I |
|
|
912 | develop for myself mostly, so I actually use most of the extensions I |
|
|
913 | write. |
|
|
914 | .PP |
|
|
915 | The selection stuff mainly makes the selection perl-error-message aware |
|
|
916 | and tells it to convert pelr error mssages into vi-commands to load the |
|
|
917 | relevant file and go tot he error line number. |
|
|
918 | .PP |
|
|
919 | .Vb 2 |
|
|
920 | \& URxvt.scrollstyle: plain |
|
|
921 | \& URxvt.secondaryScroll: true |
|
|
922 | .Ve |
|
|
923 | .PP |
|
|
924 | As the documentation says: plain is the preferred scrollbar for the |
|
|
925 | author. The \f(CW\*(C`secondaryScroll\*(C'\fR confgiures urxvt to scroll in full-screen |
|
|
926 | apps, like screen, so lines scorlled out of screen end up in urxvt's |
|
|
927 | scrollback buffer. |
|
|
928 | .PP |
|
|
929 | .Vb 7 |
|
|
930 | \& URxvt.background: #000000 |
|
|
931 | \& URxvt.foreground: gray90 |
|
|
932 | \& URxvt.color7: gray90 |
|
|
933 | \& URxvt.colorBD: #ffffff |
|
|
934 | \& URxvt.cursorColor: #e0e080 |
|
|
935 | \& URxvt.throughColor: #8080f0 |
|
|
936 | \& URxvt.highlightColor: #f0f0f0 |
|
|
937 | .Ve |
|
|
938 | .PP |
|
|
939 | Some colours. Not sure which ones are being used or even non\-defaults, but |
|
|
940 | these are in my .Xdefaults. Most notably, they set foreground/background |
|
|
941 | to light gray/black, and also make sure that the colour 7 matches the |
|
|
942 | default foreground colour. |
|
|
943 | .PP |
|
|
944 | .Vb 1 |
|
|
945 | \& URxvt.underlineColor: yellow |
|
|
946 | .Ve |
|
|
947 | .PP |
|
|
948 | Another colour, makes underline lines look different. Sometimes hurts, but |
|
|
949 | is mostly a nice effect. |
|
|
950 | .PP |
|
|
951 | .Vb 4 |
|
|
952 | \& URxvt.geometry: 154x36 |
|
|
953 | \& URxvt.loginShell: false |
|
|
954 | \& URxvt.meta: ignore |
|
|
955 | \& URxvt.utmpInhibit: true |
|
|
956 | .Ve |
|
|
957 | .PP |
|
|
958 | Uh, well, should be mostly self\-explanatory. By specifying some defaults |
|
|
959 | manually, I can quickly switch them for testing. |
|
|
960 | .PP |
|
|
961 | .Vb 1 |
|
|
962 | \& URxvt.saveLines: 8192 |
|
|
963 | .Ve |
|
|
964 | .PP |
|
|
965 | A large scrollback buffer is essential. Really. |
|
|
966 | .PP |
|
|
967 | .Vb 1 |
|
|
968 | \& URxvt.mapAlert: true |
|
|
969 | .Ve |
|
|
970 | .PP |
|
|
971 | The only case I use it is for my \s-1IRC\s0 window, which I like to keep |
|
|
972 | iconified till people msg me (which beeps). |
|
|
973 | .PP |
|
|
974 | .Vb 1 |
|
|
975 | \& URxvt.visualBell: true |
|
|
976 | .Ve |
|
|
977 | .PP |
|
|
978 | The audible bell is often annoying, especially when in a crowd. |
|
|
979 | .PP |
|
|
980 | .Vb 1 |
|
|
981 | \& URxvt.insecure: true |
|
|
982 | .Ve |
|
|
983 | .PP |
|
|
984 | Please don't hack my mutt! Ooops... |
|
|
985 | .PP |
|
|
986 | .Vb 1 |
|
|
987 | \& URxvt.pastableTabs: false |
|
|
988 | .Ve |
|
|
989 | .PP |
|
|
990 | I once thought this is a great idea. |
|
|
991 | .PP |
|
|
992 | .Vb 9 |
|
|
993 | \& urxvt.font: 9x15bold,\e |
|
|
994 | \& \-misc\-fixed\-bold\-r\-normal\-\-15\-140\-75\-75\-c\-90\-iso10646\-1,\e |
|
|
995 | \& \-misc\-fixed\-medium\-r\-normal\-\-15\-140\-75\-75\-c\-90\-iso10646\-1, \e |
|
|
996 | \& [codeset=JISX0208]xft:Kochi Gothic, \e |
|
|
997 | \& xft:Bitstream Vera Sans Mono:autohint=true, \e |
|
|
998 | \& xft:Code2000:antialias=false |
|
|
999 | \& urxvt.boldFont: \-xos4\-terminus\-bold\-r\-normal\-\-14\-140\-72\-72\-c\-80\-iso8859\-15 |
|
|
1000 | \& urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
1001 | \& urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
1002 | .Ve |
|
|
1003 | .PP |
|
|
1004 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
|
|
1005 | overwhelmed. A special note: the \f(CW\*(C`9x15bold\*(C'\fR mentioend above is actually |
|
|
1006 | the version from XFree\-3.3, as XFree\-4 replaced it by a totally different |
|
|
1007 | font (different glyphs for \f(CW\*(C`;\*(C'\fR and many other harmless characters), |
|
|
1008 | while the second font is actually the \f(CW\*(C`9x15bold\*(C'\fR from XFree4/XOrg. The |
|
|
1009 | bold version has less chars than the medium version, so I use it for rare |
|
|
1010 | characters, too. Whene ditign sources with vim, I use italic for comments |
|
|
1011 | and other stuff, which looks quite good with Bitstream Vera anti\-aliased. |
|
|
1012 | .PP |
|
|
1013 | Terminus is a quite bad font (many very wrong glyphs), but for most of my |
|
|
1014 | purposes, it works, and gives a different look, as my normal (Non\-bold) |
|
|
1015 | font is already bold, and I want to see a difference between bold and |
|
|
1016 | normal fonts. |
|
|
1017 | .PP |
|
|
1018 | Please note that I used the \f(CW\*(C`urxvt\*(C'\fR instance name and not the \f(CW\*(C`URxvt\*(C'\fR |
|
|
1019 | class name. Thats because I use different configs for different purposes, |
|
|
1020 | for example, my \s-1IRC\s0 window is started with \f(CW\*(C`\-name IRC\*(C'\fR, and uses these |
|
|
1021 | defaults: |
|
|
1022 | .PP |
|
|
1023 | .Vb 9 |
|
|
1024 | \& IRC*title: IRC |
|
|
1025 | \& IRC*geometry: 87x12+535+542 |
|
|
1026 | \& IRC*saveLines: 0 |
|
|
1027 | \& IRC*mapAlert: true |
|
|
1028 | \& IRC*font: suxuseuro |
|
|
1029 | \& IRC*boldFont: suxuseuro |
|
|
1030 | \& IRC*colorBD: white |
|
|
1031 | \& IRC*keysym.M\-C\-1: command:\e033]710;suxuseuro\e007\e033]711;suxuseuro\e007 |
|
|
1032 | \& IRC*keysym.M\-C\-2: command:\e033]710;9x15bold\e007\e033]711;9x15bold\e007 |
|
|
1033 | .Ve |
|
|
1034 | .PP |
|
|
1035 | \&\f(CW\*(C`Alt\-Shift\-1\*(C'\fR and \f(CW\*(C`Alt\-Shift\-2\*(C'\fR switch between two different font |
|
|
1036 | sizes. \f(CW\*(C`suxuseuro\*(C'\fR allows me to keep an eye (and actually read) |
|
|
1037 | stuff while keeping a very small window. If somebody pastes something |
|
|
1038 | complicated (e.g. japanese), I temporarily switch to a larger font. |
|
|
1039 | .PP |
|
|
1040 | The above is all in my \f(CW\*(C`.Xdefaults\*(C'\fR (I don't use \f(CW\*(C`.Xresources\*(C'\fR nor |
|
|
1041 | \&\f(CW\*(C`xrdb\*(C'\fR). I also have some resources in a separate \f(CW\*(C`.Xdefaults\-hostname\*(C'\fR |
|
|
1042 | file for different hosts, for example, on ym main desktop, I use: |
|
|
1043 | .PP |
|
|
1044 | .Vb 5 |
|
|
1045 | \& URxvt.keysym.C\-M\-q: command:\e033[3;5;5t |
|
|
1046 | \& URxvt.keysym.C\-M\-y: command:\e033[3;5;606t |
|
|
1047 | \& URxvt.keysym.C\-M\-e: command:\e033[3;1605;5t |
|
|
1048 | \& URxvt.keysym.C\-M\-c: command:\e033[3;1605;606t |
|
|
1049 | \& URxvt.keysym.C\-M\-p: perl:test |
|
|
1050 | .Ve |
|
|
1051 | .PP |
|
|
1052 | The first for keysym definitions allow me to quickly bring some windows |
|
|
1053 | in the layout I like most. Ion users might start laughing but will stop |
|
|
1054 | immediately when I tell them that I use my own Fvwm2 module for much the |
|
|
1055 | same effect as Ion provides, and I only very rarely use the above key |
|
|
1056 | combinations :\-> |
|
|
1057 | .PP |
|
|
1058 | \fIWhy doesn't rxvt-unicode read my resources?\fR |
|
|
1059 | .IX Subsection "Why doesn't rxvt-unicode read my resources?" |
|
|
1060 | .PP |
|
|
1061 | Well, why, indeed? It does, in a way very similar to other X |
|
|
1062 | applications. Most importantly, this means that if you or your \s-1OS\s0 loads |
|
|
1063 | resources into the X display (the right way to do it), rxvt-unicode will |
|
|
1064 | ignore any resource files in your home directory. It will only read |
|
|
1065 | \&\fI\f(CI$HOME\fI/.Xdefaults\fR when no resources are attached to the display. |
|
|
1066 | .PP |
|
|
1067 | If you have or use an \fI\f(CI$HOME\fI/.Xresources\fR file, chances are that |
|
|
1068 | resources are loaded into your X\-server. In this case, you have to |
|
|
1069 | re-login after every change (or run \fIxrdb \-merge \f(CI$HOME\fI/.Xresources\fR). |
|
|
1070 | .PP |
|
|
1071 | Also consider the form resources have to use: |
|
|
1072 | .PP |
|
|
1073 | .Vb 1 |
|
|
1074 | \& URxvt.resource: value |
|
|
1075 | .Ve |
|
|
1076 | .PP |
|
|
1077 | If you want to use another form (there are lots of different ways of |
|
|
1078 | specifying resources), make sure you understand wether and why it |
|
|
1079 | works. If unsure, use the form above. |
|
|
1080 | .PP |
425 | .IP "When I log-in to another system it tells me about missing terminfo data?" 4 |
1081 | \fIWhen I log-in to another system it tells me about missing terminfo data?\fR |
426 | .IX Item "When I log-in to another system it tells me about missing terminfo data?" |
1082 | .IX Subsection "When I log-in to another system it tells me about missing terminfo data?" |
|
|
1083 | .PP |
427 | The terminal description used by rxvt-unicode is not as widely available |
1084 | The terminal description used by rxvt-unicode is not as widely available |
428 | as that for xterm, or even rxvt (for which the same problem often arises). |
1085 | as that for xterm, or even rxvt (for which the same problem often arises). |
429 | .Sp |
1086 | .PP |
430 | The correct solution for this problem is to install the terminfo, this can |
1087 | The correct solution for this problem is to install the terminfo, this can |
431 | be done like this (with ncurses' infocmp): |
1088 | be done like this (with ncurses' infocmp): |
432 | .Sp |
1089 | .PP |
433 | .Vb 2 |
1090 | .Vb 2 |
434 | \& REMOTE=remotesystem.domain |
1091 | \& REMOTE=remotesystem.domain |
435 | \& infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
1092 | \& infocmp rxvt\-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
436 | .Ve |
1093 | .Ve |
437 | .Sp |
1094 | .PP |
438 | \&... or by installing rxvt-unicode normally on the remote system, |
1095 | \&... or by installing rxvt-unicode normally on the remote system, |
439 | .Sp |
1096 | .PP |
440 | If you cannot or do not want to do this, then you can simply set |
1097 | If you cannot or do not want to do this, then you can simply set |
441 | \&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of |
1098 | \&\f(CW\*(C`TERM=rxvt\*(C'\fR or even \f(CW\*(C`TERM=xterm\*(C'\fR, and live with the small number of |
442 | problems arising, which includes wrong keymapping, less and different |
1099 | problems arising, which includes wrong keymapping, less and different |
443 | colours and some refresh errors in fullscreen applications. It's a nice |
1100 | colours and some refresh errors in fullscreen applications. It's a nice |
444 | quick-and-dirty workaround for rare cases, though. |
1101 | quick-and-dirty workaround for rare cases, though. |
445 | .Sp |
1102 | .PP |
446 | If you always want to do this (and are fine with the consequences) you |
1103 | If you always want to do this (and are fine with the consequences) you |
447 | can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a |
1104 | can either recompile rxvt-unicode with the desired \s-1TERM\s0 value or use a |
448 | resource to set it: |
1105 | resource to set it: |
449 | .Sp |
1106 | .PP |
450 | .Vb 1 |
1107 | .Vb 1 |
451 | \& URxvt.termName: rxvt |
1108 | \& URxvt.termName: rxvt |
452 | .Ve |
1109 | .Ve |
453 | .Sp |
1110 | .PP |
454 | If you don't plan to use \fBrxvt\fR (quite common...) you could also replace |
1111 | If you don't plan to use \fBrxvt\fR (quite common...) you could also replace |
455 | the rxvt terminfo file with the rxvt-unicode one. |
1112 | the rxvt terminfo file with the rxvt-unicode one and use \f(CW\*(C`TERM=rxvt\*(C'\fR. |
456 | .ie n .IP """tic"" outputs some error when compiling the terminfo entry." 4 |
1113 | .PP |
457 | .el .IP "\f(CWtic\fR outputs some error when compiling the terminfo entry." 4 |
1114 | \fI\f(CI\*(C`tic\*(C'\fI outputs some error when compiling the terminfo entry.\fR |
458 | .IX Item "tic outputs some error when compiling the terminfo entry." |
1115 | .IX Subsection "tic outputs some error when compiling the terminfo entry." |
|
|
1116 | .PP |
459 | Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by |
1117 | Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by |
460 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
1118 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
461 | .ie n .IP """bash""'s readline does not work correctly under @@RXVT_NAME@@." 4 |
1119 | .PP |
462 | .el .IP "\f(CWbash\fR's readline does not work correctly under @@RXVT_NAME@@." 4 |
1120 | \fI\f(CI\*(C`bash\*(C'\fI's readline does not work correctly under @@URXVT_NAME@@.\fR |
463 | .IX Item "bash's readline does not work correctly under @@RXVT_NAME@@." |
1121 | .IX Subsection "bash's readline does not work correctly under @@URXVT_NAME@@." |
464 | .PD 0 |
1122 | .PP |
|
|
1123 | See next entry. |
|
|
1124 | .PP |
465 | .IP "I need a termcap file entry." 4 |
1125 | \fII need a termcap file entry.\fR |
466 | .IX Item "I need a termcap file entry." |
1126 | .IX Subsection "I need a termcap file entry." |
467 | .PD |
1127 | .PP |
468 | One reason you might want this is that some distributions or operating |
1128 | One reason you might want this is that some distributions or operating |
469 | systems still compile some programs using the long-obsoleted termcap |
1129 | systems still compile some programs using the long-obsoleted termcap |
470 | library (Fedora Core's bash is one example) and rely on a termcap entry |
1130 | library (Fedora Core's bash is one example) and rely on a termcap entry |
471 | for \f(CW\*(C`rxvt\-unicode\*(C'\fR. |
1131 | for \f(CW\*(C`rxvt\-unicode\*(C'\fR. |
472 | .Sp |
1132 | .PP |
473 | You could use rxvt's termcap entry with resonable results in many cases. |
1133 | You could use rxvt's termcap entry with resonable results in many cases. |
474 | You can also create a termcap entry by using terminfo's infocmp program |
1134 | You can also create a termcap entry by using terminfo's infocmp program |
475 | like this: |
1135 | like this: |
476 | .Sp |
1136 | .PP |
477 | .Vb 1 |
1137 | .Vb 1 |
478 | \& infocmp -C rxvt-unicode |
1138 | \& infocmp \-C rxvt\-unicode |
479 | .Ve |
1139 | .Ve |
480 | .Sp |
1140 | .PP |
481 | Or you could use this termcap entry, generated by the command above: |
1141 | Or you could use this termcap entry, generated by the command above: |
482 | .Sp |
1142 | .PP |
483 | .Vb 20 |
1143 | .Vb 10 |
484 | \& rxvt-unicode|rxvt-unicode terminal (X Window System):\e |
1144 | \& rxvt\-unicode|rxvt\-unicode terminal (X Window System):\e |
485 | \& :am:bw:eo:km:mi:ms:xn:xo:\e |
1145 | \& :am:bw:eo:km:mi:ms:xn:xo:\e |
486 | \& :co#80:it#8:li#24:lm#0:\e |
1146 | \& :co#80:it#8:li#24:lm#0:\e |
487 | \& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e |
1147 | \& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e |
488 | \& :K1=\eEOw:K2=\eEOu:K3=\eEOy:K4=\eEOq:K5=\eEOs:LE=\eE[%dD:\e |
1148 | \& :K1=\eEOw:K2=\eEOu:K3=\eEOy:K4=\eEOq:K5=\eEOs:LE=\eE[%dD:\e |
489 | \& :RI=\eE[%dC:SF=\eE[%dS:SR=\eE[%dT:UP=\eE[%dA:ae=\eE(B:al=\eE[L:\e |
1149 | \& :RI=\eE[%dC:SF=\eE[%dS:SR=\eE[%dT:UP=\eE[%dA:ae=\eE(B:al=\eE[L:\e |
… | |
… | |
500 | \& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e |
1160 | \& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e |
501 | \& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e |
1161 | \& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e |
502 | \& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e |
1162 | \& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e |
503 | \& :vs=\eE[?25h: |
1163 | \& :vs=\eE[?25h: |
504 | .Ve |
1164 | .Ve |
505 | .ie n .IP "Why does ""ls"" no longer have coloured output?" 4 |
1165 | .PP |
506 | .el .IP "Why does \f(CWls\fR no longer have coloured output?" 4 |
1166 | \fIWhy does \f(CI\*(C`ls\*(C'\fI no longer have coloured output?\fR |
507 | .IX Item "Why does ls no longer have coloured output?" |
1167 | .IX Subsection "Why does ls no longer have coloured output?" |
|
|
1168 | .PP |
508 | The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to |
1169 | The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to |
509 | decide wether a terminal has colour, but uses it's own configuration |
1170 | decide wether a terminal has colour, but uses its own configuration |
510 | file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in it's default file (among |
1171 | file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in its default file (among |
511 | with most other terminals supporting colour). Either add: |
1172 | with most other terminals supporting colour). Either add: |
512 | .Sp |
1173 | .PP |
513 | .Vb 1 |
1174 | .Vb 1 |
514 | \& TERM rxvt-unicode |
1175 | \& TERM rxvt\-unicode |
515 | .Ve |
1176 | .Ve |
516 | .Sp |
1177 | .PP |
517 | to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add: |
1178 | to \f(CW\*(C`/etc/DIR_COLORS\*(C'\fR or simply add: |
518 | .Sp |
1179 | .PP |
519 | .Vb 1 |
1180 | .Vb 1 |
520 | \& alias ls='ls --color=auto' |
1181 | \& alias ls='ls \-\-color=auto' |
521 | .Ve |
1182 | .Ve |
522 | .Sp |
1183 | .PP |
523 | to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR. |
1184 | to your \f(CW\*(C`.profile\*(C'\fR or \f(CW\*(C`.bashrc\*(C'\fR. |
|
|
1185 | .PP |
524 | .IP "Why doesn't vim/emacs etc. use the 88 colour mode?" 4 |
1186 | \fIWhy doesn't vim/emacs etc. use the 88 colour mode?\fR |
525 | .IX Item "Why doesn't vim/emacs etc. use the 88 colour mode?" |
1187 | .IX Subsection "Why doesn't vim/emacs etc. use the 88 colour mode?" |
526 | .PD 0 |
1188 | .PP |
|
|
1189 | See next entry. |
|
|
1190 | .PP |
527 | .IP "Why doesn't vim/emacs etc. make use of italic?" 4 |
1191 | \fIWhy doesn't vim/emacs etc. make use of italic?\fR |
528 | .IX Item "Why doesn't vim/emacs etc. make use of italic?" |
1192 | .IX Subsection "Why doesn't vim/emacs etc. make use of italic?" |
|
|
1193 | .PP |
|
|
1194 | See next entry. |
|
|
1195 | .PP |
529 | .IP "Why are the secondary screen-related options not working properly?" 4 |
1196 | \fIWhy are the secondary screen-related options not working properly?\fR |
530 | .IX Item "Why are the secondary screen-related options not working properly?" |
1197 | .IX Subsection "Why are the secondary screen-related options not working properly?" |
531 | .PD |
1198 | .PP |
532 | Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged |
1199 | Make sure you are using \f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR. Some pre-packaged |
533 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
1200 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
534 | by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra |
1201 | by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra |
535 | features. Unfortunately, some of these (most notably, again, Debian |
1202 | features. Unfortunately, some of these (most notably, again, Debian |
536 | GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo |
1203 | GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo |
537 | file, so you will need to install it on your own (See the question \fBWhen |
1204 | file, so you will need to install it on your own (See the question \fBWhen |
538 | I log-in to another system it tells me about missing terminfo data?\fR on |
1205 | I log-in to another system it tells me about missing terminfo data?\fR on |
539 | how to do this). |
1206 | how to do this). |
540 | .IP "My numerical keypad acts weird and generates differing output?" 4 |
1207 | .Sh "Encoding / Locale / Input Method Issues" |
541 | .IX Item "My numerical keypad acts weird and generates differing output?" |
1208 | .IX Subsection "Encoding / Locale / Input Method Issues" |
542 | Some Debian GNUL/Linux users seem to have this problem, although no |
|
|
543 | specific details were reported so far. It is possible that this is caused |
|
|
544 | by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how |
|
|
545 | this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible |
|
|
546 | keymap. See the answer to the previous question, and please report if that |
|
|
547 | helped. |
|
|
548 | .IP "Rxvt-unicode does not seem to understand the selected encoding?" 4 |
1209 | \fIRxvt-unicode does not seem to understand the selected encoding?\fR |
549 | .IX Item "Rxvt-unicode does not seem to understand the selected encoding?" |
1210 | .IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?" |
550 | .PD 0 |
1211 | .PP |
|
|
1212 | See next entry. |
|
|
1213 | .PP |
551 | .IP "Unicode does not seem to work?" 4 |
1214 | \fIUnicode does not seem to work?\fR |
552 | .IX Item "Unicode does not seem to work?" |
1215 | .IX Subsection "Unicode does not seem to work?" |
553 | .PD |
1216 | .PP |
554 | If you encounter strange problems like typing an accented character but |
1217 | If you encounter strange problems like typing an accented character but |
555 | getting two unrelated other characters or similar, or if program output is |
1218 | getting two unrelated other characters or similar, or if program output is |
556 | subtly garbled, then you should check your locale settings. |
1219 | subtly garbled, then you should check your locale settings. |
557 | .Sp |
1220 | .PP |
558 | Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the |
1221 | Rxvt-unicode must be started with the same \f(CW\*(C`LC_CTYPE\*(C'\fR setting as the |
559 | programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the |
1222 | programs. Often rxvt-unicode is started in the \f(CW\*(C`C\*(C'\fR locale, while the |
560 | login script running within the rxvt-unicode window changes the locale to |
1223 | login script running within the rxvt-unicode window changes the locale to |
561 | something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work. |
1224 | something else, e.g. \f(CW\*(C`en_GB.UTF\-8\*(C'\fR. Needless to say, this is not going to work. |
562 | .Sp |
1225 | .PP |
563 | The best thing is to fix your startup environment, as you will likely run |
1226 | The best thing is to fix your startup environment, as you will likely run |
564 | into other problems. If nothing works you can try this in your .profile. |
1227 | into other problems. If nothing works you can try this in your .profile. |
565 | .Sp |
1228 | .PP |
566 | .Vb 1 |
1229 | .Vb 1 |
567 | \& printf '\ee]701;%s\e007' "$LC_CTYPE" |
1230 | \& printf '\e33]701;%s\e007' "$LC_CTYPE" |
568 | .Ve |
1231 | .Ve |
569 | .Sp |
1232 | .PP |
570 | If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not |
1233 | If this doesn't work, then maybe you use a \f(CW\*(C`LC_CTYPE\*(C'\fR specification not |
571 | supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which |
1234 | supported on your systems. Some systems have a \f(CW\*(C`locale\*(C'\fR command which |
572 | displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as |
1235 | displays this (also, \f(CW\*(C`perl \-e0\*(C'\fR can be used to check locale settings, as |
573 | it will complain loudly if it cannot set the locale). If it displays something |
1236 | it will complain loudly if it cannot set the locale). If it displays something |
574 | like: |
1237 | like: |
575 | .Sp |
1238 | .PP |
576 | .Vb 1 |
1239 | .Vb 1 |
577 | \& locale: Cannot set LC_CTYPE to default locale: ... |
1240 | \& locale: Cannot set LC_CTYPE to default locale: ... |
578 | .Ve |
1241 | .Ve |
579 | .Sp |
1242 | .PP |
580 | Then the locale you specified is not supported on your system. |
1243 | Then the locale you specified is not supported on your system. |
581 | .Sp |
1244 | .PP |
582 | If nothing works and you are sure that everything is set correctly then |
1245 | If nothing works and you are sure that everything is set correctly then |
583 | you will need to remember a little known fact: Some programs just don't |
1246 | you will need to remember a little known fact: Some programs just don't |
584 | support locales :( |
1247 | support locales :( |
585 | .IP "Why do some characters look so much different than others?" 4 |
1248 | .PP |
586 | .IX Item "Why do some characters look so much different than others?" |
1249 | \fIHow does rxvt-unicode determine the encoding to use?\fR |
|
|
1250 | .IX Subsection "How does rxvt-unicode determine the encoding to use?" |
|
|
1251 | .PP |
|
|
1252 | See next entry. |
|
|
1253 | .PP |
|
|
1254 | \fIIs there an option to switch encodings?\fR |
|
|
1255 | .IX Subsection "Is there an option to switch encodings?" |
|
|
1256 | .PP |
|
|
1257 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
|
|
1258 | specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about |
|
|
1259 | \&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O. |
|
|
1260 | .PP |
|
|
1261 | The reasons is that there exists a perfectly fine mechanism for selecting |
|
|
1262 | the encoding, doing I/O and (most important) communicating this to all |
|
|
1263 | applications so everybody agrees on character properties such as width |
|
|
1264 | and code number. This mechanism is the \fIlocale\fR. Applications not using |
|
|
1265 | that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of |
|
|
1266 | characters wrong as it uses its own, locale-independent table under all |
|
|
1267 | locales). |
|
|
1268 | .PP |
|
|
1269 | Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All |
|
|
1270 | programs doing the same (that is, most) will automatically agree in the |
|
|
1271 | interpretation of characters. |
|
|
1272 | .PP |
|
|
1273 | Unfortunately, there is no system-independent way to select locales, nor |
|
|
1274 | is there a standard on how locale specifiers will look like. |
|
|
1275 | .PP |
|
|
1276 | On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable |
|
|
1277 | contains an arbitrary string which corresponds to an already-installed |
|
|
1278 | 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, |
|
|
1279 | \&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms |
|
|
1280 | (i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common. |
|
|
1281 | .PP |
|
|
1282 | Rxvt-unicode ignores all other locale categories, and except for |
|
|
1283 | the encoding, ignores country or language-specific settings, |
|
|
1284 | 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 |
|
|
1285 | rxvt\-unicode. |
|
|
1286 | .PP |
|
|
1287 | If you want to use a specific encoding you have to make sure you start |
|
|
1288 | rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category. |
|
|
1289 | .PP |
|
|
1290 | \fICan I switch locales at runtime?\fR |
|
|
1291 | .IX Subsection "Can I switch locales at runtime?" |
|
|
1292 | .PP |
|
|
1293 | Yes, using an escape sequence. Try something like this, which sets |
|
|
1294 | rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR. |
|
|
1295 | .PP |
|
|
1296 | .Vb 1 |
|
|
1297 | \& printf '\e33]701;%s\e007' ja_JP.SJIS |
|
|
1298 | .Ve |
|
|
1299 | .PP |
|
|
1300 | See also the previous answer. |
|
|
1301 | .PP |
|
|
1302 | Sometimes this capability is rather handy when you want to work in |
|
|
1303 | one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it |
|
|
1304 | (e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which |
|
|
1305 | first switches to a locale supported by xjdic and back later: |
|
|
1306 | .PP |
|
|
1307 | .Vb 3 |
|
|
1308 | \& printf '\e33]701;%s\e007' ja_JP.SJIS |
|
|
1309 | \& xjdic \-js |
|
|
1310 | \& printf '\e33]701;%s\e007' de_DE.UTF\-8 |
|
|
1311 | .Ve |
|
|
1312 | .PP |
|
|
1313 | You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except |
|
|
1314 | for some locales where character width differs between program\- and |
|
|
1315 | rxvt\-unicode\-locales. |
|
|
1316 | .PP |
|
|
1317 | \fII have problems getting my input method working.\fR |
|
|
1318 | .IX Subsection "I have problems getting my input method working." |
|
|
1319 | .PP |
|
|
1320 | Try a search engine, as this is slightly different for every input method server. |
|
|
1321 | .PP |
|
|
1322 | Here is a checklist: |
|
|
1323 | .IP "\- Make sure your locale \fIand\fR the imLocale are supported on your \s-1OS\s0." 4 |
|
|
1324 | .IX Item "- Make sure your locale and the imLocale are supported on your OS." |
|
|
1325 | Try \f(CW\*(C`locale \-a\*(C'\fR or check the documentation for your \s-1OS\s0. |
|
|
1326 | .IP "\- Make sure your locale or imLocale matches a locale supported by your \s-1XIM\s0." 4 |
|
|
1327 | .IX Item "- Make sure your locale or imLocale matches a locale supported by your XIM." |
|
|
1328 | For example, \fBkinput2\fR does not support \s-1UTF\-8\s0 locales, you should use |
|
|
1329 | \&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR or equivalent. |
|
|
1330 | .IP "\- Make sure your \s-1XIM\s0 server is actually running." 4 |
|
|
1331 | .IX Item "- Make sure your XIM server is actually running." |
587 | .PD 0 |
1332 | .PD 0 |
588 | .IP "How does rxvt-unicode choose fonts?" 4 |
1333 | .ie n .IP "\- Make sure the ""XMODIFIERS""\fR environment variable is set correctly when \fIstarting rxvt\-unicode." 4 |
589 | .IX Item "How does rxvt-unicode choose fonts?" |
1334 | .el .IP "\- Make sure the \f(CWXMODIFIERS\fR environment variable is set correctly when \fIstarting\fR rxvt\-unicode." 4 |
|
|
1335 | .IX Item "- Make sure the XMODIFIERS environment variable is set correctly when starting rxvt-unicode." |
590 | .PD |
1336 | .PD |
591 | Most fonts do not contain the full range of Unicode, which is |
1337 | When you want to use e.g. \fBkinput2\fR, it must be set to |
592 | fine. Chances are that the font you (or the admin/package maintainer of |
1338 | \&\f(CW\*(C`@im=kinput2\*(C'\fR. For \fBscim\fR, use \f(CW\*(C`@im=SCIM\*(C'\fR. Youc an see what input |
593 | your system/os) have specified does not cover all the characters you want |
1339 | method servers are running with this command: |
594 | to display. |
|
|
595 | .Sp |
|
|
596 | \&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement |
|
|
597 | font. Often the result is fine, but sometimes the chosen font looks |
|
|
598 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
|
|
599 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
|
|
600 | intelligence to detect that a specific glyph is wrong: it has to believe |
|
|
601 | the font that the characters it claims to contain indeed look correct. |
|
|
602 | .Sp |
|
|
603 | In that case, select a font of your taste and add it to the font list, |
|
|
604 | e.g.: |
|
|
605 | .Sp |
1340 | .Sp |
606 | .Vb 1 |
1341 | .Vb 1 |
607 | \& @@RXVT_NAME@@ -fn basefont,font2,font3... |
1342 | \& xprop \-root XIM_SERVERS |
608 | .Ve |
1343 | .Ve |
609 | .Sp |
1344 | .IP "" 4 |
610 | When rxvt-unicode sees a character, it will first look at the base |
1345 | .PP |
611 | font. If the base font does not contain the character, it will go to the |
1346 | \fIMy input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?\fR |
612 | next font, and so on. Specifying your own fonts will also speed up this |
1347 | .IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?" |
613 | search and use less resources within rxvt-unicode and the X\-server. |
1348 | .PP |
614 | .Sp |
1349 | You can specify separate locales for the input method and the rest of the |
615 | The only limitation is that none of the fonts may be larger than the base |
1350 | terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR: |
616 | font, as the base font defines the terminal character cell size, which |
1351 | .PP |
617 | must be the same due to the way terminals work. |
1352 | .Vb 1 |
618 | .IP "Why do some chinese characters look so different than others?" 4 |
1353 | \& URxvt.imlocale: ja_JP.EUC\-JP |
619 | .IX Item "Why do some chinese characters look so different than others?" |
1354 | .Ve |
620 | This is because there is a difference between script and language \*(-- |
1355 | .PP |
621 | rxvt-unicode does not know which language the text that is output is, |
1356 | Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still |
622 | as it only knows the unicode character codes. If rxvt-unicode first |
1357 | use your input method. Please note, however, that, depending on your Xlib |
623 | sees a japanese/chinese character, it might choose a japanese font for |
1358 | version, you may not be able to input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a |
624 | display. Subsequent japanese characters will use that font. Now, many |
1359 | normal way then, as your input method limits you. |
625 | chinese characters aren't represented in japanese fonts, so when the first |
1360 | .PP |
626 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
1361 | \fIRxvt-unicode crashes when the X Input Method changes or exits.\fR |
627 | \&\*(-- unfortunately at this point, it will still use the japanese font for |
1362 | .IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits." |
628 | chinese characters that are also in the japanese font. |
1363 | .PP |
629 | .Sp |
1364 | Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by |
630 | The workaround is easy: just tag a chinese font at the end of your font |
1365 | design. Applications can avoid some crashes at the expense of memory |
631 | list (see the previous question). The key is to view the font list as |
1366 | leaks, and Input Methods can avoid some crashes by careful ordering at |
632 | a preference list: If you expect more japanese, list a japanese font |
1367 | exit time. \fBkinput2\fR (and derived input methods) generally succeeds, |
633 | first. If you expect more chinese, put a chinese font first. |
1368 | while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however, |
634 | .Sp |
1369 | crashes cannot be completely avoided even if both sides cooperate. |
635 | In the future it might be possible to switch language preferences at |
1370 | .PP |
636 | runtime (the internal data structure has no problem with using different |
1371 | So the only workaround is not to kill your Input Method Servers. |
637 | fonts for the same character at the same time, but no interface for this |
1372 | .Sh "Operating Systems / Package Maintaining" |
638 | has been designed yet). |
1373 | .IX Subsection "Operating Systems / Package Maintaining" |
639 | .Sp |
1374 | \fII am using Debian GNU/Linux and have a problem...\fR |
640 | 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). |
1375 | .IX Subsection "I am using Debian GNU/Linux and have a problem..." |
641 | .IP "Why does rxvt-unicode sometimes leave pixel droppings?" 4 |
1376 | .PP |
642 | .IX Item "Why does rxvt-unicode sometimes leave pixel droppings?" |
1377 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
643 | Most fonts were not designed for terminal use, which means that character |
1378 | patches that considerably change the behaviour of rxvt-unicode (but |
644 | size varies a lot. A font that is otherwise fine for terminal use might |
1379 | unfortunately this notice has been removed). Before reporting a bug to |
645 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
1380 | the original rxvt-unicode author please download and install the genuine |
646 | these characters. For characters that are just \*(L"a bit\*(R" too wide a special |
1381 | version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce |
647 | \&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters. |
1382 | the problem. If you cannot, chances are that the problems are specific to |
648 | .Sp |
1383 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
649 | All of this requires that fonts do not lie about character sizes, |
1384 | Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug). |
650 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
1385 | .PP |
651 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
1386 | For other problems that also affect the Debian package, you can and |
652 | ask for the character bounding box, which unfortunately is wrong in these |
1387 | probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a |
653 | cases). |
1388 | bug in the Debian version and it serves as a reminder for other users that |
654 | .Sp |
1389 | might encounter the same issue. |
655 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
1390 | .PP |
656 | or the respective font. If you encounter this problem you might try using |
1391 | \fII am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?\fR |
657 | the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you |
1392 | .IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?" |
658 | might be forced to use a different font. |
1393 | .PP |
659 | .Sp |
1394 | You should build one binary with the default options. \fIconfigure\fR |
660 | All of this is not a problem when using X11 core fonts, as their bounding |
1395 | now enables most useful options, and the trend goes to making them |
661 | box data is correct. |
1396 | runtime\-switchable, too, so there is usually no drawback to enbaling them, |
|
|
1397 | except higher disk and possibly memory usage. The perl interpreter should |
|
|
1398 | be enabled, as important functionality (menus, selection, likely more in |
|
|
1399 | the future) depends on it. |
|
|
1400 | .PP |
|
|
1401 | You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources |
|
|
1402 | system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful |
|
|
1403 | behaviour. If your distribution aims at low memory, add an empty |
|
|
1404 | \&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the |
|
|
1405 | perl interpreter disabled until the user enables it. |
|
|
1406 | .PP |
|
|
1407 | If you can/want build more binaries, I recommend building a minimal |
|
|
1408 | one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with |
|
|
1409 | \&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of |
|
|
1410 | encodings built-in that increase download times and are rarely used). |
|
|
1411 | .PP |
|
|
1412 | \fII need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?\fR |
|
|
1413 | .IX Subsection "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?" |
|
|
1414 | .PP |
|
|
1415 | It should be, starting with release 7.1. You are encouraged to properly |
|
|
1416 | install urxvt with privileges necessary for your \s-1OS\s0 now. |
|
|
1417 | .PP |
|
|
1418 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
|
|
1419 | into a helper process for privileged operations (pty handling on some |
|
|
1420 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
|
|
1421 | immediately. This is much safer than most other terminals that keep |
|
|
1422 | privileges while running (but is more relevant to urxvt, as it contains |
|
|
1423 | things as perl interpreters, which might be \*(L"helpful\*(R" to attackers). |
|
|
1424 | .PP |
|
|
1425 | This forking is done as the very first within \fImain()\fR, which is very early |
|
|
1426 | and reduces possible bugs to initialisation code run before \fImain()\fR, or |
|
|
1427 | things like the dynamic loader of your system, which should result in very |
|
|
1428 | little risk. |
|
|
1429 | .PP |
662 | .IP "On Solaris 9, many line-drawing characters are too wide." 4 |
1430 | \fIOn Solaris 9, many line-drawing characters are too wide.\fR |
663 | .IX Item "On Solaris 9, many line-drawing characters are too wide." |
1431 | .IX Subsection "On Solaris 9, many line-drawing characters are too wide." |
|
|
1432 | .PP |
664 | Seems to be a known bug, read |
1433 | Seems to be a known bug, read |
665 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
1434 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
666 | following ugly workaround to get non-double-wide-characters working: |
1435 | following ugly workaround to get non-double-wide-characters working: |
667 | .Sp |
1436 | .PP |
668 | .Vb 1 |
1437 | .Vb 1 |
669 | \& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
1438 | \& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
670 | .Ve |
1439 | .Ve |
671 | .IP "My Compose (Multi_key) key is no longer working." 4 |
1440 | .PP |
672 | .IX Item "My Compose (Multi_key) key is no longer working." |
|
|
673 | The most common causes for this are that either your locale is not set |
|
|
674 | correctly, or you specified a \fBpreeditStyle\fR that is not supported by |
|
|
675 | your input method. For example, if you specified \fBOverTheSpot\fR and |
|
|
676 | your input method (e.g. the default input method handling Compose keys) |
|
|
677 | does not support this (for instance because it is not visual), then |
|
|
678 | rxvt-unicode will continue without an input method. |
|
|
679 | .Sp |
|
|
680 | In this case either do not specify a \fBpreeditStyle\fR or specify more than |
|
|
681 | one pre-edit style, such as \fBOverTheSpot,Root,None\fR. |
|
|
682 | .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 |
|
|
683 | .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 |
|
|
684 | .IX Item "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755" |
|
|
685 | Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on |
|
|
686 | international keyboards) or simply use \s-1ISO\s0 14755 support to your |
|
|
687 | advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other |
|
|
688 | codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape |
|
|
689 | character and so on. |
|
|
690 | .IP "How can I keep rxvt-unicode from using reverse video so much?" 4 |
|
|
691 | .IX Item "How can I keep rxvt-unicode from using reverse video so much?" |
|
|
692 | First of all, make sure you are running with the right terminal settings |
|
|
693 | (\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then |
|
|
694 | make sure you have specified colours for italic and bold, as otherwise |
|
|
695 | rxvt-unicode might use reverse video to simulate the effect: |
|
|
696 | .Sp |
|
|
697 | .Vb 2 |
|
|
698 | \& URxvt.colorBD: white |
|
|
699 | \& URxvt.colorIT: green |
|
|
700 | .Ve |
|
|
701 | .IP "Some programs assume totally weird colours (red instead of blue), how can I fix that?" 4 |
|
|
702 | .IX Item "Some programs assume totally weird colours (red instead of blue), how can I fix that?" |
|
|
703 | For some unexplainable reason, some rare programs assume a very weird |
|
|
704 | colour palette when confronted with a terminal with more than the standard |
|
|
705 | 8 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix |
|
|
706 | these programs not to assume non-ISO colours without very good reasons. |
|
|
707 | .Sp |
|
|
708 | In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo |
|
|
709 | definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will |
|
|
710 | fix colours but keep you from using other rxvt-unicode features. |
|
|
711 | .IP "I am on FreeBSD and rxvt-unicode does not seem to work at all." 4 |
1441 | \fII am on FreeBSD and rxvt-unicode does not seem to work at all.\fR |
712 | .IX Item "I am on FreeBSD and rxvt-unicode does not seem to work at all." |
1442 | .IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all." |
|
|
1443 | .PP |
713 | Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined |
1444 | Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined |
714 | in your compile environment, or an implementation that implements it, |
1445 | in your compile environment, or an implementation that implements it, |
715 | wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that |
1446 | wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that |
716 | \&\fBwchar_t\fR is represented as unicode. |
1447 | \&\fBwchar_t\fR is represented as unicode. |
717 | .Sp |
1448 | .PP |
718 | As you might have guessed, FreeBSD does neither define this symobl nor |
1449 | As you might have guessed, FreeBSD does neither define this symobl nor |
719 | does it support it. Instead, it uses it's own internal representation of |
1450 | does it support it. Instead, it uses its own internal representation of |
720 | \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. |
1451 | \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. |
721 | .Sp |
1452 | .PP |
722 | However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and |
1453 | However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and |
723 | \&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. |
1454 | \&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. |
724 | .Sp |
1455 | .PP |
725 | \&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language |
1456 | \&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language |
726 | apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized) |
1457 | apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized) |
727 | representation of \fBwchar_t\fR makes it impossible to convert between |
1458 | representation of \fBwchar_t\fR makes it impossible to convert between |
728 | \&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding |
1459 | \&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding |
729 | without implementing OS-specific-wrappers for each and every locale. There |
1460 | without implementing OS-specific-wrappers for each and every locale. There |
730 | simply are no APIs to convert \fBwchar_t\fR into anything except the current |
1461 | simply are no APIs to convert \fBwchar_t\fR into anything except the current |
731 | locale encoding. |
1462 | locale encoding. |
732 | .Sp |
1463 | .PP |
733 | Some applications (such as the formidable \fBmlterm\fR) work around this |
1464 | Some applications (such as the formidable \fBmlterm\fR) work around this |
734 | by carrying their own replacement functions for character set handling |
1465 | by carrying their own replacement functions for character set handling |
735 | with them, and either implementing OS-dependent hacks or doing multiple |
1466 | with them, and either implementing OS-dependent hacks or doing multiple |
736 | conversions (which is slow and unreliable in case the \s-1OS\s0 implements |
1467 | conversions (which is slow and unreliable in case the \s-1OS\s0 implements |
737 | encodings slightly different than the terminal emulator). |
1468 | encodings slightly different than the terminal emulator). |
738 | .Sp |
1469 | .PP |
739 | The rxvt-unicode author insists that the right way to fix this is in the |
1470 | The rxvt-unicode author insists that the right way to fix this is in the |
740 | system libraries once and for all, instead of forcing every app to carry |
1471 | system libraries once and for all, instead of forcing every app to carry |
741 | complete replacements for them :) |
1472 | complete replacements for them :) |
|
|
1473 | .PP |
742 | .IP "I use Solaris 9 and it doesn't compile/work/etc." 4 |
1474 | \fII use Solaris 9 and it doesn't compile/work/etc.\fR |
743 | .IX Item "I use Solaris 9 and it doesn't compile/work/etc." |
1475 | .IX Subsection "I use Solaris 9 and it doesn't compile/work/etc." |
|
|
1476 | .PP |
744 | Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst |
1477 | Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst |
745 | problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem. |
1478 | problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem. |
|
|
1479 | .PP |
746 | .IP "How can I use rxvt-unicode under cygwin?" 4 |
1480 | \fIHow can I use rxvt-unicode under cygwin?\fR |
747 | .IX Item "How can I use rxvt-unicode under cygwin?" |
1481 | .IX Subsection "How can I use rxvt-unicode under cygwin?" |
|
|
1482 | .PP |
748 | rxvt-unicode should compile and run out of the box on cygwin, using |
1483 | rxvt-unicode should compile and run out of the box on cygwin, using |
749 | the X11 libraries that come with cygwin. libW11 emulation is no |
1484 | the X11 libraries that come with cygwin. libW11 emulation is no |
750 | longer supported (and makes no sense, either, as it only supported a |
1485 | longer supported (and makes no sense, either, as it only supported a |
751 | single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or |
1486 | single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or |
752 | \&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the |
1487 | \&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the |
753 | old libW11 emulation. |
1488 | old libW11 emulation. |
754 | .Sp |
1489 | .PP |
755 | At the time of this writing, cygwin didn't seem to support any multi-byte |
1490 | At the time of this writing, cygwin didn't seem to support any multi-byte |
756 | encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited |
1491 | encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited |
757 | to 8\-bit encodings. |
1492 | to 8\-bit encodings. |
758 | .IP "How does rxvt-unicode determine the encoding to use?" 4 |
|
|
759 | .IX Item "How does rxvt-unicode determine the encoding to use?" |
|
|
760 | .PD 0 |
|
|
761 | .IP "Is there an option to switch encodings?" 4 |
|
|
762 | .IX Item "Is there an option to switch encodings?" |
|
|
763 | .PD |
|
|
764 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
|
|
765 | specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about |
|
|
766 | \&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O. |
|
|
767 | .Sp |
|
|
768 | The reasons is that there exists a perfectly fine mechanism for selecting |
|
|
769 | the encoding, doing I/O and (most important) communicating this to all |
|
|
770 | applications so everybody agrees on character properties such as width |
|
|
771 | and code number. This mechanism is the \fIlocale\fR. Applications not using |
|
|
772 | that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of |
|
|
773 | characters wrong as it uses it's own, locale-independent table under all |
|
|
774 | locales). |
|
|
775 | .Sp |
|
|
776 | Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All |
|
|
777 | programs doing the same (that is, most) will automatically agree in the |
|
|
778 | interpretation of characters. |
|
|
779 | .Sp |
|
|
780 | Unfortunately, there is no system-independent way to select locales, nor |
|
|
781 | is there a standard on how locale specifiers will look like. |
|
|
782 | .Sp |
|
|
783 | On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable |
|
|
784 | contains an arbitrary string which corresponds to an already-installed |
|
|
785 | 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, |
|
|
786 | \&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms |
|
|
787 | (i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common. |
|
|
788 | .Sp |
|
|
789 | Rxvt-unicode ignores all other locale categories, and except for |
|
|
790 | the encoding, ignores country or language-specific settings, |
|
|
791 | 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 |
|
|
792 | rxvt\-unicode. |
|
|
793 | .Sp |
|
|
794 | If you want to use a specific encoding you have to make sure you start |
|
|
795 | rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category. |
|
|
796 | .IP "Can I switch locales at runtime?" 4 |
|
|
797 | .IX Item "Can I switch locales at runtime?" |
|
|
798 | Yes, using an escape sequence. Try something like this, which sets |
|
|
799 | rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR. |
|
|
800 | .Sp |
|
|
801 | .Vb 1 |
|
|
802 | \& printf '\ee]701;%s\e007' ja_JP.SJIS |
|
|
803 | .Ve |
|
|
804 | .Sp |
|
|
805 | See also the previous answer. |
|
|
806 | .Sp |
|
|
807 | Sometimes this capability is rather handy when you want to work in |
|
|
808 | one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it |
|
|
809 | (e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which |
|
|
810 | first switches to a locale supported by xjdic and back later: |
|
|
811 | .Sp |
|
|
812 | .Vb 3 |
|
|
813 | \& printf '\ee]701;%s\e007' ja_JP.SJIS |
|
|
814 | \& xjdic -js |
|
|
815 | \& printf '\ee]701;%s\e007' de_DE.UTF-8 |
|
|
816 | .Ve |
|
|
817 | .Sp |
|
|
818 | You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except |
|
|
819 | for some locales where character width differs between program\- and |
|
|
820 | rxvt\-unicode\-locales. |
|
|
821 | .IP "Can I switch the fonts at runtime?" 4 |
|
|
822 | .IX Item "Can I switch the fonts at runtime?" |
|
|
823 | Yes, using an escape sequence. Try something like this, which has the same |
|
|
824 | effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately: |
|
|
825 | .Sp |
|
|
826 | .Vb 1 |
|
|
827 | \& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic" |
|
|
828 | .Ve |
|
|
829 | .Sp |
|
|
830 | This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
831 | japanese font), but you have to switch to chinese temporarily, where |
|
|
832 | japanese fonts would only be in your way. |
|
|
833 | .Sp |
|
|
834 | You can think of this as a kind of manual \s-1ISO\-2022\s0 switching. |
|
|
835 | .IP "Why do italic characters look as if clipped?" 4 |
|
|
836 | .IX Item "Why do italic characters look as if clipped?" |
|
|
837 | Many fonts have difficulties with italic characters and hinting. For |
|
|
838 | example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans |
|
|
839 | Mono\*(C'\fR completely fails in it's italic face. A workaround might be to |
|
|
840 | enable freetype autohinting, i.e. like this: |
|
|
841 | .Sp |
|
|
842 | .Vb 2 |
|
|
843 | \& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
844 | \& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
845 | .Ve |
|
|
846 | .IP "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?" 4 |
|
|
847 | .IX Item "My input method wants <some encoding> but I want UTF-8, what can I do?" |
|
|
848 | You can specify separate locales for the input method and the rest of the |
|
|
849 | terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR: |
|
|
850 | .Sp |
|
|
851 | .Vb 1 |
|
|
852 | \& URxvt.imlocale: ja_JP.EUC-JP |
|
|
853 | .Ve |
|
|
854 | .Sp |
|
|
855 | Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still |
|
|
856 | use your input method. Please note, however, that you will not be able to |
|
|
857 | input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input |
|
|
858 | method limits you. |
|
|
859 | .IP "Rxvt-unicode crashes when the X Input Method changes or exits." 4 |
|
|
860 | .IX Item "Rxvt-unicode crashes when the X Input Method changes or exits." |
|
|
861 | Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by |
|
|
862 | design. Applications can avoid some crashes at the expense of memory |
|
|
863 | leaks, and Input Methods can avoid some crashes by careful ordering at |
|
|
864 | exit time. \fBkinput2\fR (and derived input methods) generally succeeds, |
|
|
865 | while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however, |
|
|
866 | crashes cannot be completely avoided even if both sides cooperate. |
|
|
867 | .Sp |
|
|
868 | So the only workaround is not to kill your Input Method Servers. |
|
|
869 | .IP "Rxvt-unicode uses gobs of memory, how can I reduce that?" 4 |
|
|
870 | .IX Item "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
|
|
871 | Rxvt-unicode tries to obey the rule of not charging you for something you |
|
|
872 | don't use. One thing you should try is to configure out all settings that |
|
|
873 | you don't need, for example, Xft support is a resource hog by design, |
|
|
874 | when used. Compiling it out ensures that no Xft font will be loaded |
|
|
875 | accidentally when rxvt-unicode tries to find a font for your characters. |
|
|
876 | .Sp |
|
|
877 | Also, many people (me included) like large windows and even larger |
|
|
878 | scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use |
|
|
879 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
|
|
880 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
|
|
881 | use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as |
|
|
882 | rxvt-unicode then uses 8 bytes per screen cell. |
|
|
883 | .IP "Can I speed up Xft rendering somehow?" 4 |
|
|
884 | .IX Item "Can I speed up Xft rendering somehow?" |
|
|
885 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
886 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
887 | antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of |
|
|
888 | memory and also speeds up rendering considerably. |
|
|
889 | .IP "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 4 |
|
|
890 | .IX Item "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" |
|
|
891 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
892 | fall back to it's default font search list it will prefer X11 core |
|
|
893 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
894 | antialiasing disabled for most of them, because the author thinks they |
|
|
895 | look best that way. |
|
|
896 | .Sp |
|
|
897 | If you want antialiasing, you have to specify the fonts manually. |
|
|
898 | .IP "Mouse cut/paste suddenly no longer works." 4 |
|
|
899 | .IX Item "Mouse cut/paste suddenly no longer works." |
|
|
900 | Make sure that mouse reporting is actually turned off since killing |
|
|
901 | some editors prematurely may leave the mouse in mouse report mode. I've |
|
|
902 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
|
|
903 | quick check is to see if cut/paste works when the Alt or Shift keys are |
|
|
904 | depressed. |
|
|
905 | .IP "What's with this bold/blink stuff?" 4 |
|
|
906 | .IX Item "What's with this bold/blink stuff?" |
|
|
907 | If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the |
|
|
908 | standard foreground colour. |
|
|
909 | .Sp |
|
|
910 | For the standard background colour, blinking will actually make the |
|
|
911 | text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard |
|
|
912 | colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be |
|
|
913 | ignored. |
|
|
914 | .Sp |
|
|
915 | On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity |
|
|
916 | foreground/background colors. |
|
|
917 | .Sp |
|
|
918 | color0\-7 are the low-intensity colors. |
|
|
919 | .Sp |
|
|
920 | color8\-15 are the corresponding high-intensity colors. |
|
|
921 | .IP "I don't like the screen colors. How do I change them?" 4 |
|
|
922 | .IX Item "I don't like the screen colors. How do I change them?" |
|
|
923 | You can change the screen colors at run-time using \fI~/.Xdefaults\fR |
|
|
924 | resources (or as long\-options). |
|
|
925 | .Sp |
|
|
926 | Here are values that are supposed to resemble a \s-1VGA\s0 screen, |
|
|
927 | including the murky brown that passes for low-intensity yellow: |
|
|
928 | .Sp |
|
|
929 | .Vb 8 |
|
|
930 | \& URxvt.color0: #000000 |
|
|
931 | \& URxvt.color1: #A80000 |
|
|
932 | \& URxvt.color2: #00A800 |
|
|
933 | \& URxvt.color3: #A8A800 |
|
|
934 | \& URxvt.color4: #0000A8 |
|
|
935 | \& URxvt.color5: #A800A8 |
|
|
936 | \& URxvt.color6: #00A8A8 |
|
|
937 | \& URxvt.color7: #A8A8A8 |
|
|
938 | .Ve |
|
|
939 | .Sp |
|
|
940 | .Vb 8 |
|
|
941 | \& URxvt.color8: #000054 |
|
|
942 | \& URxvt.color9: #FF0054 |
|
|
943 | \& URxvt.color10: #00FF54 |
|
|
944 | \& URxvt.color11: #FFFF54 |
|
|
945 | \& URxvt.color12: #0000FF |
|
|
946 | \& URxvt.color13: #FF00FF |
|
|
947 | \& URxvt.color14: #00FFFF |
|
|
948 | \& URxvt.color15: #FFFFFF |
|
|
949 | .Ve |
|
|
950 | .Sp |
|
|
951 | And here is a more complete set of non-standard colors described (not by |
|
|
952 | me) as \*(L"pretty girly\*(R". |
|
|
953 | .Sp |
|
|
954 | .Vb 18 |
|
|
955 | \& URxvt.cursorColor: #dc74d1 |
|
|
956 | \& URxvt.pointerColor: #dc74d1 |
|
|
957 | \& URxvt.background: #0e0e0e |
|
|
958 | \& URxvt.foreground: #4ad5e1 |
|
|
959 | \& URxvt.color0: #000000 |
|
|
960 | \& URxvt.color8: #8b8f93 |
|
|
961 | \& URxvt.color1: #dc74d1 |
|
|
962 | \& URxvt.color9: #dc74d1 |
|
|
963 | \& URxvt.color2: #0eb8c7 |
|
|
964 | \& URxvt.color10: #0eb8c7 |
|
|
965 | \& URxvt.color3: #dfe37e |
|
|
966 | \& URxvt.color11: #dfe37e |
|
|
967 | \& URxvt.color5: #9e88f0 |
|
|
968 | \& URxvt.color13: #9e88f0 |
|
|
969 | \& URxvt.color6: #73f7ff |
|
|
970 | \& URxvt.color14: #73f7ff |
|
|
971 | \& URxvt.color7: #e1dddd |
|
|
972 | \& URxvt.color15: #e1dddd |
|
|
973 | .Ve |
|
|
974 | .IP "How can I start @@RXVT_NAME@@d in a race-free way?" 4 |
|
|
975 | .IX Item "How can I start @@RXVT_NAME@@d in a race-free way?" |
|
|
976 | Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the |
|
|
977 | display, create the listening socket and then fork. |
|
|
978 | .IP "What's with the strange Backspace/Delete key behaviour?" 4 |
|
|
979 | .IX Item "What's with the strange Backspace/Delete key behaviour?" |
|
|
980 | Assuming that the physical Backspace key corresponds to the |
|
|
981 | BackSpace keysym (not likely for Linux ... see the following |
|
|
982 | question) there are two standard values that can be used for |
|
|
983 | Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR. |
|
|
984 | .Sp |
|
|
985 | Historically, either value is correct, but rxvt-unicode adopts the debian |
|
|
986 | policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct |
|
|
987 | choice :). |
|
|
988 | .Sp |
|
|
989 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
|
|
990 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
|
|
991 | started from a terminal (say, from a menu or by remote shell), then the |
|
|
992 | system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will |
|
|
993 | be used (which may not be the same as your stty setting). |
|
|
994 | .Sp |
|
|
995 | For starting a new rxvt\-unicode: |
|
|
996 | .Sp |
|
|
997 | .Vb 3 |
|
|
998 | \& # use Backspace = ^H |
|
|
999 | \& $ stty erase ^H |
|
|
1000 | \& $ @@RXVT_NAME@@ |
|
|
1001 | .Ve |
|
|
1002 | .Sp |
|
|
1003 | .Vb 3 |
|
|
1004 | \& # use Backspace = ^? |
|
|
1005 | \& $ stty erase ^? |
|
|
1006 | \& $ @@RXVT_NAME@@ |
|
|
1007 | .Ve |
|
|
1008 | .Sp |
|
|
1009 | Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. |
|
|
1010 | .Sp |
|
|
1011 | For an existing rxvt\-unicode: |
|
|
1012 | .Sp |
|
|
1013 | .Vb 3 |
|
|
1014 | \& # use Backspace = ^H |
|
|
1015 | \& $ stty erase ^H |
|
|
1016 | \& $ echo -n "^[[36h" |
|
|
1017 | .Ve |
|
|
1018 | .Sp |
|
|
1019 | .Vb 3 |
|
|
1020 | \& # use Backspace = ^? |
|
|
1021 | \& $ stty erase ^? |
|
|
1022 | \& $ echo -n "^[[36l" |
|
|
1023 | .Ve |
|
|
1024 | .Sp |
|
|
1025 | This helps satisfy some of the Backspace discrepancies that occur, but |
|
|
1026 | if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value |
|
|
1027 | properly reflects that. |
|
|
1028 | .Sp |
|
|
1029 | The Delete key is a another casualty of the ill-defined Backspace problem. |
|
|
1030 | To avoid confusion between the Backspace and Delete keys, the Delete |
|
|
1031 | key has been assigned an escape sequence to match the vt100 for Execute |
|
|
1032 | (\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo. |
|
|
1033 | .Sp |
|
|
1034 | Some other Backspace problems: |
|
|
1035 | .Sp |
|
|
1036 | some editors use termcap/terminfo, |
|
|
1037 | some editors (vim I'm told) expect Backspace = ^H, |
|
|
1038 | \&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help. |
|
|
1039 | .Sp |
|
|
1040 | Perhaps someday this will all be resolved in a consistent manner. |
|
|
1041 | .IP "I don't like the key\-bindings. How do I change them?" 4 |
|
|
1042 | .IX Item "I don't like the key-bindings. How do I change them?" |
|
|
1043 | There are some compile-time selections available via configure. Unless |
|
|
1044 | you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can |
|
|
1045 | use the `keysym' resource to alter the keystrings associated with keysyms. |
|
|
1046 | .Sp |
|
|
1047 | Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR |
|
|
1048 | .Sp |
|
|
1049 | .Vb 20 |
|
|
1050 | \& URxvt.keysym.Home: \e033[1~ |
|
|
1051 | \& URxvt.keysym.End: \e033[4~ |
|
|
1052 | \& URxvt.keysym.C-apostrophe: \e033<C-'> |
|
|
1053 | \& URxvt.keysym.C-slash: \e033<C-/> |
|
|
1054 | \& URxvt.keysym.C-semicolon: \e033<C-;> |
|
|
1055 | \& URxvt.keysym.C-grave: \e033<C-`> |
|
|
1056 | \& URxvt.keysym.C-comma: \e033<C-,> |
|
|
1057 | \& URxvt.keysym.C-period: \e033<C-.> |
|
|
1058 | \& URxvt.keysym.C-0x60: \e033<C-`> |
|
|
1059 | \& URxvt.keysym.C-Tab: \e033<C-Tab> |
|
|
1060 | \& URxvt.keysym.C-Return: \e033<C-Return> |
|
|
1061 | \& URxvt.keysym.S-Return: \e033<S-Return> |
|
|
1062 | \& URxvt.keysym.S-space: \e033<S-Space> |
|
|
1063 | \& URxvt.keysym.M-Up: \e033<M-Up> |
|
|
1064 | \& URxvt.keysym.M-Down: \e033<M-Down> |
|
|
1065 | \& URxvt.keysym.M-Left: \e033<M-Left> |
|
|
1066 | \& URxvt.keysym.M-Right: \e033<M-Right> |
|
|
1067 | \& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 > |
|
|
1068 | \& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
1069 | \& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007 |
|
|
1070 | .Ve |
|
|
1071 | .Sp |
|
|
1072 | See some more examples in the documentation for the \fBkeysym\fR resource. |
|
|
1073 | .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 |
|
|
1074 | .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." |
|
|
1075 | .Vb 6 |
|
|
1076 | \& KP_Insert == Insert |
|
|
1077 | \& F22 == Print |
|
|
1078 | \& F27 == Home |
|
|
1079 | \& F29 == Prior |
|
|
1080 | \& F33 == End |
|
|
1081 | \& F35 == Next |
|
|
1082 | .Ve |
|
|
1083 | .Sp |
|
|
1084 | Rather than have rxvt-unicode try to accommodate all the various possible |
|
|
1085 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
|
|
1086 | required for your particular machine. |
|
|
1087 | .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 |
|
|
1088 | .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." |
|
|
1089 | rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can |
|
|
1090 | check and see if that is set. Note that several programs, \s-1JED\s0, slrn, |
|
|
1091 | Midnight Commander automatically check this variable to decide whether or |
|
|
1092 | not to use color. |
|
|
1093 | .IP "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?" 4 |
|
|
1094 | .IX Item "How do I set the correct, full IP address for the DISPLAY variable?" |
|
|
1095 | If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled |
|
|
1096 | insecure mode then it is possible to use the following shell script |
|
|
1097 | snippets to correctly set the display. If your version of rxvt-unicode |
|
|
1098 | wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then |
|
|
1099 | the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a |
|
|
1100 | regular xterm. |
|
|
1101 | .Sp |
|
|
1102 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
|
|
1103 | snippets: |
|
|
1104 | .Sp |
|
|
1105 | .Vb 12 |
|
|
1106 | \& # Bourne/Korn/POSIX family of shells: |
|
|
1107 | \& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
|
|
1108 | \& if [ ${TERM:-foo} = xterm ]; then |
|
|
1109 | \& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
|
|
1110 | \& echo -n '^[Z' |
|
|
1111 | \& read term_id |
|
|
1112 | \& stty icanon echo |
|
|
1113 | \& if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
|
|
1114 | \& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
|
|
1115 | \& read DISPLAY # set it in our local shell |
|
|
1116 | \& fi |
|
|
1117 | \& fi |
|
|
1118 | .Ve |
|
|
1119 | .IP "How do I compile the manual pages for myself?" 4 |
|
|
1120 | .IX Item "How do I compile the manual pages for myself?" |
|
|
1121 | You need to have a recent version of perl installed as \fI/usr/bin/perl\fR, |
|
|
1122 | one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to |
|
|
1123 | the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR. |
|
|
1124 | .IP "My question isn't answered here, can I ask a human?" 4 |
|
|
1125 | .IX Item "My question isn't answered here, can I ask a human?" |
|
|
1126 | Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR, |
|
|
1127 | channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be |
|
|
1128 | interested in learning about new and exciting problems (but not FAQs :). |
|
|
1129 | .SH "RXVT TECHNICAL REFERENCE" |
1493 | .SH "RXVT-UNICODE TECHNICAL REFERENCE" |
1130 | .IX Header "RXVT TECHNICAL REFERENCE" |
1494 | .IX Header "RXVT-UNICODE TECHNICAL REFERENCE" |
1131 | .SH "DESCRIPTION" |
|
|
1132 | .IX Header "DESCRIPTION" |
|
|
1133 | The rest of this document describes various technical aspects of |
1495 | The rest of this document describes various technical aspects of |
1134 | \&\fBrxvt-unicode\fR. First the description of supported command sequences, |
1496 | \&\fBrxvt-unicode\fR. First the description of supported command sequences, |
1135 | followed by pixmap support and last by a description of all features |
1497 | followed by pixmap support and last by a description of all features |
1136 | selectable at \f(CW\*(C`configure\*(C'\fR time. |
1498 | selectable at \f(CW\*(C`configure\*(C'\fR time. |
1137 | .SH "Definitions" |
1499 | .Sh "Definitions" |
1138 | .IX Header "Definitions" |
1500 | .IX Subsection "Definitions" |
1139 | .ie n .IP "\fB\fB""c""\fB\fR" 4 |
1501 | .ie n .IP "\fB\fB""c""\fB\fR" 4 |
1140 | .el .IP "\fB\f(CBc\fB\fR" 4 |
1502 | .el .IP "\fB\f(CBc\fB\fR" 4 |
1141 | .IX Item "c" |
1503 | .IX Item "c" |
1142 | The literal character c. |
1504 | The literal character c. |
1143 | .ie n .IP "\fB\fB""C""\fB\fR" 4 |
1505 | .ie n .IP "\fB\fB""C""\fB\fR" 4 |
… | |
… | |
1156 | parameters, separated by \f(CW\*(C`;\*(C'\fR character(s). |
1518 | parameters, separated by \f(CW\*(C`;\*(C'\fR character(s). |
1157 | .ie n .IP "\fB\fB""Pt""\fB\fR" 4 |
1519 | .ie n .IP "\fB\fB""Pt""\fB\fR" 4 |
1158 | .el .IP "\fB\f(CBPt\fB\fR" 4 |
1520 | .el .IP "\fB\f(CBPt\fB\fR" 4 |
1159 | .IX Item "Pt" |
1521 | .IX Item "Pt" |
1160 | A text parameter composed of printable characters. |
1522 | A text parameter composed of printable characters. |
1161 | .SH "Values" |
1523 | .Sh "Values" |
1162 | .IX Header "Values" |
1524 | .IX Subsection "Values" |
1163 | .ie n .IP "\fB\fB""ENQ""\fB\fR" 4 |
1525 | .ie n .IP "\fB\fB""ENQ""\fB\fR" 4 |
1164 | .el .IP "\fB\f(CBENQ\fB\fR" 4 |
1526 | .el .IP "\fB\f(CBENQ\fB\fR" 4 |
1165 | .IX Item "ENQ" |
1527 | .IX Item "ENQ" |
1166 | Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0) |
1528 | Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0) |
1167 | request attributes from terminal. See \fB\f(CB\*(C`ESC [ Ps c\*(C'\fB\fR. |
1529 | request attributes from terminal. See \fB\f(CB\*(C`ESC [ Ps c\*(C'\fB\fR. |
… | |
… | |
1205 | Switch to Standard Character Set |
1567 | Switch to Standard Character Set |
1206 | .ie n .IP "\fB\fB""SPC""\fB\fR" 4 |
1568 | .ie n .IP "\fB\fB""SPC""\fB\fR" 4 |
1207 | .el .IP "\fB\f(CBSPC\fB\fR" 4 |
1569 | .el .IP "\fB\f(CBSPC\fB\fR" 4 |
1208 | .IX Item "SPC" |
1570 | .IX Item "SPC" |
1209 | Space Character |
1571 | Space Character |
1210 | .SH "Escape Sequences" |
1572 | .Sh "Escape Sequences" |
1211 | .IX Header "Escape Sequences" |
1573 | .IX Subsection "Escape Sequences" |
1212 | .ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4 |
1574 | .ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4 |
1213 | .el .IP "\fB\f(CBESC # 8\fB\fR" 4 |
1575 | .el .IP "\fB\f(CBESC # 8\fB\fR" 4 |
1214 | .IX Item "ESC # 8" |
1576 | .IX Item "ESC # 8" |
1215 | \&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0) |
1577 | \&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0) |
1216 | .ie n .IP "\fB\fB""ESC 7""\fB\fR" 4 |
1578 | .ie n .IP "\fB\fB""ESC 7""\fB\fR" 4 |
… | |
… | |
1305 | C = < Multinational character set unimplemented |
1667 | C = < Multinational character set unimplemented |
1306 | C = 5 Finnish character set unimplemented |
1668 | C = 5 Finnish character set unimplemented |
1307 | C = C Finnish character set unimplemented |
1669 | C = C Finnish character set unimplemented |
1308 | C = K German character set unimplemented |
1670 | C = K German character set unimplemented |
1309 | .TE |
1671 | .TE |
1310 | |
|
|
1311 | .PP |
1672 | .PP |
1312 | |
1673 | |
1313 | .IX Xref "CSI" |
1674 | .IX Xref "CSI" |
1314 | .SH "CSI (Command Sequence Introducer) Sequences" |
1675 | .Sh "\s-1CSI\s0 (Command Sequence Introducer) Sequences" |
1315 | .IX Header "CSI (Command Sequence Introducer) Sequences" |
1676 | .IX Subsection "CSI (Command Sequence Introducer) Sequences" |
1316 | .ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4 |
1677 | .ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4 |
1317 | .el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4 |
1678 | .el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4 |
1318 | .IX Item "ESC [ Ps @" |
1679 | .IX Item "ESC [ Ps @" |
1319 | Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR (Blank) Character(s) [default: 1] (\s-1ICH\s0) |
1680 | Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR (Blank) Character(s) [default: 1] (\s-1ICH\s0) |
1320 | .IX Xref "ESCOBPsA" |
1681 | .IX Xref "ESCOBPsA" |
… | |
… | |
1364 | l l . |
1725 | l l . |
1365 | Ps = 0 Clear Below (default) |
1726 | Ps = 0 Clear Below (default) |
1366 | Ps = 1 Clear Above |
1727 | Ps = 1 Clear Above |
1367 | Ps = 2 Clear All |
1728 | Ps = 2 Clear All |
1368 | .TE |
1729 | .TE |
1369 | |
|
|
1370 | .ie n .IP "\fB\fB""ESC [ Ps K""\fB\fR" 4 |
1730 | .ie n .IP "\fB\fB""ESC [ Ps K""\fB\fR" 4 |
1371 | .el .IP "\fB\f(CBESC [ Ps K\fB\fR" 4 |
1731 | .el .IP "\fB\f(CBESC [ Ps K\fB\fR" 4 |
1372 | .IX Item "ESC [ Ps K" |
1732 | .IX Item "ESC [ Ps K" |
1373 | Erase in Line (\s-1EL\s0) |
1733 | Erase in Line (\s-1EL\s0) |
1374 | .TS |
1734 | .TS |
1375 | l l . |
1735 | l l . |
1376 | Ps = 0 Clear to Right (default) |
1736 | Ps = 0 Clear to Right (default) |
1377 | Ps = 1 Clear to Left |
1737 | Ps = 1 Clear to Left |
1378 | Ps = 2 Clear All |
1738 | Ps = 2 Clear All |
1379 | .TE |
1739 | .TE |
1380 | |
|
|
1381 | .ie n .IP "\fB\fB""ESC [ Ps L""\fB\fR" 4 |
1740 | .ie n .IP "\fB\fB""ESC [ Ps L""\fB\fR" 4 |
1382 | .el .IP "\fB\f(CBESC [ Ps L\fB\fR" 4 |
1741 | .el .IP "\fB\f(CBESC [ Ps L\fB\fR" 4 |
1383 | .IX Item "ESC [ Ps L" |
1742 | .IX Item "ESC [ Ps L" |
1384 | Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR Line(s) [default: 1] (\s-1IL\s0) |
1743 | Insert \fB\f(CB\*(C`Ps\*(C'\fB\fR Line(s) [default: 1] (\s-1IL\s0) |
1385 | .ie n .IP "\fB\fB""ESC [ Ps M""\fB\fR" 4 |
1744 | .ie n .IP "\fB\fB""ESC [ Ps M""\fB\fR" 4 |
… | |
… | |
1403 | l l . |
1762 | l l . |
1404 | Ps = 0 Tab Set (HTS) |
1763 | Ps = 0 Tab Set (HTS) |
1405 | Ps = 2 Tab Clear (TBC), Clear Current Column (default) |
1764 | Ps = 2 Tab Clear (TBC), Clear Current Column (default) |
1406 | Ps = 5 Tab Clear (TBC), Clear All |
1765 | Ps = 5 Tab Clear (TBC), Clear All |
1407 | .TE |
1766 | .TE |
1408 | |
|
|
1409 | .ie n .IP "\fB\fB""ESC [ Ps X""\fB\fR" 4 |
1767 | .ie n .IP "\fB\fB""ESC [ Ps X""\fB\fR" 4 |
1410 | .el .IP "\fB\f(CBESC [ Ps X\fB\fR" 4 |
1768 | .el .IP "\fB\f(CBESC [ Ps X\fB\fR" 4 |
1411 | .IX Item "ESC [ Ps X" |
1769 | .IX Item "ESC [ Ps X" |
1412 | Erase \fB\f(CB\*(C`Ps\*(C'\fB\fR Character(s) [default: 1] (\s-1ECH\s0) |
1770 | Erase \fB\f(CB\*(C`Ps\*(C'\fB\fR Character(s) [default: 1] (\s-1ECH\s0) |
1413 | .ie n .IP "\fB\fB""ESC [ Ps Z""\fB\fR" 4 |
1771 | .ie n .IP "\fB\fB""ESC [ Ps Z""\fB\fR" 4 |
… | |
… | |
1448 | .TS |
1806 | .TS |
1449 | l l . |
1807 | l l . |
1450 | Ps = 0 Clear Current Column (default) |
1808 | Ps = 0 Clear Current Column (default) |
1451 | Ps = 3 Clear All (TBC) |
1809 | Ps = 3 Clear All (TBC) |
1452 | .TE |
1810 | .TE |
1453 | |
|
|
1454 | .ie n .IP "\fB\fB""ESC [ Pm h""\fB\fR" 4 |
1811 | .ie n .IP "\fB\fB""ESC [ Pm h""\fB\fR" 4 |
1455 | .el .IP "\fB\f(CBESC [ Pm h\fB\fR" 4 |
1812 | .el .IP "\fB\f(CBESC [ Pm h\fB\fR" 4 |
1456 | .IX Item "ESC [ Pm h" |
1813 | .IX Item "ESC [ Pm h" |
1457 | Set Mode (\s-1SM\s0). See \fB\f(CB\*(C`ESC [ Pm l\*(C'\fB\fR sequence for description of \f(CW\*(C`Pm\*(C'\fR. |
1814 | Set Mode (\s-1SM\s0). See \fB\f(CB\*(C`ESC [ Pm l\*(C'\fB\fR sequence for description of \f(CW\*(C`Pm\*(C'\fR. |
1458 | .ie n .IP "\fB\fB""ESC [ Ps i""\fB\fR" 4 |
1815 | .ie n .IP "\fB\fB""ESC [ Ps i""\fB\fR" 4 |
… | |
… | |
1463 | l l . |
1820 | l l . |
1464 | Ps = 0 print screen (MC0) |
1821 | Ps = 0 print screen (MC0) |
1465 | Ps = 4 disable transparent print mode (MC4) |
1822 | Ps = 4 disable transparent print mode (MC4) |
1466 | Ps = 5 enable transparent print mode (MC5) |
1823 | Ps = 5 enable transparent print mode (MC5) |
1467 | .TE |
1824 | .TE |
1468 | |
|
|
1469 | .ie n .IP "\fB\fB""ESC [ Pm l""\fB\fR" 4 |
1825 | .ie n .IP "\fB\fB""ESC [ Pm l""\fB\fR" 4 |
1470 | .el .IP "\fB\f(CBESC [ Pm l\fB\fR" 4 |
1826 | .el .IP "\fB\f(CBESC [ Pm l\fB\fR" 4 |
1471 | .IX Item "ESC [ Pm l" |
1827 | .IX Item "ESC [ Pm l" |
1472 | Reset Mode (\s-1RM\s0) |
1828 | Reset Mode (\s-1RM\s0) |
1473 | .RS 4 |
1829 | .RS 4 |
… | |
… | |
1477 | .TS |
1833 | .TS |
1478 | l l . |
1834 | l l . |
1479 | h Insert Mode (SMIR) |
1835 | h Insert Mode (SMIR) |
1480 | l Replace Mode (RMIR) |
1836 | l Replace Mode (RMIR) |
1481 | .TE |
1837 | .TE |
1482 | |
|
|
1483 | .PD 0 |
1838 | .PD 0 |
1484 | .ie n .IP "\fB\fB""Ps = 20""\fB\fR (partially implemented)" 4 |
1839 | .ie n .IP "\fB\fB""Ps = 20""\fB\fR (partially implemented)" 4 |
1485 | .el .IP "\fB\f(CBPs = 20\fB\fR (partially implemented)" 4 |
1840 | .el .IP "\fB\f(CBPs = 20\fB\fR (partially implemented)" 4 |
1486 | .IX Item "Ps = 20 (partially implemented)" |
1841 | .IX Item "Ps = 20 (partially implemented)" |
1487 | .TS |
1842 | .TS |
1488 | l l . |
1843 | l l . |
1489 | h Automatic Newline (LNM) |
1844 | h Automatic Newline (LNM) |
1490 | l Normal Linefeed (LNM) |
1845 | l Normal Linefeed (LNM) |
1491 | .TE |
1846 | .TE |
1492 | |
|
|
1493 | .RE |
1847 | .RE |
1494 | .RS 4 |
1848 | .RS 4 |
1495 | .RE |
1849 | .RE |
1496 | .ie n .IP "\fB\fB""ESC [ Pm m""\fB\fR" 4 |
1850 | .ie n .IP "\fB\fB""ESC [ Pm m""\fB\fR" 4 |
1497 | .el .IP "\fB\f(CBESC [ Pm m\fB\fR" 4 |
1851 | .el .IP "\fB\f(CBESC [ Pm m\fB\fR" 4 |
… | |
… | |
1526 | Ps = 95 / 105 fg/bg Bright Magenta |
1880 | Ps = 95 / 105 fg/bg Bright Magenta |
1527 | Ps = 96 / 106 fg/bg Bright Cyan |
1881 | Ps = 96 / 106 fg/bg Bright Cyan |
1528 | Ps = 97 / 107 fg/bg Bright White |
1882 | Ps = 97 / 107 fg/bg Bright White |
1529 | Ps = 99 / 109 fg/bg Bright Default |
1883 | Ps = 99 / 109 fg/bg Bright Default |
1530 | .TE |
1884 | .TE |
1531 | |
|
|
1532 | .ie n .IP "\fB\fB""ESC [ Ps n""\fB\fR" 4 |
1885 | .ie n .IP "\fB\fB""ESC [ Ps n""\fB\fR" 4 |
1533 | .el .IP "\fB\f(CBESC [ Ps n\fB\fR" 4 |
1886 | .el .IP "\fB\f(CBESC [ Ps n\fB\fR" 4 |
1534 | .IX Item "ESC [ Ps n" |
1887 | .IX Item "ESC [ Ps n" |
1535 | Device Status Report (\s-1DSR\s0) |
1888 | Device Status Report (\s-1DSR\s0) |
1536 | .TS |
1889 | .TS |
… | |
… | |
1538 | Ps = 5 Status Report ESC [ 0 n (``OK'') |
1891 | Ps = 5 Status Report ESC [ 0 n (``OK'') |
1539 | Ps = 6 Report Cursor Position (CPR) [row;column] as ESC [ r ; c R |
1892 | Ps = 6 Report Cursor Position (CPR) [row;column] as ESC [ r ; c R |
1540 | Ps = 7 Request Display Name |
1893 | Ps = 7 Request Display Name |
1541 | Ps = 8 Request Version Number (place in window title) |
1894 | Ps = 8 Request Version Number (place in window title) |
1542 | .TE |
1895 | .TE |
1543 | |
|
|
1544 | .ie n .IP "\fB\fB""ESC [ Ps;Ps r""\fB\fR" 4 |
1896 | .ie n .IP "\fB\fB""ESC [ Ps;Ps r""\fB\fR" 4 |
1545 | .el .IP "\fB\f(CBESC [ Ps;Ps r\fB\fR" 4 |
1897 | .el .IP "\fB\f(CBESC [ Ps;Ps r\fB\fR" 4 |
1546 | .IX Item "ESC [ Ps;Ps r" |
1898 | .IX Item "ESC [ Ps;Ps r" |
1547 | Set Scrolling Region [top;bottom] |
1899 | Set Scrolling Region [top;bottom] |
1548 | [default: full size of window] (\s-1CSR\s0) |
1900 | [default: full size of window] (\s-1CSR\s0) |
… | |
… | |
1571 | Ps = 19 Currently the same as Ps = 18, but responds with Ps = 9 |
1923 | Ps = 19 Currently the same as Ps = 18, but responds with Ps = 9 |
1572 | Ps = 20 Reports icon label (ESC ] L NAME \234) |
1924 | Ps = 20 Reports icon label (ESC ] L NAME \234) |
1573 | Ps = 21 Reports window title (ESC ] l NAME \234) |
1925 | Ps = 21 Reports window title (ESC ] l NAME \234) |
1574 | Ps = 24.. Set window height to Ps rows |
1926 | Ps = 24.. Set window height to Ps rows |
1575 | .TE |
1927 | .TE |
1576 | |
|
|
1577 | .ie n .IP "\fB\fB""ESC [ u""\fB\fR" 4 |
1928 | .ie n .IP "\fB\fB""ESC [ u""\fB\fR" 4 |
1578 | .el .IP "\fB\f(CBESC [ u\fB\fR" 4 |
1929 | .el .IP "\fB\f(CBESC [ u\fB\fR" 4 |
1579 | .IX Item "ESC [ u" |
1930 | .IX Item "ESC [ u" |
1580 | Restore Cursor |
1931 | Restore Cursor |
1581 | .ie n .IP "\fB\fB""ESC [ Ps x""\fB\fR" 4 |
1932 | .ie n .IP "\fB\fB""ESC [ Ps x""\fB\fR" 4 |
… | |
… | |
1583 | .IX Item "ESC [ Ps x" |
1934 | .IX Item "ESC [ Ps x" |
1584 | Request Terminal Parameters (\s-1DECREQTPARM\s0) |
1935 | Request Terminal Parameters (\s-1DECREQTPARM\s0) |
1585 | .PP |
1936 | .PP |
1586 | |
1937 | |
1587 | .IX Xref "PrivateModes" |
1938 | .IX Xref "PrivateModes" |
1588 | .SH "DEC Private Modes" |
1939 | .Sh "\s-1DEC\s0 Private Modes" |
1589 | .IX Header "DEC Private Modes" |
1940 | .IX Subsection "DEC Private Modes" |
1590 | .ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4 |
1941 | .ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4 |
1591 | .el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4 |
1942 | .el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4 |
1592 | .IX Item "ESC [ ? Pm h" |
1943 | .IX Item "ESC [ ? Pm h" |
1593 | \&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0) |
1944 | \&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0) |
1594 | .ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4 |
1945 | .ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4 |
… | |
… | |
1606 | .ie n .IP "\fB\fB""ESC [ ? Pm t""\fB\fR" 4 |
1957 | .ie n .IP "\fB\fB""ESC [ ? Pm t""\fB\fR" 4 |
1607 | .el .IP "\fB\f(CBESC [ ? Pm t\fB\fR" 4 |
1958 | .el .IP "\fB\f(CBESC [ ? Pm t\fB\fR" 4 |
1608 | .IX Item "ESC [ ? Pm t" |
1959 | .IX Item "ESC [ ? Pm t" |
1609 | Toggle \s-1DEC\s0 Private Mode Values (rxvt extension). \fIwhere\fR |
1960 | Toggle \s-1DEC\s0 Private Mode Values (rxvt extension). \fIwhere\fR |
1610 | .RS 4 |
1961 | .RS 4 |
1611 | .ie n .IP "\fB\fB""Ps = 1""\fB\fR (\s-1DECCKM\s0)" 4 |
1962 | .ie n .IP "\fB\fB""Pm = 1""\fB\fR (\s-1DECCKM\s0)" 4 |
1612 | .el .IP "\fB\f(CBPs = 1\fB\fR (\s-1DECCKM\s0)" 4 |
1963 | .el .IP "\fB\f(CBPm = 1\fB\fR (\s-1DECCKM\s0)" 4 |
1613 | .IX Item "Ps = 1 (DECCKM)" |
1964 | .IX Item "Pm = 1 (DECCKM)" |
1614 | .TS |
1965 | .TS |
1615 | l l . |
1966 | l l . |
1616 | h Application Cursor Keys |
1967 | h Application Cursor Keys |
1617 | l Normal Cursor Keys |
1968 | l Normal Cursor Keys |
1618 | .TE |
1969 | .TE |
1619 | |
|
|
1620 | .PD 0 |
1970 | .PD 0 |
1621 | .ie n .IP "\fB\fB""Ps = 2""\fB\fR (\s-1ANSI/VT52\s0 mode)" 4 |
1971 | .ie n .IP "\fB\fB""Pm = 2""\fB\fR (\s-1ANSI/VT52\s0 mode)" 4 |
1622 | .el .IP "\fB\f(CBPs = 2\fB\fR (\s-1ANSI/VT52\s0 mode)" 4 |
1972 | .el .IP "\fB\f(CBPm = 2\fB\fR (\s-1ANSI/VT52\s0 mode)" 4 |
1623 | .IX Item "Ps = 2 (ANSI/VT52 mode)" |
1973 | .IX Item "Pm = 2 (ANSI/VT52 mode)" |
1624 | .TS |
1974 | .TS |
1625 | l l . |
1975 | l l . |
1626 | h Enter VT52 mode |
1976 | h Enter VT52 mode |
1627 | l Enter VT52 mode |
1977 | l Enter VT52 mode |
1628 | .TE |
1978 | .TE |
1629 | |
|
|
1630 | .ie n .IP "\fB\fB""Ps = 3""\fB\fR" 4 |
1979 | .ie n .IP "\fB\fB""Pm = 3""\fB\fR" 4 |
1631 | .el .IP "\fB\f(CBPs = 3\fB\fR" 4 |
1980 | .el .IP "\fB\f(CBPm = 3\fB\fR" 4 |
1632 | .IX Item "Ps = 3" |
1981 | .IX Item "Pm = 3" |
1633 | .TS |
1982 | .TS |
1634 | l l . |
1983 | l l . |
1635 | h 132 Column Mode (DECCOLM) |
1984 | h 132 Column Mode (DECCOLM) |
1636 | l 80 Column Mode (DECCOLM) |
1985 | l 80 Column Mode (DECCOLM) |
1637 | .TE |
1986 | .TE |
1638 | |
|
|
1639 | .ie n .IP "\fB\fB""Ps = 4""\fB\fR" 4 |
1987 | .ie n .IP "\fB\fB""Pm = 4""\fB\fR" 4 |
1640 | .el .IP "\fB\f(CBPs = 4\fB\fR" 4 |
1988 | .el .IP "\fB\f(CBPm = 4\fB\fR" 4 |
1641 | .IX Item "Ps = 4" |
1989 | .IX Item "Pm = 4" |
1642 | .TS |
1990 | .TS |
1643 | l l . |
1991 | l l . |
1644 | h Smooth (Slow) Scroll (DECSCLM) |
1992 | h Smooth (Slow) Scroll (DECSCLM) |
1645 | l Jump (Fast) Scroll (DECSCLM) |
1993 | l Jump (Fast) Scroll (DECSCLM) |
1646 | .TE |
1994 | .TE |
1647 | |
|
|
1648 | .ie n .IP "\fB\fB""Ps = 5""\fB\fR" 4 |
1995 | .ie n .IP "\fB\fB""Pm = 5""\fB\fR" 4 |
1649 | .el .IP "\fB\f(CBPs = 5\fB\fR" 4 |
1996 | .el .IP "\fB\f(CBPm = 5\fB\fR" 4 |
1650 | .IX Item "Ps = 5" |
1997 | .IX Item "Pm = 5" |
1651 | .TS |
1998 | .TS |
1652 | l l . |
1999 | l l . |
1653 | h Reverse Video (DECSCNM) |
2000 | h Reverse Video (DECSCNM) |
1654 | l Normal Video (DECSCNM) |
2001 | l Normal Video (DECSCNM) |
1655 | .TE |
2002 | .TE |
1656 | |
|
|
1657 | .ie n .IP "\fB\fB""Ps = 6""\fB\fR" 4 |
2003 | .ie n .IP "\fB\fB""Pm = 6""\fB\fR" 4 |
1658 | .el .IP "\fB\f(CBPs = 6\fB\fR" 4 |
2004 | .el .IP "\fB\f(CBPm = 6\fB\fR" 4 |
1659 | .IX Item "Ps = 6" |
2005 | .IX Item "Pm = 6" |
1660 | .TS |
2006 | .TS |
1661 | l l . |
2007 | l l . |
1662 | h Origin Mode (DECOM) |
2008 | h Origin Mode (DECOM) |
1663 | l Normal Cursor Mode (DECOM) |
2009 | l Normal Cursor Mode (DECOM) |
1664 | .TE |
2010 | .TE |
1665 | |
|
|
1666 | .ie n .IP "\fB\fB""Ps = 7""\fB\fR" 4 |
2011 | .ie n .IP "\fB\fB""Pm = 7""\fB\fR" 4 |
1667 | .el .IP "\fB\f(CBPs = 7\fB\fR" 4 |
2012 | .el .IP "\fB\f(CBPm = 7\fB\fR" 4 |
1668 | .IX Item "Ps = 7" |
2013 | .IX Item "Pm = 7" |
1669 | .TS |
2014 | .TS |
1670 | l l . |
2015 | l l . |
1671 | h Wraparound Mode (DECAWM) |
2016 | h Wraparound Mode (DECAWM) |
1672 | l No Wraparound Mode (DECAWM) |
2017 | l No Wraparound Mode (DECAWM) |
1673 | .TE |
2018 | .TE |
1674 | |
|
|
1675 | .ie n .IP "\fB\fB""Ps = 8""\fB\fR \fIunimplemented\fR" 4 |
2019 | .ie n .IP "\fB\fB""Pm = 8""\fB\fR \fIunimplemented\fR" 4 |
1676 | .el .IP "\fB\f(CBPs = 8\fB\fR \fIunimplemented\fR" 4 |
2020 | .el .IP "\fB\f(CBPm = 8\fB\fR \fIunimplemented\fR" 4 |
1677 | .IX Item "Ps = 8 unimplemented" |
2021 | .IX Item "Pm = 8 unimplemented" |
1678 | .TS |
2022 | .TS |
1679 | l l . |
2023 | l l . |
1680 | h Auto-repeat Keys (DECARM) |
2024 | h Auto-repeat Keys (DECARM) |
1681 | l No Auto-repeat Keys (DECARM) |
2025 | l No Auto-repeat Keys (DECARM) |
1682 | .TE |
2026 | .TE |
1683 | |
|
|
1684 | .ie n .IP "\fB\fB""Ps = 9""\fB\fR X10 XTerm" 4 |
2027 | .ie n .IP "\fB\fB""Pm = 9""\fB\fR X10 XTerm" 4 |
1685 | .el .IP "\fB\f(CBPs = 9\fB\fR X10 XTerm" 4 |
2028 | .el .IP "\fB\f(CBPm = 9\fB\fR X10 XTerm" 4 |
1686 | .IX Item "Ps = 9 X10 XTerm" |
2029 | .IX Item "Pm = 9 X10 XTerm" |
1687 | .TS |
2030 | .TS |
1688 | l l . |
2031 | l l . |
1689 | h Send Mouse X & Y on button press. |
2032 | h Send Mouse X & Y on button press. |
1690 | l No mouse reporting. |
2033 | l No mouse reporting. |
1691 | .TE |
2034 | .TE |
1692 | |
|
|
1693 | .ie n .IP "\fB\fB""Ps = 25""\fB\fR" 4 |
2035 | .ie n .IP "\fB\fB""Pm = 25""\fB\fR" 4 |
1694 | .el .IP "\fB\f(CBPs = 25\fB\fR" 4 |
2036 | .el .IP "\fB\f(CBPm = 25\fB\fR" 4 |
1695 | .IX Item "Ps = 25" |
2037 | .IX Item "Pm = 25" |
1696 | .TS |
2038 | .TS |
1697 | l l . |
2039 | l l . |
1698 | h Visible cursor {cnorm/cvvis} |
2040 | h Visible cursor {cnorm/cvvis} |
1699 | l Invisible cursor {civis} |
2041 | l Invisible cursor {civis} |
1700 | .TE |
2042 | .TE |
1701 | |
|
|
1702 | .ie n .IP "\fB\fB""Ps = 30""\fB\fR" 4 |
2043 | .ie n .IP "\fB\fB""Pm = 30""\fB\fR" 4 |
1703 | .el .IP "\fB\f(CBPs = 30\fB\fR" 4 |
2044 | .el .IP "\fB\f(CBPm = 30\fB\fR" 4 |
1704 | .IX Item "Ps = 30" |
2045 | .IX Item "Pm = 30" |
1705 | .TS |
2046 | .TS |
1706 | l l . |
2047 | l l . |
1707 | h scrollBar visisble |
2048 | h scrollBar visisble |
1708 | l scrollBar invisisble |
2049 | l scrollBar invisisble |
1709 | .TE |
2050 | .TE |
1710 | |
|
|
1711 | .ie n .IP "\fB\fB""Ps = 35""\fB\fR (\fBrxvt\fR)" 4 |
2051 | .ie n .IP "\fB\fB""Pm = 35""\fB\fR (\fBrxvt\fR)" 4 |
1712 | .el .IP "\fB\f(CBPs = 35\fB\fR (\fBrxvt\fR)" 4 |
2052 | .el .IP "\fB\f(CBPm = 35\fB\fR (\fBrxvt\fR)" 4 |
1713 | .IX Item "Ps = 35 (rxvt)" |
2053 | .IX Item "Pm = 35 (rxvt)" |
1714 | .TS |
2054 | .TS |
1715 | l l . |
2055 | l l . |
1716 | h Allow XTerm Shift+key sequences |
2056 | h Allow XTerm Shift+key sequences |
1717 | l Disallow XTerm Shift+key sequences |
2057 | l Disallow XTerm Shift+key sequences |
1718 | .TE |
2058 | .TE |
1719 | |
|
|
1720 | .ie n .IP "\fB\fB""Ps = 38""\fB\fR \fIunimplemented\fR" 4 |
2059 | .ie n .IP "\fB\fB""Pm = 38""\fB\fR \fIunimplemented\fR" 4 |
1721 | .el .IP "\fB\f(CBPs = 38\fB\fR \fIunimplemented\fR" 4 |
2060 | .el .IP "\fB\f(CBPm = 38\fB\fR \fIunimplemented\fR" 4 |
1722 | .IX Item "Ps = 38 unimplemented" |
2061 | .IX Item "Pm = 38 unimplemented" |
1723 | .PD |
2062 | .PD |
1724 | Enter Tektronix Mode (\s-1DECTEK\s0) |
2063 | Enter Tektronix Mode (\s-1DECTEK\s0) |
1725 | .ie n .IP "\fB\fB""Ps = 40""\fB\fR" 4 |
2064 | .ie n .IP "\fB\fB""Pm = 40""\fB\fR" 4 |
1726 | .el .IP "\fB\f(CBPs = 40\fB\fR" 4 |
2065 | .el .IP "\fB\f(CBPm = 40\fB\fR" 4 |
1727 | .IX Item "Ps = 40" |
2066 | .IX Item "Pm = 40" |
1728 | .TS |
2067 | .TS |
1729 | l l . |
2068 | l l . |
1730 | h Allow 80/132 Mode |
2069 | h Allow 80/132 Mode |
1731 | l Disallow 80/132 Mode |
2070 | l Disallow 80/132 Mode |
1732 | .TE |
2071 | .TE |
1733 | |
|
|
1734 | .PD 0 |
2072 | .PD 0 |
1735 | .ie n .IP "\fB\fB""Ps = 44""\fB\fR \fIunimplemented\fR" 4 |
2073 | .ie n .IP "\fB\fB""Pm = 44""\fB\fR \fIunimplemented\fR" 4 |
1736 | .el .IP "\fB\f(CBPs = 44\fB\fR \fIunimplemented\fR" 4 |
2074 | .el .IP "\fB\f(CBPm = 44\fB\fR \fIunimplemented\fR" 4 |
1737 | .IX Item "Ps = 44 unimplemented" |
2075 | .IX Item "Pm = 44 unimplemented" |
1738 | .TS |
2076 | .TS |
1739 | l l . |
2077 | l l . |
1740 | h Turn On Margin Bell |
2078 | h Turn On Margin Bell |
1741 | l Turn Off Margin Bell |
2079 | l Turn Off Margin Bell |
1742 | .TE |
2080 | .TE |
1743 | |
|
|
1744 | .ie n .IP "\fB\fB""Ps = 45""\fB\fR \fIunimplemented\fR" 4 |
2081 | .ie n .IP "\fB\fB""Pm = 45""\fB\fR \fIunimplemented\fR" 4 |
1745 | .el .IP "\fB\f(CBPs = 45\fB\fR \fIunimplemented\fR" 4 |
2082 | .el .IP "\fB\f(CBPm = 45\fB\fR \fIunimplemented\fR" 4 |
1746 | .IX Item "Ps = 45 unimplemented" |
2083 | .IX Item "Pm = 45 unimplemented" |
1747 | .TS |
2084 | .TS |
1748 | l l . |
2085 | l l . |
1749 | h Reverse-wraparound Mode |
2086 | h Reverse-wraparound Mode |
1750 | l No Reverse-wraparound Mode |
2087 | l No Reverse-wraparound Mode |
1751 | .TE |
2088 | .TE |
1752 | |
|
|
1753 | .ie n .IP "\fB\fB""Ps = 46""\fB\fR \fIunimplemented\fR" 4 |
2089 | .ie n .IP "\fB\fB""Pm = 46""\fB\fR \fIunimplemented\fR" 4 |
1754 | .el .IP "\fB\f(CBPs = 46\fB\fR \fIunimplemented\fR" 4 |
2090 | .el .IP "\fB\f(CBPm = 46\fB\fR \fIunimplemented\fR" 4 |
1755 | .IX Item "Ps = 46 unimplemented" |
2091 | .IX Item "Pm = 46 unimplemented" |
1756 | .ie n .IP "\fB\fB""Ps = 47""\fB\fR" 4 |
2092 | .ie n .IP "\fB\fB""Pm = 47""\fB\fR" 4 |
1757 | .el .IP "\fB\f(CBPs = 47\fB\fR" 4 |
2093 | .el .IP "\fB\f(CBPm = 47\fB\fR" 4 |
1758 | .IX Item "Ps = 47" |
2094 | .IX Item "Pm = 47" |
1759 | .TS |
2095 | .TS |
1760 | l l . |
2096 | l l . |
1761 | h Use Alternate Screen Buffer |
2097 | h Use Alternate Screen Buffer |
1762 | l Use Normal Screen Buffer |
2098 | l Use Normal Screen Buffer |
1763 | .TE |
2099 | .TE |
1764 | |
|
|
1765 | .PD |
2100 | .PD |
1766 | |
2101 | |
1767 | .IX Xref "Priv66" |
2102 | .IX Xref "Priv66" |
1768 | .ie n .IP "\fB\fB""Ps = 66""\fB\fR" 4 |
2103 | .ie n .IP "\fB\fB""Pm = 66""\fB\fR" 4 |
1769 | .el .IP "\fB\f(CBPs = 66\fB\fR" 4 |
2104 | .el .IP "\fB\f(CBPm = 66\fB\fR" 4 |
1770 | .IX Item "Ps = 66" |
2105 | .IX Item "Pm = 66" |
1771 | .TS |
2106 | .TS |
1772 | l l . |
2107 | l l . |
1773 | h Application Keypad (DECPAM) == ESC = |
2108 | h Application Keypad (DECPAM) == ESC = |
1774 | l Normal Keypad (DECPNM) == ESC > |
2109 | l Normal Keypad (DECPNM) == ESC > |
1775 | .TE |
2110 | .TE |
1776 | |
|
|
1777 | .PD 0 |
2111 | .PD 0 |
1778 | .ie n .IP "\fB\fB""Ps = 67""\fB\fR" 4 |
2112 | .ie n .IP "\fB\fB""Pm = 67""\fB\fR" 4 |
1779 | .el .IP "\fB\f(CBPs = 67\fB\fR" 4 |
2113 | .el .IP "\fB\f(CBPm = 67\fB\fR" 4 |
1780 | .IX Item "Ps = 67" |
2114 | .IX Item "Pm = 67" |
1781 | .TS |
2115 | .TS |
1782 | l l . |
2116 | l l . |
1783 | h Backspace key sends BS (DECBKM) |
2117 | h Backspace key sends BS (DECBKM) |
1784 | l Backspace key sends DEL |
2118 | l Backspace key sends DEL |
1785 | .TE |
2119 | .TE |
1786 | |
|
|
1787 | .ie n .IP "\fB\fB""Ps = 1000""\fB\fR (X11 XTerm)" 4 |
2120 | .ie n .IP "\fB\fB""Pm = 1000""\fB\fR (X11 XTerm)" 4 |
1788 | .el .IP "\fB\f(CBPs = 1000\fB\fR (X11 XTerm)" 4 |
2121 | .el .IP "\fB\f(CBPm = 1000\fB\fR (X11 XTerm)" 4 |
1789 | .IX Item "Ps = 1000 (X11 XTerm)" |
2122 | .IX Item "Pm = 1000 (X11 XTerm)" |
1790 | .TS |
2123 | .TS |
1791 | l l . |
2124 | l l . |
1792 | h Send Mouse X & Y on button press and release. |
2125 | h Send Mouse X & Y on button press and release. |
1793 | l No mouse reporting. |
2126 | l No mouse reporting. |
1794 | .TE |
2127 | .TE |
1795 | |
|
|
1796 | .ie n .IP "\fB\fB""Ps = 1001""\fB\fR (X11 XTerm) \fIunimplemented\fR" 4 |
2128 | .ie n .IP "\fB\fB""Pm = 1001""\fB\fR (X11 XTerm) \fIunimplemented\fR" 4 |
1797 | .el .IP "\fB\f(CBPs = 1001\fB\fR (X11 XTerm) \fIunimplemented\fR" 4 |
2129 | .el .IP "\fB\f(CBPm = 1001\fB\fR (X11 XTerm) \fIunimplemented\fR" 4 |
1798 | .IX Item "Ps = 1001 (X11 XTerm) unimplemented" |
2130 | .IX Item "Pm = 1001 (X11 XTerm) unimplemented" |
1799 | .TS |
2131 | .TS |
1800 | l l . |
2132 | l l . |
1801 | h Use Hilite Mouse Tracking. |
2133 | h Use Hilite Mouse Tracking. |
1802 | l No mouse reporting. |
2134 | l No mouse reporting. |
1803 | .TE |
2135 | .TE |
1804 | |
|
|
1805 | .ie n .IP "\fB\fB""Ps = 1010""\fB\fR (\fBrxvt\fR)" 4 |
2136 | .ie n .IP "\fB\fB""Pm = 1010""\fB\fR (\fBrxvt\fR)" 4 |
1806 | .el .IP "\fB\f(CBPs = 1010\fB\fR (\fBrxvt\fR)" 4 |
2137 | .el .IP "\fB\f(CBPm = 1010\fB\fR (\fBrxvt\fR)" 4 |
1807 | .IX Item "Ps = 1010 (rxvt)" |
2138 | .IX Item "Pm = 1010 (rxvt)" |
1808 | .TS |
2139 | .TS |
1809 | l l . |
2140 | l l . |
1810 | h Don't scroll to bottom on TTY output |
2141 | h Don't scroll to bottom on TTY output |
1811 | l Scroll to bottom on TTY output |
2142 | l Scroll to bottom on TTY output |
1812 | .TE |
2143 | .TE |
1813 | |
|
|
1814 | .ie n .IP "\fB\fB""Ps = 1011""\fB\fR (\fBrxvt\fR)" 4 |
2144 | .ie n .IP "\fB\fB""Pm = 1011""\fB\fR (\fBrxvt\fR)" 4 |
1815 | .el .IP "\fB\f(CBPs = 1011\fB\fR (\fBrxvt\fR)" 4 |
2145 | .el .IP "\fB\f(CBPm = 1011\fB\fR (\fBrxvt\fR)" 4 |
1816 | .IX Item "Ps = 1011 (rxvt)" |
2146 | .IX Item "Pm = 1011 (rxvt)" |
1817 | .TS |
2147 | .TS |
1818 | l l . |
2148 | l l . |
1819 | h Scroll to bottom when a key is pressed |
2149 | h Scroll to bottom when a key is pressed |
1820 | l Don't scroll to bottom when a key is pressed |
2150 | l Don't scroll to bottom when a key is pressed |
1821 | .TE |
2151 | .TE |
1822 | |
|
|
1823 | .ie n .IP "\fB\fB""Ps = 1021""\fB\fR (\fBrxvt\fR)" 4 |
2152 | .ie n .IP "\fB\fB""Pm = 1021""\fB\fR (\fBrxvt\fR)" 4 |
1824 | .el .IP "\fB\f(CBPs = 1021\fB\fR (\fBrxvt\fR)" 4 |
2153 | .el .IP "\fB\f(CBPm = 1021\fB\fR (\fBrxvt\fR)" 4 |
1825 | .IX Item "Ps = 1021 (rxvt)" |
2154 | .IX Item "Pm = 1021 (rxvt)" |
1826 | .TS |
2155 | .TS |
1827 | l l . |
2156 | l l . |
1828 | h Bold/italic implies high intensity (see option -is) |
2157 | h Bold/italic implies high intensity (see option -is) |
1829 | l Font styles have no effect on intensity (Compile styles) |
2158 | l Font styles have no effect on intensity (Compile styles) |
1830 | .TE |
2159 | .TE |
1831 | |
|
|
1832 | .ie n .IP "\fB\fB""Ps = 1047""\fB\fR" 4 |
2160 | .ie n .IP "\fB\fB""Pm = 1047""\fB\fR" 4 |
1833 | .el .IP "\fB\f(CBPs = 1047\fB\fR" 4 |
2161 | .el .IP "\fB\f(CBPm = 1047\fB\fR" 4 |
1834 | .IX Item "Ps = 1047" |
2162 | .IX Item "Pm = 1047" |
1835 | .TS |
2163 | .TS |
1836 | l l . |
2164 | l l . |
1837 | h Use Alternate Screen Buffer |
2165 | h Use Alternate Screen Buffer |
1838 | l Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it |
2166 | l Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it |
1839 | .TE |
2167 | .TE |
1840 | |
|
|
1841 | .ie n .IP "\fB\fB""Ps = 1048""\fB\fR" 4 |
2168 | .ie n .IP "\fB\fB""Pm = 1048""\fB\fR" 4 |
1842 | .el .IP "\fB\f(CBPs = 1048\fB\fR" 4 |
2169 | .el .IP "\fB\f(CBPm = 1048\fB\fR" 4 |
1843 | .IX Item "Ps = 1048" |
2170 | .IX Item "Pm = 1048" |
1844 | .TS |
2171 | .TS |
1845 | l l . |
2172 | l l . |
1846 | h Save cursor position |
2173 | h Save cursor position |
1847 | l Restore cursor position |
2174 | l Restore cursor position |
1848 | .TE |
2175 | .TE |
1849 | |
|
|
1850 | .ie n .IP "\fB\fB""Ps = 1049""\fB\fR" 4 |
2176 | .ie n .IP "\fB\fB""Pm = 1049""\fB\fR" 4 |
1851 | .el .IP "\fB\f(CBPs = 1049\fB\fR" 4 |
2177 | .el .IP "\fB\f(CBPm = 1049\fB\fR" 4 |
1852 | .IX Item "Ps = 1049" |
2178 | .IX Item "Pm = 1049" |
1853 | .TS |
2179 | .TS |
1854 | l l . |
2180 | l l . |
1855 | h Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it |
2181 | h Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it |
1856 | l Use Normal Screen Buffer |
2182 | l Use Normal Screen Buffer |
1857 | .TE |
2183 | .TE |
1858 | |
|
|
1859 | .RE |
2184 | .RE |
1860 | .RS 4 |
2185 | .RS 4 |
1861 | .RE |
2186 | .RE |
1862 | .PD |
2187 | .PD |
1863 | .PP |
2188 | .PP |
1864 | |
2189 | |
1865 | .IX Xref "XTerm" |
2190 | .IX Xref "XTerm" |
1866 | .SH "XTerm Operating System Commands" |
2191 | .Sh "XTerm Operating System Commands" |
1867 | .IX Header "XTerm Operating System Commands" |
2192 | .IX Subsection "XTerm Operating System Commands" |
1868 | .ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4 |
2193 | .ie n .IP "\fB\fB""ESC ] Ps;Pt ST""\fB\fR" 4 |
1869 | .el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4 |
2194 | .el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4 |
1870 | .IX Item "ESC ] Ps;Pt ST" |
2195 | .IX Item "ESC ] Ps;Pt ST" |
1871 | Set XTerm Parameters. 8\-bit \s-1ST:\s0 0x9c, 7\-bit \s-1ST\s0 sequence: \s-1ESC\s0 \e (0x1b, |
2196 | Set XTerm Parameters. 8\-bit \s-1ST:\s0 0x9c, 7\-bit \s-1ST\s0 sequence: \s-1ESC\s0 \e (0x1b, |
1872 | 0x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any |
2197 | 0x5c), backwards compatible terminator \s-1BEL\s0 (0x07) is also accepted. any |
… | |
… | |
1903 | Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles). |
2228 | Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles). |
1904 | Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
2229 | Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
1905 | Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
2230 | Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
1906 | Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl). |
2231 | Ps = 777 Call the perl extension with the given string, which should be of the form extension:parameters (Compile perl). |
1907 | .TE |
2232 | .TE |
1908 | |
|
|
1909 | .PP |
|
|
1910 | |
|
|
1911 | .IX Xref "XPM" |
|
|
1912 | .SH "XPM" |
2233 | .SH "XPM" |
1913 | .IX Header "XPM" |
2234 | .IX Header "XPM" |
1914 | For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value |
2235 | For the \s-1XPM\s0 XTerm escape sequence \fB\f(CB\*(C`ESC ] 20 ; Pt ST\*(C'\fB\fR then value |
1915 | of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a |
2236 | of \fB\f(CB\*(C`Pt\*(C'\fB\fR can be the name of the background pixmap followed by a |
1916 | sequence of scaling/positioning commands separated by semi\-colons. The |
2237 | sequence of scaling/positioning commands separated by semi\-colons. The |
… | |
… | |
1974 | 0 Button1 pressed |
2295 | 0 Button1 pressed |
1975 | 1 Button2 pressed |
2296 | 1 Button2 pressed |
1976 | 2 Button3 pressed |
2297 | 2 Button3 pressed |
1977 | 3 button released (X11 mouse report) |
2298 | 3 button released (X11 mouse report) |
1978 | .TE |
2299 | .TE |
1979 | |
|
|
1980 | .PP |
2300 | .PP |
1981 | The upper bits of \fB\f(CB\*(C`<b>\*(C'\fB\fR indicate the modifiers when the |
2301 | The upper bits of \fB\f(CB\*(C`<b>\*(C'\fB\fR indicate the modifiers when the |
1982 | button was pressed and are added together (X11 mouse report only): |
2302 | button was pressed and are added together (X11 mouse report only): |
1983 | .ie n .IP "State = \fB\fB""(<b> \- SPACE) & 60""\fB\fR" 4 |
2303 | .ie n .IP "State = \fB\fB""(<b> \- SPACE) & 60""\fB\fR" 4 |
1984 | .el .IP "State = \fB\f(CB(<b> \- SPACE) & 60\fB\fR" 4 |
2304 | .el .IP "State = \fB\f(CB(<b> \- SPACE) & 60\fB\fR" 4 |
… | |
… | |
1986 | .TS |
2306 | .TS |
1987 | l l . |
2307 | l l . |
1988 | 4 Shift |
2308 | 4 Shift |
1989 | 8 Meta |
2309 | 8 Meta |
1990 | 16 Control |
2310 | 16 Control |
1991 | 32 Double Click (Rxvt extension) |
2311 | 32 Double Click (rxvt extension) |
1992 | .TE |
2312 | .TE |
1993 | |
|
|
1994 | Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR |
2313 | Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR |
1995 | .Sp |
2314 | .Sp |
1996 | Row = \fB\f(CB\*(C`<y> \- SPACE\*(C'\fB\fR |
2315 | Row = \fB\f(CB\*(C`<y> \- SPACE\*(C'\fB\fR |
1997 | .SH "Key Codes" |
2316 | .SH "Key Codes" |
1998 | .IX Header "Key Codes" |
2317 | .IX Header "Key Codes" |
… | |
… | |
2062 | XK_KP_6 6 ESC O v |
2381 | XK_KP_6 6 ESC O v |
2063 | XK_KP_7 7 ESC O w |
2382 | XK_KP_7 7 ESC O w |
2064 | XK_KP_8 8 ESC O x |
2383 | XK_KP_8 8 ESC O x |
2065 | XK_KP_9 9 ESC O y |
2384 | XK_KP_9 9 ESC O y |
2066 | .TE |
2385 | .TE |
2067 | |
|
|
2068 | .SH "CONFIGURE OPTIONS" |
2386 | .SH "CONFIGURE OPTIONS" |
2069 | .IX Header "CONFIGURE OPTIONS" |
2387 | .IX Header "CONFIGURE OPTIONS" |
2070 | General hint: if you get compile errors, then likely your configuration |
2388 | General hint: if you get compile errors, then likely your configuration |
2071 | hasn't been tested well. Either try with \f(CW\*(C`\-\-enable\-everything\*(C'\fR or use |
2389 | hasn't been tested well. Either try with \f(CW\*(C`\-\-enable\-everything\*(C'\fR or use |
2072 | the \fI./reconf\fR script as a base for experiments. \fI./reconf\fR is used by |
2390 | the \fI./reconf\fR script as a base for experiments. \fI./reconf\fR is used by |
… | |
… | |
2110 | zh_ext rarely used but very big chinese encodigs |
2428 | zh_ext rarely used but very big chinese encodigs |
2111 | jp common japanese encodings |
2429 | jp common japanese encodings |
2112 | jp_ext rarely used but big japanese encodings |
2430 | jp_ext rarely used but big japanese encodings |
2113 | kr korean encodings |
2431 | kr korean encodings |
2114 | .TE |
2432 | .TE |
2115 | |
|
|
2116 | .IP "\-\-enable\-xim (default: on)" 4 |
2433 | .IP "\-\-enable\-xim (default: on)" 4 |
2117 | .IX Item "--enable-xim (default: on)" |
2434 | .IX Item "--enable-xim (default: on)" |
2118 | Add support for \s-1XIM\s0 (X Input Method) protocol. This allows using |
2435 | Add support for \s-1XIM\s0 (X Input Method) protocol. This allows using |
2119 | alternative input methods (e.g. kinput2) and will also correctly |
2436 | alternative input methods (e.g. kinput2) and will also correctly |
2120 | set up the input for people using dead keys or compose keys. |
2437 | set up the input for people using dead keys or compose keys. |
… | |
… | |
2228 | disable this. |
2545 | disable this. |
2229 | .Sp |
2546 | .Sp |
2230 | A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly |
2547 | A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly |
2231 | in combination with other switches) is: |
2548 | in combination with other switches) is: |
2232 | .Sp |
2549 | .Sp |
2233 | .Vb 15 |
2550 | .Vb 10 |
2234 | \& MWM-hints |
2551 | \& MWM\-hints |
2235 | \& EWMH-hints (pid, utf8 names) and protocols (ping) |
2552 | \& EWMH\-hints (pid, utf8 names) and protocols (ping) |
2236 | \& seperate underline colour (-underlineColor) |
2553 | \& seperate underline colour (\-underlineColor) |
2237 | \& settable border widths and borderless switch (-w, -b, -bl) |
2554 | \& settable border widths and borderless switch (\-w, \-b, \-bl) |
2238 | \& visual depth selection (-depth) |
2555 | \& visual depth selection (\-depth) |
2239 | \& settable extra linespacing /-lsp) |
2556 | \& settable extra linespacing /\-lsp) |
2240 | \& iso-14755-2 and -3, and visual feedback |
2557 | \& iso\-14755\-2 and \-3, and visual feedback |
2241 | \& tripleclickwords (-tcw) |
2558 | \& tripleclickwords (\-tcw) |
2242 | \& settable insecure mode (-insecure) |
2559 | \& settable insecure mode (\-insecure) |
2243 | \& keysym remapping support |
2560 | \& keysym remapping support |
2244 | \& cursor blinking and underline cursor (-cb, -uc) |
2561 | \& cursor blinking and underline cursor (\-cb, \-uc) |
2245 | \& XEmbed support (-embed) |
2562 | \& XEmbed support (\-embed) |
2246 | \& user-pty (-pty-fd) |
2563 | \& user\-pty (\-pty\-fd) |
2247 | \& hold on exit (-hold) |
2564 | \& hold on exit (\-hold) |
2248 | \& skip builtin block graphics (-sbg) |
2565 | \& skip builtin block graphics (\-sbg) |
|
|
2566 | \& separate highlightcolor support (\-hc) |
2249 | .Ve |
2567 | .Ve |
2250 | .Sp |
2568 | .Sp |
2251 | It also enabled some non-essential features otherwise disabled, such as: |
2569 | It also enables some non-essential features otherwise disabled, such as: |
2252 | .Sp |
2570 | .Sp |
2253 | .Vb 11 |
2571 | .Vb 11 |
2254 | \& some round-trip time optimisations |
2572 | \& some round\-trip time optimisations |
2255 | \& nearest color allocation on pseudocolor screens |
2573 | \& nearest color allocation on pseudocolor screens |
2256 | \& UTF8_STRING supporr for selection |
2574 | \& UTF8_STRING supporr for selection |
2257 | \& sgr modes 90..97 and 100..107 |
2575 | \& sgr modes 90..97 and 100..107 |
2258 | \& backindex and forwardindex escape sequences |
2576 | \& backindex and forwardindex escape sequences |
2259 | \& view change/zero scorllback esacpe sequences |
2577 | \& view change/zero scorllback esacpe sequences |
… | |
… | |
2285 | .IX Item "--disable-new-selection" |
2603 | .IX Item "--disable-new-selection" |
2286 | Remove support for mouse selection style like that of xterm. |
2604 | Remove support for mouse selection style like that of xterm. |
2287 | .IP "\-\-enable\-dmalloc (default: off)" 4 |
2605 | .IP "\-\-enable\-dmalloc (default: off)" 4 |
2288 | .IX Item "--enable-dmalloc (default: off)" |
2606 | .IX Item "--enable-dmalloc (default: off)" |
2289 | Use Gray Watson's malloc \- which is good for debugging See |
2607 | Use Gray Watson's malloc \- which is good for debugging See |
2290 | http://www.letters.com/dmalloc/ for details If you use either this or the |
2608 | <http://www.letters.com/dmalloc/> for details If you use either this or the |
2291 | next option, you may need to edit src/Makefile after compiling to point |
2609 | next option, you may need to edit src/Makefile after compiling to point |
2292 | \&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places. |
2610 | \&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places. |
2293 | .Sp |
2611 | .Sp |
2294 | You can only use either this option and the following (should |
2612 | You can only use either this option and the following (should |
2295 | you use either) . |
2613 | you use either) . |
… | |
… | |
2340 | .IX Header "AUTHORS" |
2658 | .IX Header "AUTHORS" |
2341 | Marc Lehmann <rxvt@schmorp.de> converted this document to pod and |
2659 | Marc Lehmann <rxvt@schmorp.de> converted this document to pod and |
2342 | reworked it from the original Rxvt documentation, which was done by Geoff |
2660 | reworked it from the original Rxvt documentation, which was done by Geoff |
2343 | Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other |
2661 | Wing <gcw@pobox.com>, who in turn used the XTerm documentation and other |
2344 | sources. |
2662 | sources. |
|
|
2663 | .SH "POD ERRORS" |
|
|
2664 | .IX Header "POD ERRORS" |
|
|
2665 | Hey! \fBThe above document had some coding errors, which are explained below:\fR |
|
|
2666 | .IP "Around line 2952:" 4 |
|
|
2667 | .IX Item "Around line 2952:" |
|
|
2668 | =back doesn't take any parameters, but you said =back X<Mouse> |
|
|
2669 | .IP "Around line 3048:" 4 |
|
|
2670 | .IX Item "Around line 3048:" |
|
|
2671 | =back doesn't take any parameters, but you said =back X<KeyCodes> |