| … | |
… | |
| 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-30" "7.4" "RXVT-UNICODE" |
132 | .TH rxvt 7 "2006-01-31" "7.5" "RXVT-UNICODE" |
| 133 | .SH "NAME" |
133 | .SH "NAME" |
| 134 | RXVT REFERENCE \- FAQ, command sequences and other background information |
134 | RXVT REFERENCE \- FAQ, command sequences and other background information |
| 135 | .SH "SYNOPSIS" |
135 | .SH "SYNOPSIS" |
| 136 | .IX Header "SYNOPSIS" |
136 | .IX Header "SYNOPSIS" |
| 137 | .Vb 2 |
137 | .Vb 2 |
| … | |
… | |
| 151 | .SH "DESCRIPTION" |
151 | .SH "DESCRIPTION" |
| 152 | .IX Header "DESCRIPTION" |
152 | .IX Header "DESCRIPTION" |
| 153 | This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting |
153 | This document contains the \s-1FAQ\s0, the \s-1RXVT\s0 \s-1TECHNICAL\s0 \s-1REFERENCE\s0 documenting |
| 154 | all escape sequences, and other background information. |
154 | all escape sequences, and other background information. |
| 155 | .PP |
155 | .PP |
| 156 | The newest version of this document is |
156 | The newest version of this document is also available on the World Wide Web at |
| 157 | also available on the World Wide Web at |
|
|
| 158 | <http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>. |
157 | <http://cvs.schmorp.de/browse/*checkout*/rxvt\-unicode/doc/rxvt.7.html>. |
| 159 | .SH "FREQUENTLY ASKED QUESTIONS" |
158 | .SH "FREQUENTLY ASKED QUESTIONS" |
| 160 | .IX Header "FREQUENTLY ASKED QUESTIONS" |
159 | .IX Header "FREQUENTLY ASKED QUESTIONS" |
| 161 | .IP "The new selection selects pieces that are too big, how can I select single words?" 4 |
160 | .Sh "The new selection selects pieces that are too big, how can I select single words?" |
| 162 | .IX Item "The new selection selects pieces that are too big, how can I select single words?" |
161 | .IX Subsection "The new selection selects pieces that are too big, how can I select single words?" |
| 163 | Yes. For example, if you want to select alphanumeric words, you can use |
162 | Yes. For example, if you want to select alphanumeric words, you can use |
| 164 | the following resource: |
163 | the following resource: |
| 165 | .Sp |
164 | .PP |
| 166 | .Vb 1 |
165 | .Vb 1 |
| 167 | \& URxvt.selection.pattern-0: ([[:word:]]+) |
166 | \& URxvt.selection.pattern-0: ([[:word:]]+) |
| 168 | .Ve |
167 | .Ve |
| 169 | .Sp |
168 | .PP |
| 170 | If you click more than twice, the selection will be extended |
169 | If you click more than twice, the selection will be extended |
| 171 | more and more. |
170 | more and more. |
| 172 | .Sp |
171 | .PP |
| 173 | To get a selection that is very similar to the old code, try this pattern: |
172 | To get a selection that is very similar to the old code, try this pattern: |
| 174 | .Sp |
173 | .PP |
| 175 | .Vb 1 |
174 | .Vb 1 |
| 176 | \& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+) |
175 | \& URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\e\e\e\e]^`{|})]+) |
| 177 | .Ve |
176 | .Ve |
| 178 | .Sp |
177 | .PP |
| 179 | Please also note that the \fILeftClick Shift-LeftClik\fR combination also |
178 | Please also note that the \fILeftClick Shift-LeftClik\fR combination also |
| 180 | selects words like the old code. |
179 | selects words like the old code. |
| 181 | .IP "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" 4 |
180 | .IP "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" 4 |
| 182 | .IX Item "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" |
181 | .IX Item "I don't like the new selection/popups/hotkeys/perl, how do I change/disable it?" |
| 183 | You can disable the perl extension completely by setting the |
182 | You can disable the perl extension completely by setting the |
| … | |
… | |
| 199 | scrollback search mode is triggered by \fBM\-s\fR. You can move it to any |
198 | scrollback search mode is triggered by \fBM\-s\fR. You can move it to any |
| 200 | other combination either by setting the \fBsearchable-scrollback\fR resource: |
199 | other combination either by setting the \fBsearchable-scrollback\fR resource: |
| 201 | .Sp |
200 | .Sp |
| 202 | .Vb 1 |
201 | .Vb 1 |
| 203 | \& URxvt.searchable-scrollback: CM-s |
202 | \& URxvt.searchable-scrollback: CM-s |
|
|
203 | .Ve |
|
|
204 | .IP "The cursor moves when selecting text in the current input line, how do I switch this off?" 4 |
|
|
205 | .IX Item "The cursor moves when selecting text in the current input line, how do I switch this off?" |
|
|
206 | .PD 0 |
|
|
207 | .IP "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?" 4 |
|
|
208 | .IX Item "During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this?" |
|
|
209 | .PD |
|
|
210 | These are caused by the \f(CW\*(C`readline\*(C'\fR perl extension. Under normal |
|
|
211 | circumstances, it will move your cursor around when you click into the |
|
|
212 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
213 | but when running a program that doesn't parse cursor movements or in some |
|
|
214 | cases during rlogin sessions, it fails to detect this properly. |
|
|
215 | .Sp |
|
|
216 | You can permamently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR |
|
|
217 | extension: |
|
|
218 | .Sp |
|
|
219 | .Vb 1 |
|
|
220 | \& URxvt.perl-ext-common: default,-readline |
| 204 | .Ve |
221 | .Ve |
| 205 | .IP "Why doesn't rxvt-unicode read my resources?" 4 |
222 | .IP "Why doesn't rxvt-unicode read my resources?" 4 |
| 206 | .IX Item "Why doesn't rxvt-unicode read my resources?" |
223 | .IX Item "Why doesn't rxvt-unicode read my resources?" |
| 207 | Well, why, indeed? It does, in a way very similar to other X |
224 | Well, why, indeed? It does, in a way very similar to other X |
| 208 | applications. Most importantly, this means that if you or your \s-1OS\s0 loads |
225 | applications. Most importantly, this means that if you or your \s-1OS\s0 loads |
| … | |
… | |
| 226 | .IP "I can't get transparency working, what am I doing wrong?" 4 |
243 | .IP "I can't get transparency working, what am I doing wrong?" 4 |
| 227 | .IX Item "I can't get transparency working, what am I doing wrong?" |
244 | .IX Item "I can't get transparency working, what am I doing wrong?" |
| 228 | First of all, transparency isn't officially supported in rxvt\-unicode, so |
245 | First of all, transparency isn't officially supported in rxvt\-unicode, so |
| 229 | you are mostly on your own. Do not bug the author about it (but you may |
246 | you are mostly on your own. Do not bug the author about it (but you may |
| 230 | bug everybody else). Also, if you can't get it working consider it a rite |
247 | bug everybody else). Also, if you can't get it working consider it a rite |
| 231 | of passage, and you failed. |
248 | of passage: ... and you failed. |
| 232 | .Sp |
249 | .Sp |
| 233 | Here are three ways to get transparency. \fBDo\fR read the manpage and option |
250 | Here are four ways to get transparency. \fBDo\fR read the manpage and option |
| 234 | descriptions for the programs mentioned and rxvt\-unicode. Really, do it! |
251 | descriptions for the programs mentioned and rxvt\-unicode. Really, do it! |
| 235 | .Sp |
252 | .Sp |
| 236 | 1. Use inheritPixmap: |
253 | 1. Use inheritPixmap: |
| 237 | .Sp |
254 | .Sp |
| 238 | .Vb 2 |
255 | .Vb 2 |
| … | |
… | |
| 256 | are unable to read. |
273 | are unable to read. |
| 257 | .Sp |
274 | .Sp |
| 258 | 3. Use an \s-1ARGB\s0 visual: |
275 | 3. Use an \s-1ARGB\s0 visual: |
| 259 | .Sp |
276 | .Sp |
| 260 | .Vb 1 |
277 | .Vb 1 |
| 261 | \& @@RXVT_NAME@@ -depth 432 -fg grey90 -bg rgba:0000/0000/0000/c000 |
278 | \& @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
| 262 | .Ve |
279 | .Ve |
| 263 | .Sp |
280 | .Sp |
| 264 | This requires \s-1XFT\s0 support, and support form your X\-server. If that doesn't |
281 | This requires \s-1XFT\s0 support, and the support of your X\-server. If that |
| 265 | work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't there yet, |
282 | doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't |
| 266 | no matter what they claim. Rxvt-Unicode contains the neccessary bugfixes |
283 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
| 267 | and workarounds for Xft and Xlib to make it work. |
284 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
|
|
285 | doesn't mean that your \s-1WM\s0 has the required kludges in place. |
|
|
286 | .Sp |
|
|
287 | 4. Use xcompmgr and let it do the job: |
|
|
288 | .Sp |
|
|
289 | .Vb 2 |
|
|
290 | \& xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \e |
|
|
291 | \& -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
|
|
292 | .Ve |
|
|
293 | .Sp |
|
|
294 | Then click on a window you want to make transparent. Replace \f(CW0xc0000000\fR |
|
|
295 | by other values to change the degree of opacity. If it doesn't work and |
|
|
296 | your server crashes, you got to keep the pieces. |
| 268 | .IP "Isn't rxvt supposed to be small? Don't all those features bloat?" 4 |
297 | .IP "Isn't rxvt supposed to be small? Don't all those features bloat?" 4 |
| 269 | .IX Item "Isn't rxvt supposed to be small? Don't all those features bloat?" |
298 | .IX Item "Isn't rxvt supposed to be small? Don't all those features bloat?" |
| 270 | I often get asked about this, and I think, no, they didn't cause extra |
299 | I often get asked about this, and I think, no, they didn't cause extra |
| 271 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
300 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
| 272 | that the urxvt binary is larger (due to some encoding tables always being |
301 | that the urxvt binary is larger (due to some encoding tables always being |
