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