… | |
… | |
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 | .Sh "The new selection selects pieces that are too big, how can I select single words?" |
160 | .Sh "Meta, Features & Commandline Issues" |
161 | .IX Subsection "The new selection selects pieces that are too big, how can I select single words?" |
161 | .IX Subsection "Meta, Features & Commandline Issues" |
162 | If you want to select e.g. alphanumeric words, you can use the following |
162 | \fIMy question isn't answered here, can I ask a human?\fR |
163 | setting: |
163 | .IX Subsection "My question isn't answered here, can I ask a human?" |
|
|
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: |
164 | .PP |
175 | .PP |
165 | .Vb 1 |
176 | .Vb 1 |
166 | \& URxvt.selection.pattern-0: ([[:word:]]+) |
177 | \& @@URXVT_NAME@@ -pe tabbed |
167 | .Ve |
178 | .Ve |
168 | .PP |
|
|
169 | If you click more than twice, the selection will be extended |
|
|
170 | more and more. |
|
|
171 | .PP |
|
|
172 | To get a selection that is very similar to the old code, try this pattern: |
|
|
173 | .PP |
179 | .PP |
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 | .PP |
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 | .Sh "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" |
186 | embedded into other programs, as witnessed by \fIdoc/rxvt\-tabbed\fR or |
181 | .IX Subsection "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 |
|
|
184 | rxvt-unicode from initialising perl, saving memory. |
|
|
185 | .PP |
189 | .PP |
186 | If you only want to disable specific features, you first have to |
190 | \fIHow do I know which rxvt-unicode version I'm using?\fR |
187 | identify which perl extension is responsible. For this, read the section |
191 | .IX Subsection "How do I know which rxvt-unicode version I'm using?" |
188 | \&\fB\s-1PREPACKAGED\s0 \s-1EXTENSIONS\s0\fR in the @@RXVT_NAME@@\fIperl\fR\|(3) manpage. For |
|
|
189 | example, to disable the \fBselection-popup\fR and \fBoption-popup\fR, specify |
|
|
190 | this \fBperl-ext-common\fR resource: |
|
|
191 | .PP |
192 | .PP |
|
|
193 | The version number is displayed with the usage (\-h). Also the escape |
|
|
194 | sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When |
|
|
195 | using the @@URXVT_NAME@@c client, the version displayed is that of the |
|
|
196 | daemon. |
|
|
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 | .PP |
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 |
|
|
199 | other combination either by setting the \fBsearchable-scrollback\fR resource: |
|
|
200 | .PP |
278 | .PP |
201 | .Vb 1 |
279 | You need to have a recent version of perl installed as \fI/usr/bin/perl\fR, |
202 | \& URxvt.searchable-scrollback: CM-s |
280 | one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to |
203 | .Ve |
281 | the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR. |
204 | .PP |
282 | .PP |
205 | \fIThe cursor moves when selecting text in the current input line, how do I switch this off?\fR |
|
|
206 | .IX Subsection "The cursor moves when selecting text in the current input line, how do I switch this off?" |
|
|
207 | .PP |
|
|
208 | See next entry. |
|
|
209 | .Sh "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?" |
|
|
210 | .IX Subsection "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?" |
|
|
211 | These are caused by the \f(CW\*(C`readline\*(C'\fR perl extension. Under normal |
|
|
212 | circumstances, it will move your cursor around when you click into the |
|
|
213 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
214 | but when running a program that doesn't parse cursor movements or in some |
|
|
215 | cases during rlogin sessions, it fails to detect this properly. |
|
|
216 | .PP |
|
|
217 | You can permamently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR |
|
|
218 | extension: |
|
|
219 | .PP |
|
|
220 | .Vb 1 |
|
|
221 | \& URxvt.perl-ext-common: default,-readline |
|
|
222 | .Ve |
|
|
223 | .Sh "Why doesn't rxvt-unicode read my resources?" |
|
|
224 | .IX Subsection "Why doesn't rxvt-unicode read my resources?" |
|
|
225 | Well, why, indeed? It does, in a way very similar to other X |
|
|
226 | applications. Most importantly, this means that if you or your \s-1OS\s0 loads |
|
|
227 | resources into the X display (the right way to do it), rxvt-unicode will |
|
|
228 | ignore any resource files in your home directory. It will only read |
|
|
229 | \&\fI$HOME/.Xdefaults\fR when no resources are attached to the display. |
|
|
230 | .PP |
|
|
231 | If you have or use an \fI$HOME/.Xresources\fR file, chances are that |
|
|
232 | resources are loaded into your X\-server. In this case, you have to |
|
|
233 | re-login after every change (or run \fIxrdb \-merge \f(CI$HOME\fI/.Xresources\fR). |
|
|
234 | .PP |
|
|
235 | Also consider the form resources have to use: |
|
|
236 | .PP |
|
|
237 | .Vb 1 |
|
|
238 | \& URxvt.resource: value |
|
|
239 | .Ve |
|
|
240 | .PP |
|
|
241 | If you want to use another form (there are lots of different ways of |
|
|
242 | specifying resources), make sure you understand wether and why it |
|
|
243 | works. If unsure, use the form above. |
|
|
244 | .Sh "I can't get transparency working, what am I doing wrong?" |
|
|
245 | .IX Subsection "I can't get transparency working, what am I doing wrong?" |
|
|
246 | First of all, transparency isn't officially supported in rxvt\-unicode, so |
|
|
247 | you are mostly on your own. Do not bug the author about it (but you may |
|
|
248 | bug everybody else). Also, if you can't get it working consider it a rite |
|
|
249 | of passage: ... and you failed. |
|
|
250 | .PP |
|
|
251 | Here are four ways to get transparency. \fBDo\fR read the manpage and option |
|
|
252 | descriptions for the programs mentioned and rxvt\-unicode. Really, do it! |
|
|
253 | .PP |
|
|
254 | 1. Use inheritPixmap: |
|
|
255 | .PP |
|
|
256 | .Vb 2 |
|
|
257 | \& Esetroot wallpaper.jpg |
|
|
258 | \& @@RXVT_NAME@@ -ip -tint red -sh 40 |
|
|
259 | .Ve |
|
|
260 | .PP |
|
|
261 | That works. If you think it doesn't, you lack transparency and tinting |
|
|
262 | support, or you are unable to read. |
|
|
263 | .PP |
|
|
264 | 2. Use a simple pixmap and emulate pseudo\-transparency. This enables you |
|
|
265 | to use effects other than tinting and shading: Just shade/tint/whatever |
|
|
266 | your picture with gimp: |
|
|
267 | .PP |
|
|
268 | .Vb 2 |
|
|
269 | \& convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
|
|
270 | \& @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background |
|
|
271 | .Ve |
|
|
272 | .PP |
|
|
273 | That works. If you think it doesn't, you lack \s-1XPM\s0 and Perl support, or you |
|
|
274 | are unable to read. |
|
|
275 | .PP |
|
|
276 | 3. Use an \s-1ARGB\s0 visual: |
|
|
277 | .PP |
|
|
278 | .Vb 1 |
|
|
279 | \& @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
|
|
280 | .Ve |
|
|
281 | .PP |
|
|
282 | This requires \s-1XFT\s0 support, and the support of your X\-server. If that |
|
|
283 | doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't |
|
|
284 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
|
|
285 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
|
|
286 | doesn't mean that your \s-1WM\s0 has the required kludges in place. |
|
|
287 | .PP |
|
|
288 | 4. Use xcompmgr and let it do the job: |
|
|
289 | .PP |
|
|
290 | .Vb 2 |
|
|
291 | \& xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \e |
|
|
292 | \& -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
|
|
293 | .Ve |
|
|
294 | .PP |
|
|
295 | Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR |
|
|
296 | by other values to change the degree of opacity. If it doesn't work and |
|
|
297 | your server crashes, you got to keep the pieces. |
|
|
298 | .Sh "Isn't rxvt supposed to be small? Don't all those features bloat?" |
283 | \fIIsn't rxvt-unicode supposed to be small? Don't all those features bloat?\fR |
299 | .IX Subsection "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 |
300 | 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 |
301 | 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 |
302 | 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 |
303 | 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 |
304 | 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 |
… | |
… | |
309 | \& text data bss drs rss filename |
295 | \& text data bss drs rss filename |
310 | \& 98398 1664 24 15695 1824 rxvt --disable-everything |
296 | \& 98398 1664 24 15695 1824 rxvt --disable-everything |
311 | \& 188985 9048 66616 18222 1788 urxvt --disable-everything |
297 | \& 188985 9048 66616 18222 1788 urxvt --disable-everything |
312 | .Ve |
298 | .Ve |
313 | .PP |
299 | .PP |
314 | 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 |
315 | 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 |
316 | libc), the two diverge, but not unreasnobaly so. |
302 | libc), the two diverge, but not unreasnobaly so. |
317 | .PP |
303 | .PP |
318 | .Vb 3 |
304 | .Vb 3 |
319 | \& text data bss drs rss filename |
305 | \& text data bss drs rss filename |
… | |
… | |
338 | 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 |
339 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
325 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
340 | 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 |
341 | 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 |
342 | extremely well *g*. |
328 | extremely well *g*. |
|
|
329 | .PP |
343 | .Sh "Why \*(C+, isn't that unportable/bloated/uncool?" |
330 | \fIWhy \*(C+, isn't that unportable/bloated/uncool?\fR |
344 | .IX Subsection "Why , isn't that unportable/bloated/uncool?" |
331 | .IX Subsection "Why , isn't that unportable/bloated/uncool?" |
|
|
332 | .PP |
345 | 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 |
346 | 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 |
347 | 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 |
348 | shorter: It simply wouldn't exist without \*(C+. |
336 | shorter: It simply wouldn't exist without \*(C+. |
349 | .PP |
337 | .PP |
… | |
… | |
375 | \& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
363 | \& /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
376 | .Ve |
364 | .Ve |
377 | .PP |
365 | .PP |
378 | No large bloated libraries (of course, none were linked in statically), |
366 | No large bloated libraries (of course, none were linked in statically), |
379 | except maybe libX11 :) |
367 | except maybe libX11 :) |
380 | .Sh "Does it support tabs, can I have a tabbed rxvt\-unicode?" |
368 | .Sh "Rendering, Font & Look and Feel Issues" |
381 | .IX Subsection "Does it support tabs, can I have a tabbed rxvt-unicode?" |
369 | .IX Subsection "Rendering, Font & Look and Feel Issues" |
382 | 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 |
383 | 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?" |
384 | give you tabs: |
372 | .PP |
|
|
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: |
385 | .PP |
404 | .PP |
386 | .Vb 1 |
405 | .Vb 1 |
387 | \& @@RXVT_NAME@@ -pe tabbed |
406 | \& @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
388 | .Ve |
407 | .Ve |
|
|
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: |
389 | .PP |
479 | .PP |
390 | .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 |
391 | \& URxvt.perl-ext-common: default,tabbed |
724 | \& URxvt.perl-ext-common: default,-readline |
392 | .Ve |
725 | .Ve |
393 | .PP |
726 | .PP |
394 | It will also work fine with tabbing functionality of many window managers |
727 | \fIMy numerical keypad acts weird and generates differing output?\fR |
395 | or similar tabbing programs, and its embedding-features allow it to be |
728 | .IX Subsection "My numerical keypad acts weird and generates differing output?" |
396 | embedded into other programs, as witnessed by \fIdoc/rxvt\-tabbed\fR or |
|
|
397 | the upcoming \f(CW\*(C`Gtk2::URxvt\*(C'\fR perl module, which features a tabbed urxvt |
|
|
398 | (murxvt) terminal as an example embedding application. |
|
|
399 | .Sh "How do I know which rxvt-unicode version I'm using?" |
|
|
400 | .IX Subsection "How do I know which rxvt-unicode version I'm using?" |
|
|
401 | The version number is displayed with the usage (\-h). Also the escape |
|
|
402 | sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. When |
|
|
403 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
|
|
404 | daemon. |
|
|
405 | .Sh "I am using Debian GNU/Linux and have a problem..." |
|
|
406 | .IX Subsection "I am using Debian GNU/Linux and have a problem..." |
|
|
407 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
408 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
409 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
410 | the original rxvt-unicode author please download and install the genuine |
|
|
411 | version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce |
|
|
412 | the problem. If you cannot, chances are that the problems are specific to |
|
|
413 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
|
|
414 | Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug). |
|
|
415 | .PP |
729 | .PP |
416 | For other problems that also affect the Debian package, you can and |
730 | Some Debian GNUL/Linux users seem to have this problem, although no |
417 | probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a |
731 | specific details were reported so far. It is possible that this is caused |
418 | bug in the Debian version and it serves as a reminder for other users that |
732 | by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how |
419 | might encounter the same issue. |
733 | this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible |
420 | .Sh "I am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?" |
734 | keymap. See the answer to the previous question, and please report if that |
421 | .IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?" |
735 | helped. |
422 | You should build one binary with the default options. \fIconfigure\fR |
|
|
423 | now enables most useful options, and the trend goes to making them |
|
|
424 | runtime\-switchable, too, so there is usually no drawback to enbaling them, |
|
|
425 | except higher disk and possibly memory usage. The perl interpreter should |
|
|
426 | be enabled, as important functionality (menus, selection, likely more in |
|
|
427 | the future) depends on it. |
|
|
428 | .PP |
736 | .PP |
429 | You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources |
737 | \fIMy Compose (Multi_key) key is no longer working.\fR |
430 | system-wide (except maybe with \f(CW\*(C`defaults\*(C'\fR). This will result in useful |
738 | .IX Subsection "My Compose (Multi_key) key is no longer working." |
431 | behaviour. If your distribution aims at low memory, add an empty |
|
|
432 | \&\f(CW\*(C`perl\-ext\-common\*(C'\fR resource to the app-defaults file. This will keep the |
|
|
433 | perl interpreter disabled until the user enables it. |
|
|
434 | .PP |
739 | .PP |
435 | If you can/want build more binaries, I recommend building a minimal |
740 | The most common causes for this are that either your locale is not set |
436 | one with \f(CW\*(C`\-\-disable\-everything\*(C'\fR (very useful) and a maximal one with |
741 | correctly, or you specified a \fBpreeditStyle\fR that is not supported by |
437 | \&\f(CW\*(C`\-\-enable\-everything\*(C'\fR (less useful, it will be very big due to a lot of |
742 | your input method. For example, if you specified \fBOverTheSpot\fR and |
438 | encodings built-in that increase download times and are rarely used). |
743 | your input method (e.g. the default input method handling Compose keys) |
439 | .Sh "I need to make it setuid/setgid to support utmp/ptys on my \s-1OS\s0, is this safe?" |
744 | does not support this (for instance because it is not visual), then |
440 | .IX Subsection "I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe?" |
745 | rxvt-unicode will continue without an input method. |
441 | It should be, starting with release 7.1. You are encouraged to properly |
|
|
442 | install urxvt with privileges necessary for your \s-1OS\s0 now. |
|
|
443 | .PP |
746 | .PP |
444 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
747 | In this case either do not specify a \fBpreeditStyle\fR or specify more than |
445 | into a helper process for privileged operations (pty handling on some |
748 | one pre-edit style, such as \fBOverTheSpot,Root,None\fR. |
446 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
|
|
447 | immediately. This is much safer than most other terminals that keep |
|
|
448 | privileges while running (but is more relevant to urxvt, as it contains |
|
|
449 | things as perl interpreters, which might be \*(L"helpful\*(R" to attackers). |
|
|
450 | .PP |
749 | .PP |
451 | This forking is done as the very first within \fImain()\fR, which is very early |
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 |
452 | and reduces possible bugs to initialisation code run before \fImain()\fR, or |
751 | .IX Subsection "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755" |
453 | things like the dynamic loader of your system, which should result in very |
752 | .PP |
454 | little risk. |
753 | Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on |
|
|
754 | international keyboards) or simply use \s-1ISO\s0 14755 support to your |
|
|
755 | advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other |
|
|
756 | codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape |
|
|
757 | character and so on. |
|
|
758 | .PP |
|
|
759 | \fIMouse cut/paste suddenly no longer works.\fR |
|
|
760 | .IX Subsection "Mouse cut/paste suddenly no longer works." |
|
|
761 | .PP |
|
|
762 | Make sure that mouse reporting is actually turned off since killing |
|
|
763 | some editors prematurely may leave the mouse in mouse report mode. I've |
|
|
764 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
|
|
765 | quick check is to see if cut/paste works when the Alt or Shift keys are |
|
|
766 | depressed. |
|
|
767 | .PP |
|
|
768 | \fIWhat's with the strange Backspace/Delete key behaviour?\fR |
|
|
769 | .IX Subsection "What's with the strange Backspace/Delete key behaviour?" |
|
|
770 | .PP |
|
|
771 | Assuming that the physical Backspace key corresponds to the |
|
|
772 | BackSpace keysym (not likely for Linux ... see the following |
|
|
773 | question) there are two standard values that can be used for |
|
|
774 | Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR. |
|
|
775 | .PP |
|
|
776 | Historically, either value is correct, but rxvt-unicode adopts the debian |
|
|
777 | policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct |
|
|
778 | choice :). |
|
|
779 | .PP |
|
|
780 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
|
|
781 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
|
|
782 | started from a terminal (say, from a menu or by remote shell), then the |
|
|
783 | system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will |
|
|
784 | be used (which may not be the same as your stty setting). |
|
|
785 | .PP |
|
|
786 | For starting a new rxvt\-unicode: |
|
|
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 |
455 | .Sh "When I log-in to another system it tells me about missing terminfo data?" |
1091 | \fIWhen I log-in to another system it tells me about missing terminfo data?\fR |
456 | .IX Subsection "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 |
457 | 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 |
458 | 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). |
459 | .PP |
1096 | .PP |
460 | 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 |
461 | be done like this (with ncurses' infocmp): |
1098 | be done like this (with ncurses' infocmp): |
… | |
… | |
480 | .Vb 1 |
1117 | .Vb 1 |
481 | \& URxvt.termName: rxvt |
1118 | \& URxvt.termName: rxvt |
482 | .Ve |
1119 | .Ve |
483 | .PP |
1120 | .PP |
484 | 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 |
485 | 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. |
486 | .ie n .Sh """tic"" outputs some error when compiling the terminfo entry." |
1123 | .PP |
487 | .el .Sh "\f(CWtic\fP outputs some error when compiling the terminfo entry." |
1124 | \fI\f(CI\*(C`tic\*(C'\fI outputs some error when compiling the terminfo entry.\fR |
488 | .IX Subsection "tic outputs some error when compiling the terminfo entry." |
1125 | .IX Subsection "tic outputs some error when compiling the terminfo entry." |
|
|
1126 | .PP |
489 | 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 |
490 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
1128 | \&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again. |
491 | .ie n .Sh """bash""'s readline does not work correctly under @@RXVT_NAME@@." |
1129 | .PP |
492 | .el .Sh "\f(CWbash\fP's readline does not work correctly under @@RXVT_NAME@@." |
1130 | \fI\f(CI\*(C`bash\*(C'\fI's readline does not work correctly under @@URXVT_NAME@@.\fR |
493 | .IX Subsection "bash's readline does not work correctly under @@RXVT_NAME@@." |
1131 | .IX Subsection "bash's readline does not work correctly under @@URXVT_NAME@@." |
|
|
1132 | .PP |
494 | See next entry. |
1133 | See next entry. |
|
|
1134 | .PP |
495 | .Sh "I need a termcap file entry." |
1135 | \fII need a termcap file entry.\fR |
496 | .IX Subsection "I need a termcap file entry." |
1136 | .IX Subsection "I need a termcap file entry." |
|
|
1137 | .PP |
497 | 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 |
498 | systems still compile some programs using the long-obsoleted termcap |
1139 | systems still compile some programs using the long-obsoleted termcap |
499 | library (Fedora Core's bash is one example) and rely on a termcap entry |
1140 | library (Fedora Core's bash is one example) and rely on a termcap entry |
500 | for \f(CW\*(C`rxvt\-unicode\*(C'\fR. |
1141 | for \f(CW\*(C`rxvt\-unicode\*(C'\fR. |
501 | .PP |
1142 | .PP |
… | |
… | |
529 | \& :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 |
530 | \& :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 |
531 | \& :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 |
532 | \& :vs=\eE[?25h: |
1173 | \& :vs=\eE[?25h: |
533 | .Ve |
1174 | .Ve |
534 | .ie n .Sh "Why does ""ls"" no longer have coloured output?" |
1175 | .PP |
535 | .el .Sh "Why does \f(CWls\fP no longer have coloured output?" |
1176 | \fIWhy does \f(CI\*(C`ls\*(C'\fI no longer have coloured output?\fR |
536 | .IX Subsection "Why does ls no longer have coloured output?" |
1177 | .IX Subsection "Why does ls no longer have coloured output?" |
|
|
1178 | .PP |
537 | 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 |
538 | 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 |
539 | 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 |
540 | with most other terminals supporting colour). Either add: |
1182 | with most other terminals supporting colour). Either add: |
541 | .PP |
1183 | .PP |
… | |
… | |
548 | .Vb 1 |
1190 | .Vb 1 |
549 | \& alias ls='ls --color=auto' |
1191 | \& alias ls='ls --color=auto' |
550 | .Ve |
1192 | .Ve |
551 | .PP |
1193 | .PP |
552 | 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 |
553 | .Sh "Why doesn't vim/emacs etc. use the 88 colour mode?" |
1196 | \fIWhy doesn't vim/emacs etc. use the 88 colour mode?\fR |
554 | .IX Subsection "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?" |
|
|
1198 | .PP |
555 | See next entry. |
1199 | See next entry. |
|
|
1200 | .PP |
556 | .Sh "Why doesn't vim/emacs etc. make use of italic?" |
1201 | \fIWhy doesn't vim/emacs etc. make use of italic?\fR |
557 | .IX Subsection "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 |
558 | See next entry. |
1204 | See next entry. |
|
|
1205 | .PP |
559 | .Sh "Why are the secondary screen-related options not working properly?" |
1206 | \fIWhy are the secondary screen-related options not working properly?\fR |
560 | .IX Subsection "Why are the secondary screen-related options not working properly?" |
1207 | .IX Subsection "Why are the secondary screen-related options not working properly?" |
|
|
1208 | .PP |
561 | 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 |
562 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
1210 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
563 | by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra |
1211 | by setting \f(CW\*(C`TERM\*(C'\fR to \f(CW\*(C`rxvt\*(C'\fR, which doesn't have these extra |
564 | features. Unfortunately, some of these (most notably, again, Debian |
1212 | features. Unfortunately, some of these (most notably, again, Debian |
565 | GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo |
1213 | GNU/Linux) furthermore fail to even install the \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo |
566 | file, so you will need to install it on your own (See the question \fBWhen |
1214 | file, so you will need to install it on your own (See the question \fBWhen |
567 | I log-in to another system it tells me about missing terminfo data?\fR on |
1215 | I log-in to another system it tells me about missing terminfo data?\fR on |
568 | how to do this). |
1216 | how to do this). |
569 | .Sh "My numerical keypad acts weird and generates differing output?" |
1217 | .Sh "Encoding / Locale / Input Method Issues" |
570 | .IX Subsection "My numerical keypad acts weird and generates differing output?" |
1218 | .IX Subsection "Encoding / Locale / Input Method Issues" |
571 | Some Debian GNUL/Linux users seem to have this problem, although no |
|
|
572 | specific details were reported so far. It is possible that this is caused |
|
|
573 | by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how |
|
|
574 | this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible |
|
|
575 | keymap. See the answer to the previous question, and please report if that |
|
|
576 | helped. |
|
|
577 | .Sh "Rxvt-unicode does not seem to understand the selected encoding?" |
1219 | \fIRxvt-unicode does not seem to understand the selected encoding?\fR |
578 | .IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?" |
1220 | .IX Subsection "Rxvt-unicode does not seem to understand the selected encoding?" |
|
|
1221 | .PP |
579 | See next entry. |
1222 | See next entry. |
|
|
1223 | .PP |
580 | .Sh "Unicode does not seem to work?" |
1224 | \fIUnicode does not seem to work?\fR |
581 | .IX Subsection "Unicode does not seem to work?" |
1225 | .IX Subsection "Unicode does not seem to work?" |
|
|
1226 | .PP |
582 | If you encounter strange problems like typing an accented character but |
1227 | If you encounter strange problems like typing an accented character but |
583 | 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 |
584 | subtly garbled, then you should check your locale settings. |
1229 | subtly garbled, then you should check your locale settings. |
585 | .PP |
1230 | .PP |
586 | 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 |
… | |
… | |
608 | Then the locale you specified is not supported on your system. |
1253 | Then the locale you specified is not supported on your system. |
609 | .PP |
1254 | .PP |
610 | 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 |
611 | 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 |
612 | support locales :( |
1257 | support locales :( |
613 | .Sh "Why do some characters look so much different than others?" |
1258 | .PP |
614 | .IX Subsection "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 |
615 | See next entry. |
1262 | See next entry. |
616 | .Sh "How does rxvt-unicode choose fonts?" |
|
|
617 | .IX Subsection "How does rxvt-unicode choose fonts?" |
|
|
618 | Most fonts do not contain the full range of Unicode, which is |
|
|
619 | fine. Chances are that the font you (or the admin/package maintainer of |
|
|
620 | your system/os) have specified does not cover all the characters you want |
|
|
621 | to display. |
|
|
622 | .PP |
1263 | .PP |
623 | \&\fBrxvt-unicode\fR makes a best-effort try at finding a replacement |
1264 | \fIIs there an option to switch encodings?\fR |
624 | font. Often the result is fine, but sometimes the chosen font looks |
1265 | .IX Subsection "Is there an option to switch encodings?" |
625 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
|
|
626 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
|
|
627 | intelligence to detect that a specific glyph is wrong: it has to believe |
|
|
628 | the font that the characters it claims to contain indeed look correct. |
|
|
629 | .PP |
1266 | .PP |
630 | In that case, select a font of your taste and add it to the font list, |
1267 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
631 | e.g.: |
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. |
632 | .PP |
1305 | .PP |
633 | .Vb 1 |
1306 | .Vb 1 |
634 | \& @@RXVT_NAME@@ -fn basefont,font2,font3... |
1307 | \& printf '\ee]701;%s\e007' ja_JP.SJIS |
635 | .Ve |
1308 | .Ve |
636 | .PP |
1309 | .PP |
637 | When rxvt-unicode sees a character, it will first look at the base |
1310 | See also the previous answer. |
638 | font. If the base font does not contain the character, it will go to the |
|
|
639 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
640 | search and use less resources within rxvt-unicode and the X\-server. |
|
|
641 | .PP |
1311 | .PP |
642 | The only limitation is that none of the fonts may be larger than the base |
1312 | Sometimes this capability is rather handy when you want to work in |
643 | font, as the base font defines the terminal character cell size, which |
1313 | one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it |
644 | must be the same due to the way terminals work. |
1314 | (e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which |
645 | .Sh "Why do some chinese characters look so different than others?" |
1315 | first switches to a locale supported by xjdic and back later: |
646 | .IX Subsection "Why do some chinese characters look so different than others?" |
|
|
647 | This is because there is a difference between script and language \*(-- |
|
|
648 | rxvt-unicode does not know which language the text that is output is, |
|
|
649 | as it only knows the unicode character codes. If rxvt-unicode first |
|
|
650 | sees a japanese/chinese character, it might choose a japanese font for |
|
|
651 | display. Subsequent japanese characters will use that font. Now, many |
|
|
652 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
653 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
654 | \&\*(-- unfortunately at this point, it will still use the japanese font for |
|
|
655 | chinese characters that are also in the japanese font. |
|
|
656 | .PP |
1316 | .PP |
657 | The workaround is easy: just tag a chinese font at the end of your font |
1317 | .Vb 3 |
658 | list (see the previous question). The key is to view the font list as |
1318 | \& printf '\ee]701;%s\e007' ja_JP.SJIS |
659 | a preference list: If you expect more japanese, list a japanese font |
1319 | \& xjdic -js |
660 | first. If you expect more chinese, put a chinese font first. |
1320 | \& printf '\ee]701;%s\e007' de_DE.UTF-8 |
|
|
1321 | .Ve |
661 | .PP |
1322 | .PP |
662 | In the future it might be possible to switch language preferences at |
1323 | You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except |
663 | runtime (the internal data structure has no problem with using different |
1324 | for some locales where character width differs between program\- and |
664 | fonts for the same character at the same time, but no interface for this |
1325 | rxvt\-unicode\-locales. |
665 | has been designed yet). |
|
|
666 | .PP |
1326 | .PP |
667 | Until then, you might get away with switching fonts at runtime (see \*(L"Can I switch the fonts at runtime?\*(R" later in this document). |
1327 | \fII have problems getting my input method working.\fR |
668 | .Sh "Why does rxvt-unicode sometimes leave pixel droppings?" |
1328 | .IX Subsection "I have problems getting my input method working." |
669 | .IX Subsection "Why does rxvt-unicode sometimes leave pixel droppings?" |
|
|
670 | Most fonts were not designed for terminal use, which means that character |
|
|
671 | size varies a lot. A font that is otherwise fine for terminal use might |
|
|
672 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
|
|
673 | these characters. For characters that are just \*(L"a bit\*(R" too wide a special |
|
|
674 | \&\*(L"careful\*(R" rendering mode is used that redraws adjacent characters. |
|
|
675 | .PP |
1329 | .PP |
676 | All of this requires that fonts do not lie about character sizes, |
1330 | Try a search engine, as this is slightly different for every input method server. |
677 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
|
|
678 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
|
|
679 | ask for the character bounding box, which unfortunately is wrong in these |
|
|
680 | cases). |
|
|
681 | .PP |
1331 | .PP |
682 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
1332 | Here is a checklist: |
683 | or the respective font. If you encounter this problem you might try using |
1333 | .IP "\- Make sure your locale \fIand\fR the imLocale are supported on your \s-1OS\s0." 4 |
684 | the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you |
1334 | .IX Item "- Make sure your locale and the imLocale are supported on your OS." |
685 | might be forced to use a different font. |
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." |
|
|
1342 | .PD 0 |
|
|
1343 | .ie n .IP "\- Make sure the ""XMODIFIERS""\fR environment variable is set correctly when \fIstarting rxvt\-unicode." 4 |
|
|
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." |
|
|
1346 | .PD |
|
|
1347 | When you want to use e.g. \fBkinput2\fR, it must be set to |
|
|
1348 | \&\f(CW\*(C`@im=kinput2\*(C'\fR. For \fBscim\fR, use \f(CW\*(C`@im=SCIM\*(C'\fR. Youc an see what input |
|
|
1349 | method servers are running with this command: |
|
|
1350 | .Sp |
|
|
1351 | .Vb 1 |
|
|
1352 | \& xprop -root XIM_SERVERS |
|
|
1353 | .Ve |
|
|
1354 | .IP "*" 4 |
686 | .PP |
1355 | .PP |
687 | All of this is not a problem when using X11 core fonts, as their bounding |
1356 | \fIMy input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?\fR |
688 | box data is correct. |
1357 | .IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?" |
|
|
1358 | .PP |
|
|
1359 | You can specify separate locales for the input method and the rest of the |
|
|
1360 | terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR: |
|
|
1361 | .PP |
|
|
1362 | .Vb 1 |
|
|
1363 | \& URxvt.imlocale: ja_JP.EUC-JP |
|
|
1364 | .Ve |
|
|
1365 | .PP |
|
|
1366 | Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still |
|
|
1367 | use your input method. Please note, however, that, depending on your Xlib |
|
|
1368 | version, you may not be able to input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a |
|
|
1369 | normal way then, as your input method limits you. |
|
|
1370 | .PP |
|
|
1371 | \fIRxvt-unicode crashes when the X Input Method changes or exits.\fR |
|
|
1372 | .IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits." |
|
|
1373 | .PP |
|
|
1374 | Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by |
|
|
1375 | design. Applications can avoid some crashes at the expense of memory |
|
|
1376 | leaks, and Input Methods can avoid some crashes by careful ordering at |
|
|
1377 | exit time. \fBkinput2\fR (and derived input methods) generally succeeds, |
|
|
1378 | while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however, |
|
|
1379 | crashes cannot be completely avoided even if both sides cooperate. |
|
|
1380 | .PP |
|
|
1381 | So the only workaround is not to kill your Input Method Servers. |
|
|
1382 | .Sh "Operating Systems / Package Maintaining" |
|
|
1383 | .IX Subsection "Operating Systems / Package Maintaining" |
|
|
1384 | \fII am using Debian GNU/Linux and have a problem...\fR |
|
|
1385 | .IX Subsection "I am using Debian GNU/Linux and have a problem..." |
|
|
1386 | .PP |
|
|
1387 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
1388 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
1389 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
1390 | the original rxvt-unicode author please download and install the genuine |
|
|
1391 | version (<http://software.schmorp.de#rxvt\-unicode>) and try to reproduce |
|
|
1392 | the problem. If you cannot, chances are that the problems are specific to |
|
|
1393 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
|
|
1394 | Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug). |
|
|
1395 | .PP |
|
|
1396 | For other problems that also affect the Debian package, you can and |
|
|
1397 | probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a |
|
|
1398 | bug in the Debian version and it serves as a reminder for other users that |
|
|
1399 | might encounter the same issue. |
|
|
1400 | .PP |
|
|
1401 | \fII am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?\fR |
|
|
1402 | .IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?" |
|
|
1403 | .PP |
|
|
1404 | You should build one binary with the default options. \fIconfigure\fR |
|
|
1405 | now enables most useful options, and the trend goes to making them |
|
|
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 |
689 | .Sh "On Solaris 9, many line-drawing characters are too wide." |
1440 | \fIOn Solaris 9, many line-drawing characters are too wide.\fR |
690 | .IX Subsection "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 |
691 | Seems to be a known bug, read |
1443 | Seems to be a known bug, read |
692 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
1444 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
693 | following ugly workaround to get non-double-wide-characters working: |
1445 | following ugly workaround to get non-double-wide-characters working: |
694 | .PP |
1446 | .PP |
695 | .Vb 1 |
1447 | .Vb 1 |
696 | \& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
1448 | \& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
697 | .Ve |
1449 | .Ve |
698 | .Sh "My Compose (Multi_key) key is no longer working." |
|
|
699 | .IX Subsection "My Compose (Multi_key) key is no longer working." |
|
|
700 | The most common causes for this are that either your locale is not set |
|
|
701 | correctly, or you specified a \fBpreeditStyle\fR that is not supported by |
|
|
702 | your input method. For example, if you specified \fBOverTheSpot\fR and |
|
|
703 | your input method (e.g. the default input method handling Compose keys) |
|
|
704 | does not support this (for instance because it is not visual), then |
|
|
705 | rxvt-unicode will continue without an input method. |
|
|
706 | .PP |
1450 | .PP |
707 | In this case either do not specify a \fBpreeditStyle\fR or specify more than |
|
|
708 | one pre-edit style, such as \fBOverTheSpot,Root,None\fR. |
|
|
709 | .ie n .Sh "I cannot type ""Ctrl\-Shift\-2"" to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" |
|
|
710 | .el .Sh "I cannot type \f(CWCtrl\-Shift\-2\fP to get an \s-1ASCII\s0 \s-1NUL\s0 character due to \s-1ISO\s0 14755" |
|
|
711 | .IX Subsection "I cannot type Ctrl-Shift-2 to get an ASCII NUL character due to ISO 14755" |
|
|
712 | Either try \f(CW\*(C`Ctrl\-2\*(C'\fR alone (it often is mapped to \s-1ASCII\s0 \s-1NUL\s0 even on |
|
|
713 | international keyboards) or simply use \s-1ISO\s0 14755 support to your |
|
|
714 | advantage, typing <Ctrl\-Shift\-0> to get a \s-1ASCII\s0 \s-1NUL\s0. This works for other |
|
|
715 | codes, too, such as \f(CW\*(C`Ctrl\-Shift\-1\-d\*(C'\fR to type the default telnet escape |
|
|
716 | character and so on. |
|
|
717 | .Sh "How can I keep rxvt-unicode from using reverse video so much?" |
|
|
718 | .IX Subsection "How can I keep rxvt-unicode from using reverse video so much?" |
|
|
719 | First of all, make sure you are running with the right terminal settings |
|
|
720 | (\f(CW\*(C`TERM=rxvt\-unicode\*(C'\fR), which will get rid of most of these effects. Then |
|
|
721 | make sure you have specified colours for italic and bold, as otherwise |
|
|
722 | rxvt-unicode might use reverse video to simulate the effect: |
|
|
723 | .PP |
|
|
724 | .Vb 2 |
|
|
725 | \& URxvt.colorBD: white |
|
|
726 | \& URxvt.colorIT: green |
|
|
727 | .Ve |
|
|
728 | .Sh "Some programs assume totally weird colours (red instead of blue), how can I fix that?" |
|
|
729 | .IX Subsection "Some programs assume totally weird colours (red instead of blue), how can I fix that?" |
|
|
730 | For some unexplainable reason, some rare programs assume a very weird |
|
|
731 | colour palette when confronted with a terminal with more than the standard |
|
|
732 | 8 colours (rxvt\-unicode supports 88). The right fix is, of course, to fix |
|
|
733 | these programs not to assume non-ISO colours without very good reasons. |
|
|
734 | .PP |
|
|
735 | In the meantime, you can either edit your \f(CW\*(C`rxvt\-unicode\*(C'\fR terminfo |
|
|
736 | definition to only claim 8 colour support or use \f(CW\*(C`TERM=rxvt\*(C'\fR, which will |
|
|
737 | fix colours but keep you from using other rxvt-unicode features. |
|
|
738 | .Sh "I am on FreeBSD and rxvt-unicode does not seem to work at all." |
1451 | \fII am on FreeBSD and rxvt-unicode does not seem to work at all.\fR |
739 | .IX Subsection "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 |
740 | 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 |
741 | in your compile environment, or an implementation that implements it, |
1455 | in your compile environment, or an implementation that implements it, |
742 | 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 |
743 | \&\fBwchar_t\fR is represented as unicode. |
1457 | \&\fBwchar_t\fR is represented as unicode. |
744 | .PP |
1458 | .PP |
… | |
… | |
764 | encodings slightly different than the terminal emulator). |
1478 | encodings slightly different than the terminal emulator). |
765 | .PP |
1479 | .PP |
766 | 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 |
767 | 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 |
768 | complete replacements for them :) |
1482 | complete replacements for them :) |
|
|
1483 | .PP |
769 | .Sh "I use Solaris 9 and it doesn't compile/work/etc." |
1484 | \fII use Solaris 9 and it doesn't compile/work/etc.\fR |
770 | .IX Subsection "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 |
771 | 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 |
772 | 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 |
773 | .Sh "How can I use rxvt-unicode under cygwin?" |
1490 | \fIHow can I use rxvt-unicode under cygwin?\fR |
774 | .IX Subsection "How can I use rxvt-unicode under cygwin?" |
1491 | .IX Subsection "How can I use rxvt-unicode under cygwin?" |
|
|
1492 | .PP |
775 | 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 |
776 | the X11 libraries that come with cygwin. libW11 emulation is no |
1494 | the X11 libraries that come with cygwin. libW11 emulation is no |
777 | 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 |
778 | 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 |
779 | \&\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 |
780 | old libW11 emulation. |
1498 | old libW11 emulation. |
781 | .PP |
1499 | .PP |
782 | 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 |
783 | 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 |
784 | to 8\-bit encodings. |
1502 | to 8\-bit encodings. |
785 | .Sh "How does rxvt-unicode determine the encoding to use?" |
|
|
786 | .IX Subsection "How does rxvt-unicode determine the encoding to use?" |
|
|
787 | See next entry. |
|
|
788 | .Sh "Is there an option to switch encodings?" |
|
|
789 | .IX Subsection "Is there an option to switch encodings?" |
|
|
790 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
|
|
791 | specific \*(L"utf\-8\*(R" mode, such as xterm. In fact, it doesn't even know about |
|
|
792 | \&\s-1UTF\-8\s0 or any other encodings with respect to terminal I/O. |
|
|
793 | .PP |
|
|
794 | The reasons is that there exists a perfectly fine mechanism for selecting |
|
|
795 | the encoding, doing I/O and (most important) communicating this to all |
|
|
796 | applications so everybody agrees on character properties such as width |
|
|
797 | and code number. This mechanism is the \fIlocale\fR. Applications not using |
|
|
798 | that info will have problems (for example, \f(CW\*(C`xterm\*(C'\fR gets the width of |
|
|
799 | characters wrong as it uses it's own, locale-independent table under all |
|
|
800 | locales). |
|
|
801 | .PP |
|
|
802 | Rxvt-unicode uses the \f(CW\*(C`LC_CTYPE\*(C'\fR locale category to select encoding. All |
|
|
803 | programs doing the same (that is, most) will automatically agree in the |
|
|
804 | interpretation of characters. |
|
|
805 | .PP |
|
|
806 | Unfortunately, there is no system-independent way to select locales, nor |
|
|
807 | is there a standard on how locale specifiers will look like. |
|
|
808 | .PP |
|
|
809 | On most systems, the content of the \f(CW\*(C`LC_CTYPE\*(C'\fR environment variable |
|
|
810 | contains an arbitrary string which corresponds to an already-installed |
|
|
811 | locale. Common names for locales are \f(CW\*(C`en_US.UTF\-8\*(C'\fR, \f(CW\*(C`de_DE.ISO\-8859\-15\*(C'\fR, |
|
|
812 | \&\f(CW\*(C`ja_JP.EUC\-JP\*(C'\fR, i.e. \f(CW\*(C`language_country.encoding\*(C'\fR, but other forms |
|
|
813 | (i.e. \f(CW\*(C`de\*(C'\fR or \f(CW\*(C`german\*(C'\fR) are also common. |
|
|
814 | .PP |
|
|
815 | Rxvt-unicode ignores all other locale categories, and except for |
|
|
816 | the encoding, ignores country or language-specific settings, |
|
|
817 | i.e. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR and \f(CW\*(C`ja_JP.UTF\-8\*(C'\fR are the normally same to |
|
|
818 | rxvt\-unicode. |
|
|
819 | .PP |
|
|
820 | If you want to use a specific encoding you have to make sure you start |
|
|
821 | rxvt-unicode with the correct \f(CW\*(C`LC_CTYPE\*(C'\fR category. |
|
|
822 | .Sh "Can I switch locales at runtime?" |
|
|
823 | .IX Subsection "Can I switch locales at runtime?" |
|
|
824 | Yes, using an escape sequence. Try something like this, which sets |
|
|
825 | rxvt\-unicode's idea of \f(CW\*(C`LC_CTYPE\*(C'\fR. |
|
|
826 | .PP |
|
|
827 | .Vb 1 |
|
|
828 | \& printf '\ee]701;%s\e007' ja_JP.SJIS |
|
|
829 | .Ve |
|
|
830 | .PP |
|
|
831 | See also the previous answer. |
|
|
832 | .PP |
|
|
833 | Sometimes this capability is rather handy when you want to work in |
|
|
834 | one locale (e.g. \f(CW\*(C`de_DE.UTF\-8\*(C'\fR) but some programs don't support it |
|
|
835 | (e.g. \s-1UTF\-8\s0). For example, I use this script to start \f(CW\*(C`xjdic\*(C'\fR, which |
|
|
836 | first switches to a locale supported by xjdic and back later: |
|
|
837 | .PP |
|
|
838 | .Vb 3 |
|
|
839 | \& printf '\ee]701;%s\e007' ja_JP.SJIS |
|
|
840 | \& xjdic -js |
|
|
841 | \& printf '\ee]701;%s\e007' de_DE.UTF-8 |
|
|
842 | .Ve |
|
|
843 | .PP |
|
|
844 | You can also use xterm's \f(CW\*(C`luit\*(C'\fR program, which usually works fine, except |
|
|
845 | for some locales where character width differs between program\- and |
|
|
846 | rxvt\-unicode\-locales. |
|
|
847 | .Sh "Can I switch the fonts at runtime?" |
|
|
848 | .IX Subsection "Can I switch the fonts at runtime?" |
|
|
849 | Yes, using an escape sequence. Try something like this, which has the same |
|
|
850 | effect as using the \f(CW\*(C`\-fn\*(C'\fR switch, and takes effect immediately: |
|
|
851 | .PP |
|
|
852 | .Vb 1 |
|
|
853 | \& printf '\ee]50;%s\e007' "9x15bold,xft:Kochi Gothic" |
|
|
854 | .Ve |
|
|
855 | .PP |
|
|
856 | This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
857 | japanese font), but you have to switch to chinese temporarily, where |
|
|
858 | japanese fonts would only be in your way. |
|
|
859 | .PP |
|
|
860 | You can think of this as a kind of manual \s-1ISO\-2022\s0 switching. |
|
|
861 | .Sh "Why do italic characters look as if clipped?" |
|
|
862 | .IX Subsection "Why do italic characters look as if clipped?" |
|
|
863 | Many fonts have difficulties with italic characters and hinting. For |
|
|
864 | example, the otherwise very nicely hinted font \f(CW\*(C`xft:Bitstream Vera Sans |
|
|
865 | Mono\*(C'\fR completely fails in it's italic face. A workaround might be to |
|
|
866 | enable freetype autohinting, i.e. like this: |
|
|
867 | .PP |
|
|
868 | .Vb 2 |
|
|
869 | \& URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
870 | \& URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
871 | .Ve |
|
|
872 | .Sh "My input method wants <some encoding> but I want \s-1UTF\-8\s0, what can I do?" |
|
|
873 | .IX Subsection "My input method wants <some encoding> but I want UTF-8, what can I do?" |
|
|
874 | You can specify separate locales for the input method and the rest of the |
|
|
875 | terminal, using the resource \f(CW\*(C`imlocale\*(C'\fR: |
|
|
876 | .PP |
|
|
877 | .Vb 1 |
|
|
878 | \& URxvt.imlocale: ja_JP.EUC-JP |
|
|
879 | .Ve |
|
|
880 | .PP |
|
|
881 | Now you can start your terminal with \f(CW\*(C`LC_CTYPE=ja_JP.UTF\-8\*(C'\fR and still |
|
|
882 | use your input method. Please note, however, that you will not be able to |
|
|
883 | input characters outside \f(CW\*(C`EUC\-JP\*(C'\fR in a normal way then, as your input |
|
|
884 | method limits you. |
|
|
885 | .Sh "Rxvt-unicode crashes when the X Input Method changes or exits." |
|
|
886 | .IX Subsection "Rxvt-unicode crashes when the X Input Method changes or exits." |
|
|
887 | Unfortunately, this is unavoidable, as the \s-1XIM\s0 protocol is racy by |
|
|
888 | design. Applications can avoid some crashes at the expense of memory |
|
|
889 | leaks, and Input Methods can avoid some crashes by careful ordering at |
|
|
890 | exit time. \fBkinput2\fR (and derived input methods) generally succeeds, |
|
|
891 | while \fB\s-1SCIM\s0\fR (or similar input methods) fails. In the end, however, |
|
|
892 | crashes cannot be completely avoided even if both sides cooperate. |
|
|
893 | .PP |
|
|
894 | So the only workaround is not to kill your Input Method Servers. |
|
|
895 | .Sh "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
|
|
896 | .IX Subsection "Rxvt-unicode uses gobs of memory, how can I reduce that?" |
|
|
897 | Rxvt-unicode tries to obey the rule of not charging you for something you |
|
|
898 | don't use. One thing you should try is to configure out all settings that |
|
|
899 | you don't need, for example, Xft support is a resource hog by design, |
|
|
900 | when used. Compiling it out ensures that no Xft font will be loaded |
|
|
901 | accidentally when rxvt-unicode tries to find a font for your characters. |
|
|
902 | .PP |
|
|
903 | Also, many people (me included) like large windows and even larger |
|
|
904 | scrollback buffers: Without \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR, rxvt-unicode will use |
|
|
905 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
|
|
906 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
|
|
907 | use 10 Megabytes of memory. With \f(CW\*(C`\-\-enable\-unicode3\*(C'\fR it gets worse, as |
|
|
908 | rxvt-unicode then uses 8 bytes per screen cell. |
|
|
909 | .Sh "Can I speed up Xft rendering somehow?" |
|
|
910 | .IX Subsection "Can I speed up Xft rendering somehow?" |
|
|
911 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
912 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
913 | antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of |
|
|
914 | memory and also speeds up rendering considerably. |
|
|
915 | .Sh "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" |
|
|
916 | .IX Subsection "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" |
|
|
917 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
918 | fall back to it's default font search list it will prefer X11 core |
|
|
919 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
920 | antialiasing disabled for most of them, because the author thinks they |
|
|
921 | look best that way. |
|
|
922 | .PP |
|
|
923 | If you want antialiasing, you have to specify the fonts manually. |
|
|
924 | .Sh "Mouse cut/paste suddenly no longer works." |
|
|
925 | .IX Subsection "Mouse cut/paste suddenly no longer works." |
|
|
926 | Make sure that mouse reporting is actually turned off since killing |
|
|
927 | some editors prematurely may leave the mouse in mouse report mode. I've |
|
|
928 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
|
|
929 | quick check is to see if cut/paste works when the Alt or Shift keys are |
|
|
930 | depressed. |
|
|
931 | .Sh "What's with this bold/blink stuff?" |
|
|
932 | .IX Subsection "What's with this bold/blink stuff?" |
|
|
933 | If no bold colour is set via \f(CW\*(C`colorBD:\*(C'\fR, bold will invert text using the |
|
|
934 | standard foreground colour. |
|
|
935 | .PP |
|
|
936 | For the standard background colour, blinking will actually make the |
|
|
937 | text blink when compiled with \f(CW\*(C`\-\-enable\-blinking\*(C'\fR. with standard |
|
|
938 | colours. Without \f(CW\*(C`\-\-enable\-blinking\*(C'\fR, the blink attribute will be |
|
|
939 | ignored. |
|
|
940 | .PP |
|
|
941 | On \s-1ANSI\s0 colours, bold/blink attributes are used to set high-intensity |
|
|
942 | foreground/background colors. |
|
|
943 | .PP |
|
|
944 | color0\-7 are the low-intensity colors. |
|
|
945 | .PP |
|
|
946 | color8\-15 are the corresponding high-intensity colors. |
|
|
947 | .Sh "I don't like the screen colors. How do I change them?" |
|
|
948 | .IX Subsection "I don't like the screen colors. How do I change them?" |
|
|
949 | You can change the screen colors at run-time using \fI~/.Xdefaults\fR |
|
|
950 | resources (or as long\-options). |
|
|
951 | .PP |
|
|
952 | Here are values that are supposed to resemble a \s-1VGA\s0 screen, |
|
|
953 | including the murky brown that passes for low-intensity yellow: |
|
|
954 | .PP |
|
|
955 | .Vb 8 |
|
|
956 | \& URxvt.color0: #000000 |
|
|
957 | \& URxvt.color1: #A80000 |
|
|
958 | \& URxvt.color2: #00A800 |
|
|
959 | \& URxvt.color3: #A8A800 |
|
|
960 | \& URxvt.color4: #0000A8 |
|
|
961 | \& URxvt.color5: #A800A8 |
|
|
962 | \& URxvt.color6: #00A8A8 |
|
|
963 | \& URxvt.color7: #A8A8A8 |
|
|
964 | .Ve |
|
|
965 | .PP |
|
|
966 | .Vb 8 |
|
|
967 | \& URxvt.color8: #000054 |
|
|
968 | \& URxvt.color9: #FF0054 |
|
|
969 | \& URxvt.color10: #00FF54 |
|
|
970 | \& URxvt.color11: #FFFF54 |
|
|
971 | \& URxvt.color12: #0000FF |
|
|
972 | \& URxvt.color13: #FF00FF |
|
|
973 | \& URxvt.color14: #00FFFF |
|
|
974 | \& URxvt.color15: #FFFFFF |
|
|
975 | .Ve |
|
|
976 | .PP |
|
|
977 | And here is a more complete set of non-standard colors described (not by |
|
|
978 | me) as \*(L"pretty girly\*(R". |
|
|
979 | .PP |
|
|
980 | .Vb 18 |
|
|
981 | \& URxvt.cursorColor: #dc74d1 |
|
|
982 | \& URxvt.pointerColor: #dc74d1 |
|
|
983 | \& URxvt.background: #0e0e0e |
|
|
984 | \& URxvt.foreground: #4ad5e1 |
|
|
985 | \& URxvt.color0: #000000 |
|
|
986 | \& URxvt.color8: #8b8f93 |
|
|
987 | \& URxvt.color1: #dc74d1 |
|
|
988 | \& URxvt.color9: #dc74d1 |
|
|
989 | \& URxvt.color2: #0eb8c7 |
|
|
990 | \& URxvt.color10: #0eb8c7 |
|
|
991 | \& URxvt.color3: #dfe37e |
|
|
992 | \& URxvt.color11: #dfe37e |
|
|
993 | \& URxvt.color5: #9e88f0 |
|
|
994 | \& URxvt.color13: #9e88f0 |
|
|
995 | \& URxvt.color6: #73f7ff |
|
|
996 | \& URxvt.color14: #73f7ff |
|
|
997 | \& URxvt.color7: #e1dddd |
|
|
998 | \& URxvt.color15: #e1dddd |
|
|
999 | .Ve |
|
|
1000 | .Sh "How can I start @@RXVT_NAME@@d in a race-free way?" |
|
|
1001 | .IX Subsection "How can I start @@RXVT_NAME@@d in a race-free way?" |
|
|
1002 | Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the |
|
|
1003 | display, create the listening socket and then fork. |
|
|
1004 | .Sh "What's with the strange Backspace/Delete key behaviour?" |
|
|
1005 | .IX Subsection "What's with the strange Backspace/Delete key behaviour?" |
|
|
1006 | Assuming that the physical Backspace key corresponds to the |
|
|
1007 | BackSpace keysym (not likely for Linux ... see the following |
|
|
1008 | question) there are two standard values that can be used for |
|
|
1009 | Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR. |
|
|
1010 | .PP |
|
|
1011 | Historically, either value is correct, but rxvt-unicode adopts the debian |
|
|
1012 | policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct |
|
|
1013 | choice :). |
|
|
1014 | .PP |
|
|
1015 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
|
|
1016 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
|
|
1017 | started from a terminal (say, from a menu or by remote shell), then the |
|
|
1018 | system value of `erase', which corresponds to \s-1CERASE\s0 in <termios.h>, will |
|
|
1019 | be used (which may not be the same as your stty setting). |
|
|
1020 | .PP |
|
|
1021 | For starting a new rxvt\-unicode: |
|
|
1022 | .PP |
|
|
1023 | .Vb 3 |
|
|
1024 | \& # use Backspace = ^H |
|
|
1025 | \& $ stty erase ^H |
|
|
1026 | \& $ @@RXVT_NAME@@ |
|
|
1027 | .Ve |
|
|
1028 | .PP |
|
|
1029 | .Vb 3 |
|
|
1030 | \& # use Backspace = ^? |
|
|
1031 | \& $ stty erase ^? |
|
|
1032 | \& $ @@RXVT_NAME@@ |
|
|
1033 | .Ve |
|
|
1034 | .PP |
|
|
1035 | Toggle with \f(CW\*(C`ESC [ 36 h\*(C'\fR / \f(CW\*(C`ESC [ 36 l\*(C'\fR. |
|
|
1036 | .PP |
|
|
1037 | For an existing rxvt\-unicode: |
|
|
1038 | .PP |
|
|
1039 | .Vb 3 |
|
|
1040 | \& # use Backspace = ^H |
|
|
1041 | \& $ stty erase ^H |
|
|
1042 | \& $ echo -n "^[[36h" |
|
|
1043 | .Ve |
|
|
1044 | .PP |
|
|
1045 | .Vb 3 |
|
|
1046 | \& # use Backspace = ^? |
|
|
1047 | \& $ stty erase ^? |
|
|
1048 | \& $ echo -n "^[[36l" |
|
|
1049 | .Ve |
|
|
1050 | .PP |
|
|
1051 | This helps satisfy some of the Backspace discrepancies that occur, but |
|
|
1052 | if you use Backspace = \f(CW\*(C`^H\*(C'\fR, make sure that the termcap/terminfo value |
|
|
1053 | properly reflects that. |
|
|
1054 | .PP |
|
|
1055 | The Delete key is a another casualty of the ill-defined Backspace problem. |
|
|
1056 | To avoid confusion between the Backspace and Delete keys, the Delete |
|
|
1057 | key has been assigned an escape sequence to match the vt100 for Execute |
|
|
1058 | (\f(CW\*(C`ESC [ 3 ~\*(C'\fR) and is in the supplied termcap/terminfo. |
|
|
1059 | .PP |
|
|
1060 | Some other Backspace problems: |
|
|
1061 | .PP |
|
|
1062 | some editors use termcap/terminfo, |
|
|
1063 | some editors (vim I'm told) expect Backspace = ^H, |
|
|
1064 | \&\s-1GNU\s0 Emacs (and Emacs-like editors) use ^H for help. |
|
|
1065 | .PP |
|
|
1066 | Perhaps someday this will all be resolved in a consistent manner. |
|
|
1067 | .Sh "I don't like the key\-bindings. How do I change them?" |
|
|
1068 | .IX Subsection "I don't like the key-bindings. How do I change them?" |
|
|
1069 | There are some compile-time selections available via configure. Unless |
|
|
1070 | you have run \*(L"configure\*(R" with the \f(CW\*(C`\-\-disable\-resources\*(C'\fR option you can |
|
|
1071 | use the `keysym' resource to alter the keystrings associated with keysyms. |
|
|
1072 | .PP |
|
|
1073 | Here's an example for a URxvt session started using \f(CW\*(C`@@RXVT_NAME@@ \-name URxvt\*(C'\fR |
|
|
1074 | .PP |
|
|
1075 | .Vb 20 |
|
|
1076 | \& URxvt.keysym.Home: \e033[1~ |
|
|
1077 | \& URxvt.keysym.End: \e033[4~ |
|
|
1078 | \& URxvt.keysym.C-apostrophe: \e033<C-'> |
|
|
1079 | \& URxvt.keysym.C-slash: \e033<C-/> |
|
|
1080 | \& URxvt.keysym.C-semicolon: \e033<C-;> |
|
|
1081 | \& URxvt.keysym.C-grave: \e033<C-`> |
|
|
1082 | \& URxvt.keysym.C-comma: \e033<C-,> |
|
|
1083 | \& URxvt.keysym.C-period: \e033<C-.> |
|
|
1084 | \& URxvt.keysym.C-0x60: \e033<C-`> |
|
|
1085 | \& URxvt.keysym.C-Tab: \e033<C-Tab> |
|
|
1086 | \& URxvt.keysym.C-Return: \e033<C-Return> |
|
|
1087 | \& URxvt.keysym.S-Return: \e033<S-Return> |
|
|
1088 | \& URxvt.keysym.S-space: \e033<S-Space> |
|
|
1089 | \& URxvt.keysym.M-Up: \e033<M-Up> |
|
|
1090 | \& URxvt.keysym.M-Down: \e033<M-Down> |
|
|
1091 | \& URxvt.keysym.M-Left: \e033<M-Left> |
|
|
1092 | \& URxvt.keysym.M-Right: \e033<M-Right> |
|
|
1093 | \& URxvt.keysym.M-C-0: list \e033<M-C- 0123456789 > |
|
|
1094 | \& URxvt.keysym.M-C-a: list \e033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
1095 | \& URxvt.keysym.F12: command:\e033]701;zh_CN.GBK\e007 |
|
|
1096 | .Ve |
|
|
1097 | .PP |
|
|
1098 | See some more examples in the documentation for the \fBkeysym\fR resource. |
|
|
1099 | .Sh "I'm using keyboard model \s-1XXX\s0 that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize." |
|
|
1100 | .IX Subsection "I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following mappings that rxvt-unicode doesn't recognize." |
|
|
1101 | .Vb 6 |
|
|
1102 | \& KP_Insert == Insert |
|
|
1103 | \& F22 == Print |
|
|
1104 | \& F27 == Home |
|
|
1105 | \& F29 == Prior |
|
|
1106 | \& F33 == End |
|
|
1107 | \& F35 == Next |
|
|
1108 | .Ve |
|
|
1109 | .PP |
|
|
1110 | Rather than have rxvt-unicode try to accommodate all the various possible |
|
|
1111 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
|
|
1112 | required for your particular machine. |
|
|
1113 | .Sh "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
|
|
1114 | .IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
|
|
1115 | rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", so you can |
|
|
1116 | check and see if that is set. Note that several programs, \s-1JED\s0, slrn, |
|
|
1117 | Midnight Commander automatically check this variable to decide whether or |
|
|
1118 | not to use color. |
|
|
1119 | .Sh "How do I set the correct, full \s-1IP\s0 address for the \s-1DISPLAY\s0 variable?" |
|
|
1120 | .IX Subsection "How do I set the correct, full IP address for the DISPLAY variable?" |
|
|
1121 | If you've compiled rxvt-unicode with \s-1DISPLAY_IS_IP\s0 and have enabled |
|
|
1122 | insecure mode then it is possible to use the following shell script |
|
|
1123 | snippets to correctly set the display. If your version of rxvt-unicode |
|
|
1124 | wasn't also compiled with \s-1ESCZ_ANSWER\s0 (as assumed in these snippets) then |
|
|
1125 | the \s-1COLORTERM\s0 variable can be used to distinguish rxvt-unicode from a |
|
|
1126 | regular xterm. |
|
|
1127 | .PP |
|
|
1128 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
|
|
1129 | snippets: |
|
|
1130 | .PP |
|
|
1131 | .Vb 12 |
|
|
1132 | \& # Bourne/Korn/POSIX family of shells: |
|
|
1133 | \& [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
|
|
1134 | \& if [ ${TERM:-foo} = xterm ]; then |
|
|
1135 | \& stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
|
|
1136 | \& echo -n '^[Z' |
|
|
1137 | \& read term_id |
|
|
1138 | \& stty icanon echo |
|
|
1139 | \& if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
|
|
1140 | \& echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
|
|
1141 | \& read DISPLAY # set it in our local shell |
|
|
1142 | \& fi |
|
|
1143 | \& fi |
|
|
1144 | .Ve |
|
|
1145 | .Sh "How do I compile the manual pages for myself?" |
|
|
1146 | .IX Subsection "How do I compile the manual pages for myself?" |
|
|
1147 | You need to have a recent version of perl installed as \fI/usr/bin/perl\fR, |
|
|
1148 | one that comes with \fIpod2man\fR, \fIpod2text\fR and \fIpod2html\fR. Then go to |
|
|
1149 | the doc subdirectory and enter \f(CW\*(C`make alldoc\*(C'\fR. |
|
|
1150 | .Sh "My question isn't answered here, can I ask a human?" |
|
|
1151 | .IX Subsection "My question isn't answered here, can I ask a human?" |
|
|
1152 | Before sending me mail, you could go to \s-1IRC:\s0 \f(CW\*(C`irc.freenode.net\*(C'\fR, |
|
|
1153 | channel \f(CW\*(C`#rxvt\-unicode\*(C'\fR has some rxvt-unicode enthusiasts that might be |
|
|
1154 | interested in learning about new and exciting problems (but not FAQs :). |
|
|
1155 | .SH "RXVT TECHNICAL REFERENCE" |
1503 | .SH "RXVT-UNICODE TECHNICAL REFERENCE" |
1156 | .IX Header "RXVT TECHNICAL REFERENCE" |
1504 | .IX Header "RXVT-UNICODE TECHNICAL REFERENCE" |
1157 | .SH "DESCRIPTION" |
|
|
1158 | .IX Header "DESCRIPTION" |
|
|
1159 | The rest of this document describes various technical aspects of |
1505 | The rest of this document describes various technical aspects of |
1160 | \&\fBrxvt-unicode\fR. First the description of supported command sequences, |
1506 | \&\fBrxvt-unicode\fR. First the description of supported command sequences, |
1161 | 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 |
1162 | selectable at \f(CW\*(C`configure\*(C'\fR time. |
1508 | selectable at \f(CW\*(C`configure\*(C'\fR time. |
1163 | .SH "Definitions" |
1509 | .Sh "Definitions" |
1164 | .IX Header "Definitions" |
1510 | .IX Subsection "Definitions" |
1165 | .ie n .IP "\fB\fB""c""\fB\fR" 4 |
1511 | .ie n .IP "\fB\fB""c""\fB\fR" 4 |
1166 | .el .IP "\fB\f(CBc\fB\fR" 4 |
1512 | .el .IP "\fB\f(CBc\fB\fR" 4 |
1167 | .IX Item "c" |
1513 | .IX Item "c" |
1168 | The literal character c. |
1514 | The literal character c. |
1169 | .ie n .IP "\fB\fB""C""\fB\fR" 4 |
1515 | .ie n .IP "\fB\fB""C""\fB\fR" 4 |
… | |
… | |
1182 | parameters, separated by \f(CW\*(C`;\*(C'\fR character(s). |
1528 | parameters, separated by \f(CW\*(C`;\*(C'\fR character(s). |
1183 | .ie n .IP "\fB\fB""Pt""\fB\fR" 4 |
1529 | .ie n .IP "\fB\fB""Pt""\fB\fR" 4 |
1184 | .el .IP "\fB\f(CBPt\fB\fR" 4 |
1530 | .el .IP "\fB\f(CBPt\fB\fR" 4 |
1185 | .IX Item "Pt" |
1531 | .IX Item "Pt" |
1186 | A text parameter composed of printable characters. |
1532 | A text parameter composed of printable characters. |
1187 | .SH "Values" |
1533 | .Sh "Values" |
1188 | .IX Header "Values" |
1534 | .IX Subsection "Values" |
1189 | .ie n .IP "\fB\fB""ENQ""\fB\fR" 4 |
1535 | .ie n .IP "\fB\fB""ENQ""\fB\fR" 4 |
1190 | .el .IP "\fB\f(CBENQ\fB\fR" 4 |
1536 | .el .IP "\fB\f(CBENQ\fB\fR" 4 |
1191 | .IX Item "ENQ" |
1537 | .IX Item "ENQ" |
1192 | Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0) |
1538 | Enquiry (Ctrl\-E) = Send Device Attributes (\s-1DA\s0) |
1193 | 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. |
… | |
… | |
1231 | Switch to Standard Character Set |
1577 | Switch to Standard Character Set |
1232 | .ie n .IP "\fB\fB""SPC""\fB\fR" 4 |
1578 | .ie n .IP "\fB\fB""SPC""\fB\fR" 4 |
1233 | .el .IP "\fB\f(CBSPC\fB\fR" 4 |
1579 | .el .IP "\fB\f(CBSPC\fB\fR" 4 |
1234 | .IX Item "SPC" |
1580 | .IX Item "SPC" |
1235 | Space Character |
1581 | Space Character |
1236 | .SH "Escape Sequences" |
1582 | .Sh "Escape Sequences" |
1237 | .IX Header "Escape Sequences" |
1583 | .IX Subsection "Escape Sequences" |
1238 | .ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4 |
1584 | .ie n .IP "\fB\fB""ESC # 8""\fB\fR" 4 |
1239 | .el .IP "\fB\f(CBESC # 8\fB\fR" 4 |
1585 | .el .IP "\fB\f(CBESC # 8\fB\fR" 4 |
1240 | .IX Item "ESC # 8" |
1586 | .IX Item "ESC # 8" |
1241 | \&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0) |
1587 | \&\s-1DEC\s0 Screen Alignment Test (\s-1DECALN\s0) |
1242 | .ie n .IP "\fB\fB""ESC 7""\fB\fR" 4 |
1588 | .ie n .IP "\fB\fB""ESC 7""\fB\fR" 4 |
… | |
… | |
1335 | .TE |
1681 | .TE |
1336 | |
1682 | |
1337 | .PP |
1683 | .PP |
1338 | |
1684 | |
1339 | .IX Xref "CSI" |
1685 | .IX Xref "CSI" |
1340 | .SH "CSI (Command Sequence Introducer) Sequences" |
1686 | .Sh "\s-1CSI\s0 (Command Sequence Introducer) Sequences" |
1341 | .IX Header "CSI (Command Sequence Introducer) Sequences" |
1687 | .IX Subsection "CSI (Command Sequence Introducer) Sequences" |
1342 | .ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4 |
1688 | .ie n .IP "\fB\fB""ESC [ Ps @""\fB\fR" 4 |
1343 | .el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4 |
1689 | .el .IP "\fB\f(CBESC [ Ps @\fB\fR" 4 |
1344 | .IX Item "ESC [ Ps @" |
1690 | .IX Item "ESC [ Ps @" |
1345 | 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) |
1346 | .IX Xref "ESCOBPsA" |
1692 | .IX Xref "ESCOBPsA" |
… | |
… | |
1609 | .IX Item "ESC [ Ps x" |
1955 | .IX Item "ESC [ Ps x" |
1610 | Request Terminal Parameters (\s-1DECREQTPARM\s0) |
1956 | Request Terminal Parameters (\s-1DECREQTPARM\s0) |
1611 | .PP |
1957 | .PP |
1612 | |
1958 | |
1613 | .IX Xref "PrivateModes" |
1959 | .IX Xref "PrivateModes" |
1614 | .SH "DEC Private Modes" |
1960 | .Sh "\s-1DEC\s0 Private Modes" |
1615 | .IX Header "DEC Private Modes" |
1961 | .IX Subsection "DEC Private Modes" |
1616 | .ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4 |
1962 | .ie n .IP "\fB\fB""ESC [ ? Pm h""\fB\fR" 4 |
1617 | .el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4 |
1963 | .el .IP "\fB\f(CBESC [ ? Pm h\fB\fR" 4 |
1618 | .IX Item "ESC [ ? Pm h" |
1964 | .IX Item "ESC [ ? Pm h" |
1619 | \&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0) |
1965 | \&\s-1DEC\s0 Private Mode Set (\s-1DECSET\s0) |
1620 | .ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4 |
1966 | .ie n .IP "\fB\fB""ESC [ ? Pm l""\fB\fR" 4 |
… | |
… | |
1887 | .RE |
2233 | .RE |
1888 | .PD |
2234 | .PD |
1889 | .PP |
2235 | .PP |
1890 | |
2236 | |
1891 | .IX Xref "XTerm" |
2237 | .IX Xref "XTerm" |
1892 | .SH "XTerm Operating System Commands" |
2238 | .Sh "XTerm Operating System Commands" |
1893 | .IX Header "XTerm Operating System Commands" |
2239 | .IX Subsection "XTerm Operating System Commands" |
1894 | .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 |
1895 | .el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4 |
2241 | .el .IP "\fB\f(CBESC ] Ps;Pt ST\fB\fR" 4 |
1896 | .IX Item "ESC ] Ps;Pt ST" |
2242 | .IX Item "ESC ] Ps;Pt ST" |
1897 | 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, |
1898 | 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 |
… | |
… | |
1930 | 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). |
1931 | 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). |
1932 | 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). |
1933 | .TE |
2279 | .TE |
1934 | |
2280 | |
1935 | .PP |
|
|
1936 | |
|
|
1937 | .IX Xref "XPM" |
|
|
1938 | .SH "XPM" |
2281 | .SH "XPM" |
1939 | .IX Header "XPM" |
2282 | .IX Header "XPM" |
1940 | 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 |
1941 | 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 |
1942 | sequence of scaling/positioning commands separated by semi\-colons. The |
2285 | sequence of scaling/positioning commands separated by semi\-colons. The |
… | |
… | |
2012 | .TS |
2355 | .TS |
2013 | l l . |
2356 | l l . |
2014 | 4 Shift |
2357 | 4 Shift |
2015 | 8 Meta |
2358 | 8 Meta |
2016 | 16 Control |
2359 | 16 Control |
2017 | 32 Double Click (Rxvt extension) |
2360 | 32 Double Click (rxvt extension) |
2018 | .TE |
2361 | .TE |
2019 | |
2362 | |
2020 | Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR |
2363 | Col = \fB\f(CB\*(C`<x> \- SPACE\*(C'\fB\fR |
2021 | .Sp |
2364 | .Sp |
2022 | Row = \fB\f(CB\*(C`<y> \- SPACE\*(C'\fB\fR |
2365 | Row = \fB\f(CB\*(C`<y> \- SPACE\*(C'\fB\fR |
… | |
… | |
2311 | .IX Item "--disable-new-selection" |
2654 | .IX Item "--disable-new-selection" |
2312 | Remove support for mouse selection style like that of xterm. |
2655 | Remove support for mouse selection style like that of xterm. |
2313 | .IP "\-\-enable\-dmalloc (default: off)" 4 |
2656 | .IP "\-\-enable\-dmalloc (default: off)" 4 |
2314 | .IX Item "--enable-dmalloc (default: off)" |
2657 | .IX Item "--enable-dmalloc (default: off)" |
2315 | Use Gray Watson's malloc \- which is good for debugging See |
2658 | Use Gray Watson's malloc \- which is good for debugging See |
2316 | 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 |
2317 | 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 |
2318 | \&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places. |
2661 | \&\s-1DINCLUDE\s0 and \s-1DLIB\s0 to the right places. |
2319 | .Sp |
2662 | .Sp |
2320 | You can only use either this option and the following (should |
2663 | You can only use either this option and the following (should |
2321 | you use either) . |
2664 | you use either) . |