… | |
… | |
16 | =head1 DESCRIPTION |
16 | =head1 DESCRIPTION |
17 | |
17 | |
18 | This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting |
18 | This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting |
19 | all escape sequences, and other background information. |
19 | all escape sequences, and other background information. |
20 | |
20 | |
21 | The newest version of this document is |
21 | The newest version of this document is also available on the World Wide Web at |
22 | also available on the World Wide Web at |
|
|
23 | L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. |
22 | L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. |
24 | |
23 | |
25 | =head1 FREQUENTLY ASKED QUESTIONS |
24 | =head1 FREQUENTLY ASKED QUESTIONS |
26 | |
25 | |
27 | =over 4 |
26 | =head2 The new selection selects pieces that are too big, how can I select |
|
|
27 | single words? |
28 | |
28 | |
|
|
29 | If you want to select e.g. alphanumeric words, you can use the following |
|
|
30 | setting: |
|
|
31 | |
|
|
32 | URxvt.selection.pattern-0: ([[:word:]]+) |
|
|
33 | |
|
|
34 | If you click more than twice, the selection will be extended |
|
|
35 | more and more. |
|
|
36 | |
|
|
37 | To get a selection that is very similar to the old code, try this pattern: |
|
|
38 | |
|
|
39 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
|
|
40 | |
|
|
41 | Please also note that the I<LeftClick Shift-LeftClik> combination also |
|
|
42 | selects words like the old code. |
|
|
43 | |
|
|
44 | =head2 I don't like the new selection/popups/hotkeys/perl, how do I |
|
|
45 | change/disable it? |
|
|
46 | |
|
|
47 | You can disable the perl extension completely by setting the |
|
|
48 | B<perl-ext-common> resource to the empty string, which also keeps |
|
|
49 | rxvt-unicode from initialising perl, saving memory. |
|
|
50 | |
|
|
51 | If you only want to disable specific features, you first have to |
|
|
52 | identify which perl extension is responsible. For this, read the section |
|
|
53 | B<PREPACKAGED EXTENSIONS> in the @@RXVT_NAME@@perl(3) manpage. For |
|
|
54 | example, to disable the B<selection-popup> and B<option-popup>, specify |
|
|
55 | this B<perl-ext-common> resource: |
|
|
56 | |
|
|
57 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
|
|
58 | |
|
|
59 | This will keep the default extensions, but disable the two popup |
|
|
60 | extensions. Some extensions can also be configured, for example, |
|
|
61 | scrollback search mode is triggered by B<M-s>. You can move it to any |
|
|
62 | other combination either by setting the B<searchable-scrollback> resource: |
|
|
63 | |
|
|
64 | URxvt.searchable-scrollback: CM-s |
|
|
65 | |
|
|
66 | =head2 The cursor moves when selecting text in the current input line, how |
|
|
67 | do I switch this off? |
|
|
68 | |
|
|
69 | =head2 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor |
|
|
70 | outputs strange escape sequences, how do I fix this? |
|
|
71 | |
|
|
72 | These are caused by the C<readline> perl extension. Under normal |
|
|
73 | circumstances, it will move your cursor around when you click into the |
|
|
74 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
75 | but when running a program that doesn't parse cursor movements or in some |
|
|
76 | cases during rlogin sessions, it fails to detect this properly. |
|
|
77 | |
|
|
78 | You can permamently switch this feature off by disabling the C<readline> |
|
|
79 | extension: |
|
|
80 | |
|
|
81 | URxvt.perl-ext-common: default,-readline |
|
|
82 | |
|
|
83 | =head2 Why doesn't rxvt-unicode read my resources? |
|
|
84 | |
|
|
85 | Well, why, indeed? It does, in a way very similar to other X |
|
|
86 | applications. Most importantly, this means that if you or your OS loads |
|
|
87 | resources into the X display (the right way to do it), rxvt-unicode will |
|
|
88 | ignore any resource files in your home directory. It will only read |
|
|
89 | F<$HOME/.Xdefaults> when no resources are attached to the display. |
|
|
90 | |
|
|
91 | If you have or use an F<$HOME/.Xresources> file, chances are that |
|
|
92 | resources are loaded into your X-server. In this case, you have to |
|
|
93 | re-login after every change (or run F<xrdb -merge $HOME/.Xresources>). |
|
|
94 | |
|
|
95 | Also consider the form resources have to use: |
|
|
96 | |
|
|
97 | URxvt.resource: value |
|
|
98 | |
|
|
99 | If you want to use another form (there are lots of different ways of |
|
|
100 | specifying resources), make sure you understand wether and why it |
|
|
101 | works. If unsure, use the form above. |
|
|
102 | |
|
|
103 | =head2 I can't get transparency working, what am I doing wrong? |
|
|
104 | |
|
|
105 | First of all, transparency isn't officially supported in rxvt-unicode, so |
|
|
106 | you are mostly on your own. Do not bug the author about it (but you may |
|
|
107 | bug everybody else). Also, if you can't get it working consider it a rite |
|
|
108 | of passage: ... and you failed. |
|
|
109 | |
|
|
110 | Here are four ways to get transparency. B<Do> read the manpage and option |
|
|
111 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
|
|
112 | |
|
|
113 | 1. Use inheritPixmap: |
|
|
114 | |
|
|
115 | Esetroot wallpaper.jpg |
|
|
116 | @@RXVT_NAME@@ -ip -tint red -sh 40 |
|
|
117 | |
|
|
118 | That works. If you think it doesn't, you lack transparency and tinting |
|
|
119 | support, or you are unable to read. |
|
|
120 | |
|
|
121 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
|
|
122 | to use effects other than tinting and shading: Just shade/tint/whatever |
|
|
123 | your picture with gimp: |
|
|
124 | |
|
|
125 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
|
|
126 | @@RXVT_NAME@@ -pixmap background.xpm -pe automove-background |
|
|
127 | |
|
|
128 | That works. If you think it doesn't, you lack XPM and Perl support, or you |
|
|
129 | are unable to read. |
|
|
130 | |
|
|
131 | 3. Use an ARGB visual: |
|
|
132 | |
|
|
133 | @@RXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
|
|
134 | |
|
|
135 | This requires XFT support, and the support of your X-server. If that |
|
|
136 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
|
|
137 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
|
|
138 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
|
|
139 | doesn't mean that your WM has the required kludges in place. |
|
|
140 | |
|
|
141 | 4. Use xcompmgr and let it do the job: |
|
|
142 | |
|
|
143 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
|
|
144 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
|
|
145 | |
|
|
146 | Then click on a window you want to make transparent. Replace C<0xc0000000> |
|
|
147 | by other values to change the degree of opacity. If it doesn't work and |
|
|
148 | your server crashes, you got to keep the pieces. |
|
|
149 | |
29 | =item Isn't rxvt supposed to be small? Don't all those features bloat? |
150 | =head2 Isn't rxvt supposed to be small? Don't all those features bloat? |
30 | |
151 | |
31 | I often get asked about this, and I think, no, they didn't cause extra |
152 | I often get asked about this, and I think, no, they didn't cause extra |
32 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
153 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
33 | that the urxvt binary is larger (due to some encoding tables always being |
154 | that the urxvt binary is larger (due to some encoding tables always being |
34 | compiled in), but it actually uses less memory (RSS) after startup. Even |
155 | compiled in), but it actually uses less memory (RSS) after startup. Even |
… | |
… | |
66 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
187 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
67 | 43180k in daemons that stay around after exit, plus half a minute of |
188 | 43180k in daemons that stay around after exit, plus half a minute of |
68 | startup time, including the hundreds of warnings it spits out), it fares |
189 | startup time, including the hundreds of warnings it spits out), it fares |
69 | extremely well *g*. |
190 | extremely well *g*. |
70 | |
191 | |
71 | =item Why C++, isn't that unportable/bloated/uncool? |
192 | =head2 Why C++, isn't that unportable/bloated/uncool? |
72 | |
193 | |
73 | Is this a question? :) It comes up very often. The simple answer is: I had |
194 | Is this a question? :) It comes up very often. The simple answer is: I had |
74 | to write it, and C++ allowed me to write and maintain it in a fraction |
195 | to write it, and C++ allowed me to write and maintain it in a fraction |
75 | of the time and effort (which is a scarce resource for me). Put even |
196 | of the time and effort (which is a scarce resource for me). Put even |
76 | shorter: It simply wouldn't exist without C++. |
197 | shorter: It simply wouldn't exist without C++. |
… | |
… | |
100 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
221 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
101 | |
222 | |
102 | No large bloated libraries (of course, none were linked in statically), |
223 | No large bloated libraries (of course, none were linked in statically), |
103 | except maybe libX11 :) |
224 | except maybe libX11 :) |
104 | |
225 | |
105 | =item Does it support tabs, can I have a tabbed rxvt-unicode? |
226 | =head2 Does it support tabs, can I have a tabbed rxvt-unicode? |
106 | |
227 | |
107 | rxvt-unicode does not directly support tabs. It will work fine with |
228 | Beginning with version 7.3, there is a perl extension that implements a |
108 | tabbing functionality of many window managers or similar tabbing programs, |
229 | simple tabbed terminal. It is installed by default, so any of these should |
109 | and its embedding-features allow it to be embedded into other programs, |
230 | give you tabs: |
110 | as witnessed by F<doc/rxvt-tabbed> or the upcoming C<Gtk2::URxvt> perl |
|
|
111 | module, which features a tabbed urxvt (murxvt) terminal as an example |
|
|
112 | embedding application. |
|
|
113 | |
231 | |
|
|
232 | @@RXVT_NAME@@ -pe tabbed |
|
|
233 | |
|
|
234 | URxvt.perl-ext-common: default,tabbed |
|
|
235 | |
|
|
236 | It will also work fine with tabbing functionality of many window managers |
|
|
237 | or similar tabbing programs, and its embedding-features allow it to be |
|
|
238 | embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or |
|
|
239 | the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt |
|
|
240 | (murxvt) terminal as an example embedding application. |
|
|
241 | |
114 | =item How do I know which rxvt-unicode version I'm using? |
242 | =head2 How do I know which rxvt-unicode version I'm using? |
115 | |
243 | |
116 | The version number is displayed with the usage (-h). Also the escape |
244 | The version number is displayed with the usage (-h). Also the escape |
117 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
245 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
118 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
246 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
119 | daemon. |
247 | daemon. |
120 | |
248 | |
121 | =item I am using Debian GNU/Linux and have a problem... |
249 | =head2 I am using Debian GNU/Linux and have a problem... |
122 | |
250 | |
123 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
251 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
124 | patches that considerably change the behaviour of rxvt-unicode. Before |
252 | patches that considerably change the behaviour of rxvt-unicode (but |
125 | reporting a bug to the original rxvt-unicode author please download and |
253 | unfortunately this notice has been removed). Before reporting a bug to |
126 | install the genuine version (L<http://software.schmorp.de#rxvt-unicode>) |
254 | the original rxvt-unicode author please download and install the genuine |
127 | and try to reproduce the problem. If you cannot, chances are that the |
255 | version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
128 | problems are specific to Debian GNU/Linux, in which case it should be |
256 | the problem. If you cannot, chances are that the problems are specific to |
129 | reported via the Debian Bug Tracking System (use C<reportbug> to report |
257 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
130 | the bug). |
258 | Tracking System (use C<reportbug> to report the bug). |
131 | |
259 | |
132 | For other problems that also affect the Debian package, you can and |
260 | For other problems that also affect the Debian package, you can and |
133 | probably should use the Debian BTS, too, because, after all, it's also a |
261 | probably should use the Debian BTS, too, because, after all, it's also a |
134 | bug in the Debian version and it serves as a reminder for other users that |
262 | bug in the Debian version and it serves as a reminder for other users that |
135 | might encounter the same issue. |
263 | might encounter the same issue. |
136 | |
264 | |
137 | =item I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
265 | =head2 I am maintaining rxvt-unicode for distribution/OS XXX, any |
|
|
266 | recommendation? |
138 | |
267 | |
139 | You should build one binary with the default options. F<configure> |
268 | You should build one binary with the default options. F<configure> |
140 | now enables most useful options, and the trend goes to making them |
269 | now enables most useful options, and the trend goes to making them |
141 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
270 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
142 | except higher disk and possibly memory usage. The perl interpreter should |
271 | except higher disk and possibly memory usage. The perl interpreter should |
… | |
… | |
152 | If you can/want build more binaries, I recommend building a minimal |
281 | If you can/want build more binaries, I recommend building a minimal |
153 | one with C<--disable-everything> (very useful) and a maximal one with |
282 | one with C<--disable-everything> (very useful) and a maximal one with |
154 | C<--enable-everything> (less useful, it will be very big due to a lot of |
283 | C<--enable-everything> (less useful, it will be very big due to a lot of |
155 | encodings built-in that increase download times and are rarely used). |
284 | encodings built-in that increase download times and are rarely used). |
156 | |
285 | |
157 | =item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
286 | =head2 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
158 | |
287 | |
159 | Likely not. While I honestly try to make it secure, and am probably not |
288 | It should be, starting with release 7.1. You are encouraged to properly |
160 | bad at it, I think it is simply unreasonable to expect all of freetype |
289 | install urxvt with privileges necessary for your OS now. |
161 | + fontconfig + xft + xlib + perl + ... + rxvt-unicode itself to all be |
|
|
162 | secure. Also, rxvt-unicode disables some options when it detects that it |
|
|
163 | runs setuid or setgid, which is not nice. Besides, with the embedded perl |
|
|
164 | interpreter the possibility for security problems easily multiplies. |
|
|
165 | |
290 | |
166 | Elevated privileges are only required for utmp and pty operations on some |
291 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
167 | systems (for example, GNU/Linux doesn't need any extra privileges for |
292 | into a helper process for privileged operations (pty handling on some |
168 | ptys, but some need it for utmp support). It is planned to mvoe this into |
293 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
169 | a forked handler process, but this is not yet done. |
294 | immediately. This is much safer than most other terminals that keep |
|
|
295 | privileges while running (but is more relevant to urxvt, as it contains |
|
|
296 | things as perl interpreters, which might be "helpful" to attackers). |
170 | |
297 | |
171 | So, while setuid/setgid operation is supported and not a problem on your |
298 | This forking is done as the very first within main(), which is very early |
172 | typical single-user-no-other-logins unix desktop, always remember that |
299 | and reduces possible bugs to initialisation code run before main(), or |
173 | its an awful lot of code, most of which isn't checked for security issues |
300 | things like the dynamic loader of your system, which should result in very |
174 | regularly. |
301 | little risk. |
175 | |
302 | |
176 | =item When I log-in to another system it tells me about missing terminfo data? |
303 | =head2 When I log-in to another system it tells me about missing terminfo data? |
177 | |
304 | |
178 | The terminal description used by rxvt-unicode is not as widely available |
305 | The terminal description used by rxvt-unicode is not as widely available |
179 | as that for xterm, or even rxvt (for which the same problem often arises). |
306 | as that for xterm, or even rxvt (for which the same problem often arises). |
180 | |
307 | |
181 | The correct solution for this problem is to install the terminfo, this can |
308 | The correct solution for this problem is to install the terminfo, this can |
… | |
… | |
199 | URxvt.termName: rxvt |
326 | URxvt.termName: rxvt |
200 | |
327 | |
201 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
328 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
202 | the rxvt terminfo file with the rxvt-unicode one. |
329 | the rxvt terminfo file with the rxvt-unicode one. |
203 | |
330 | |
204 | =item C<tic> outputs some error when compiling the terminfo entry. |
331 | =head2 C<tic> outputs some error when compiling the terminfo entry. |
205 | |
332 | |
206 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
333 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
207 | C<enacs=\E[0@> and try again. |
334 | C<enacs=\E[0@> and try again. |
208 | |
335 | |
209 | =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
336 | =head2 C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
210 | |
337 | |
211 | =item I need a termcap file entry. |
338 | =head2 I need a termcap file entry. |
212 | |
339 | |
213 | One reason you might want this is that some distributions or operating |
340 | One reason you might want this is that some distributions or operating |
214 | systems still compile some programs using the long-obsoleted termcap |
341 | systems still compile some programs using the long-obsoleted termcap |
215 | library (Fedora Core's bash is one example) and rely on a termcap entry |
342 | library (Fedora Core's bash is one example) and rely on a termcap entry |
216 | for C<rxvt-unicode>. |
343 | for C<rxvt-unicode>. |
… | |
… | |
242 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
369 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
243 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
370 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
244 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
371 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
245 | :vs=\E[?25h: |
372 | :vs=\E[?25h: |
246 | |
373 | |
247 | =item Why does C<ls> no longer have coloured output? |
374 | =head2 Why does C<ls> no longer have coloured output? |
248 | |
375 | |
249 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
376 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
250 | decide wether a terminal has colour, but uses it's own configuration |
377 | decide wether a terminal has colour, but uses it's own configuration |
251 | file. Needless to say, C<rxvt-unicode> is not in it's default file (among |
378 | file. Needless to say, C<rxvt-unicode> is not in it's default file (among |
252 | with most other terminals supporting colour). Either add: |
379 | with most other terminals supporting colour). Either add: |
… | |
… | |
257 | |
384 | |
258 | alias ls='ls --color=auto' |
385 | alias ls='ls --color=auto' |
259 | |
386 | |
260 | to your C<.profile> or C<.bashrc>. |
387 | to your C<.profile> or C<.bashrc>. |
261 | |
388 | |
262 | =item Why doesn't vim/emacs etc. use the 88 colour mode? |
389 | =head2 Why doesn't vim/emacs etc. use the 88 colour mode? |
263 | |
390 | |
264 | =item Why doesn't vim/emacs etc. make use of italic? |
391 | =head2 Why doesn't vim/emacs etc. make use of italic? |
265 | |
392 | |
266 | =item Why are the secondary screen-related options not working properly? |
393 | =head2 Why are the secondary screen-related options not working properly? |
267 | |
394 | |
268 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
395 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
269 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
396 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
270 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
397 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
271 | features. Unfortunately, some of these (most notably, again, Debian |
398 | features. Unfortunately, some of these (most notably, again, Debian |
272 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
399 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
273 | file, so you will need to install it on your own (See the question B<When |
400 | file, so you will need to install it on your own (See the question B<When |
274 | I log-in to another system it tells me about missing terminfo data?> on |
401 | I log-in to another system it tells me about missing terminfo data?> on |
275 | how to do this). |
402 | how to do this). |
276 | |
403 | |
277 | =item My numerical keypad acts weird and generates differing output? |
404 | =head2 My numerical keypad acts weird and generates differing output? |
278 | |
405 | |
279 | Some Debian GNUL/Linux users seem to have this problem, although no |
406 | Some Debian GNUL/Linux users seem to have this problem, although no |
280 | specific details were reported so far. It is possible that this is caused |
407 | specific details were reported so far. It is possible that this is caused |
281 | by the wrong C<TERM> setting, although the details of wether and how |
408 | by the wrong C<TERM> setting, although the details of wether and how |
282 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
409 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
283 | keymap. See the answer to the previous question, and please report if that |
410 | keymap. See the answer to the previous question, and please report if that |
284 | helped. |
411 | helped. |
285 | |
412 | |
286 | =item Rxvt-unicode does not seem to understand the selected encoding? |
413 | =head2 Rxvt-unicode does not seem to understand the selected encoding? |
287 | |
414 | |
288 | =item Unicode does not seem to work? |
415 | =head2 Unicode does not seem to work? |
289 | |
416 | |
290 | If you encounter strange problems like typing an accented character but |
417 | If you encounter strange problems like typing an accented character but |
291 | getting two unrelated other characters or similar, or if program output is |
418 | getting two unrelated other characters or similar, or if program output is |
292 | subtly garbled, then you should check your locale settings. |
419 | subtly garbled, then you should check your locale settings. |
293 | |
420 | |
… | |
… | |
313 | |
440 | |
314 | If nothing works and you are sure that everything is set correctly then |
441 | If nothing works and you are sure that everything is set correctly then |
315 | you will need to remember a little known fact: Some programs just don't |
442 | you will need to remember a little known fact: Some programs just don't |
316 | support locales :( |
443 | support locales :( |
317 | |
444 | |
318 | =item Why do some characters look so much different than others? |
445 | =head2 Why do some characters look so much different than others? |
319 | |
446 | |
320 | =item How does rxvt-unicode choose fonts? |
447 | =head2 How does rxvt-unicode choose fonts? |
321 | |
448 | |
322 | Most fonts do not contain the full range of Unicode, which is |
449 | Most fonts do not contain the full range of Unicode, which is |
323 | fine. Chances are that the font you (or the admin/package maintainer of |
450 | fine. Chances are that the font you (or the admin/package maintainer of |
324 | your system/os) have specified does not cover all the characters you want |
451 | your system/os) have specified does not cover all the characters you want |
325 | to display. |
452 | to display. |
… | |
… | |
343 | |
470 | |
344 | The only limitation is that none of the fonts may be larger than the base |
471 | The only limitation is that none of the fonts may be larger than the base |
345 | font, as the base font defines the terminal character cell size, which |
472 | font, as the base font defines the terminal character cell size, which |
346 | must be the same due to the way terminals work. |
473 | must be the same due to the way terminals work. |
347 | |
474 | |
348 | =item Why do some chinese characters look so different than others? |
475 | =head2 Why do some chinese characters look so different than others? |
349 | |
476 | |
350 | This is because there is a difference between script and language -- |
477 | This is because there is a difference between script and language -- |
351 | rxvt-unicode does not know which language the text that is output is, |
478 | rxvt-unicode does not know which language the text that is output is, |
352 | as it only knows the unicode character codes. If rxvt-unicode first |
479 | as it only knows the unicode character codes. If rxvt-unicode first |
353 | sees a japanese/chinese character, it might choose a japanese font for |
480 | sees a japanese/chinese character, it might choose a japanese font for |
… | |
… | |
368 | has been designed yet). |
495 | has been designed yet). |
369 | |
496 | |
370 | Until then, you might get away with switching fonts at runtime (see L<Can |
497 | Until then, you might get away with switching fonts at runtime (see L<Can |
371 | I switch the fonts at runtime?> later in this document). |
498 | I switch the fonts at runtime?> later in this document). |
372 | |
499 | |
373 | =item Why does rxvt-unicode sometimes leave pixel droppings? |
500 | =head2 Why does rxvt-unicode sometimes leave pixel droppings? |
374 | |
501 | |
375 | Most fonts were not designed for terminal use, which means that character |
502 | Most fonts were not designed for terminal use, which means that character |
376 | size varies a lot. A font that is otherwise fine for terminal use might |
503 | size varies a lot. A font that is otherwise fine for terminal use might |
377 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
504 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
378 | these characters. For characters that are just "a bit" too wide a special |
505 | these characters. For characters that are just "a bit" too wide a special |
… | |
… | |
390 | might be forced to use a different font. |
517 | might be forced to use a different font. |
391 | |
518 | |
392 | All of this is not a problem when using X11 core fonts, as their bounding |
519 | All of this is not a problem when using X11 core fonts, as their bounding |
393 | box data is correct. |
520 | box data is correct. |
394 | |
521 | |
395 | =item On Solaris 9, many line-drawing characters are too wide. |
522 | =head2 On Solaris 9, many line-drawing characters are too wide. |
396 | |
523 | |
397 | Seems to be a known bug, read |
524 | Seems to be a known bug, read |
398 | L<http://nixdoc.net/files/forum/about34198.html>. Some people use the |
525 | L<http://nixdoc.net/files/forum/about34198.html>. Some people use the |
399 | following ugly workaround to get non-double-wide-characters working: |
526 | following ugly workaround to get non-double-wide-characters working: |
400 | |
527 | |
401 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
528 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
402 | |
529 | |
403 | =item My Compose (Multi_key) key is no longer working. |
530 | =head2 My Compose (Multi_key) key is no longer working. |
404 | |
531 | |
405 | The most common causes for this are that either your locale is not set |
532 | The most common causes for this are that either your locale is not set |
406 | correctly, or you specified a B<preeditStyle> that is not supported by |
533 | correctly, or you specified a B<preeditStyle> that is not supported by |
407 | your input method. For example, if you specified B<OverTheSpot> and |
534 | your input method. For example, if you specified B<OverTheSpot> and |
408 | your input method (e.g. the default input method handling Compose keys) |
535 | your input method (e.g. the default input method handling Compose keys) |
… | |
… | |
410 | rxvt-unicode will continue without an input method. |
537 | rxvt-unicode will continue without an input method. |
411 | |
538 | |
412 | In this case either do not specify a B<preeditStyle> or specify more than |
539 | In this case either do not specify a B<preeditStyle> or specify more than |
413 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
540 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
414 | |
541 | |
415 | =item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
542 | =head2 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
416 | |
543 | |
417 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
544 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
418 | international keyboards) or simply use ISO 14755 support to your |
545 | international keyboards) or simply use ISO 14755 support to your |
419 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
546 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
420 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
547 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
421 | character and so on. |
548 | character and so on. |
422 | |
549 | |
423 | =item How can I keep rxvt-unicode from using reverse video so much? |
550 | =head2 How can I keep rxvt-unicode from using reverse video so much? |
424 | |
551 | |
425 | First of all, make sure you are running with the right terminal settings |
552 | First of all, make sure you are running with the right terminal settings |
426 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
553 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
427 | make sure you have specified colours for italic and bold, as otherwise |
554 | make sure you have specified colours for italic and bold, as otherwise |
428 | rxvt-unicode might use reverse video to simulate the effect: |
555 | rxvt-unicode might use reverse video to simulate the effect: |
429 | |
556 | |
430 | URxvt.colorBD: white |
557 | URxvt.colorBD: white |
431 | URxvt.colorIT: green |
558 | URxvt.colorIT: green |
432 | |
559 | |
433 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
560 | =head2 Some programs assume totally weird colours (red instead of blue), how can I fix that? |
434 | |
561 | |
435 | For some unexplainable reason, some rare programs assume a very weird |
562 | For some unexplainable reason, some rare programs assume a very weird |
436 | colour palette when confronted with a terminal with more than the standard |
563 | colour palette when confronted with a terminal with more than the standard |
437 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
564 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
438 | these programs not to assume non-ISO colours without very good reasons. |
565 | these programs not to assume non-ISO colours without very good reasons. |
439 | |
566 | |
440 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
567 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
441 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
568 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
442 | fix colours but keep you from using other rxvt-unicode features. |
569 | fix colours but keep you from using other rxvt-unicode features. |
443 | |
570 | |
444 | =item I am on FreeBSD and rxvt-unicode does not seem to work at all. |
571 | =head2 I am on FreeBSD and rxvt-unicode does not seem to work at all. |
445 | |
572 | |
446 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
573 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
447 | in your compile environment, or an implementation that implements it, |
574 | in your compile environment, or an implementation that implements it, |
448 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
575 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
449 | B<wchar_t> is represented as unicode. |
576 | B<wchar_t> is represented as unicode. |
… | |
… | |
471 | |
598 | |
472 | The rxvt-unicode author insists that the right way to fix this is in the |
599 | The rxvt-unicode author insists that the right way to fix this is in the |
473 | system libraries once and for all, instead of forcing every app to carry |
600 | system libraries once and for all, instead of forcing every app to carry |
474 | complete replacements for them :) |
601 | complete replacements for them :) |
475 | |
602 | |
476 | =item I use Solaris 9 and it doesn't compile/work/etc. |
603 | =head2 I use Solaris 9 and it doesn't compile/work/etc. |
477 | |
604 | |
478 | Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst |
605 | Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst |
479 | problems with C<wcwidth> and a compile problem. |
606 | problems with C<wcwidth> and a compile problem. |
480 | |
607 | |
481 | =item How can I use rxvt-unicode under cygwin? |
608 | =head2 How can I use rxvt-unicode under cygwin? |
482 | |
609 | |
483 | rxvt-unicode should compile and run out of the box on cygwin, using |
610 | rxvt-unicode should compile and run out of the box on cygwin, using |
484 | the X11 libraries that come with cygwin. libW11 emulation is no |
611 | the X11 libraries that come with cygwin. libW11 emulation is no |
485 | longer supported (and makes no sense, either, as it only supported a |
612 | longer supported (and makes no sense, either, as it only supported a |
486 | single font). I recommend starting the X-server in C<-multiwindow> or |
613 | single font). I recommend starting the X-server in C<-multiwindow> or |
… | |
… | |
489 | |
616 | |
490 | At the time of this writing, cygwin didn't seem to support any multi-byte |
617 | At the time of this writing, cygwin didn't seem to support any multi-byte |
491 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
618 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
492 | to 8-bit encodings. |
619 | to 8-bit encodings. |
493 | |
620 | |
494 | =item How does rxvt-unicode determine the encoding to use? |
621 | =head2 How does rxvt-unicode determine the encoding to use? |
495 | |
622 | |
496 | =item Is there an option to switch encodings? |
623 | =head2 Is there an option to switch encodings? |
497 | |
624 | |
498 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
625 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
499 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
626 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
500 | UTF-8 or any other encodings with respect to terminal I/O. |
627 | UTF-8 or any other encodings with respect to terminal I/O. |
501 | |
628 | |
… | |
… | |
526 | rxvt-unicode. |
653 | rxvt-unicode. |
527 | |
654 | |
528 | If you want to use a specific encoding you have to make sure you start |
655 | If you want to use a specific encoding you have to make sure you start |
529 | rxvt-unicode with the correct C<LC_CTYPE> category. |
656 | rxvt-unicode with the correct C<LC_CTYPE> category. |
530 | |
657 | |
531 | =item Can I switch locales at runtime? |
658 | =head2 Can I switch locales at runtime? |
532 | |
659 | |
533 | Yes, using an escape sequence. Try something like this, which sets |
660 | Yes, using an escape sequence. Try something like this, which sets |
534 | rxvt-unicode's idea of C<LC_CTYPE>. |
661 | rxvt-unicode's idea of C<LC_CTYPE>. |
535 | |
662 | |
536 | printf '\e]701;%s\007' ja_JP.SJIS |
663 | printf '\e]701;%s\007' ja_JP.SJIS |
… | |
… | |
548 | |
675 | |
549 | You can also use xterm's C<luit> program, which usually works fine, except |
676 | You can also use xterm's C<luit> program, which usually works fine, except |
550 | for some locales where character width differs between program- and |
677 | for some locales where character width differs between program- and |
551 | rxvt-unicode-locales. |
678 | rxvt-unicode-locales. |
552 | |
679 | |
553 | =item Can I switch the fonts at runtime? |
680 | =head2 Can I switch the fonts at runtime? |
554 | |
681 | |
555 | Yes, using an escape sequence. Try something like this, which has the same |
682 | Yes, using an escape sequence. Try something like this, which has the same |
556 | effect as using the C<-fn> switch, and takes effect immediately: |
683 | effect as using the C<-fn> switch, and takes effect immediately: |
557 | |
684 | |
558 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
685 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
… | |
… | |
561 | japanese font), but you have to switch to chinese temporarily, where |
688 | japanese font), but you have to switch to chinese temporarily, where |
562 | japanese fonts would only be in your way. |
689 | japanese fonts would only be in your way. |
563 | |
690 | |
564 | You can think of this as a kind of manual ISO-2022 switching. |
691 | You can think of this as a kind of manual ISO-2022 switching. |
565 | |
692 | |
566 | =item Why do italic characters look as if clipped? |
693 | =head2 Why do italic characters look as if clipped? |
567 | |
694 | |
568 | Many fonts have difficulties with italic characters and hinting. For |
695 | Many fonts have difficulties with italic characters and hinting. For |
569 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
696 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
570 | Mono> completely fails in it's italic face. A workaround might be to |
697 | Mono> completely fails in it's italic face. A workaround might be to |
571 | enable freetype autohinting, i.e. like this: |
698 | enable freetype autohinting, i.e. like this: |
572 | |
699 | |
573 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
700 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
574 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
701 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
575 | |
702 | |
576 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
703 | =head2 My input method wants <some encoding> but I want UTF-8, what can I do? |
577 | |
704 | |
578 | You can specify separate locales for the input method and the rest of the |
705 | You can specify separate locales for the input method and the rest of the |
579 | terminal, using the resource C<imlocale>: |
706 | terminal, using the resource C<imlocale>: |
580 | |
707 | |
581 | URxvt*imlocale: ja_JP.EUC-JP |
708 | URxvt.imlocale: ja_JP.EUC-JP |
582 | |
709 | |
583 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
710 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
584 | use your input method. Please note, however, that you will not be able to |
711 | use your input method. Please note, however, that you will not be able to |
585 | input characters outside C<EUC-JP> in a normal way then, as your input |
712 | input characters outside C<EUC-JP> in a normal way then, as your input |
586 | method limits you. |
713 | method limits you. |
587 | |
714 | |
588 | =item Rxvt-unicode crashes when the X Input Method changes or exits. |
715 | =head2 Rxvt-unicode crashes when the X Input Method changes or exits. |
589 | |
716 | |
590 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
717 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
591 | design. Applications can avoid some crashes at the expense of memory |
718 | design. Applications can avoid some crashes at the expense of memory |
592 | leaks, and Input Methods can avoid some crashes by careful ordering at |
719 | leaks, and Input Methods can avoid some crashes by careful ordering at |
593 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
720 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
594 | while B<SCIM> (or similar input methods) fails. In the end, however, |
721 | while B<SCIM> (or similar input methods) fails. In the end, however, |
595 | crashes cannot be completely avoided even if both sides cooperate. |
722 | crashes cannot be completely avoided even if both sides cooperate. |
596 | |
723 | |
597 | So the only workaround is not to kill your Input Method Servers. |
724 | So the only workaround is not to kill your Input Method Servers. |
598 | |
725 | |
599 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
726 | =head2 Rxvt-unicode uses gobs of memory, how can I reduce that? |
600 | |
727 | |
601 | Rxvt-unicode tries to obey the rule of not charging you for something you |
728 | Rxvt-unicode tries to obey the rule of not charging you for something you |
602 | don't use. One thing you should try is to configure out all settings that |
729 | don't use. One thing you should try is to configure out all settings that |
603 | you don't need, for example, Xft support is a resource hog by design, |
730 | you don't need, for example, Xft support is a resource hog by design, |
604 | when used. Compiling it out ensures that no Xft font will be loaded |
731 | when used. Compiling it out ensures that no Xft font will be loaded |
… | |
… | |
609 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
736 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
610 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
737 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
611 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
738 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
612 | rxvt-unicode then uses 8 bytes per screen cell. |
739 | rxvt-unicode then uses 8 bytes per screen cell. |
613 | |
740 | |
614 | =item Can I speed up Xft rendering somehow? |
741 | =head2 Can I speed up Xft rendering somehow? |
615 | |
742 | |
616 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
743 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
617 | it is simply slow. If you still want Xft fonts you might try to disable |
744 | it is simply slow. If you still want Xft fonts you might try to disable |
618 | antialiasing (by appending C<:antialias=false>), which saves lots of |
745 | antialiasing (by appending C<:antialias=false>), which saves lots of |
619 | memory and also speeds up rendering considerably. |
746 | memory and also speeds up rendering considerably. |
620 | |
747 | |
621 | =item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
748 | =head2 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
622 | |
749 | |
623 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
750 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
624 | fall back to it's default font search list it will prefer X11 core |
751 | fall back to it's default font search list it will prefer X11 core |
625 | fonts, because they are small and fast, and then use Xft fonts. It has |
752 | fonts, because they are small and fast, and then use Xft fonts. It has |
626 | antialiasing disabled for most of them, because the author thinks they |
753 | antialiasing disabled for most of them, because the author thinks they |
627 | look best that way. |
754 | look best that way. |
628 | |
755 | |
629 | If you want antialiasing, you have to specify the fonts manually. |
756 | If you want antialiasing, you have to specify the fonts manually. |
630 | |
757 | |
631 | =item Mouse cut/paste suddenly no longer works. |
758 | =head2 Mouse cut/paste suddenly no longer works. |
632 | |
759 | |
633 | Make sure that mouse reporting is actually turned off since killing |
760 | Make sure that mouse reporting is actually turned off since killing |
634 | some editors prematurely may leave the mouse in mouse report mode. I've |
761 | some editors prematurely may leave the mouse in mouse report mode. I've |
635 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
762 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
636 | quick check is to see if cut/paste works when the Alt or Shift keys are |
763 | quick check is to see if cut/paste works when the Alt or Shift keys are |
637 | depressed. See @@RXVT_NAME@@(7) |
764 | depressed. |
638 | |
765 | |
639 | =item What's with this bold/blink stuff? |
766 | =head2 What's with this bold/blink stuff? |
640 | |
767 | |
641 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
768 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
642 | standard foreground colour. |
769 | standard foreground colour. |
643 | |
770 | |
644 | For the standard background colour, blinking will actually make the |
771 | For the standard background colour, blinking will actually make the |
… | |
… | |
651 | |
778 | |
652 | color0-7 are the low-intensity colors. |
779 | color0-7 are the low-intensity colors. |
653 | |
780 | |
654 | color8-15 are the corresponding high-intensity colors. |
781 | color8-15 are the corresponding high-intensity colors. |
655 | |
782 | |
656 | =item I don't like the screen colors. How do I change them? |
783 | =head2 I don't like the screen colors. How do I change them? |
657 | |
784 | |
658 | You can change the screen colors at run-time using F<~/.Xdefaults> |
785 | You can change the screen colors at run-time using F<~/.Xdefaults> |
659 | resources (or as long-options). |
786 | resources (or as long-options). |
660 | |
787 | |
661 | Here are values that are supposed to resemble a VGA screen, |
788 | Here are values that are supposed to resemble a VGA screen, |
… | |
… | |
699 | URxvt.color6: #73f7ff |
826 | URxvt.color6: #73f7ff |
700 | URxvt.color14: #73f7ff |
827 | URxvt.color14: #73f7ff |
701 | URxvt.color7: #e1dddd |
828 | URxvt.color7: #e1dddd |
702 | URxvt.color15: #e1dddd |
829 | URxvt.color15: #e1dddd |
703 | |
830 | |
704 | =item How can I start @@RXVT_NAME@@d in a race-free way? |
831 | =head2 How can I start @@RXVT_NAME@@d in a race-free way? |
705 | |
832 | |
706 | Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the |
833 | Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the |
707 | display, create the listening socket and then fork. |
834 | display, create the listening socket and then fork. |
708 | |
835 | |
709 | =item What's with the strange Backspace/Delete key behaviour? |
836 | =head2 What's with the strange Backspace/Delete key behaviour? |
710 | |
837 | |
711 | Assuming that the physical Backspace key corresponds to the |
838 | Assuming that the physical Backspace key corresponds to the |
712 | BackSpace keysym (not likely for Linux ... see the following |
839 | BackSpace keysym (not likely for Linux ... see the following |
713 | question) there are two standard values that can be used for |
840 | question) there are two standard values that can be used for |
714 | Backspace: C<^H> and C<^?>. |
841 | Backspace: C<^H> and C<^?>. |
… | |
… | |
731 | |
858 | |
732 | # use Backspace = ^? |
859 | # use Backspace = ^? |
733 | $ stty erase ^? |
860 | $ stty erase ^? |
734 | $ @@RXVT_NAME@@ |
861 | $ @@RXVT_NAME@@ |
735 | |
862 | |
736 | Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7). |
863 | Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>. |
737 | |
864 | |
738 | For an existing rxvt-unicode: |
865 | For an existing rxvt-unicode: |
739 | |
866 | |
740 | # use Backspace = ^H |
867 | # use Backspace = ^H |
741 | $ stty erase ^H |
868 | $ stty erase ^H |
… | |
… | |
760 | some editors (vim I'm told) expect Backspace = ^H, |
887 | some editors (vim I'm told) expect Backspace = ^H, |
761 | GNU Emacs (and Emacs-like editors) use ^H for help. |
888 | GNU Emacs (and Emacs-like editors) use ^H for help. |
762 | |
889 | |
763 | Perhaps someday this will all be resolved in a consistent manner. |
890 | Perhaps someday this will all be resolved in a consistent manner. |
764 | |
891 | |
765 | =item I don't like the key-bindings. How do I change them? |
892 | =head2 I don't like the key-bindings. How do I change them? |
766 | |
893 | |
767 | There are some compile-time selections available via configure. Unless |
894 | There are some compile-time selections available via configure. Unless |
768 | you have run "configure" with the C<--disable-resources> option you can |
895 | you have run "configure" with the C<--disable-resources> option you can |
769 | use the `keysym' resource to alter the keystrings associated with keysyms. |
896 | use the `keysym' resource to alter the keystrings associated with keysyms. |
770 | |
897 | |
… | |
… | |
791 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
918 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
792 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
919 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
793 | |
920 | |
794 | See some more examples in the documentation for the B<keysym> resource. |
921 | See some more examples in the documentation for the B<keysym> resource. |
795 | |
922 | |
796 | =item I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
923 | =head2 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
797 | How do I make use of them? For example, the Sun Keyboard type 4 |
924 | How do I make use of them? For example, the Sun Keyboard type 4 |
798 | has the following mappings that rxvt-unicode doesn't recognize. |
925 | has the following mappings that rxvt-unicode doesn't recognize. |
799 | |
926 | |
800 | KP_Insert == Insert |
927 | KP_Insert == Insert |
801 | F22 == Print |
928 | F22 == Print |
… | |
… | |
806 | |
933 | |
807 | Rather than have rxvt-unicode try to accommodate all the various possible |
934 | Rather than have rxvt-unicode try to accommodate all the various possible |
808 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
935 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
809 | required for your particular machine. |
936 | required for your particular machine. |
810 | |
937 | |
811 | =item How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
938 | =head2 How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
812 | I need this to decide about setting colors etc. |
939 | I need this to decide about setting colors etc. |
813 | |
940 | |
814 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
941 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
815 | check and see if that is set. Note that several programs, JED, slrn, |
942 | check and see if that is set. Note that several programs, JED, slrn, |
816 | Midnight Commander automatically check this variable to decide whether or |
943 | Midnight Commander automatically check this variable to decide whether or |
817 | not to use color. |
944 | not to use color. |
818 | |
945 | |
819 | =item How do I set the correct, full IP address for the DISPLAY variable? |
946 | =head2 How do I set the correct, full IP address for the DISPLAY variable? |
820 | |
947 | |
821 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
948 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
822 | insecure mode then it is possible to use the following shell script |
949 | insecure mode then it is possible to use the following shell script |
823 | snippets to correctly set the display. If your version of rxvt-unicode |
950 | snippets to correctly set the display. If your version of rxvt-unicode |
824 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
951 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
… | |
… | |
839 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
966 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
840 | read DISPLAY # set it in our local shell |
967 | read DISPLAY # set it in our local shell |
841 | fi |
968 | fi |
842 | fi |
969 | fi |
843 | |
970 | |
844 | =item How do I compile the manual pages for myself? |
971 | =head2 How do I compile the manual pages for myself? |
845 | |
972 | |
846 | You need to have a recent version of perl installed as F</usr/bin/perl>, |
973 | You need to have a recent version of perl installed as F</usr/bin/perl>, |
847 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
974 | one that comes with F<pod2man>, F<pod2text> and F<pod2html>. Then go to |
848 | the doc subdirectory and enter C<make alldoc>. |
975 | the doc subdirectory and enter C<make alldoc>. |
849 | |
976 | |
850 | =item My question isn't answered here, can I ask a human? |
977 | =head2 My question isn't answered here, can I ask a human? |
851 | |
978 | |
852 | Before sending me mail, you could go to IRC: C<irc.freenode.net>, |
979 | Before sending me mail, you could go to IRC: C<irc.freenode.net>, |
853 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
980 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
854 | interested in learning about new and exciting problems (but not FAQs :). |
981 | interested in learning about new and exciting problems (but not FAQs :). |
855 | |
982 | |
856 | =back |
|
|
857 | |
|
|
858 | =head1 RXVT TECHNICAL REFERENCE |
983 | =head1 RXVT TECHNICAL REFERENCE |
859 | |
984 | |
860 | =head1 DESCRIPTION |
985 | =head1 DESCRIPTION |
861 | |
986 | |
862 | The rest of this document describes various technical aspects of |
987 | The rest of this document describes various technical aspects of |
863 | B<rxvt-unicode>. First the description of supported command sequences, |
988 | B<rxvt-unicode>. First the description of supported command sequences, |
864 | followed by menu and pixmap support and last by a description of all |
989 | followed by pixmap support and last by a description of all features |
865 | features selectable at C<configure> time. |
990 | selectable at C<configure> time. |
866 | |
991 | |
867 | =head1 Definitions |
992 | =head1 Definitions |
868 | |
993 | |
869 | =over 4 |
994 | =over 4 |
870 | |
995 | |
… | |
… | |
1438 | B<< C<h> >> Send Mouse X & Y on button press. |
1563 | B<< C<h> >> Send Mouse X & Y on button press. |
1439 | B<< C<l> >> No mouse reporting. |
1564 | B<< C<l> >> No mouse reporting. |
1440 | |
1565 | |
1441 | =end table |
1566 | =end table |
1442 | |
1567 | |
1443 | =item B<< C<Ps = 10> >> (B<rxvt>) |
|
|
1444 | |
|
|
1445 | =begin table |
|
|
1446 | |
|
|
1447 | B<< C<h> >> menuBar visible |
|
|
1448 | B<< C<l> >> menuBar invisible |
|
|
1449 | |
|
|
1450 | =end table |
|
|
1451 | |
|
|
1452 | =item B<< C<Ps = 25> >> |
1568 | =item B<< C<Ps = 25> >> |
1453 | |
1569 | |
1454 | =begin table |
1570 | =begin table |
1455 | |
1571 | |
1456 | B<< C<h> >> Visible cursor {cnorm/cvvis} |
1572 | B<< C<h> >> Visible cursor {cnorm/cvvis} |
… | |
… | |
1638 | B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >> |
1754 | B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >> |
1639 | B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >> |
1755 | B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >> |
1640 | B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >> |
1756 | B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >> |
1641 | B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706] |
1757 | B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> [deprecated, see 706] |
1642 | B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707] |
1758 | B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> [deprecated, see 707] |
1643 | B<< C<Ps = 20> >> Change default background to B<< C<Pt> >> |
1759 | B<< C<Ps = 20> >> Change background pixmap parameters (see section XPM) (Compile XPM). |
1644 | B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>. |
1760 | B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>. |
1645 | B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented> |
1761 | B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented> |
1646 | B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>. |
1762 | B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>. |
1647 | B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >> |
1763 | B<< C<Ps = 50> >> Set fontset to B<< C<Pt> >>, with the following special values of B<< C<Pt> >> (B<rxvt>) B<< C<#+n> >> change up B<< C<n> >> B<< C<#-n> >> change down B<< C<n> >> if B<< C<n> >> is missing of 0, a value of 1 is used I<empty> change to font0 B<< C<n> >> change to font B<< C<n> >> |
1648 | B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >> |
1764 | B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >> |
1649 | B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills). |
1765 | B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (Compile frills). |
1650 | B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar). |
1766 | B<< C<Ps = 702> >> Request version if B<< C<Pt> >> is B<< C<?> >>, returning C<rxvt-unicode>, the resource name, the major and minor version numbers, e.g. C<ESC ] 702 ; rxvt-unicode ; urxvt ; 7 ; 4 ST>. |
1651 | B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >> |
1767 | B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >> |
1652 | B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency). |
1768 | B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency). |
1653 | B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >> |
1769 | B<< C<Ps = 706> >> Change colour of bold characters to B<< C<Pt> >> |
1654 | B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >> |
1770 | B<< C<Ps = 707> >> Change colour of underlined characters to B<< C<Pt> >> |
1655 | B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>. |
1771 | B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>. |
… | |
… | |
1662 | |
1778 | |
1663 | =end table |
1779 | =end table |
1664 | |
1780 | |
1665 | =back |
1781 | =back |
1666 | |
1782 | |
1667 | X<menuBar> |
|
|
1668 | |
|
|
1669 | =head1 menuBar |
|
|
1670 | |
|
|
1671 | B<< The exact syntax used is I<almost> solidified. >> |
|
|
1672 | In the menus, B<DON'T> try to use menuBar commands that add or remove a |
|
|
1673 | menuBar. |
|
|
1674 | |
|
|
1675 | Note that in all of the commands, the B<< I</path/> >> I<cannot> be |
|
|
1676 | omitted: use B<./> to specify a menu relative to the current menu. |
|
|
1677 | |
|
|
1678 | =head2 Overview of menuBar operation |
|
|
1679 | |
|
|
1680 | For the menuBar XTerm escape sequence C<ESC ] 703 ; Pt ST>, the syntax |
|
|
1681 | of C<Pt> can be used for a variety of tasks: |
|
|
1682 | |
|
|
1683 | At the top level is the current menuBar which is a member of a circular |
|
|
1684 | linked-list of other such menuBars. |
|
|
1685 | |
|
|
1686 | The menuBar acts as a parent for the various drop-down menus, which in |
|
|
1687 | turn, may have labels, separator lines, menuItems and subMenus. |
|
|
1688 | |
|
|
1689 | The menuItems are the useful bits: you can use them to mimic keyboard |
|
|
1690 | input or even to send text or escape sequences back to rxvt. |
|
|
1691 | |
|
|
1692 | The menuBar syntax is intended to provide a simple yet robust method of |
|
|
1693 | constructing and manipulating menus and navigating through the |
|
|
1694 | menuBars. |
|
|
1695 | |
|
|
1696 | The first step is to use the tag B<< [menu:I<name>] >> which creates |
|
|
1697 | the menuBar called I<name> and allows access. You may now or menus, |
|
|
1698 | subMenus, and menuItems. Finally, use the tag B<[done]> to set the |
|
|
1699 | menuBar access as B<readonly> to prevent accidental corruption of the |
|
|
1700 | menus. To re-access the current menuBar for alterations, use the tag |
|
|
1701 | B<[menu]>, make the alterations and then use B<[done]> |
|
|
1702 | |
|
|
1703 | X<menuBarCommands> |
|
|
1704 | |
|
|
1705 | =head2 Commands |
|
|
1706 | |
|
|
1707 | =over 4 |
|
|
1708 | |
|
|
1709 | =item B<< [menu:+I<name>] >> |
|
|
1710 | |
|
|
1711 | access the named menuBar for creation or alteration. If a new menuBar |
|
|
1712 | is created, it is called I<name> (max of 15 chars) and the current |
|
|
1713 | menuBar is pushed onto the stack |
|
|
1714 | |
|
|
1715 | =item B<[menu]> |
|
|
1716 | |
|
|
1717 | access the current menuBar for alteration |
|
|
1718 | |
|
|
1719 | =item B<< [title:+I<string>] >> |
|
|
1720 | |
|
|
1721 | set the current menuBar's title to I<string>, which may contain the |
|
|
1722 | following format specifiers: |
|
|
1723 | |
|
|
1724 | B<%n> rxvt name (as per the B<-name> command-line option) |
|
|
1725 | B<%v> rxvt version |
|
|
1726 | B<%%> literal B<%> character |
|
|
1727 | |
|
|
1728 | =item B<[done]> |
|
|
1729 | |
|
|
1730 | set menuBar access as B<readonly>. |
|
|
1731 | End-of-file tag for B<< [read:+I<file>] >> operations. |
|
|
1732 | |
|
|
1733 | =item B<< [read:+I<file>] >> |
|
|
1734 | |
|
|
1735 | read menu commands directly from I<file> (extension ".menu" will be |
|
|
1736 | appended if required.) Start reading at a line with B<[menu]> or B<< |
|
|
1737 | [menu:+I<name> >> and continuing until B<[done]> is encountered. |
|
|
1738 | |
|
|
1739 | Blank and comment lines (starting with B<#>) are ignored. Actually, |
|
|
1740 | since any invalid menu commands are also ignored, almost anything could |
|
|
1741 | be construed as a comment line, but this may be tightened up in the |
|
|
1742 | future ... so don't count on it!. |
|
|
1743 | |
|
|
1744 | =item B<< [read:+I<file>;+I<name>] >> |
|
|
1745 | |
|
|
1746 | The same as B<< [read:+I<file>] >>, but start reading at a line with |
|
|
1747 | B<< [menu:+I<name>] >> and continuing until B<< [done:+I<name>] >> or |
|
|
1748 | B<[done]> is encountered. |
|
|
1749 | |
|
|
1750 | =item B<[dump]> |
|
|
1751 | |
|
|
1752 | dump all menuBars to the file B</tmp/rxvt-PID> in a format suitable for |
|
|
1753 | later rereading. |
|
|
1754 | |
|
|
1755 | =item B<[rm:name]> |
|
|
1756 | |
|
|
1757 | remove the named menuBar |
|
|
1758 | |
|
|
1759 | =item B<[rm] [rm:]> |
|
|
1760 | |
|
|
1761 | remove the current menuBar |
|
|
1762 | |
|
|
1763 | =item B<[rm*] [rm:*]> |
|
|
1764 | |
|
|
1765 | remove all menuBars |
|
|
1766 | |
|
|
1767 | =item B<[swap]> |
|
|
1768 | |
|
|
1769 | swap the top two menuBars |
|
|
1770 | |
|
|
1771 | =item B<[prev]> |
|
|
1772 | |
|
|
1773 | access the previous menuBar |
|
|
1774 | |
|
|
1775 | =item B<[next]> |
|
|
1776 | |
|
|
1777 | access the next menuBar |
|
|
1778 | |
|
|
1779 | =item B<[show]> |
|
|
1780 | |
|
|
1781 | Enable display of the menuBar |
|
|
1782 | |
|
|
1783 | =item B<[hide]> |
|
|
1784 | |
|
|
1785 | Disable display of the menuBar |
|
|
1786 | |
|
|
1787 | =item B<< [pixmap:+I<name>] >> |
|
|
1788 | |
|
|
1789 | =item B<< [pixmap:+I<name>;I<scaling>] >> |
|
|
1790 | |
|
|
1791 | (set the background pixmap globally |
|
|
1792 | |
|
|
1793 | B<< A Future implementation I<may> make this local to the menubar >>) |
|
|
1794 | |
|
|
1795 | =item B<< [:+I<command>:] >> |
|
|
1796 | |
|
|
1797 | ignore the menu readonly status and issue a I<command> to or a menu or |
|
|
1798 | menuitem or change the ; a useful shortcut for setting the quick arrows |
|
|
1799 | from a menuBar. |
|
|
1800 | |
|
|
1801 | =back |
|
|
1802 | |
|
|
1803 | X<menuBarAdd> |
|
|
1804 | |
|
|
1805 | =head2 Adding and accessing menus |
|
|
1806 | |
|
|
1807 | The following commands may also be B<+> prefixed. |
|
|
1808 | |
|
|
1809 | =over 4 |
|
|
1810 | |
|
|
1811 | =item B</+> |
|
|
1812 | |
|
|
1813 | access menuBar top level |
|
|
1814 | |
|
|
1815 | =item B<./+> |
|
|
1816 | |
|
|
1817 | access current menu level |
|
|
1818 | |
|
|
1819 | =item B<../+> |
|
|
1820 | |
|
|
1821 | access parent menu (1 level up) |
|
|
1822 | |
|
|
1823 | =item B<../../> |
|
|
1824 | |
|
|
1825 | access parent menu (multiple levels up) |
|
|
1826 | |
|
|
1827 | =item B<< I</path/>menu >> |
|
|
1828 | |
|
|
1829 | add/access menu |
|
|
1830 | |
|
|
1831 | =item B<< I</path/>menu/* >> |
|
|
1832 | |
|
|
1833 | add/access menu and clear it if it exists |
|
|
1834 | |
|
|
1835 | =item B<< I</path/>{-} >> |
|
|
1836 | |
|
|
1837 | add separator |
|
|
1838 | |
|
|
1839 | =item B<< I</path/>{item} >> |
|
|
1840 | |
|
|
1841 | add B<item> as a label |
|
|
1842 | |
|
|
1843 | =item B<< I</path/>{item} action >> |
|
|
1844 | |
|
|
1845 | add/alter I<menuitem> with an associated I<action> |
|
|
1846 | |
|
|
1847 | =item B<< I</path/>{item}{right-text} >> |
|
|
1848 | |
|
|
1849 | add/alter I<menuitem> with B<right-text> as the right-justified text |
|
|
1850 | and as the associated I<action> |
|
|
1851 | |
|
|
1852 | =item B<< I</path/>{item}{rtext} action >> |
|
|
1853 | |
|
|
1854 | add/alter I<menuitem> with an associated I<action> and with B<rtext> as |
|
|
1855 | the right-justified text. |
|
|
1856 | |
|
|
1857 | =back |
|
|
1858 | |
|
|
1859 | =over 4 |
|
|
1860 | |
|
|
1861 | =item Special characters in I<action> must be backslash-escaped: |
|
|
1862 | |
|
|
1863 | B<\a \b \E \e \n \r \t \octal> |
|
|
1864 | |
|
|
1865 | =item or in control-character notation: |
|
|
1866 | |
|
|
1867 | B<^@, ^A .. ^Z .. ^_, ^?> |
|
|
1868 | |
|
|
1869 | =back |
|
|
1870 | |
|
|
1871 | To send a string starting with a B<NUL> (B<^@>) character to the |
|
|
1872 | program, start I<action> with a pair of B<NUL> characters (B<^@^@>), |
|
|
1873 | the first of which will be stripped off and the balance directed to the |
|
|
1874 | program. Otherwise if I<action> begins with B<NUL> followed by |
|
|
1875 | non-+B<NUL> characters, the leading B<NUL> is stripped off and the |
|
|
1876 | balance is sent back to rxvt. |
|
|
1877 | |
|
|
1878 | As a convenience for the many Emacs-type editors, I<action> may start |
|
|
1879 | with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be |
|
|
1880 | appended if missed from B<M-x> commands. |
|
|
1881 | |
|
|
1882 | As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or |
|
|
1883 | quick arrow), a B<BEL> (B<^G>) will be appended if needed. |
|
|
1884 | |
|
|
1885 | =over 4 |
|
|
1886 | |
|
|
1887 | =item For example, |
|
|
1888 | |
|
|
1889 | B<M-xapropos> is equivalent to B<\Exapropos\r> |
|
|
1890 | |
|
|
1891 | =item and |
|
|
1892 | |
|
|
1893 | B<\E]703;mona;100> is equivalent to B<\E]703;mona;100\a> |
|
|
1894 | |
|
|
1895 | =back |
|
|
1896 | |
|
|
1897 | The option B<< {I<right-rtext>} >> will be right-justified. In the |
|
|
1898 | absence of a specified action, this text will be used as the I<action> |
|
|
1899 | as well. |
|
|
1900 | |
|
|
1901 | =over 4 |
|
|
1902 | |
|
|
1903 | =item For example, |
|
|
1904 | |
|
|
1905 | B</File/{Open}{^X^F}> is equivalent to B</File/{Open}{^X^F} ^X^F> |
|
|
1906 | |
|
|
1907 | =back |
|
|
1908 | |
|
|
1909 | The left label I<is> necessary, since it's used for matching, but |
|
|
1910 | implicitly hiding the left label (by using same name for both left and |
|
|
1911 | right labels), or explicitly hiding the left label (by preceeding it |
|
|
1912 | with a dot), makes it possible to have right-justified text only. |
|
|
1913 | |
|
|
1914 | =over 4 |
|
|
1915 | |
|
|
1916 | =item For example, |
|
|
1917 | |
|
|
1918 | B</File/{Open}{Open} Open-File-Action> |
|
|
1919 | |
|
|
1920 | =item or hiding it |
|
|
1921 | |
|
|
1922 | B</File/{.anylabel}{Open} Open-File-Action> |
|
|
1923 | |
|
|
1924 | =back |
|
|
1925 | |
|
|
1926 | X<menuBarRemove> |
|
|
1927 | |
|
|
1928 | =head2 Removing menus |
|
|
1929 | |
|
|
1930 | =over 4 |
|
|
1931 | |
|
|
1932 | =item B<< -/*+ >> |
|
|
1933 | |
|
|
1934 | remove all menus from the menuBar, the same as B<[clear]> |
|
|
1935 | |
|
|
1936 | =item B<< -+I</path>menu+ >> |
|
|
1937 | |
|
|
1938 | remove menu |
|
|
1939 | |
|
|
1940 | =item B<< -+I</path>{item}+ >> |
|
|
1941 | |
|
|
1942 | remove item |
|
|
1943 | |
|
|
1944 | =item B<< -+I</path>{-} >> |
|
|
1945 | |
|
|
1946 | remove separator) |
|
|
1947 | |
|
|
1948 | =item B<-/path/menu/*> |
|
|
1949 | |
|
|
1950 | remove all items, separators and submenus from menu |
|
|
1951 | |
|
|
1952 | =back |
|
|
1953 | |
|
|
1954 | X<menuBarArrows> |
|
|
1955 | |
|
|
1956 | =head2 Quick Arrows |
|
|
1957 | |
|
|
1958 | The menus also provide a hook for I<quick arrows> to provide easier |
|
|
1959 | user access. If nothing has been explicitly set, the default is to |
|
|
1960 | emulate the curror keys. The syntax permits each arrow to be altered |
|
|
1961 | individually or all four at once without re-entering their common |
|
|
1962 | beginning/end text. For example, to explicitly associate cursor actions |
|
|
1963 | with the arrows, any of the following forms could be used: |
|
|
1964 | |
|
|
1965 | =over 4 |
|
|
1966 | |
|
|
1967 | =item B<< <r>+I<Right> >> |
|
|
1968 | |
|
|
1969 | =item B<< <l>+I<Left> >> |
|
|
1970 | |
|
|
1971 | =item B<< <u>+I<Up> >> |
|
|
1972 | |
|
|
1973 | =item B<< <d>+I<Down> >> |
|
|
1974 | |
|
|
1975 | Define actions for the respective arrow buttons |
|
|
1976 | |
|
|
1977 | =item B<< <b>+I<Begin> >> |
|
|
1978 | |
|
|
1979 | =item B<< <e>+I<End> >> |
|
|
1980 | |
|
|
1981 | Define common beginning/end parts for I<quick arrows> which used in |
|
|
1982 | conjunction with the above <r> <l> <u> <d> constructs |
|
|
1983 | |
|
|
1984 | =back |
|
|
1985 | |
|
|
1986 | =over 4 |
|
|
1987 | |
|
|
1988 | =item For example, define arrows individually, |
|
|
1989 | |
|
|
1990 | <u>\E[A |
|
|
1991 | |
|
|
1992 | <d>\E[B |
|
|
1993 | |
|
|
1994 | <r>\E[C |
|
|
1995 | |
|
|
1996 | <l>\E[D |
|
|
1997 | |
|
|
1998 | =item or all at once |
|
|
1999 | |
|
|
2000 | <u>\E[AZ<><d>\E[BZ<><r>\E[CZ<><l>\E[D |
|
|
2001 | |
|
|
2002 | =item or more compactly (factoring out common parts) |
|
|
2003 | |
|
|
2004 | <b>\E[<u>AZ<><d>BZ<><r>CZ<><l>D |
|
|
2005 | |
|
|
2006 | =back |
|
|
2007 | |
|
|
2008 | X<menuBarSummary> |
|
|
2009 | |
|
|
2010 | =head2 Command Summary |
|
|
2011 | |
|
|
2012 | A short summary of the most I<common> commands: |
|
|
2013 | |
|
|
2014 | =over 4 |
|
|
2015 | |
|
|
2016 | =item [menu:name] |
|
|
2017 | |
|
|
2018 | use an existing named menuBar or start a new one |
|
|
2019 | |
|
|
2020 | =item [menu] |
|
|
2021 | |
|
|
2022 | use the current menuBar |
|
|
2023 | |
|
|
2024 | =item [title:string] |
|
|
2025 | |
|
|
2026 | set menuBar title |
|
|
2027 | |
|
|
2028 | =item [done] |
|
|
2029 | |
|
|
2030 | set menu access to readonly and, if reading from a file, signal EOF |
|
|
2031 | |
|
|
2032 | =item [done:name] |
|
|
2033 | |
|
|
2034 | if reading from a file using [read:file;name] signal EOF |
|
|
2035 | |
|
|
2036 | =item [rm:name] |
|
|
2037 | |
|
|
2038 | remove named menuBar(s) |
|
|
2039 | |
|
|
2040 | =item [rm] [rm:] |
|
|
2041 | |
|
|
2042 | remove current menuBar |
|
|
2043 | |
|
|
2044 | =item [rm*] [rm:*] |
|
|
2045 | |
|
|
2046 | remove all menuBar(s) |
|
|
2047 | |
|
|
2048 | =item [swap] |
|
|
2049 | |
|
|
2050 | swap top two menuBars |
|
|
2051 | |
|
|
2052 | =item [prev] |
|
|
2053 | |
|
|
2054 | access the previous menuBar |
|
|
2055 | |
|
|
2056 | =item [next] |
|
|
2057 | |
|
|
2058 | access the next menuBar |
|
|
2059 | |
|
|
2060 | =item [show] |
|
|
2061 | |
|
|
2062 | map menuBar |
|
|
2063 | |
|
|
2064 | =item [hide] |
|
|
2065 | |
|
|
2066 | unmap menuBar |
|
|
2067 | |
|
|
2068 | =item [pixmap;file] |
|
|
2069 | |
|
|
2070 | =item [pixmap;file;scaling] |
|
|
2071 | |
|
|
2072 | set a background pixmap |
|
|
2073 | |
|
|
2074 | =item [read:file] |
|
|
2075 | |
|
|
2076 | =item [read:file;name] |
|
|
2077 | |
|
|
2078 | read in a menu from a file |
|
|
2079 | |
|
|
2080 | =item [dump] |
|
|
2081 | |
|
|
2082 | dump out all menuBars to /tmp/rxvt-PID |
|
|
2083 | |
|
|
2084 | =item / |
|
|
2085 | |
|
|
2086 | access menuBar top level |
|
|
2087 | |
|
|
2088 | =item ./ |
|
|
2089 | |
|
|
2090 | =item ../ |
|
|
2091 | |
|
|
2092 | =item ../../ |
|
|
2093 | |
|
|
2094 | access current or parent menu level |
|
|
2095 | |
|
|
2096 | =item /path/menu |
|
|
2097 | |
|
|
2098 | add/access menu |
|
|
2099 | |
|
|
2100 | =item /path/{-} |
|
|
2101 | |
|
|
2102 | add separator |
|
|
2103 | |
|
|
2104 | =item /path/{item}{rtext} action |
|
|
2105 | |
|
|
2106 | add/alter menu item |
|
|
2107 | |
|
|
2108 | =item -/* |
|
|
2109 | |
|
|
2110 | remove all menus from the menuBar |
|
|
2111 | |
|
|
2112 | =item -/path/menu |
|
|
2113 | |
|
|
2114 | remove menu items, separators and submenus from menu |
|
|
2115 | |
|
|
2116 | =item -/path/menu |
|
|
2117 | |
|
|
2118 | remove menu |
|
|
2119 | |
|
|
2120 | =item -/path/{item} |
|
|
2121 | |
|
|
2122 | remove item |
|
|
2123 | |
|
|
2124 | =item -/path/{-} |
|
|
2125 | |
|
|
2126 | remove separator |
|
|
2127 | |
|
|
2128 | =item <b>Begin<r>Right<l>Left<u>Up<d>Down<e>End |
|
|
2129 | |
|
|
2130 | menu quick arrows |
|
|
2131 | |
|
|
2132 | =back |
|
|
2133 | X<XPM> |
1783 | X<XPM> |
2134 | |
1784 | |
2135 | =head1 XPM |
1785 | =head1 XPM |
2136 | |
1786 | |
2137 | For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value |
1787 | For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value |
… | |
… | |
2384 | alternative input methods (e.g. kinput2) and will also correctly |
2034 | alternative input methods (e.g. kinput2) and will also correctly |
2385 | set up the input for people using dead keys or compose keys. |
2035 | set up the input for people using dead keys or compose keys. |
2386 | |
2036 | |
2387 | =item --enable-unicode3 (default: off) |
2037 | =item --enable-unicode3 (default: off) |
2388 | |
2038 | |
|
|
2039 | Recommended to stay off unless you really need non-BMP characters. |
|
|
2040 | |
2389 | Enable direct support for displaying unicode codepoints above |
2041 | Enable direct support for displaying unicode codepoints above |
2390 | 65535 (the basic multilingual page). This increases storage |
2042 | 65535 (the basic multilingual page). This increases storage |
2391 | requirements per character from 2 to 4 bytes. X11 fonts do not yet |
2043 | requirements per character from 2 to 4 bytes. X11 fonts do not yet |
2392 | support these extra characters, but Xft does. |
2044 | support these extra characters, but Xft does. |
2393 | |
2045 | |
… | |
… | |
2403 | composite characters. This is required for proper viewing of text |
2055 | composite characters. This is required for proper viewing of text |
2404 | where accents are encoded as seperate unicode characters. This is |
2056 | where accents are encoded as seperate unicode characters. This is |
2405 | done by using precomposited characters when available or creating |
2057 | done by using precomposited characters when available or creating |
2406 | new pseudo-characters when no precomposed form exists. |
2058 | new pseudo-characters when no precomposed form exists. |
2407 | |
2059 | |
2408 | Without --enable-unicode3, the number of additional precomposed characters |
2060 | Without --enable-unicode3, the number of additional precomposed |
2409 | is rather limited (2048, if this is full, rxvt-unicode will use the |
2061 | characters is somewhat limited (the 6400 private use characters will be |
2410 | private use area, extending the number of combinations to 8448). With |
|
|
2411 | --enable-unicode3, no practical limit exists. |
2062 | (ab-)used). With --enable-unicode3, no practical limit exists. |
2412 | |
2063 | |
2413 | This option will also enable storage (but not display) of characters |
2064 | This option will also enable storage (but not display) of characters |
2414 | beyond plane 0 (>65535) when --enable-unicode3 was not specified. |
2065 | beyond plane 0 (>65535) when --enable-unicode3 was not specified. |
2415 | |
2066 | |
2416 | The combining table also contains entries for arabic presentation forms, |
2067 | The combining table also contains entries for arabic presentation forms, |
2417 | but these are not currently used. Bug me if you want these to be used (and |
2068 | but these are not currently used. Bug me if you want these to be used (and |
2418 | tell me how these are to be used...). |
2069 | tell me how these are to be used...). |
2419 | |
2070 | |
2420 | =item --enable-fallback(=CLASS) (default: Rxvt) |
2071 | =item --enable-fallback(=CLASS) (default: Rxvt) |
2421 | |
2072 | |
2422 | When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback. |
2073 | When reading resource settings, also read settings for class CLASS. To |
|
|
2074 | disable resource fallback use --disable-fallback. |
2423 | |
2075 | |
2424 | =item --with-res-name=NAME (default: urxvt) |
2076 | =item --with-res-name=NAME (default: urxvt) |
2425 | |
2077 | |
2426 | Use the given name as default application name when |
2078 | Use the given name as default application name when |
2427 | reading resources. Specify --with-res-name=rxvt to replace rxvt. |
2079 | reading resources. Specify --with-res-name=rxvt to replace rxvt. |
… | |
… | |
2464 | |
2116 | |
2465 | =item --enable-tinting (default: on) |
2117 | =item --enable-tinting (default: on) |
2466 | |
2118 | |
2467 | Add support for tinting of transparent backgrounds (requires C<--enable-transparency>). |
2119 | Add support for tinting of transparent backgrounds (requires C<--enable-transparency>). |
2468 | |
2120 | |
2469 | =item --enable-menubar (default: off) [DEPRECATED] |
|
|
2470 | |
|
|
2471 | Add support for our menu bar system (this interacts badly with dynamic |
|
|
2472 | locale switching currently). This option is DEPRECATED and will be removed |
|
|
2473 | in the future. |
|
|
2474 | |
|
|
2475 | =item --enable-rxvt-scroll (default: on) |
2121 | =item --enable-rxvt-scroll (default: on) |
2476 | |
2122 | |
2477 | Add support for the original rxvt scrollbar. |
2123 | Add support for the original rxvt scrollbar. |
2478 | |
2124 | |
2479 | =item --enable-next-scroll (default: on) |
2125 | =item --enable-next-scroll (default: on) |
… | |
… | |
2488 | |
2134 | |
2489 | Add support for a very unobtrusive, plain-looking scrollbar that |
2135 | Add support for a very unobtrusive, plain-looking scrollbar that |
2490 | is the favourite of the rxvt-unicode author, having used it for |
2136 | is the favourite of the rxvt-unicode author, having used it for |
2491 | many years. |
2137 | many years. |
2492 | |
2138 | |
2493 | =item --enable-half-shadow (default: off) |
|
|
2494 | |
|
|
2495 | Make shadows on the scrollbar only half the normal width & height. |
|
|
2496 | only applicable to rxvt scrollbars. |
|
|
2497 | |
|
|
2498 | =item --enable-ttygid (default: off) |
2139 | =item --enable-ttygid (default: off) |
2499 | |
2140 | |
2500 | Change tty device setting to group "tty" - only use this if |
2141 | Change tty device setting to group "tty" - only use this if |
2501 | your system uses this type of security. |
2142 | your system uses this type of security. |
2502 | |
2143 | |
… | |
… | |
2510 | do it. |
2151 | do it. |
2511 | |
2152 | |
2512 | =item --disable-resources |
2153 | =item --disable-resources |
2513 | |
2154 | |
2514 | Removes any support for resource checking. |
2155 | Removes any support for resource checking. |
2515 | |
|
|
2516 | =item --enable-xgetdefault |
|
|
2517 | |
|
|
2518 | Make resources checking via XGetDefault() instead of our small |
|
|
2519 | version which only checks ~/.Xdefaults, or if that doesn't exist then |
|
|
2520 | ~/.Xresources. |
|
|
2521 | |
|
|
2522 | Please note that nowadays, things like XIM will automatically pull in and |
|
|
2523 | use the full X resource manager, so the overhead of using it might be very |
|
|
2524 | small, if nonexistant. |
|
|
2525 | |
|
|
2526 | =item --enable-strings (default: off) |
|
|
2527 | |
|
|
2528 | Add support for our possibly faster memset() function and other |
|
|
2529 | various routines, overriding your system's versions which may |
|
|
2530 | have been hand-crafted in assembly or may require extra libraries |
|
|
2531 | to link in. (this breaks ANSI-C rules and has problems on many |
|
|
2532 | GNU/Linux systems). |
|
|
2533 | |
2156 | |
2534 | =item --disable-swapscreen |
2157 | =item --disable-swapscreen |
2535 | |
2158 | |
2536 | Remove support for secondary/swap screen. |
2159 | Remove support for secondary/swap screen. |
2537 | |
2160 | |
… | |
… | |
2546 | |
2169 | |
2547 | MWM-hints |
2170 | MWM-hints |
2548 | EWMH-hints (pid, utf8 names) and protocols (ping) |
2171 | EWMH-hints (pid, utf8 names) and protocols (ping) |
2549 | seperate underline colour (-underlineColor) |
2172 | seperate underline colour (-underlineColor) |
2550 | settable border widths and borderless switch (-w, -b, -bl) |
2173 | settable border widths and borderless switch (-w, -b, -bl) |
|
|
2174 | visual depth selection (-depth) |
2551 | settable extra linespacing /-lsp) |
2175 | settable extra linespacing /-lsp) |
2552 | iso-14755-2 and -3, and visual feedback |
2176 | iso-14755-2 and -3, and visual feedback |
2553 | backindex and forwardindex escape sequence |
|
|
2554 | window op and some xterm/OSC escape sequences |
|
|
2555 | tripleclickwords (-tcw) |
2177 | tripleclickwords (-tcw) |
2556 | settable insecure mode (-insecure) |
2178 | settable insecure mode (-insecure) |
2557 | keysym remapping support |
2179 | keysym remapping support |
2558 | cursor blinking and underline cursor (-cb, -uc) |
2180 | cursor blinking and underline cursor (-cb, -uc) |
2559 | XEmbed support (-embed) |
2181 | XEmbed support (-embed) |
2560 | user-pty (-pty-fd) |
2182 | user-pty (-pty-fd) |
2561 | hold on exit (-hold) |
2183 | hold on exit (-hold) |
2562 | skip builtin block graphics (-sbg) |
2184 | skip builtin block graphics (-sbg) |
|
|
2185 | |
|
|
2186 | It also enabled some non-essential features otherwise disabled, such as: |
|
|
2187 | |
|
|
2188 | some round-trip time optimisations |
|
|
2189 | nearest color allocation on pseudocolor screens |
|
|
2190 | UTF8_STRING supporr for selection |
2563 | sgr modes 90..97 and 100..107 |
2191 | sgr modes 90..97 and 100..107 |
|
|
2192 | backindex and forwardindex escape sequences |
|
|
2193 | view change/zero scorllback esacpe sequences |
|
|
2194 | locale switching escape sequence |
|
|
2195 | window op and some xterm/OSC escape sequences |
|
|
2196 | rectangular selections |
|
|
2197 | trailing space removal for selections |
|
|
2198 | verbose X error handling |
2564 | |
2199 | |
2565 | =item --enable-iso14755 (default: on) |
2200 | =item --enable-iso14755 (default: on) |
2566 | |
2201 | |
2567 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2202 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2568 | F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by |
2203 | F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by |
… | |
… | |
2611 | |
2246 | |
2612 | =item --enable-pointer-blank (default: on) |
2247 | =item --enable-pointer-blank (default: on) |
2613 | |
2248 | |
2614 | Add support to have the pointer disappear when typing or inactive. |
2249 | Add support to have the pointer disappear when typing or inactive. |
2615 | |
2250 | |
2616 | =item --enable-perl (default: off) |
2251 | =item --enable-perl (default: on) |
2617 | |
2252 | |
2618 | Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)> |
2253 | Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)> |
2619 | manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files |
2254 | manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the files |
2620 | in F<src/perl-ext/> for the extensions that are installed by default. The |
2255 | in F<src/perl-ext/> for the extensions that are installed by default. The |
2621 | perl interpreter that is used can be specified via the C<PERL> environment |
2256 | perl interpreter that is used can be specified via the C<PERL> environment |