… | |
… | |
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/rxvt-unicode/doc/rxvt.7.html>. |
24 | |
23 | |
25 | =head1 FREQUENTLY ASKED QUESTIONS |
24 | =head1 RXVT-UNICODE/URXVT FREQUENTLY ASKED QUESTIONS |
26 | |
25 | |
27 | =over 4 |
|
|
28 | |
26 | |
|
|
27 | =head2 Meta, Features & Commandline Issues |
|
|
28 | |
|
|
29 | =head3 My question isn't answered here, can I ask a human? |
|
|
30 | |
|
|
31 | Before sending me mail, you could go to IRC: C<irc.freenode.net>, |
|
|
32 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
|
|
33 | interested in learning about new and exciting problems (but not FAQs :). |
|
|
34 | |
|
|
35 | =head3 Does it support tabs, can I have a tabbed rxvt-unicode? |
|
|
36 | |
|
|
37 | Beginning with version 7.3, there is a perl extension that implements a |
|
|
38 | simple tabbed terminal. It is installed by default, so any of these should |
|
|
39 | give you tabs: |
|
|
40 | |
|
|
41 | @@URXVT_NAME@@ -pe tabbed |
|
|
42 | |
|
|
43 | URxvt.perl-ext-common: default,tabbed |
|
|
44 | |
|
|
45 | It will also work fine with tabbing functionality of many window managers |
|
|
46 | or similar tabbing programs, and its embedding-features allow it to be |
|
|
47 | embedded into other programs, as witnessed by F<doc/rxvt-tabbed> or |
|
|
48 | the upcoming C<Gtk2::URxvt> perl module, which features a tabbed urxvt |
|
|
49 | (murxvt) terminal as an example embedding application. |
|
|
50 | |
|
|
51 | =head3 How do I know which rxvt-unicode version I'm using? |
|
|
52 | |
|
|
53 | The version number is displayed with the usage (-h). Also the escape |
|
|
54 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
|
|
55 | using the @@URXVT_NAME@@c client, the version displayed is that of the |
|
|
56 | daemon. |
|
|
57 | |
|
|
58 | =head3 Rxvt-unicode uses gobs of memory, how can I reduce that? |
|
|
59 | |
|
|
60 | Rxvt-unicode tries to obey the rule of not charging you for something you |
|
|
61 | don't use. One thing you should try is to configure out all settings that |
|
|
62 | you don't need, for example, Xft support is a resource hog by design, |
|
|
63 | when used. Compiling it out ensures that no Xft font will be loaded |
|
|
64 | accidentally when rxvt-unicode tries to find a font for your characters. |
|
|
65 | |
|
|
66 | Also, many people (me included) like large windows and even larger |
|
|
67 | scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use |
|
|
68 | 6 bytes per screen cell. For a 160x?? window this amounts to almost a |
|
|
69 | kilobyte per line. A scrollback buffer of 10000 lines will then (if full) |
|
|
70 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
|
|
71 | rxvt-unicode then uses 8 bytes per screen cell. |
|
|
72 | |
|
|
73 | =head3 How can I start @@URXVT_NAME@@d in a race-free way? |
|
|
74 | |
|
|
75 | Try C<@@URXVT_NAME@@d -f -o>, which tells @@URXVT_NAME@@d to open the |
|
|
76 | display, create the listening socket and then fork. |
|
|
77 | |
|
|
78 | =head3 How can I start @@URXVT_NAME@@d automatically when I run @@URXVT_NAME@@c? |
|
|
79 | |
|
|
80 | If you want to start @@URXVT_NAME@@d automatically whenever you run |
|
|
81 | @@URXVT_NAME@@c and the daemon isn't running yet, use this script: |
|
|
82 | |
|
|
83 | #!/bin/sh |
|
|
84 | @@URXVT_NAME@@c "$@" |
|
|
85 | if [ $? -eq 2 ]; then |
|
|
86 | @@URXVT_NAME@@d -q -o -f |
|
|
87 | @@URXVT_NAME@@c "$@" |
|
|
88 | fi |
|
|
89 | |
|
|
90 | This tries to create a new terminal, and if fails with exit status 2, |
|
|
91 | meaning it couldn't connect to the daemon, it will start the daemon and |
|
|
92 | re-run the command. Subsequent invocations of the script will re-use the |
|
|
93 | existing daemon. |
|
|
94 | |
|
|
95 | =head3 How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc. |
|
|
96 | |
|
|
97 | The original rxvt and rxvt-unicode always export the variable "COLORTERM", |
|
|
98 | so you can check and see if that is set. Note that several programs, JED, |
|
|
99 | slrn, Midnight Commander automatically check this variable to decide |
|
|
100 | whether or not to use color. |
|
|
101 | |
|
|
102 | =head3 How do I set the correct, full IP address for the DISPLAY variable? |
|
|
103 | |
|
|
104 | If you've compiled rxvt-unicode with DISPLAY_IS_IP and have enabled |
|
|
105 | insecure mode then it is possible to use the following shell script |
|
|
106 | snippets to correctly set the display. If your version of rxvt-unicode |
|
|
107 | wasn't also compiled with ESCZ_ANSWER (as assumed in these snippets) then |
|
|
108 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
|
|
109 | regular xterm. |
|
|
110 | |
|
|
111 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
|
|
112 | snippets: |
|
|
113 | |
|
|
114 | # Bourne/Korn/POSIX family of shells: |
|
|
115 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
|
|
116 | if [ ${TERM:-foo} = xterm ]; then |
|
|
117 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
|
|
118 | echo -n '^[Z' |
|
|
119 | read term_id |
|
|
120 | stty icanon echo |
|
|
121 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
|
|
122 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
|
|
123 | read DISPLAY # set it in our local shell |
|
|
124 | fi |
|
|
125 | fi |
|
|
126 | |
|
|
127 | =head3 How do I compile the manual pages on my own? |
|
|
128 | |
|
|
129 | You need to have a recent version of perl installed as F</usr/bin/perl>, |
|
|
130 | one that comes with F<pod2man>, F<pod2text> and F<pod2xhtml> (from |
|
|
131 | F<Pod::Xhtml>). Then go to the doc subdirectory and enter C<make alldoc>. |
|
|
132 | |
29 | =item Isn't rxvt supposed to be small? Don't all those features bloat? |
133 | =head3 Isn't rxvt-unicode supposed to be small? Don't all those features bloat? |
30 | |
134 | |
31 | I often get asked about this, and I think, no, they didn't cause extra |
135 | 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 |
136 | 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 |
137 | 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 |
138 | compiled in), but it actually uses less memory (RSS) after startup. Even |
… | |
… | |
38 | |
142 | |
39 | text data bss drs rss filename |
143 | text data bss drs rss filename |
40 | 98398 1664 24 15695 1824 rxvt --disable-everything |
144 | 98398 1664 24 15695 1824 rxvt --disable-everything |
41 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
145 | 188985 9048 66616 18222 1788 urxvt --disable-everything |
42 | |
146 | |
43 | When you C<--enable-everything> (which _is_ unfair, as this involves xft |
147 | When you C<--enable-everything> (which I<is> unfair, as this involves xft |
44 | and full locale/XIM support which are quite bloaty inside libX11 and my |
148 | and full locale/XIM support which are quite bloaty inside libX11 and my |
45 | libc), the two diverge, but not unreasnobaly so. |
149 | libc), the two diverge, but not unreasonably so. |
46 | |
150 | |
47 | text data bss drs rss filename |
151 | text data bss drs rss filename |
48 | 163431 2152 24 20123 2060 rxvt --enable-everything |
152 | 163431 2152 24 20123 2060 rxvt --enable-everything |
49 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
153 | 1035683 49680 66648 29096 3680 urxvt --enable-everything |
50 | |
154 | |
… | |
… | |
66 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
170 | (21152k + extra 4204k in separate processes) or konsole (22200k + extra |
67 | 43180k in daemons that stay around after exit, plus half a minute of |
171 | 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 |
172 | startup time, including the hundreds of warnings it spits out), it fares |
69 | extremely well *g*. |
173 | extremely well *g*. |
70 | |
174 | |
71 | =item Why C++, isn't that unportable/bloated/uncool? |
175 | =head3 Why C++, isn't that unportable/bloated/uncool? |
72 | |
176 | |
73 | Is this a question? :) It comes up very often. The simple answer is: I had |
177 | 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 |
178 | 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 |
179 | of the time and effort (which is a scarce resource for me). Put even |
76 | shorter: It simply wouldn't exist without C++. |
180 | shorter: It simply wouldn't exist without C++. |
… | |
… | |
93 | |
197 | |
94 | And here is rxvt-unicode: |
198 | And here is rxvt-unicode: |
95 | |
199 | |
96 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
200 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
97 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
201 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
98 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
202 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
99 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
203 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
100 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
204 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
101 | |
205 | |
102 | No large bloated libraries (of course, none were linked in statically), |
206 | No large bloated libraries (of course, none were linked in statically), |
103 | except maybe libX11 :) |
207 | except maybe libX11 :) |
104 | |
208 | |
105 | =item Does it support tabs, can I have a tabbed rxvt-unicode? |
|
|
106 | |
209 | |
107 | rxvt-unicode does not directly support tabs. It will work fine with |
210 | =head2 Rendering, Font & Look and Feel Issues |
108 | tabbing functionality of many window managers or similar tabbing programs, |
|
|
109 | and its embedding-features allow it to be embedded into other programs, |
|
|
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 | |
211 | |
114 | =item How do I know which rxvt-unicode version I'm using? |
212 | =head3 I can't get transparency working, what am I doing wrong? |
115 | |
213 | |
116 | The version number is displayed with the usage (-h). Also the escape |
214 | First of all, please address all transparency related issues to Sasha Vasko at |
117 | sequence C<ESC [ 8 n> sets the window title to the version number. When |
215 | sasha@aftercode.net and do not bug the author about it. Also, if you can't |
118 | using the @@RXVT_NAME@@c client, the version displayed is that of the |
216 | get it working consider it a rite of passage: ... and you failed. |
119 | daemon. |
|
|
120 | |
217 | |
121 | =item I am using Debian GNU/Linux and have a problem... |
218 | Here are four ways to get transparency. B<Do> read the manpage and option |
|
|
219 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
122 | |
220 | |
123 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
221 | 1. Use transparent mode: |
124 | patches that considerably change the behaviour of rxvt-unicode. Before |
|
|
125 | reporting a bug to the original rxvt-unicode author please download and |
|
|
126 | install the genuine version (L<http://software.schmorp.de#rxvt-unicode>) |
|
|
127 | and try to reproduce the problem. If you cannot, chances are that the |
|
|
128 | problems are specific to Debian GNU/Linux, in which case it should be |
|
|
129 | reported via the Debian Bug Tracking System (use C<reportbug> to report |
|
|
130 | the bug). |
|
|
131 | |
222 | |
132 | For other problems that also affect the Debian package, you can and |
223 | Esetroot wallpaper.jpg |
133 | probably should use the Debian BTS, too, because, after all, it's also a |
224 | @@URXVT_NAME@@ -tr -tint red -sh 40 |
134 | bug in the Debian version and it serves as a reminder for other users that |
|
|
135 | might encounter the same issue. |
|
|
136 | |
225 | |
137 | =item I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
226 | That works. If you think it doesn't, you lack transparency and tinting |
|
|
227 | support, or you are unable to read. |
138 | |
228 | |
139 | You should build one binary with the default options. F<configure> |
229 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
140 | now enables most useful options, and the trend goes to making them |
230 | to use effects other than tinting and shading: Just shade/tint/whatever |
141 | runtime-switchable, too, so there is usually no drawback to enbaling them, |
231 | your picture with gimp or any other tool: |
142 | except higher disk and possibly memory usage. The perl interpreter should |
|
|
143 | be enabled, as important functionality (menus, selection, likely more in |
|
|
144 | the future) depends on it. |
|
|
145 | |
232 | |
146 | You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources |
233 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
147 | system-wide (except maybe with C<defaults>). This will result in useful |
234 | @@URXVT_NAME@@ -pixmap "background.jpg;:root" |
148 | behaviour. If your distribution aims at low memory, add an empty |
|
|
149 | C<perl-ext-common> resource to the app-defaults file. This will keep the |
|
|
150 | perl interpreter disabled until the user enables it. |
|
|
151 | |
235 | |
152 | If you can/want build more binaries, I recommend building a minimal |
236 | That works. If you think it doesn't, you lack AfterImage support, or you |
153 | one with C<--disable-everything> (very useful) and a maximal one with |
237 | are unable to read. |
154 | 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). |
|
|
156 | |
238 | |
157 | =item I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
239 | 3. Use an ARGB visual: |
158 | |
240 | |
159 | Likely not. While I honestly try to make it secure, and am probably not |
241 | @@URXVT_NAME@@ -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
160 | bad at it, I think it is simply unreasonable to expect all of freetype |
|
|
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 | |
242 | |
166 | Elevated privileges are only required for utmp and pty operations on some |
243 | This requires XFT support, and the support of your X-server. If that |
167 | systems (for example, GNU/Linux doesn't need any extra privileges for |
244 | doesn't work for you, blame Xorg and Keith Packard. ARGB visuals aren't |
168 | ptys, but some need it for utmp support). It is planned to mvoe this into |
245 | there yet, no matter what they claim. Rxvt-Unicode contains the necessary |
169 | a forked handler process, but this is not yet done. |
246 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
|
|
247 | doesn't mean that your WM has the required kludges in place. |
170 | |
248 | |
171 | So, while setuid/setgid operation is supported and not a problem on your |
249 | 4. Use xcompmgr and let it do the job: |
172 | typical single-user-no-other-logins unix desktop, always remember that |
|
|
173 | its an awful lot of code, most of which isn't checked for security issues |
|
|
174 | regularly. |
|
|
175 | |
250 | |
|
|
251 | xprop -frame -f _NET_WM_WINDOW_OPACITY 32c \ |
|
|
252 | -set _NET_WM_WINDOW_OPACITY 0xc0000000 |
|
|
253 | |
|
|
254 | Then click on a window you want to make transparent. Replace C<0xc0000000> |
|
|
255 | by other values to change the degree of opacity. If it doesn't work and |
|
|
256 | your server crashes, you got to keep the pieces. |
|
|
257 | |
|
|
258 | =head3 Why does rxvt-unicode sometimes leave pixel droppings? |
|
|
259 | |
|
|
260 | Most fonts were not designed for terminal use, which means that character |
|
|
261 | size varies a lot. A font that is otherwise fine for terminal use might |
|
|
262 | contain some characters that are simply too wide. Rxvt-unicode will avoid |
|
|
263 | these characters. For characters that are just "a bit" too wide a special |
|
|
264 | "careful" rendering mode is used that redraws adjacent characters. |
|
|
265 | |
|
|
266 | All of this requires that fonts do not lie about character sizes, |
|
|
267 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
|
|
268 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
|
|
269 | ask for the character bounding box, which unfortunately is wrong in these |
|
|
270 | cases). |
|
|
271 | |
|
|
272 | It's not clear (to me at least), whether this is a bug in Xft, freetype, |
|
|
273 | or the respective font. If you encounter this problem you might try using |
|
|
274 | the C<-lsp> option to give the font more height. If that doesn't work, you |
|
|
275 | might be forced to use a different font. |
|
|
276 | |
|
|
277 | All of this is not a problem when using X11 core fonts, as their bounding |
|
|
278 | box data is correct. |
|
|
279 | |
|
|
280 | =head3 How can I keep rxvt-unicode from using reverse video so much? |
|
|
281 | |
|
|
282 | First of all, make sure you are running with the right terminal settings |
|
|
283 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
|
|
284 | make sure you have specified colours for italic and bold, as otherwise |
|
|
285 | rxvt-unicode might use reverse video to simulate the effect: |
|
|
286 | |
|
|
287 | URxvt.colorBD: white |
|
|
288 | URxvt.colorIT: green |
|
|
289 | |
|
|
290 | =head3 Some programs assume totally weird colours (red instead of blue), how can I fix that? |
|
|
291 | |
|
|
292 | For some unexplainable reason, some rare programs assume a very weird |
|
|
293 | colour palette when confronted with a terminal with more than the standard |
|
|
294 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
|
|
295 | these programs not to assume non-ISO colours without very good reasons. |
|
|
296 | |
|
|
297 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
|
|
298 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
|
|
299 | fix colours but keep you from using other rxvt-unicode features. |
|
|
300 | |
|
|
301 | =head3 Can I switch the fonts at runtime? |
|
|
302 | |
|
|
303 | Yes, using an escape sequence. Try something like this, which has the same |
|
|
304 | effect as using the C<-fn> switch, and takes effect immediately: |
|
|
305 | |
|
|
306 | printf '\33]50;%s\007' "9x15bold,xft:Kochi Gothic" |
|
|
307 | |
|
|
308 | This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
309 | japanese font), but you have to switch to chinese temporarily, where |
|
|
310 | japanese fonts would only be in your way. |
|
|
311 | |
|
|
312 | You can think of this as a kind of manual ISO-2022 switching. |
|
|
313 | |
|
|
314 | =head3 Why do italic characters look as if clipped? |
|
|
315 | |
|
|
316 | Many fonts have difficulties with italic characters and hinting. For |
|
|
317 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
|
|
318 | Mono> completely fails in its italic face. A workaround might be to |
|
|
319 | enable freetype autohinting, i.e. like this: |
|
|
320 | |
|
|
321 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
322 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
323 | |
|
|
324 | =head3 Can I speed up Xft rendering somehow? |
|
|
325 | |
|
|
326 | Yes, the most obvious way to speed it up is to avoid Xft entirely, as |
|
|
327 | it is simply slow. If you still want Xft fonts you might try to disable |
|
|
328 | antialiasing (by appending C<:antialias=false>), which saves lots of |
|
|
329 | memory and also speeds up rendering considerably. |
|
|
330 | |
|
|
331 | =head3 Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
|
|
332 | |
|
|
333 | Rxvt-unicode will use whatever you specify as a font. If it needs to |
|
|
334 | fall back to its default font search list it will prefer X11 core |
|
|
335 | fonts, because they are small and fast, and then use Xft fonts. It has |
|
|
336 | antialiasing disabled for most of them, because the author thinks they |
|
|
337 | look best that way. |
|
|
338 | |
|
|
339 | If you want antialiasing, you have to specify the fonts manually. |
|
|
340 | |
|
|
341 | =head3 What's with this bold/blink stuff? |
|
|
342 | |
|
|
343 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
|
|
344 | standard foreground colour. |
|
|
345 | |
|
|
346 | For the standard background colour, blinking will actually make |
|
|
347 | the text blink when compiled with C<--enable-text-blink>. Without |
|
|
348 | C<--enable-text-blink>, the blink attribute will be ignored. |
|
|
349 | |
|
|
350 | On ANSI colours, bold/blink attributes are used to set high-intensity |
|
|
351 | foreground/background colors. |
|
|
352 | |
|
|
353 | color0-7 are the low-intensity colors. |
|
|
354 | |
|
|
355 | color8-15 are the corresponding high-intensity colors. |
|
|
356 | |
|
|
357 | =head3 I don't like the screen colors. How do I change them? |
|
|
358 | |
|
|
359 | You can change the screen colors at run-time using F<~/.Xdefaults> |
|
|
360 | resources (or as long-options). |
|
|
361 | |
|
|
362 | Here are values that are supposed to resemble a VGA screen, |
|
|
363 | including the murky brown that passes for low-intensity yellow: |
|
|
364 | |
|
|
365 | URxvt.color0: #000000 |
|
|
366 | URxvt.color1: #A80000 |
|
|
367 | URxvt.color2: #00A800 |
|
|
368 | URxvt.color3: #A8A800 |
|
|
369 | URxvt.color4: #0000A8 |
|
|
370 | URxvt.color5: #A800A8 |
|
|
371 | URxvt.color6: #00A8A8 |
|
|
372 | URxvt.color7: #A8A8A8 |
|
|
373 | |
|
|
374 | URxvt.color8: #000054 |
|
|
375 | URxvt.color9: #FF0054 |
|
|
376 | URxvt.color10: #00FF54 |
|
|
377 | URxvt.color11: #FFFF54 |
|
|
378 | URxvt.color12: #0000FF |
|
|
379 | URxvt.color13: #FF00FF |
|
|
380 | URxvt.color14: #00FFFF |
|
|
381 | URxvt.color15: #FFFFFF |
|
|
382 | |
|
|
383 | And here is a more complete set of non-standard colors. |
|
|
384 | |
|
|
385 | URxvt.cursorColor: #dc74d1 |
|
|
386 | URxvt.pointerColor: #dc74d1 |
|
|
387 | URxvt.background: #0e0e0e |
|
|
388 | URxvt.foreground: #4ad5e1 |
|
|
389 | URxvt.color0: #000000 |
|
|
390 | URxvt.color8: #8b8f93 |
|
|
391 | URxvt.color1: #dc74d1 |
|
|
392 | URxvt.color9: #dc74d1 |
|
|
393 | URxvt.color2: #0eb8c7 |
|
|
394 | URxvt.color10: #0eb8c7 |
|
|
395 | URxvt.color3: #dfe37e |
|
|
396 | URxvt.color11: #dfe37e |
|
|
397 | URxvt.color5: #9e88f0 |
|
|
398 | URxvt.color13: #9e88f0 |
|
|
399 | URxvt.color6: #73f7ff |
|
|
400 | URxvt.color14: #73f7ff |
|
|
401 | URxvt.color7: #e1dddd |
|
|
402 | URxvt.color15: #e1dddd |
|
|
403 | |
|
|
404 | They have been described (not by me) as "pretty girly". |
|
|
405 | |
|
|
406 | =head3 Why do some characters look so much different than others? |
|
|
407 | |
|
|
408 | See next entry. |
|
|
409 | |
|
|
410 | =head3 How does rxvt-unicode choose fonts? |
|
|
411 | |
|
|
412 | Most fonts do not contain the full range of Unicode, which is |
|
|
413 | fine. Chances are that the font you (or the admin/package maintainer of |
|
|
414 | your system/os) have specified does not cover all the characters you want |
|
|
415 | to display. |
|
|
416 | |
|
|
417 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
|
|
418 | font. Often the result is fine, but sometimes the chosen font looks |
|
|
419 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
|
|
420 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
|
|
421 | intelligence to detect that a specific glyph is wrong: it has to believe |
|
|
422 | the font that the characters it claims to contain indeed look correct. |
|
|
423 | |
|
|
424 | In that case, select a font of your taste and add it to the font list, |
|
|
425 | e.g.: |
|
|
426 | |
|
|
427 | @@URXVT_NAME@@ -fn basefont,font2,font3... |
|
|
428 | |
|
|
429 | When rxvt-unicode sees a character, it will first look at the base |
|
|
430 | font. If the base font does not contain the character, it will go to the |
|
|
431 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
432 | search and use less resources within rxvt-unicode and the X-server. |
|
|
433 | |
|
|
434 | The only limitation is that none of the fonts may be larger than the base |
|
|
435 | font, as the base font defines the terminal character cell size, which |
|
|
436 | must be the same due to the way terminals work. |
|
|
437 | |
|
|
438 | =head3 Why do some chinese characters look so different than others? |
|
|
439 | |
|
|
440 | This is because there is a difference between script and language -- |
|
|
441 | rxvt-unicode does not know which language the text that is output is, |
|
|
442 | as it only knows the unicode character codes. If rxvt-unicode first |
|
|
443 | sees a japanese/chinese character, it might choose a japanese font for |
|
|
444 | display. Subsequent japanese characters will use that font. Now, many |
|
|
445 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
446 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
447 | -- unfortunately at this point, it will still use the japanese font for |
|
|
448 | chinese characters that are also in the japanese font. |
|
|
449 | |
|
|
450 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
451 | list (see the previous question). The key is to view the font list as |
|
|
452 | a preference list: If you expect more japanese, list a japanese font |
|
|
453 | first. If you expect more chinese, put a chinese font first. |
|
|
454 | |
|
|
455 | In the future it might be possible to switch language preferences at |
|
|
456 | runtime (the internal data structure has no problem with using different |
|
|
457 | fonts for the same character at the same time, but no interface for this |
|
|
458 | has been designed yet). |
|
|
459 | |
|
|
460 | Until then, you might get away with switching fonts at runtime (see L<Can |
|
|
461 | I switch the fonts at runtime?> later in this document). |
|
|
462 | |
|
|
463 | =head3 How can I make mplayer display video correctly? |
|
|
464 | |
|
|
465 | We are working on it, in the meantime, as a workaround, use something like: |
|
|
466 | |
|
|
467 | @@URXVT_NAME@@ -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' |
|
|
468 | |
|
|
469 | |
|
|
470 | =head2 Keyboard, Mouse & User Interaction |
|
|
471 | |
|
|
472 | =head3 The new selection selects pieces that are too big, how can I select single words? |
|
|
473 | |
|
|
474 | If you want to select e.g. alphanumeric words, you can use the following |
|
|
475 | setting: |
|
|
476 | |
|
|
477 | URxvt.selection.pattern-0: ([[:word:]]+) |
|
|
478 | |
|
|
479 | If you click more than twice, the selection will be extended |
|
|
480 | more and more. |
|
|
481 | |
|
|
482 | To get a selection that is very similar to the old code, try this pattern: |
|
|
483 | |
|
|
484 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
|
|
485 | |
|
|
486 | Please also note that the I<LeftClick Shift-LeftClik> combination also |
|
|
487 | selects words like the old code. |
|
|
488 | |
|
|
489 | =head3 I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
|
|
490 | |
|
|
491 | You can disable the perl extension completely by setting the |
|
|
492 | B<perl-ext-common> resource to the empty string, which also keeps |
|
|
493 | rxvt-unicode from initialising perl, saving memory. |
|
|
494 | |
|
|
495 | If you only want to disable specific features, you first have to |
|
|
496 | identify which perl extension is responsible. For this, read the section |
|
|
497 | B<PREPACKAGED EXTENSIONS> in the @@URXVT_NAME@@perl(3) manpage. For |
|
|
498 | example, to disable the B<selection-popup> and B<option-popup>, specify |
|
|
499 | this B<perl-ext-common> resource: |
|
|
500 | |
|
|
501 | URxvt.perl-ext-common: default,-selection-popup,-option-popup |
|
|
502 | |
|
|
503 | This will keep the default extensions, but disable the two popup |
|
|
504 | extensions. Some extensions can also be configured, for example, |
|
|
505 | scrollback search mode is triggered by B<M-s>. You can move it to any |
|
|
506 | other combination either by setting the B<searchable-scrollback> resource: |
|
|
507 | |
|
|
508 | URxvt.searchable-scrollback: CM-s |
|
|
509 | |
|
|
510 | =head3 The cursor moves when selecting text in the current input line, how do I switch this off? |
|
|
511 | |
|
|
512 | See next entry. |
|
|
513 | |
|
|
514 | =head3 During rlogin/ssh/telnet/etc. sessions, clicking near the cursor outputs strange escape sequences, how do I fix this? |
|
|
515 | |
|
|
516 | These are caused by the C<readline> perl extension. Under normal |
|
|
517 | circumstances, it will move your cursor around when you click into the |
|
|
518 | line that contains it. It tries hard not to do this at the wrong moment, |
|
|
519 | but when running a program that doesn't parse cursor movements or in some |
|
|
520 | cases during rlogin sessions, it fails to detect this properly. |
|
|
521 | |
|
|
522 | You can permanently switch this feature off by disabling the C<readline> |
|
|
523 | extension: |
|
|
524 | |
|
|
525 | URxvt.perl-ext-common: default,-readline |
|
|
526 | |
|
|
527 | =head3 My numerical keypad acts weird and generates differing output? |
|
|
528 | |
|
|
529 | Some Debian GNUL/Linux users seem to have this problem, although no |
|
|
530 | specific details were reported so far. It is possible that this is caused |
|
|
531 | by the wrong C<TERM> setting, although the details of whether and how |
|
|
532 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
|
|
533 | keymap. See the answer to the previous question, and please report if that |
|
|
534 | helped. |
|
|
535 | |
|
|
536 | =head3 My Compose (Multi_key) key is no longer working. |
|
|
537 | |
|
|
538 | The most common causes for this are that either your locale is not set |
|
|
539 | correctly, or you specified a B<preeditStyle> that is not supported by |
|
|
540 | your input method. For example, if you specified B<OverTheSpot> and |
|
|
541 | your input method (e.g. the default input method handling Compose keys) |
|
|
542 | does not support this (for instance because it is not visual), then |
|
|
543 | rxvt-unicode will continue without an input method. |
|
|
544 | |
|
|
545 | In this case either do not specify a B<preeditStyle> or specify more than |
|
|
546 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
|
|
547 | |
|
|
548 | =head3 I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
|
|
549 | |
|
|
550 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
|
|
551 | international keyboards) or simply use ISO 14755 support to your |
|
|
552 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
|
|
553 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
|
|
554 | character and so on. |
|
|
555 | |
|
|
556 | =head3 Mouse cut/paste suddenly no longer works. |
|
|
557 | |
|
|
558 | Make sure that mouse reporting is actually turned off since killing |
|
|
559 | some editors prematurely may leave the mouse in mouse report mode. I've |
|
|
560 | heard that tcsh may use mouse reporting unless it otherwise specified. A |
|
|
561 | quick check is to see if cut/paste works when the Alt or Shift keys are |
|
|
562 | depressed. |
|
|
563 | |
|
|
564 | =head3 What's with the strange Backspace/Delete key behaviour? |
|
|
565 | |
|
|
566 | Assuming that the physical Backspace key corresponds to the |
|
|
567 | Backspace keysym (not likely for Linux ... see the following |
|
|
568 | question) there are two standard values that can be used for |
|
|
569 | Backspace: C<^H> and C<^?>. |
|
|
570 | |
|
|
571 | Historically, either value is correct, but rxvt-unicode adopts the debian |
|
|
572 | policy of using C<^?> when unsure, because it's the one and only correct |
|
|
573 | choice :). |
|
|
574 | |
|
|
575 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
|
|
576 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
|
|
577 | started from a terminal (say, from a menu or by remote shell), then the |
|
|
578 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
|
|
579 | be used (which may not be the same as your stty setting). |
|
|
580 | |
|
|
581 | For starting a new rxvt-unicode: |
|
|
582 | |
|
|
583 | # use Backspace = ^H |
|
|
584 | $ stty erase ^H |
|
|
585 | $ @@URXVT_NAME@@ |
|
|
586 | |
|
|
587 | # use Backspace = ^? |
|
|
588 | $ stty erase ^? |
|
|
589 | $ @@URXVT_NAME@@ |
|
|
590 | |
|
|
591 | Toggle with C<ESC [ 36 h> / C<ESC [ 36 l>. |
|
|
592 | |
|
|
593 | For an existing rxvt-unicode: |
|
|
594 | |
|
|
595 | # use Backspace = ^H |
|
|
596 | $ stty erase ^H |
|
|
597 | $ echo -n "^[[36h" |
|
|
598 | |
|
|
599 | # use Backspace = ^? |
|
|
600 | $ stty erase ^? |
|
|
601 | $ echo -n "^[[36l" |
|
|
602 | |
|
|
603 | This helps satisfy some of the Backspace discrepancies that occur, but |
|
|
604 | if you use Backspace = C<^H>, make sure that the termcap/terminfo value |
|
|
605 | properly reflects that. |
|
|
606 | |
|
|
607 | The Delete key is a another casualty of the ill-defined Backspace problem. |
|
|
608 | To avoid confusion between the Backspace and Delete keys, the Delete |
|
|
609 | key has been assigned an escape sequence to match the vt100 for Execute |
|
|
610 | (C<ESC [ 3 ~>) and is in the supplied termcap/terminfo. |
|
|
611 | |
|
|
612 | Some other Backspace problems: |
|
|
613 | |
|
|
614 | some editors use termcap/terminfo, |
|
|
615 | some editors (vim I'm told) expect Backspace = ^H, |
|
|
616 | GNU Emacs (and Emacs-like editors) use ^H for help. |
|
|
617 | |
|
|
618 | Perhaps someday this will all be resolved in a consistent manner. |
|
|
619 | |
|
|
620 | =head3 I don't like the key-bindings. How do I change them? |
|
|
621 | |
|
|
622 | There are some compile-time selections available via configure. Unless |
|
|
623 | you have run "configure" with the C<--disable-resources> option you can |
|
|
624 | use the `keysym' resource to alter the keystrings associated with keysyms. |
|
|
625 | |
|
|
626 | Here's an example for a URxvt session started using C<@@URXVT_NAME@@ -name URxvt> |
|
|
627 | |
|
|
628 | URxvt.keysym.Home: \033[1~ |
|
|
629 | URxvt.keysym.End: \033[4~ |
|
|
630 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
631 | URxvt.keysym.C-slash: \033<C-/> |
|
|
632 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
633 | URxvt.keysym.C-grave: \033<C-`> |
|
|
634 | URxvt.keysym.C-comma: \033<C-,> |
|
|
635 | URxvt.keysym.C-period: \033<C-.> |
|
|
636 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
637 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
638 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
639 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
640 | URxvt.keysym.S-space: \033<S-Space> |
|
|
641 | URxvt.keysym.M-Up: \033<M-Up> |
|
|
642 | URxvt.keysym.M-Down: \033<M-Down> |
|
|
643 | URxvt.keysym.M-Left: \033<M-Left> |
|
|
644 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
645 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
646 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
647 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
|
|
648 | |
|
|
649 | See some more examples in the documentation for the B<keysym> resource. |
|
|
650 | |
|
|
651 | =head3 I'm using keyboard model XXX that has extra Prior/Next/Insert keys. How do I make use of them? For example, the Sun Keyboard type 4 has the following map |
|
|
652 | |
|
|
653 | KP_Insert == Insert |
|
|
654 | F22 == Print |
|
|
655 | F27 == Home |
|
|
656 | F29 == Prior |
|
|
657 | F33 == End |
|
|
658 | F35 == Next |
|
|
659 | |
|
|
660 | Rather than have rxvt-unicode try to accommodate all the various possible |
|
|
661 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
|
|
662 | required for your particular machine. |
|
|
663 | |
|
|
664 | |
|
|
665 | =head2 Terminal Configuration |
|
|
666 | |
|
|
667 | =head3 Can I see a typical configuration? |
|
|
668 | |
|
|
669 | The default configuration tries to be xterm-like, which I don't like that |
|
|
670 | much, but it's least surprise to regular users. |
|
|
671 | |
|
|
672 | As a rxvt or rxvt-unicode user, you are practically supposed to invest |
|
|
673 | time into customising your terminal. To get you started, here is the |
|
|
674 | author's .Xdefaults entries, with comments on what they do. It's certainly |
|
|
675 | not I<typical>, but what's typical... |
|
|
676 | |
|
|
677 | URxvt.cutchars: "()*,<>[]{}|' |
|
|
678 | URxvt.print-pipe: cat >/tmp/xxx |
|
|
679 | |
|
|
680 | These are just for testing stuff. |
|
|
681 | |
|
|
682 | URxvt.imLocale: ja_JP.UTF-8 |
|
|
683 | URxvt.preeditType: OnTheSpot,None |
|
|
684 | |
|
|
685 | This tells rxvt-unicode to use a special locale when communicating with |
|
|
686 | the X Input Method, and also tells it to only use the OnTheSpot pre-edit |
|
|
687 | type, which requires the C<xim-onthespot> perl extension but rewards me |
|
|
688 | with correct-looking fonts. |
|
|
689 | |
|
|
690 | URxvt.perl-lib: /root/lib/urxvt |
|
|
691 | URxvt.perl-ext-common: default,selection-autotransform,selection-pastebin,xim-onthespot,remote-clipboard |
|
|
692 | URxvt.selection.pattern-0: ( at .*? line \\d+) |
|
|
693 | URxvt.selection.pattern-1: ^(/[^:]+):\ |
|
|
694 | URxvt.selection-autotransform.0: s/^([^:[:space:]]+):(\\d+):?$/:e \\Q$1\\E\\x0d:$2\\x0d/ |
|
|
695 | URxvt.selection-autotransform.1: s/^ at (.*?) line (\\d+)$/:e \\Q$1\\E\\x0d:$2\\x0d/ |
|
|
696 | |
|
|
697 | This is my perl configuration. The first two set the perl library |
|
|
698 | directory and also tells urxvt to use a large number of extensions. I |
|
|
699 | develop for myself mostly, so I actually use most of the extensions I |
|
|
700 | write. |
|
|
701 | |
|
|
702 | The selection stuff mainly makes the selection perl-error-message aware |
|
|
703 | and tells it to convert perl error messages into vi-commands to load the |
|
|
704 | relevant file and go tot he error line number. |
|
|
705 | |
|
|
706 | URxvt.scrollstyle: plain |
|
|
707 | URxvt.secondaryScroll: true |
|
|
708 | |
|
|
709 | As the documentation says: plain is the preferred scrollbar for the |
|
|
710 | author. The C<secondaryScroll> configures urxvt to scroll in full-screen |
|
|
711 | apps, like screen, so lines scrolled out of screen end up in urxvt's |
|
|
712 | scrollback buffer. |
|
|
713 | |
|
|
714 | URxvt.background: #000000 |
|
|
715 | URxvt.foreground: gray90 |
|
|
716 | URxvt.color7: gray90 |
|
|
717 | URxvt.colorBD: #ffffff |
|
|
718 | URxvt.cursorColor: #e0e080 |
|
|
719 | URxvt.throughColor: #8080f0 |
|
|
720 | URxvt.highlightColor: #f0f0f0 |
|
|
721 | |
|
|
722 | Some colours. Not sure which ones are being used or even non-defaults, but |
|
|
723 | these are in my .Xdefaults. Most notably, they set foreground/background |
|
|
724 | to light gray/black, and also make sure that the colour 7 matches the |
|
|
725 | default foreground colour. |
|
|
726 | |
|
|
727 | URxvt.underlineColor: yellow |
|
|
728 | |
|
|
729 | Another colour, makes underline lines look different. Sometimes hurts, but |
|
|
730 | is mostly a nice effect. |
|
|
731 | |
|
|
732 | URxvt.geometry: 154x36 |
|
|
733 | URxvt.loginShell: false |
|
|
734 | URxvt.meta: ignore |
|
|
735 | URxvt.utmpInhibit: true |
|
|
736 | |
|
|
737 | Uh, well, should be mostly self-explanatory. By specifying some defaults |
|
|
738 | manually, I can quickly switch them for testing. |
|
|
739 | |
|
|
740 | URxvt.saveLines: 8192 |
|
|
741 | |
|
|
742 | A large scrollback buffer is essential. Really. |
|
|
743 | |
|
|
744 | URxvt.mapAlert: true |
|
|
745 | |
|
|
746 | The only case I use it is for my IRC window, which I like to keep |
|
|
747 | iconified till people msg me (which beeps). |
|
|
748 | |
|
|
749 | URxvt.visualBell: true |
|
|
750 | |
|
|
751 | The audible bell is often annoying, especially when in a crowd. |
|
|
752 | |
|
|
753 | URxvt.insecure: true |
|
|
754 | |
|
|
755 | Please don't hack my mutt! Ooops... |
|
|
756 | |
|
|
757 | URxvt.pastableTabs: false |
|
|
758 | |
|
|
759 | I once thought this is a great idea. |
|
|
760 | |
|
|
761 | urxvt.font: 9x15bold,\ |
|
|
762 | -misc-fixed-bold-r-normal--15-140-75-75-c-90-iso10646-1,\ |
|
|
763 | -misc-fixed-medium-r-normal--15-140-75-75-c-90-iso10646-1, \ |
|
|
764 | [codeset=JISX0208]xft:Kochi Gothic, \ |
|
|
765 | xft:Bitstream Vera Sans Mono:autohint=true, \ |
|
|
766 | xft:Code2000:antialias=false |
|
|
767 | urxvt.boldFont: -xos4-terminus-bold-r-normal--14-140-72-72-c-80-iso8859-15 |
|
|
768 | urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
769 | urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
770 | |
|
|
771 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
|
|
772 | overwhelmed. A special note: the C<9x15bold> mentioned above is actually |
|
|
773 | the version from XFree-3.3, as XFree-4 replaced it by a totally different |
|
|
774 | font (different glyphs for C<;> and many other harmless characters), |
|
|
775 | while the second font is actually the C<9x15bold> from XFree4/XOrg. The |
|
|
776 | bold version has less chars than the medium version, so I use it for rare |
|
|
777 | characters, too. When editing sources with vim, I use italic for comments |
|
|
778 | and other stuff, which looks quite good with Bitstream Vera anti-aliased. |
|
|
779 | |
|
|
780 | Terminus is a quite bad font (many very wrong glyphs), but for most of my |
|
|
781 | purposes, it works, and gives a different look, as my normal (Non-bold) |
|
|
782 | font is already bold, and I want to see a difference between bold and |
|
|
783 | normal fonts. |
|
|
784 | |
|
|
785 | Please note that I used the C<urxvt> instance name and not the C<URxvt> |
|
|
786 | class name. Thats because I use different configs for different purposes, |
|
|
787 | for example, my IRC window is started with C<-name IRC>, and uses these |
|
|
788 | defaults: |
|
|
789 | |
|
|
790 | IRC*title: IRC |
|
|
791 | IRC*geometry: 87x12+535+542 |
|
|
792 | IRC*saveLines: 0 |
|
|
793 | IRC*mapAlert: true |
|
|
794 | IRC*font: suxuseuro |
|
|
795 | IRC*boldFont: suxuseuro |
|
|
796 | IRC*colorBD: white |
|
|
797 | IRC*keysym.M-C-1: command:\033]710;suxuseuro\007\033]711;suxuseuro\007 |
|
|
798 | IRC*keysym.M-C-2: command:\033]710;9x15bold\007\033]711;9x15bold\007 |
|
|
799 | |
|
|
800 | C<Alt-Shift-1> and C<Alt-Shift-2> switch between two different font |
|
|
801 | sizes. C<suxuseuro> allows me to keep an eye (and actually read) |
|
|
802 | stuff while keeping a very small window. If somebody pastes something |
|
|
803 | complicated (e.g. japanese), I temporarily switch to a larger font. |
|
|
804 | |
|
|
805 | The above is all in my C<.Xdefaults> (I don't use C<.Xresources> nor |
|
|
806 | C<xrdb>). I also have some resources in a separate C<.Xdefaults-hostname> |
|
|
807 | file for different hosts, for example, on ym main desktop, I use: |
|
|
808 | |
|
|
809 | URxvt.keysym.C-M-q: command:\033[3;5;5t |
|
|
810 | URxvt.keysym.C-M-y: command:\033[3;5;606t |
|
|
811 | URxvt.keysym.C-M-e: command:\033[3;1605;5t |
|
|
812 | URxvt.keysym.C-M-c: command:\033[3;1605;606t |
|
|
813 | URxvt.keysym.C-M-p: perl:test |
|
|
814 | |
|
|
815 | The first for keysym definitions allow me to quickly bring some windows |
|
|
816 | in the layout I like most. Ion users might start laughing but will stop |
|
|
817 | immediately when I tell them that I use my own Fvwm2 module for much the |
|
|
818 | same effect as Ion provides, and I only very rarely use the above key |
|
|
819 | combinations :-> |
|
|
820 | |
|
|
821 | =head3 Why doesn't rxvt-unicode read my resources? |
|
|
822 | |
|
|
823 | Well, why, indeed? It does, in a way very similar to other X |
|
|
824 | applications. Most importantly, this means that if you or your OS loads |
|
|
825 | resources into the X display (the right way to do it), rxvt-unicode will |
|
|
826 | ignore any resource files in your home directory. It will only read |
|
|
827 | F<$HOME/.Xdefaults> when no resources are attached to the display. |
|
|
828 | |
|
|
829 | If you have or use an F<$HOME/.Xresources> file, chances are that |
|
|
830 | resources are loaded into your X-server. In this case, you have to |
|
|
831 | re-login after every change (or run F<xrdb -merge $HOME/.Xresources>). |
|
|
832 | |
|
|
833 | Also consider the form resources have to use: |
|
|
834 | |
|
|
835 | URxvt.resource: value |
|
|
836 | |
|
|
837 | If you want to use another form (there are lots of different ways of |
|
|
838 | specifying resources), make sure you understand whether and why it |
|
|
839 | works. If unsure, use the form above. |
|
|
840 | |
176 | =item When I log-in to another system it tells me about missing terminfo data? |
841 | =head3 When I log-in to another system it tells me about missing terminfo data? |
177 | |
842 | |
178 | The terminal description used by rxvt-unicode is not as widely available |
843 | 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). |
844 | as that for xterm, or even rxvt (for which the same problem often arises). |
180 | |
845 | |
181 | The correct solution for this problem is to install the terminfo, this can |
846 | The correct solution for this problem is to install the terminfo, this can |
182 | be done like this (with ncurses' infocmp): |
847 | be done like this (with ncurses' infocmp and works as user and admin): |
183 | |
848 | |
184 | REMOTE=remotesystem.domain |
849 | REMOTE=remotesystem.domain |
185 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
850 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
186 | |
851 | |
187 | ... or by installing rxvt-unicode normally on the remote system, |
852 | ... or by installing rxvt-unicode normally on the remote system, |
|
|
853 | |
|
|
854 | One some systems you might need to set C<$TERMINFO> to the full path of |
|
|
855 | F<$HOME/.terminfo> for this to work. |
188 | |
856 | |
189 | If you cannot or do not want to do this, then you can simply set |
857 | If you cannot or do not want to do this, then you can simply set |
190 | C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
858 | C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
191 | problems arising, which includes wrong keymapping, less and different |
859 | problems arising, which includes wrong keymapping, less and different |
192 | colours and some refresh errors in fullscreen applications. It's a nice |
860 | colours and some refresh errors in fullscreen applications. It's a nice |
… | |
… | |
197 | resource to set it: |
865 | resource to set it: |
198 | |
866 | |
199 | URxvt.termName: rxvt |
867 | URxvt.termName: rxvt |
200 | |
868 | |
201 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
869 | 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. |
870 | the rxvt terminfo file with the rxvt-unicode one and use C<TERM=rxvt>. |
203 | |
871 | |
204 | =item C<tic> outputs some error when compiling the terminfo entry. |
872 | =head3 C<tic> outputs some error when compiling the terminfo entry. |
205 | |
873 | |
206 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
874 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
207 | C<enacs=\E[0@> and try again. |
875 | C<enacs=\E[0@> and try again. |
208 | |
876 | |
209 | =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
877 | =head3 C<bash>'s readline does not work correctly under @@URXVT_NAME@@. |
210 | |
878 | |
|
|
879 | See next entry. |
|
|
880 | |
211 | =item I need a termcap file entry. |
881 | =head3 I need a termcap file entry. |
212 | |
882 | |
213 | One reason you might want this is that some distributions or operating |
883 | One reason you might want this is that some distributions or operating |
214 | systems still compile some programs using the long-obsoleted termcap |
884 | 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 |
885 | library (Fedora Core's bash is one example) and rely on a termcap entry |
216 | for C<rxvt-unicode>. |
886 | for C<rxvt-unicode>. |
217 | |
887 | |
218 | You could use rxvt's termcap entry with resonable results in many cases. |
888 | You could use rxvt's termcap entry with reasonable results in many cases. |
219 | You can also create a termcap entry by using terminfo's infocmp program |
889 | You can also create a termcap entry by using terminfo's infocmp program |
220 | like this: |
890 | like this: |
221 | |
891 | |
222 | infocmp -C rxvt-unicode |
892 | infocmp -C rxvt-unicode |
223 | |
893 | |
… | |
… | |
242 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
912 | :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:\ |
913 | :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:\ |
914 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
245 | :vs=\E[?25h: |
915 | :vs=\E[?25h: |
246 | |
916 | |
247 | =item Why does C<ls> no longer have coloured output? |
917 | =head3 Why does C<ls> no longer have coloured output? |
248 | |
918 | |
249 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
919 | 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 |
920 | decide whether a terminal has colour, but uses its own configuration |
251 | file. Needless to say, C<rxvt-unicode> is not in it's default file (among |
921 | file. Needless to say, C<rxvt-unicode> is not in its default file (among |
252 | with most other terminals supporting colour). Either add: |
922 | with most other terminals supporting colour). Either add: |
253 | |
923 | |
254 | TERM rxvt-unicode |
924 | TERM rxvt-unicode |
255 | |
925 | |
256 | to C</etc/DIR_COLORS> or simply add: |
926 | to C</etc/DIR_COLORS> or simply add: |
257 | |
927 | |
258 | alias ls='ls --color=auto' |
928 | alias ls='ls --color=auto' |
259 | |
929 | |
260 | to your C<.profile> or C<.bashrc>. |
930 | to your C<.profile> or C<.bashrc>. |
261 | |
931 | |
262 | =item Why doesn't vim/emacs etc. use the 88 colour mode? |
932 | =head3 Why doesn't vim/emacs etc. use the 88 colour mode? |
263 | |
933 | |
|
|
934 | See next entry. |
|
|
935 | |
264 | =item Why doesn't vim/emacs etc. make use of italic? |
936 | =head3 Why doesn't vim/emacs etc. make use of italic? |
265 | |
937 | |
|
|
938 | See next entry. |
|
|
939 | |
266 | =item Why are the secondary screen-related options not working properly? |
940 | =head3 Why are the secondary screen-related options not working properly? |
267 | |
941 | |
268 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
942 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
269 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
943 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
270 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
944 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
271 | features. Unfortunately, some of these (most notably, again, Debian |
945 | features. Unfortunately, some of these (most notably, again, Debian |
272 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
946 | 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 |
947 | 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 |
948 | I log-in to another system it tells me about missing terminfo data?> on |
275 | how to do this). |
949 | how to do this). |
276 | |
950 | |
277 | =item My numerical keypad acts weird and generates differing output? |
|
|
278 | |
951 | |
279 | Some Debian GNUL/Linux users seem to have this problem, although no |
952 | =head2 Encoding / Locale / Input Method Issues |
280 | 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 |
|
|
282 | 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 |
|
|
284 | helped. |
|
|
285 | |
953 | |
286 | =item Rxvt-unicode does not seem to understand the selected encoding? |
954 | =head3 Rxvt-unicode does not seem to understand the selected encoding? |
287 | |
955 | |
|
|
956 | See next entry. |
|
|
957 | |
288 | =item Unicode does not seem to work? |
958 | =head3 Unicode does not seem to work? |
289 | |
959 | |
290 | If you encounter strange problems like typing an accented character but |
960 | If you encounter strange problems like typing an accented character but |
291 | getting two unrelated other characters or similar, or if program output is |
961 | getting two unrelated other characters or similar, or if program output is |
292 | subtly garbled, then you should check your locale settings. |
962 | subtly garbled, then you should check your locale settings. |
293 | |
963 | |
294 | Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
964 | Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
295 | programs. Often rxvt-unicode is started in the C<C> locale, while the |
965 | programs running in it. Often rxvt-unicode is started in the C<C> locale, |
296 | login script running within the rxvt-unicode window changes the locale to |
966 | while the login script running within the rxvt-unicode window changes the |
297 | something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work. |
967 | locale to something else, e.g. C<en_GB.UTF-8>. Needless to say, this is |
|
|
968 | not going to work, and is the most common cause for problems. |
298 | |
969 | |
299 | The best thing is to fix your startup environment, as you will likely run |
970 | The best thing is to fix your startup environment, as you will likely run |
300 | into other problems. If nothing works you can try this in your .profile. |
971 | into other problems. If nothing works you can try this in your .profile. |
301 | |
972 | |
302 | printf '\e]701;%s\007' "$LC_CTYPE" |
973 | printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too |
303 | |
974 | |
304 | If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
975 | If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
305 | supported on your systems. Some systems have a C<locale> command which |
976 | supported on your systems. Some systems have a C<locale> command which |
306 | displays this (also, C<perl -e0> can be used to check locale settings, as |
977 | displays this (also, C<perl -e0> can be used to check locale settings, as |
307 | it will complain loudly if it cannot set the locale). If it displays something |
978 | it will complain loudly if it cannot set the locale). If it displays something |
… | |
… | |
313 | |
984 | |
314 | If nothing works and you are sure that everything is set correctly then |
985 | 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 |
986 | you will need to remember a little known fact: Some programs just don't |
316 | support locales :( |
987 | support locales :( |
317 | |
988 | |
318 | =item Why do some characters look so much different than others? |
989 | =head3 How does rxvt-unicode determine the encoding to use? |
319 | |
990 | |
320 | =item How does rxvt-unicode choose fonts? |
991 | See next entry. |
321 | |
992 | |
322 | Most fonts do not contain the full range of Unicode, which is |
993 | =head3 Is there an option to switch encodings? |
323 | 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 |
|
|
325 | to display. |
|
|
326 | |
994 | |
327 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
995 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
328 | font. Often the result is fine, but sometimes the chosen font looks |
996 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
329 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
997 | UTF-8 or any other encodings with respect to terminal I/O. |
330 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
|
|
331 | intelligence to detect that a specific glyph is wrong: it has to believe |
|
|
332 | the font that the characters it claims to contain indeed look correct. |
|
|
333 | |
998 | |
334 | In that case, select a font of your taste and add it to the font list, |
999 | The reasons is that there exists a perfectly fine mechanism for selecting |
335 | e.g.: |
1000 | the encoding, doing I/O and (most important) communicating this to all |
336 | |
1001 | applications so everybody agrees on character properties such as width |
337 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
1002 | and code number. This mechanism is the I<locale>. Applications not using |
338 | |
1003 | that info will have problems (for example, C<xterm> gets the width of |
339 | When rxvt-unicode sees a character, it will first look at the base |
1004 | characters wrong as it uses its own, locale-independent table under all |
340 | font. If the base font does not contain the character, it will go to the |
|
|
341 | next font, and so on. Specifying your own fonts will also speed up this |
|
|
342 | search and use less resources within rxvt-unicode and the X-server. |
|
|
343 | |
|
|
344 | 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 |
|
|
346 | must be the same due to the way terminals work. |
|
|
347 | |
|
|
348 | =item Why do some chinese characters look so different than others? |
|
|
349 | |
|
|
350 | 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, |
|
|
352 | 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 |
|
|
354 | display. Subsequent japanese characters will use that font. Now, many |
|
|
355 | chinese characters aren't represented in japanese fonts, so when the first |
|
|
356 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
|
|
357 | -- unfortunately at this point, it will still use the japanese font for |
|
|
358 | chinese characters that are also in the japanese font. |
|
|
359 | |
|
|
360 | The workaround is easy: just tag a chinese font at the end of your font |
|
|
361 | list (see the previous question). The key is to view the font list as |
|
|
362 | a preference list: If you expect more japanese, list a japanese font |
|
|
363 | first. If you expect more chinese, put a chinese font first. |
|
|
364 | |
|
|
365 | In the future it might be possible to switch language preferences at |
|
|
366 | runtime (the internal data structure has no problem with using different |
|
|
367 | fonts for the same character at the same time, but no interface for this |
|
|
368 | has been designed yet). |
|
|
369 | |
|
|
370 | 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). |
|
|
372 | |
|
|
373 | =item Why does rxvt-unicode sometimes leave pixel droppings? |
|
|
374 | |
|
|
375 | 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 |
|
|
377 | 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 |
|
|
379 | "careful" rendering mode is used that redraws adjacent characters. |
|
|
380 | |
|
|
381 | All of this requires that fonts do not lie about character sizes, |
|
|
382 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
|
|
383 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
|
|
384 | ask for the character bounding box, which unfortunately is wrong in these |
|
|
385 | cases). |
1005 | locales). |
386 | |
1006 | |
387 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
1007 | Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
388 | or the respective font. If you encounter this problem you might try using |
1008 | programs doing the same (that is, most) will automatically agree in the |
389 | the C<-lsp> option to give the font more height. If that doesn't work, you |
1009 | interpretation of characters. |
390 | might be forced to use a different font. |
|
|
391 | |
1010 | |
392 | All of this is not a problem when using X11 core fonts, as their bounding |
1011 | Unfortunately, there is no system-independent way to select locales, nor |
393 | box data is correct. |
1012 | is there a standard on how locale specifiers will look like. |
394 | |
1013 | |
395 | =item On Solaris 9, many line-drawing characters are too wide. |
1014 | On most systems, the content of the C<LC_CTYPE> environment variable |
|
|
1015 | contains an arbitrary string which corresponds to an already-installed |
|
|
1016 | locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>, |
|
|
1017 | C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
|
|
1018 | (i.e. C<de> or C<german>) are also common. |
396 | |
1019 | |
397 | Seems to be a known bug, read |
1020 | Rxvt-unicode ignores all other locale categories, and except for |
398 | L<http://nixdoc.net/files/forum/about34198.html>. Some people use the |
1021 | the encoding, ignores country or language-specific settings, |
399 | following ugly workaround to get non-double-wide-characters working: |
1022 | i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to |
|
|
1023 | rxvt-unicode. |
400 | |
1024 | |
401 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
1025 | If you want to use a specific encoding you have to make sure you start |
|
|
1026 | rxvt-unicode with the correct C<LC_CTYPE> category. |
402 | |
1027 | |
403 | =item My Compose (Multi_key) key is no longer working. |
1028 | =head3 Can I switch locales at runtime? |
404 | |
1029 | |
405 | The most common causes for this are that either your locale is not set |
1030 | Yes, using an escape sequence. Try something like this, which sets |
406 | correctly, or you specified a B<preeditStyle> that is not supported by |
1031 | rxvt-unicode's idea of C<LC_CTYPE>. |
407 | your input method. For example, if you specified B<OverTheSpot> and |
|
|
408 | your input method (e.g. the default input method handling Compose keys) |
|
|
409 | does not support this (for instance because it is not visual), then |
|
|
410 | rxvt-unicode will continue without an input method. |
|
|
411 | |
1032 | |
412 | In this case either do not specify a B<preeditStyle> or specify more than |
1033 | printf '\33]701;%s\007' ja_JP.SJIS |
413 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
|
|
414 | |
1034 | |
415 | =item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
1035 | See also the previous answer. |
416 | |
1036 | |
417 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
1037 | Sometimes this capability is rather handy when you want to work in |
418 | international keyboards) or simply use ISO 14755 support to your |
1038 | one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it |
419 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
1039 | (e.g. UTF-8). For example, I use this script to start C<xjdic>, which |
420 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
1040 | first switches to a locale supported by xjdic and back later: |
421 | character and so on. |
|
|
422 | |
1041 | |
423 | =item How can I keep rxvt-unicode from using reverse video so much? |
1042 | printf '\33]701;%s\007' ja_JP.SJIS |
|
|
1043 | xjdic -js |
|
|
1044 | printf '\33]701;%s\007' de_DE.UTF-8 |
424 | |
1045 | |
425 | First of all, make sure you are running with the right terminal settings |
1046 | You can also use xterm's C<luit> program, which usually works fine, except |
426 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
1047 | for some locales where character width differs between program- and |
427 | make sure you have specified colours for italic and bold, as otherwise |
1048 | rxvt-unicode-locales. |
428 | rxvt-unicode might use reverse video to simulate the effect: |
|
|
429 | |
1049 | |
430 | URxvt.colorBD: white |
1050 | =head3 I have problems getting my input method working. |
431 | URxvt.colorIT: green |
|
|
432 | |
1051 | |
433 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
1052 | Try a search engine, as this is slightly different for every input method server. |
434 | |
1053 | |
435 | For some unexplainable reason, some rare programs assume a very weird |
1054 | Here is a checklist: |
436 | 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 |
|
|
438 | these programs not to assume non-ISO colours without very good reasons. |
|
|
439 | |
1055 | |
440 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
1056 | =over 4 |
441 | 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. |
|
|
443 | |
1057 | |
|
|
1058 | =item - Make sure your locale I<and> the imLocale are supported on your OS. |
|
|
1059 | |
|
|
1060 | Try C<locale -a> or check the documentation for your OS. |
|
|
1061 | |
|
|
1062 | =item - Make sure your locale or imLocale matches a locale supported by your XIM. |
|
|
1063 | |
|
|
1064 | For example, B<kinput2> does not support UTF-8 locales, you should use |
|
|
1065 | C<ja_JP.EUC-JP> or equivalent. |
|
|
1066 | |
|
|
1067 | =item - Make sure your XIM server is actually running. |
|
|
1068 | |
|
|
1069 | =item - Make sure the C<XMODIFIERS> environment variable is set correctly when I<starting> rxvt-unicode. |
|
|
1070 | |
|
|
1071 | When you want to use e.g. B<kinput2>, it must be set to |
|
|
1072 | C<@im=kinput2>. For B<scim>, use C<@im=SCIM>. You can see what input |
|
|
1073 | method servers are running with this command: |
|
|
1074 | |
|
|
1075 | xprop -root XIM_SERVERS |
|
|
1076 | |
|
|
1077 | =item |
|
|
1078 | |
|
|
1079 | =back |
|
|
1080 | |
|
|
1081 | =head3 My input method wants <some encoding> but I want UTF-8, what can I do? |
|
|
1082 | |
|
|
1083 | You can specify separate locales for the input method and the rest of the |
|
|
1084 | terminal, using the resource C<imlocale>: |
|
|
1085 | |
|
|
1086 | URxvt.imlocale: ja_JP.EUC-JP |
|
|
1087 | |
|
|
1088 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
|
|
1089 | use your input method. Please note, however, that, depending on your Xlib |
|
|
1090 | version, you may not be able to input characters outside C<EUC-JP> in a |
|
|
1091 | normal way then, as your input method limits you. |
|
|
1092 | |
|
|
1093 | =head3 Rxvt-unicode crashes when the X Input Method changes or exits. |
|
|
1094 | |
|
|
1095 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
|
|
1096 | design. Applications can avoid some crashes at the expense of memory |
|
|
1097 | leaks, and Input Methods can avoid some crashes by careful ordering at |
|
|
1098 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
|
|
1099 | while B<SCIM> (or similar input methods) fails. In the end, however, |
|
|
1100 | crashes cannot be completely avoided even if both sides cooperate. |
|
|
1101 | |
|
|
1102 | So the only workaround is not to kill your Input Method Servers. |
|
|
1103 | |
|
|
1104 | |
|
|
1105 | =head2 Operating Systems / Package Maintaining |
|
|
1106 | |
|
|
1107 | =head3 I am using Debian GNU/Linux and have a problem... |
|
|
1108 | |
|
|
1109 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
1110 | patches that considerably change the behaviour of rxvt-unicode (but |
|
|
1111 | unfortunately this notice has been removed). Before reporting a bug to |
|
|
1112 | the original rxvt-unicode author please download and install the genuine |
|
|
1113 | version (L<http://software.schmorp.de#rxvt-unicode>) and try to reproduce |
|
|
1114 | the problem. If you cannot, chances are that the problems are specific to |
|
|
1115 | Debian GNU/Linux, in which case it should be reported via the Debian Bug |
|
|
1116 | Tracking System (use C<reportbug> to report the bug). |
|
|
1117 | |
|
|
1118 | For other problems that also affect the Debian package, you can and |
|
|
1119 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
1120 | bug in the Debian version and it serves as a reminder for other users that |
|
|
1121 | might encounter the same issue. |
|
|
1122 | |
|
|
1123 | =head3 I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation? |
|
|
1124 | |
|
|
1125 | You should build one binary with the default options. F<configure> |
|
|
1126 | now enables most useful options, and the trend goes to making them |
|
|
1127 | runtime-switchable, too, so there is usually no drawback to enabling them, |
|
|
1128 | except higher disk and possibly memory usage. The perl interpreter should |
|
|
1129 | be enabled, as important functionality (menus, selection, likely more in |
|
|
1130 | the future) depends on it. |
|
|
1131 | |
|
|
1132 | You should not overwrite the C<perl-ext-common> snd C<perl-ext> resources |
|
|
1133 | system-wide (except maybe with C<defaults>). This will result in useful |
|
|
1134 | behaviour. If your distribution aims at low memory, add an empty |
|
|
1135 | C<perl-ext-common> resource to the app-defaults file. This will keep the |
|
|
1136 | perl interpreter disabled until the user enables it. |
|
|
1137 | |
|
|
1138 | If you can/want build more binaries, I recommend building a minimal |
|
|
1139 | one with C<--disable-everything> (very useful) and a maximal one with |
|
|
1140 | C<--enable-everything> (less useful, it will be very big due to a lot of |
|
|
1141 | encodings built-in that increase download times and are rarely used). |
|
|
1142 | |
|
|
1143 | =head3 I need to make it setuid/setgid to support utmp/ptys on my OS, is this safe? |
|
|
1144 | |
|
|
1145 | It should be, starting with release 7.1. You are encouraged to properly |
|
|
1146 | install urxvt with privileges necessary for your OS now. |
|
|
1147 | |
|
|
1148 | When rxvt-unicode detects that it runs setuid or setgid, it will fork |
|
|
1149 | into a helper process for privileged operations (pty handling on some |
|
|
1150 | systems, utmp/wtmp/lastlog handling on others) and drop privileges |
|
|
1151 | immediately. This is much safer than most other terminals that keep |
|
|
1152 | privileges while running (but is more relevant to urxvt, as it contains |
|
|
1153 | things as perl interpreters, which might be "helpful" to attackers). |
|
|
1154 | |
|
|
1155 | This forking is done as the very first within main(), which is very early |
|
|
1156 | and reduces possible bugs to initialisation code run before main(), or |
|
|
1157 | things like the dynamic loader of your system, which should result in very |
|
|
1158 | little risk. |
|
|
1159 | |
444 | =item I am on FreeBSD and rxvt-unicode does not seem to work at all. |
1160 | =head3 I am on FreeBSD and rxvt-unicode does not seem to work at all. |
445 | |
1161 | |
446 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
1162 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
447 | in your compile environment, or an implementation that implements it, |
1163 | in your compile environment, or an implementation that implements it, |
448 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
1164 | whether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
449 | B<wchar_t> is represented as unicode. |
1165 | B<wchar_t> is represented as unicode. |
450 | |
1166 | |
451 | As you might have guessed, FreeBSD does neither define this symobl nor |
1167 | As you might have guessed, FreeBSD does neither define this symbol nor |
452 | does it support it. Instead, it uses it's own internal representation of |
1168 | does it support it. Instead, it uses its own internal representation of |
453 | B<wchar_t>. This is, of course, completely fine with respect to standards. |
1169 | B<wchar_t>. This is, of course, completely fine with respect to standards. |
454 | |
1170 | |
455 | However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and |
1171 | However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and |
456 | C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>. |
1172 | C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>. |
457 | |
1173 | |
… | |
… | |
471 | |
1187 | |
472 | The rxvt-unicode author insists that the right way to fix this is in the |
1188 | 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 |
1189 | system libraries once and for all, instead of forcing every app to carry |
474 | complete replacements for them :) |
1190 | complete replacements for them :) |
475 | |
1191 | |
476 | =item I use Solaris 9 and it doesn't compile/work/etc. |
|
|
477 | |
|
|
478 | Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst |
|
|
479 | problems with C<wcwidth> and a compile problem. |
|
|
480 | |
|
|
481 | =item How can I use rxvt-unicode under cygwin? |
1192 | =head3 How can I use rxvt-unicode under cygwin? |
482 | |
1193 | |
483 | rxvt-unicode should compile and run out of the box on cygwin, using |
1194 | 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 |
1195 | the X11 libraries that come with cygwin. libW11 emulation is no |
485 | longer supported (and makes no sense, either, as it only supported a |
1196 | 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 |
1197 | single font). I recommend starting the X-server in C<-multiwindow> or |
… | |
… | |
489 | |
1200 | |
490 | At the time of this writing, cygwin didn't seem to support any multi-byte |
1201 | 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 |
1202 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
492 | to 8-bit encodings. |
1203 | to 8-bit encodings. |
493 | |
1204 | |
494 | =item How does rxvt-unicode determine the encoding to use? |
1205 | =head3 Character widths are not correct. |
495 | |
1206 | |
496 | =item Is there an option to switch encodings? |
1207 | urxvt uses the system wcwidth function to know the information about |
|
|
1208 | the width of characters, so on systems with incorrect locale data you |
|
|
1209 | will likely get bad results. Two notorious examples are Solaris 9, |
|
|
1210 | where single-width characters like U+2514 are reported as double-width, |
|
|
1211 | and Darwin 8, where combining chars are reported having width 1. |
497 | |
1212 | |
498 | Unlike some other terminals, rxvt-unicode has no encoding switch, and no |
1213 | The solution is to upgrade your system or switch to a better one. A |
499 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
1214 | possibly working workaround is to use a wcwidth implementation like |
500 | UTF-8 or any other encodings with respect to terminal I/O. |
|
|
501 | |
1215 | |
502 | The reasons is that there exists a perfectly fine mechanism for selecting |
1216 | http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c |
503 | the encoding, doing I/O and (most important) communicating this to all |
|
|
504 | applications so everybody agrees on character properties such as width |
|
|
505 | and code number. This mechanism is the I<locale>. Applications not using |
|
|
506 | that info will have problems (for example, C<xterm> gets the width of |
|
|
507 | characters wrong as it uses it's own, locale-independent table under all |
|
|
508 | locales). |
|
|
509 | |
1217 | |
510 | Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
|
|
511 | programs doing the same (that is, most) will automatically agree in the |
|
|
512 | interpretation of characters. |
|
|
513 | |
|
|
514 | Unfortunately, there is no system-independent way to select locales, nor |
|
|
515 | is there a standard on how locale specifiers will look like. |
|
|
516 | |
|
|
517 | On most systems, the content of the C<LC_CTYPE> environment variable |
|
|
518 | contains an arbitrary string which corresponds to an already-installed |
|
|
519 | locale. Common names for locales are C<en_US.UTF-8>, C<de_DE.ISO-8859-15>, |
|
|
520 | C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
|
|
521 | (i.e. C<de> or C<german>) are also common. |
|
|
522 | |
|
|
523 | Rxvt-unicode ignores all other locale categories, and except for |
|
|
524 | the encoding, ignores country or language-specific settings, |
|
|
525 | i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to |
|
|
526 | rxvt-unicode. |
|
|
527 | |
|
|
528 | 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. |
|
|
530 | |
|
|
531 | =item Can I switch locales at runtime? |
|
|
532 | |
|
|
533 | Yes, using an escape sequence. Try something like this, which sets |
|
|
534 | rxvt-unicode's idea of C<LC_CTYPE>. |
|
|
535 | |
|
|
536 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
537 | |
|
|
538 | See also the previous answer. |
|
|
539 | |
|
|
540 | Sometimes this capability is rather handy when you want to work in |
|
|
541 | one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it |
|
|
542 | (e.g. UTF-8). For example, I use this script to start C<xjdic>, which |
|
|
543 | first switches to a locale supported by xjdic and back later: |
|
|
544 | |
|
|
545 | printf '\e]701;%s\007' ja_JP.SJIS |
|
|
546 | xjdic -js |
|
|
547 | printf '\e]701;%s\007' de_DE.UTF-8 |
|
|
548 | |
|
|
549 | 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 |
|
|
551 | rxvt-unicode-locales. |
|
|
552 | |
|
|
553 | =item Can I switch the fonts at runtime? |
|
|
554 | |
|
|
555 | 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: |
|
|
557 | |
|
|
558 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
|
|
559 | |
|
|
560 | This is useful if you e.g. work primarily with japanese (and prefer a |
|
|
561 | japanese font), but you have to switch to chinese temporarily, where |
|
|
562 | japanese fonts would only be in your way. |
|
|
563 | |
|
|
564 | You can think of this as a kind of manual ISO-2022 switching. |
|
|
565 | |
|
|
566 | =item Why do italic characters look as if clipped? |
|
|
567 | |
|
|
568 | Many fonts have difficulties with italic characters and hinting. For |
|
|
569 | 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 |
|
|
571 | enable freetype autohinting, i.e. like this: |
|
|
572 | |
|
|
573 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
|
|
574 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
|
|
575 | |
|
|
576 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
|
|
577 | |
|
|
578 | You can specify separate locales for the input method and the rest of the |
|
|
579 | terminal, using the resource C<imlocale>: |
|
|
580 | |
|
|
581 | URxvt*imlocale: ja_JP.EUC-JP |
|
|
582 | |
|
|
583 | 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 |
|
|
585 | input characters outside C<EUC-JP> in a normal way then, as your input |
|
|
586 | method limits you. |
|
|
587 | |
|
|
588 | =item Rxvt-unicode crashes when the X Input Method changes or exits. |
|
|
589 | |
|
|
590 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
|
|
591 | design. Applications can avoid some crashes at the expense of memory |
|
|
592 | leaks, and Input Methods can avoid some crashes by careful ordering at |
|
|
593 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
|
|
594 | while B<SCIM> (or similar input methods) fails. In the end, however, |
|
|
595 | crashes cannot be completely avoided even if both sides cooperate. |
|
|
596 | |
|
|
597 | So the only workaround is not to kill your Input Method Servers. |
|
|
598 | |
|
|
599 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
|
|
600 | |
|
|
601 | 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 |
|
|
603 | 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 |
|
|
605 | accidentally when rxvt-unicode tries to find a font for your characters. |
|
|
606 | |
|
|
607 | Also, many people (me included) like large windows and even larger |
|
|
608 | scrollback buffers: Without C<--enable-unicode3>, rxvt-unicode will use |
|
|
609 | 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) |
|
|
611 | use 10 Megabytes of memory. With C<--enable-unicode3> it gets worse, as |
|
|
612 | rxvt-unicode then uses 8 bytes per screen cell. |
|
|
613 | |
|
|
614 | =item Can I speed up Xft rendering somehow? |
|
|
615 | |
|
|
616 | 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 |
|
|
618 | antialiasing (by appending C<:antialias=false>), which saves lots of |
|
|
619 | memory and also speeds up rendering considerably. |
|
|
620 | |
|
|
621 | =item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? |
|
|
622 | |
|
|
623 | 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 |
|
|
625 | 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 |
|
|
627 | look best that way. |
|
|
628 | |
|
|
629 | If you want antialiasing, you have to specify the fonts manually. |
|
|
630 | |
|
|
631 | =item Mouse cut/paste suddenly no longer works. |
|
|
632 | |
|
|
633 | 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 |
|
|
635 | 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 |
|
|
637 | depressed. See @@RXVT_NAME@@(7) |
|
|
638 | |
|
|
639 | =item What's with this bold/blink stuff? |
|
|
640 | |
|
|
641 | If no bold colour is set via C<colorBD:>, bold will invert text using the |
|
|
642 | standard foreground colour. |
|
|
643 | |
|
|
644 | For the standard background colour, blinking will actually make the |
|
|
645 | text blink when compiled with C<--enable-blinking>. with standard |
|
|
646 | colours. Without C<--enable-blinking>, the blink attribute will be |
|
|
647 | ignored. |
|
|
648 | |
|
|
649 | On ANSI colours, bold/blink attributes are used to set high-intensity |
|
|
650 | foreground/background colors. |
|
|
651 | |
|
|
652 | color0-7 are the low-intensity colors. |
|
|
653 | |
|
|
654 | color8-15 are the corresponding high-intensity colors. |
|
|
655 | |
|
|
656 | =item I don't like the screen colors. How do I change them? |
|
|
657 | |
|
|
658 | You can change the screen colors at run-time using F<~/.Xdefaults> |
|
|
659 | resources (or as long-options). |
|
|
660 | |
|
|
661 | Here are values that are supposed to resemble a VGA screen, |
|
|
662 | including the murky brown that passes for low-intensity yellow: |
|
|
663 | |
|
|
664 | URxvt.color0: #000000 |
|
|
665 | URxvt.color1: #A80000 |
|
|
666 | URxvt.color2: #00A800 |
|
|
667 | URxvt.color3: #A8A800 |
|
|
668 | URxvt.color4: #0000A8 |
|
|
669 | URxvt.color5: #A800A8 |
|
|
670 | URxvt.color6: #00A8A8 |
|
|
671 | URxvt.color7: #A8A8A8 |
|
|
672 | |
|
|
673 | URxvt.color8: #000054 |
|
|
674 | URxvt.color9: #FF0054 |
|
|
675 | URxvt.color10: #00FF54 |
|
|
676 | URxvt.color11: #FFFF54 |
|
|
677 | URxvt.color12: #0000FF |
|
|
678 | URxvt.color13: #FF00FF |
|
|
679 | URxvt.color14: #00FFFF |
|
|
680 | URxvt.color15: #FFFFFF |
|
|
681 | |
|
|
682 | And here is a more complete set of non-standard colors described (not by |
|
|
683 | me) as "pretty girly". |
|
|
684 | |
|
|
685 | URxvt.cursorColor: #dc74d1 |
|
|
686 | URxvt.pointerColor: #dc74d1 |
|
|
687 | URxvt.background: #0e0e0e |
|
|
688 | URxvt.foreground: #4ad5e1 |
|
|
689 | URxvt.color0: #000000 |
|
|
690 | URxvt.color8: #8b8f93 |
|
|
691 | URxvt.color1: #dc74d1 |
|
|
692 | URxvt.color9: #dc74d1 |
|
|
693 | URxvt.color2: #0eb8c7 |
|
|
694 | URxvt.color10: #0eb8c7 |
|
|
695 | URxvt.color3: #dfe37e |
|
|
696 | URxvt.color11: #dfe37e |
|
|
697 | URxvt.color5: #9e88f0 |
|
|
698 | URxvt.color13: #9e88f0 |
|
|
699 | URxvt.color6: #73f7ff |
|
|
700 | URxvt.color14: #73f7ff |
|
|
701 | URxvt.color7: #e1dddd |
|
|
702 | URxvt.color15: #e1dddd |
|
|
703 | |
|
|
704 | =item How can I start @@RXVT_NAME@@d in a race-free way? |
|
|
705 | |
|
|
706 | Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the |
|
|
707 | display, create the listening socket and then fork. |
|
|
708 | |
|
|
709 | =item What's with the strange Backspace/Delete key behaviour? |
|
|
710 | |
|
|
711 | Assuming that the physical Backspace key corresponds to the |
|
|
712 | BackSpace keysym (not likely for Linux ... see the following |
|
|
713 | question) there are two standard values that can be used for |
|
|
714 | Backspace: C<^H> and C<^?>. |
|
|
715 | |
|
|
716 | Historically, either value is correct, but rxvt-unicode adopts the debian |
|
|
717 | policy of using C<^?> when unsure, because it's the one only only correct |
|
|
718 | choice :). |
|
|
719 | |
|
|
720 | Rxvt-unicode tries to inherit the current stty settings and uses the value |
|
|
721 | of `erase' to guess the value for backspace. If rxvt-unicode wasn't |
|
|
722 | started from a terminal (say, from a menu or by remote shell), then the |
|
|
723 | system value of `erase', which corresponds to CERASE in <termios.h>, will |
|
|
724 | be used (which may not be the same as your stty setting). |
|
|
725 | |
|
|
726 | For starting a new rxvt-unicode: |
|
|
727 | |
|
|
728 | # use Backspace = ^H |
|
|
729 | $ stty erase ^H |
|
|
730 | $ @@RXVT_NAME@@ |
|
|
731 | |
|
|
732 | # use Backspace = ^? |
|
|
733 | $ stty erase ^? |
|
|
734 | $ @@RXVT_NAME@@ |
|
|
735 | |
|
|
736 | Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7). |
|
|
737 | |
|
|
738 | For an existing rxvt-unicode: |
|
|
739 | |
|
|
740 | # use Backspace = ^H |
|
|
741 | $ stty erase ^H |
|
|
742 | $ echo -n "^[[36h" |
|
|
743 | |
|
|
744 | # use Backspace = ^? |
|
|
745 | $ stty erase ^? |
|
|
746 | $ echo -n "^[[36l" |
|
|
747 | |
|
|
748 | This helps satisfy some of the Backspace discrepancies that occur, but |
|
|
749 | if you use Backspace = C<^H>, make sure that the termcap/terminfo value |
|
|
750 | properly reflects that. |
|
|
751 | |
|
|
752 | The Delete key is a another casualty of the ill-defined Backspace problem. |
|
|
753 | To avoid confusion between the Backspace and Delete keys, the Delete |
|
|
754 | key has been assigned an escape sequence to match the vt100 for Execute |
|
|
755 | (C<ESC [ 3 ~>) and is in the supplied termcap/terminfo. |
|
|
756 | |
|
|
757 | Some other Backspace problems: |
|
|
758 | |
|
|
759 | some editors use termcap/terminfo, |
|
|
760 | some editors (vim I'm told) expect Backspace = ^H, |
|
|
761 | GNU Emacs (and Emacs-like editors) use ^H for help. |
|
|
762 | |
|
|
763 | Perhaps someday this will all be resolved in a consistent manner. |
|
|
764 | |
|
|
765 | =item I don't like the key-bindings. How do I change them? |
|
|
766 | |
|
|
767 | There are some compile-time selections available via configure. Unless |
|
|
768 | you have run "configure" with the C<--disable-resources> option you can |
|
|
769 | use the `keysym' resource to alter the keystrings associated with keysyms. |
|
|
770 | |
|
|
771 | Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt> |
|
|
772 | |
|
|
773 | URxvt.keysym.Home: \033[1~ |
|
|
774 | URxvt.keysym.End: \033[4~ |
|
|
775 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
776 | URxvt.keysym.C-slash: \033<C-/> |
|
|
777 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
778 | URxvt.keysym.C-grave: \033<C-`> |
|
|
779 | URxvt.keysym.C-comma: \033<C-,> |
|
|
780 | URxvt.keysym.C-period: \033<C-.> |
|
|
781 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
782 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
783 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
784 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
785 | URxvt.keysym.S-space: \033<S-Space> |
|
|
786 | URxvt.keysym.M-Up: \033<M-Up> |
|
|
787 | URxvt.keysym.M-Down: \033<M-Down> |
|
|
788 | URxvt.keysym.M-Left: \033<M-Left> |
|
|
789 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
790 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
791 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
792 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
|
|
793 | |
|
|
794 | See some more examples in the documentation for the B<keysym> resource. |
|
|
795 | |
|
|
796 | =item 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 |
|
|
798 | has the following mappings that rxvt-unicode doesn't recognize. |
|
|
799 | |
|
|
800 | KP_Insert == Insert |
|
|
801 | F22 == Print |
|
|
802 | F27 == Home |
|
|
803 | F29 == Prior |
|
|
804 | F33 == End |
|
|
805 | F35 == Next |
|
|
806 | |
|
|
807 | 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 |
|
|
809 | required for your particular machine. |
|
|
810 | |
|
|
811 | =item How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
|
|
812 | I need this to decide about setting colors etc. |
|
|
813 | |
|
|
814 | 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, |
|
|
816 | Midnight Commander automatically check this variable to decide whether or |
|
|
817 | not to use color. |
|
|
818 | |
|
|
819 | =item How do I set the correct, full IP address for the DISPLAY variable? |
|
|
820 | |
|
|
821 | 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 |
|
|
823 | 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 |
|
|
825 | the COLORTERM variable can be used to distinguish rxvt-unicode from a |
|
|
826 | regular xterm. |
|
|
827 | |
|
|
828 | Courtesy of Chuck Blake <cblake@BBN.COM> with the following shell script |
|
|
829 | snippets: |
|
|
830 | |
|
|
831 | # Bourne/Korn/POSIX family of shells: |
|
|
832 | [ ${TERM:-foo} = foo ] && TERM=xterm # assume an xterm if we don't know |
|
|
833 | if [ ${TERM:-foo} = xterm ]; then |
|
|
834 | stty -icanon -echo min 0 time 15 # see if enhanced rxvt or not |
|
|
835 | echo -n '^[Z' |
|
|
836 | read term_id |
|
|
837 | stty icanon echo |
|
|
838 | if [ ""${term_id} = '^[[?1;2C' -a ${DISPLAY:-foo} = foo ]; then |
|
|
839 | echo -n '^[[7n' # query the rxvt we are in for the DISPLAY string |
|
|
840 | read DISPLAY # set it in our local shell |
|
|
841 | fi |
|
|
842 | fi |
|
|
843 | |
|
|
844 | =item How do I compile the manual pages for myself? |
|
|
845 | |
|
|
846 | 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 |
|
|
848 | the doc subdirectory and enter C<make alldoc>. |
|
|
849 | |
|
|
850 | =item My question isn't answered here, can I ask a human? |
|
|
851 | |
|
|
852 | 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 |
|
|
854 | interested in learning about new and exciting problems (but not FAQs :). |
|
|
855 | |
|
|
856 | =back |
|
|
857 | |
|
|
858 | =head1 RXVT TECHNICAL REFERENCE |
1218 | =head1 RXVT-UNICODE TECHNICAL REFERENCE |
859 | |
|
|
860 | =head1 DESCRIPTION |
|
|
861 | |
1219 | |
862 | The rest of this document describes various technical aspects of |
1220 | The rest of this document describes various technical aspects of |
863 | B<rxvt-unicode>. First the description of supported command sequences, |
1221 | B<rxvt-unicode>. First the description of supported command sequences, |
864 | followed by menu and pixmap support and last by a description of all |
1222 | followed by pixmap support and last by a description of all features |
865 | features selectable at C<configure> time. |
1223 | selectable at C<configure> time. |
866 | |
1224 | |
867 | =head1 Definitions |
1225 | =head2 Definitions |
868 | |
1226 | |
869 | =over 4 |
1227 | =over 4 |
870 | |
1228 | |
871 | =item B<< C<c> >> |
1229 | =item B<< C<c> >> |
872 | |
1230 | |
… | |
… | |
890 | |
1248 | |
891 | A text parameter composed of printable characters. |
1249 | A text parameter composed of printable characters. |
892 | |
1250 | |
893 | =back |
1251 | =back |
894 | |
1252 | |
895 | =head1 Values |
1253 | =head2 Values |
896 | |
1254 | |
897 | =over 4 |
1255 | =over 4 |
898 | |
1256 | |
899 | =item B<< C<ENQ> >> |
1257 | =item B<< C<ENQ> >> |
900 | |
1258 | |
… | |
… | |
943 | |
1301 | |
944 | Space Character |
1302 | Space Character |
945 | |
1303 | |
946 | =back |
1304 | =back |
947 | |
1305 | |
948 | =head1 Escape Sequences |
1306 | =head2 Escape Sequences |
949 | |
1307 | |
950 | =over 4 |
1308 | =over 4 |
951 | |
1309 | |
952 | =item B<< C<ESC # 8> >> |
1310 | =item B<< C<ESC # 8> >> |
953 | |
1311 | |
… | |
… | |
1051 | |
1409 | |
1052 | =back |
1410 | =back |
1053 | |
1411 | |
1054 | X<CSI> |
1412 | X<CSI> |
1055 | |
1413 | |
1056 | =head1 CSI (Command Sequence Introducer) Sequences |
1414 | =head2 CSI (Command Sequence Introducer) Sequences |
1057 | |
1415 | |
1058 | =over 4 |
1416 | =over 4 |
1059 | |
1417 | |
1060 | =item B<< C<ESC [ Ps @> >> |
1418 | =item B<< C<ESC [ Ps @> >> |
1061 | |
1419 | |
… | |
… | |
1331 | |
1689 | |
1332 | =back |
1690 | =back |
1333 | |
1691 | |
1334 | X<PrivateModes> |
1692 | X<PrivateModes> |
1335 | |
1693 | |
1336 | =head1 DEC Private Modes |
1694 | =head2 DEC Private Modes |
1337 | |
1695 | |
1338 | =over 4 |
1696 | =over 4 |
1339 | |
1697 | |
1340 | =item B<< C<ESC [ ? Pm h> >> |
1698 | =item B<< C<ESC [ ? Pm h> >> |
1341 | |
1699 | |
… | |
… | |
1357 | |
1715 | |
1358 | Toggle DEC Private Mode Values (rxvt extension). I<where> |
1716 | Toggle DEC Private Mode Values (rxvt extension). I<where> |
1359 | |
1717 | |
1360 | =over 4 |
1718 | =over 4 |
1361 | |
1719 | |
1362 | =item B<< C<Ps = 1> >> (DECCKM) |
1720 | =item B<< C<Pm = 1> >> (DECCKM) |
1363 | |
1721 | |
1364 | =begin table |
1722 | =begin table |
1365 | |
1723 | |
1366 | B<< C<h> >> Application Cursor Keys |
1724 | B<< C<h> >> Application Cursor Keys |
1367 | B<< C<l> >> Normal Cursor Keys |
1725 | B<< C<l> >> Normal Cursor Keys |
1368 | |
1726 | |
1369 | =end table |
1727 | =end table |
1370 | |
1728 | |
1371 | =item B<< C<Ps = 2> >> (ANSI/VT52 mode) |
1729 | =item B<< C<Pm = 2> >> (ANSI/VT52 mode) |
1372 | |
1730 | |
1373 | =begin table |
1731 | =begin table |
1374 | |
1732 | |
1375 | B<< C<h> >> Enter VT52 mode |
1733 | B<< C<h> >> Enter VT52 mode |
1376 | B<< C<l> >> Enter VT52 mode |
1734 | B<< C<l> >> Enter VT52 mode |
1377 | |
1735 | |
1378 | =end table |
1736 | =end table |
1379 | |
1737 | |
1380 | =item B<< C<Ps = 3> >> |
1738 | =item B<< C<Pm = 3> >> |
1381 | |
1739 | |
1382 | =begin table |
1740 | =begin table |
1383 | |
1741 | |
1384 | B<< C<h> >> 132 Column Mode (DECCOLM) |
1742 | B<< C<h> >> 132 Column Mode (DECCOLM) |
1385 | B<< C<l> >> 80 Column Mode (DECCOLM) |
1743 | B<< C<l> >> 80 Column Mode (DECCOLM) |
1386 | |
1744 | |
1387 | =end table |
1745 | =end table |
1388 | |
1746 | |
1389 | =item B<< C<Ps = 4> >> |
1747 | =item B<< C<Pm = 4> >> |
1390 | |
1748 | |
1391 | =begin table |
1749 | =begin table |
1392 | |
1750 | |
1393 | B<< C<h> >> Smooth (Slow) Scroll (DECSCLM) |
1751 | B<< C<h> >> Smooth (Slow) Scroll (DECSCLM) |
1394 | B<< C<l> >> Jump (Fast) Scroll (DECSCLM) |
1752 | B<< C<l> >> Jump (Fast) Scroll (DECSCLM) |
1395 | |
1753 | |
1396 | =end table |
1754 | =end table |
1397 | |
1755 | |
1398 | =item B<< C<Ps = 5> >> |
1756 | =item B<< C<Pm = 5> >> |
1399 | |
1757 | |
1400 | =begin table |
1758 | =begin table |
1401 | |
1759 | |
1402 | B<< C<h> >> Reverse Video (DECSCNM) |
1760 | B<< C<h> >> Reverse Video (DECSCNM) |
1403 | B<< C<l> >> Normal Video (DECSCNM) |
1761 | B<< C<l> >> Normal Video (DECSCNM) |
1404 | |
1762 | |
1405 | =end table |
1763 | =end table |
1406 | |
1764 | |
1407 | =item B<< C<Ps = 6> >> |
1765 | =item B<< C<Pm = 6> >> |
1408 | |
1766 | |
1409 | =begin table |
1767 | =begin table |
1410 | |
1768 | |
1411 | B<< C<h> >> Origin Mode (DECOM) |
1769 | B<< C<h> >> Origin Mode (DECOM) |
1412 | B<< C<l> >> Normal Cursor Mode (DECOM) |
1770 | B<< C<l> >> Normal Cursor Mode (DECOM) |
1413 | |
1771 | |
1414 | =end table |
1772 | =end table |
1415 | |
1773 | |
1416 | =item B<< C<Ps = 7> >> |
1774 | =item B<< C<Pm = 7> >> |
1417 | |
1775 | |
1418 | =begin table |
1776 | =begin table |
1419 | |
1777 | |
1420 | B<< C<h> >> Wraparound Mode (DECAWM) |
1778 | B<< C<h> >> Wraparound Mode (DECAWM) |
1421 | B<< C<l> >> No Wraparound Mode (DECAWM) |
1779 | B<< C<l> >> No Wraparound Mode (DECAWM) |
1422 | |
1780 | |
1423 | =end table |
1781 | =end table |
1424 | |
1782 | |
1425 | =item B<< C<Ps = 8> >> I<unimplemented> |
1783 | =item B<< C<Pm = 8> >> I<unimplemented> |
1426 | |
1784 | |
1427 | =begin table |
1785 | =begin table |
1428 | |
1786 | |
1429 | B<< C<h> >> Auto-repeat Keys (DECARM) |
1787 | B<< C<h> >> Auto-repeat Keys (DECARM) |
1430 | B<< C<l> >> No Auto-repeat Keys (DECARM) |
1788 | B<< C<l> >> No Auto-repeat Keys (DECARM) |
1431 | |
1789 | |
1432 | =end table |
1790 | =end table |
1433 | |
1791 | |
1434 | =item B<< C<Ps = 9> >> X10 XTerm |
1792 | =item B<< C<Pm = 9> >> X10 XTerm |
1435 | |
1793 | |
1436 | =begin table |
1794 | =begin table |
1437 | |
1795 | |
1438 | B<< C<h> >> Send Mouse X & Y on button press. |
1796 | B<< C<h> >> Send Mouse X & Y on button press. |
1439 | B<< C<l> >> No mouse reporting. |
1797 | B<< C<l> >> No mouse reporting. |
1440 | |
1798 | |
1441 | =end table |
1799 | =end table |
1442 | |
1800 | |
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> >> |
1801 | =item B<< C<Pm = 25> >> |
1453 | |
1802 | |
1454 | =begin table |
1803 | =begin table |
1455 | |
1804 | |
1456 | B<< C<h> >> Visible cursor {cnorm/cvvis} |
1805 | B<< C<h> >> Visible cursor {cnorm/cvvis} |
1457 | B<< C<l> >> Invisible cursor {civis} |
1806 | B<< C<l> >> Invisible cursor {civis} |
1458 | |
1807 | |
1459 | =end table |
1808 | =end table |
1460 | |
1809 | |
1461 | =item B<< C<Ps = 30> >> |
1810 | =item B<< C<Pm = 30> >> |
1462 | |
1811 | |
1463 | =begin table |
1812 | =begin table |
1464 | |
1813 | |
1465 | B<< C<h> >> scrollBar visisble |
1814 | B<< C<h> >> scrollBar visisble |
1466 | B<< C<l> >> scrollBar invisisble |
1815 | B<< C<l> >> scrollBar invisisble |
1467 | |
1816 | |
1468 | =end table |
1817 | =end table |
1469 | |
1818 | |
1470 | =item B<< C<Ps = 35> >> (B<rxvt>) |
1819 | =item B<< C<Pm = 35> >> (B<rxvt>) |
1471 | |
1820 | |
1472 | =begin table |
1821 | =begin table |
1473 | |
1822 | |
1474 | B<< C<h> >> Allow XTerm Shift+key sequences |
1823 | B<< C<h> >> Allow XTerm Shift+key sequences |
1475 | B<< C<l> >> Disallow XTerm Shift+key sequences |
1824 | B<< C<l> >> Disallow XTerm Shift+key sequences |
1476 | |
1825 | |
1477 | =end table |
1826 | =end table |
1478 | |
1827 | |
1479 | =item B<< C<Ps = 38> >> I<unimplemented> |
1828 | =item B<< C<Pm = 38> >> I<unimplemented> |
1480 | |
1829 | |
1481 | Enter Tektronix Mode (DECTEK) |
1830 | Enter Tektronix Mode (DECTEK) |
1482 | |
1831 | |
1483 | =item B<< C<Ps = 40> >> |
1832 | =item B<< C<Pm = 40> >> |
1484 | |
1833 | |
1485 | =begin table |
1834 | =begin table |
1486 | |
1835 | |
1487 | B<< C<h> >> Allow 80/132 Mode |
1836 | B<< C<h> >> Allow 80/132 Mode |
1488 | B<< C<l> >> Disallow 80/132 Mode |
1837 | B<< C<l> >> Disallow 80/132 Mode |
1489 | |
1838 | |
1490 | =end table |
1839 | =end table |
1491 | |
1840 | |
1492 | =item B<< C<Ps = 44> >> I<unimplemented> |
1841 | =item B<< C<Pm = 44> >> I<unimplemented> |
1493 | |
1842 | |
1494 | =begin table |
1843 | =begin table |
1495 | |
1844 | |
1496 | B<< C<h> >> Turn On Margin Bell |
1845 | B<< C<h> >> Turn On Margin Bell |
1497 | B<< C<l> >> Turn Off Margin Bell |
1846 | B<< C<l> >> Turn Off Margin Bell |
1498 | |
1847 | |
1499 | =end table |
1848 | =end table |
1500 | |
1849 | |
1501 | =item B<< C<Ps = 45> >> I<unimplemented> |
1850 | =item B<< C<Pm = 45> >> I<unimplemented> |
1502 | |
1851 | |
1503 | =begin table |
1852 | =begin table |
1504 | |
1853 | |
1505 | B<< C<h> >> Reverse-wraparound Mode |
1854 | B<< C<h> >> Reverse-wraparound Mode |
1506 | B<< C<l> >> No Reverse-wraparound Mode |
1855 | B<< C<l> >> No Reverse-wraparound Mode |
1507 | |
1856 | |
1508 | =end table |
1857 | =end table |
1509 | |
1858 | |
1510 | =item B<< C<Ps = 46> >> I<unimplemented> |
1859 | =item B<< C<Pm = 46> >> I<unimplemented> |
1511 | |
1860 | |
1512 | =item B<< C<Ps = 47> >> |
1861 | =item B<< C<Pm = 47> >> |
1513 | |
1862 | |
1514 | =begin table |
1863 | =begin table |
1515 | |
1864 | |
1516 | B<< C<h> >> Use Alternate Screen Buffer |
1865 | B<< C<h> >> Use Alternate Screen Buffer |
1517 | B<< C<l> >> Use Normal Screen Buffer |
1866 | B<< C<l> >> Use Normal Screen Buffer |
1518 | |
1867 | |
1519 | =end table |
1868 | =end table |
1520 | |
1869 | |
1521 | X<Priv66> |
1870 | X<Priv66> |
1522 | |
1871 | |
1523 | =item B<< C<Ps = 66> >> |
1872 | =item B<< C<Pm = 66> >> |
1524 | |
1873 | |
1525 | =begin table |
1874 | =begin table |
1526 | |
1875 | |
1527 | B<< C<h> >> Application Keypad (DECPAM) == C<ESC => |
1876 | B<< C<h> >> Application Keypad (DECPAM) == C<ESC => |
1528 | B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >> |
1877 | B<< C<l> >> Normal Keypad (DECPNM) == C<< ESC > >> |
1529 | |
1878 | |
1530 | =end table |
1879 | =end table |
1531 | |
1880 | |
1532 | =item B<< C<Ps = 67> >> |
1881 | =item B<< C<Pm = 67> >> |
1533 | |
1882 | |
1534 | =begin table |
1883 | =begin table |
1535 | |
1884 | |
1536 | B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >> |
1885 | B<< C<h> >> Backspace key sends B<< C<BS> (DECBKM) >> |
1537 | B<< C<l> >> Backspace key sends B<< C<DEL> >> |
1886 | B<< C<l> >> Backspace key sends B<< C<DEL> >> |
1538 | |
1887 | |
1539 | =end table |
1888 | =end table |
1540 | |
1889 | |
1541 | =item B<< C<Ps = 1000> >> (X11 XTerm) |
1890 | =item B<< C<Pm = 1000> >> (X11 XTerm) |
1542 | |
1891 | |
1543 | =begin table |
1892 | =begin table |
1544 | |
1893 | |
1545 | B<< C<h> >> Send Mouse X & Y on button press and release. |
1894 | B<< C<h> >> Send Mouse X & Y on button press and release. |
1546 | B<< C<l> >> No mouse reporting. |
1895 | B<< C<l> >> No mouse reporting. |
1547 | |
1896 | |
1548 | =end table |
1897 | =end table |
1549 | |
1898 | |
1550 | =item B<< C<Ps = 1001> >> (X11 XTerm) I<unimplemented> |
1899 | =item B<< C<Pm = 1001> >> (X11 XTerm) I<unimplemented> |
1551 | |
1900 | |
1552 | =begin table |
1901 | =begin table |
1553 | |
1902 | |
1554 | B<< C<h> >> Use Hilite Mouse Tracking. |
1903 | B<< C<h> >> Use Hilite Mouse Tracking. |
1555 | B<< C<l> >> No mouse reporting. |
1904 | B<< C<l> >> No mouse reporting. |
1556 | |
1905 | |
1557 | =end table |
1906 | =end table |
1558 | |
1907 | |
|
|
1908 | =item B<< C<Pm = 1002> >> (X11 XTerm) |
|
|
1909 | |
|
|
1910 | =begin table |
|
|
1911 | |
|
|
1912 | B<< C<h> >> Send Mouse X & Y on button press and release, and motion with a button pressed. |
|
|
1913 | B<< C<l> >> No mouse reporting. |
|
|
1914 | |
|
|
1915 | =end table |
|
|
1916 | |
|
|
1917 | =item B<< C<Pm = 1003> >> (X11 XTerm) |
|
|
1918 | |
|
|
1919 | =begin table |
|
|
1920 | |
|
|
1921 | B<< C<h> >> Send Mouse X & Y on button press and release, and motion. |
|
|
1922 | B<< C<l> >> No mouse reporting. |
|
|
1923 | |
|
|
1924 | =end table |
|
|
1925 | |
1559 | =item B<< C<Ps = 1010> >> (B<rxvt>) |
1926 | =item B<< C<Pm = 1010> >> (B<rxvt>) |
1560 | |
1927 | |
1561 | =begin table |
1928 | =begin table |
1562 | |
1929 | |
1563 | B<< C<h> >> Don't scroll to bottom on TTY output |
1930 | B<< C<h> >> Don't scroll to bottom on TTY output |
1564 | B<< C<l> >> Scroll to bottom on TTY output |
1931 | B<< C<l> >> Scroll to bottom on TTY output |
1565 | |
1932 | |
1566 | =end table |
1933 | =end table |
1567 | |
1934 | |
1568 | =item B<< C<Ps = 1011> >> (B<rxvt>) |
1935 | =item B<< C<Pm = 1011> >> (B<rxvt>) |
1569 | |
1936 | |
1570 | =begin table |
1937 | =begin table |
1571 | |
1938 | |
1572 | B<< C<h> >> Scroll to bottom when a key is pressed |
1939 | B<< C<h> >> Scroll to bottom when a key is pressed |
1573 | B<< C<l> >> Don't scroll to bottom when a key is pressed |
1940 | B<< C<l> >> Don't scroll to bottom when a key is pressed |
1574 | |
1941 | |
1575 | =end table |
1942 | =end table |
1576 | |
1943 | |
1577 | =item B<< C<Ps = 1021> >> (B<rxvt>) |
1944 | =item B<< C<Pm = 1021> >> (B<rxvt>) |
1578 | |
1945 | |
1579 | =begin table |
1946 | =begin table |
1580 | |
1947 | |
1581 | B<< C<h> >> Bold/italic implies high intensity (see option B<-is>) |
1948 | B<< C<h> >> Bold/italic implies high intensity (see option B<-is>) |
1582 | B<< C<l> >> Font styles have no effect on intensity (Compile styles) |
1949 | B<< C<l> >> Font styles have no effect on intensity (Compile styles) |
1583 | |
1950 | |
1584 | =end table |
1951 | =end table |
1585 | |
1952 | |
1586 | =item B<< C<Ps = 1047> >> |
1953 | =item B<< C<Pm = 1047> >> |
1587 | |
1954 | |
1588 | =begin table |
1955 | =begin table |
1589 | |
1956 | |
1590 | B<< C<h> >> Use Alternate Screen Buffer |
1957 | B<< C<h> >> Use Alternate Screen Buffer |
1591 | B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it |
1958 | B<< C<l> >> Use Normal Screen Buffer - clear Alternate Screen Buffer if returning from it |
1592 | |
1959 | |
1593 | =end table |
1960 | =end table |
1594 | |
1961 | |
1595 | =item B<< C<Ps = 1048> >> |
1962 | =item B<< C<Pm = 1048> >> |
1596 | |
1963 | |
1597 | =begin table |
1964 | =begin table |
1598 | |
1965 | |
1599 | B<< C<h> >> Save cursor position |
1966 | B<< C<h> >> Save cursor position |
1600 | B<< C<l> >> Restore cursor position |
1967 | B<< C<l> >> Restore cursor position |
1601 | |
1968 | |
1602 | =end table |
1969 | =end table |
1603 | |
1970 | |
1604 | =item B<< C<Ps = 1049> >> |
1971 | =item B<< C<Pm = 1049> >> |
1605 | |
1972 | |
1606 | =begin table |
1973 | =begin table |
1607 | |
1974 | |
1608 | B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it |
1975 | B<< C<h> >> Use Alternate Screen Buffer - clear Alternate Screen Buffer if switching to it |
1609 | B<< C<l> >> Use Normal Screen Buffer |
1976 | B<< C<l> >> Use Normal Screen Buffer |
… | |
… | |
1614 | |
1981 | |
1615 | =back |
1982 | =back |
1616 | |
1983 | |
1617 | X<XTerm> |
1984 | X<XTerm> |
1618 | |
1985 | |
1619 | =head1 XTerm Operating System Commands |
1986 | =head2 XTerm Operating System Commands |
1620 | |
1987 | |
1621 | =over 4 |
1988 | =over 4 |
1622 | |
1989 | |
1623 | =item B<< C<ESC ] Ps;Pt ST> >> |
1990 | =item B<< C<ESC ] Ps;Pt ST> >> |
1624 | |
1991 | |
… | |
… | |
1638 | B<< C<Ps = 12> >> Change colour of text cursor foreground to B<< C<Pt> >> |
2005 | 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> >> |
2006 | 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> >> |
2007 | 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] |
2008 | 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] |
2009 | 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> >> |
2010 | B<< C<Ps = 20> >> Change background pixmap parameters (see section BACKGROUND IMAGE) (Compile AfterImage). |
1644 | B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>. |
2011 | 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> |
2012 | 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> >>. |
2013 | 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> >> |
2014 | 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> >> |
2015 | 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). |
2016 | 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). |
2017 | 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> >> |
2018 | 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). |
2019 | 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> >> |
2020 | 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> >> |
2021 | 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>. |
2022 | B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>. |
… | |
… | |
1662 | |
2029 | |
1663 | =end table |
2030 | =end table |
1664 | |
2031 | |
1665 | =back |
2032 | =back |
1666 | |
2033 | |
1667 | X<menuBar> |
2034 | =head1 BACKGROUND IMAGE |
1668 | |
2035 | |
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> |
|
|
2134 | |
|
|
2135 | =head1 XPM |
|
|
2136 | |
|
|
2137 | For the XPM XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value |
2036 | For the BACGROUND IMAGE XTerm escape sequence B<< C<ESC ] 20 ; Pt ST> >> then value |
2138 | of B<< C<Pt> >> can be the name of the background pixmap followed by a |
2037 | of B<< C<Pt> >> can be the name of the background image file followed by a |
2139 | sequence of scaling/positioning commands separated by semi-colons. The |
2038 | sequence of scaling/positioning commands separated by semi-colons. The |
2140 | scaling/positioning commands are as follows: |
2039 | scaling/positioning commands are as follows: |
2141 | |
2040 | |
2142 | =over 4 |
2041 | =over 4 |
2143 | |
2042 | |
… | |
… | |
2181 | |
2080 | |
2182 | For example: |
2081 | For example: |
2183 | |
2082 | |
2184 | =over 4 |
2083 | =over 4 |
2185 | |
2084 | |
2186 | =item B<\E]20;funky\a> |
2085 | =item B<\E]20;funky.jpg\a> |
2187 | |
2086 | |
2188 | load B<funky.xpm> as a tiled image |
2087 | load B<funky.jpg> as a tiled image |
2189 | |
2088 | |
2190 | =item B<\E]20;mona;100\a> |
2089 | =item B<\E]20;mona.jpg;100\a> |
2191 | |
2090 | |
2192 | load B<mona.xpm> with a scaling of 100% |
2091 | load B<mona.jpg> with a scaling of 100% |
2193 | |
2092 | |
2194 | =item B<\E]20;;200;?\a> |
2093 | =item B<\E]20;;200;?\a> |
2195 | |
2094 | |
2196 | rescale the current pixmap to 200% and display the image geometry in |
2095 | rescale the current pixmap to 200% and display the image geometry in |
2197 | the title |
2096 | the title |
… | |
… | |
2236 | =begin table |
2135 | =begin table |
2237 | |
2136 | |
2238 | 4 Shift |
2137 | 4 Shift |
2239 | 8 Meta |
2138 | 8 Meta |
2240 | 16 Control |
2139 | 16 Control |
2241 | 32 Double Click I<(Rxvt extension)> |
2140 | 32 Double Click I<(rxvt extension)> |
2242 | |
2141 | |
2243 | =end table |
2142 | =end table |
2244 | |
2143 | |
2245 | Col = B<< C<< <x> - SPACE >> >> |
2144 | Col = B<< C<< <x> - SPACE >> >> |
2246 | |
2145 | |
… | |
… | |
2324 | |
2223 | |
2325 | =head1 CONFIGURE OPTIONS |
2224 | =head1 CONFIGURE OPTIONS |
2326 | |
2225 | |
2327 | General hint: if you get compile errors, then likely your configuration |
2226 | General hint: if you get compile errors, then likely your configuration |
2328 | hasn't been tested well. Either try with C<--enable-everything> or use |
2227 | hasn't been tested well. Either try with C<--enable-everything> or use |
2329 | the F<./reconf> script as a base for experiments. F<./reconf> is used by |
2228 | the default configuration (i.e. no C<--enable-xxx> or C<--disable-xxx> |
2330 | myself, so it should generally be a working config. Of course, you should |
2229 | switches). Of course, you should always report when a combination doesn't |
2331 | always report when a combination doesn't work, so it can be fixed. Marc |
2230 | work, so it can be fixed. Marc Lehmann <rxvt@schmorp.de>. |
2332 | Lehmann <rxvt@schmorp.de>. |
|
|
2333 | |
2231 | |
2334 | All |
2232 | All |
2335 | |
2233 | |
2336 | =over 4 |
2234 | =over 4 |
2337 | |
2235 | |
… | |
… | |
2369 | |
2267 | |
2370 | =begin table |
2268 | =begin table |
2371 | |
2269 | |
2372 | all all available codeset groups |
2270 | all all available codeset groups |
2373 | zh common chinese encodings |
2271 | zh common chinese encodings |
2374 | zh_ext rarely used but very big chinese encodigs |
2272 | zh_ext rarely used but very big chinese encodings |
2375 | jp common japanese encodings |
2273 | jp common japanese encodings |
2376 | jp_ext rarely used but big japanese encodings |
2274 | jp_ext rarely used but big japanese encodings |
2377 | kr korean encodings |
2275 | kr korean encodings |
2378 | |
2276 | |
2379 | =end table |
2277 | =end table |
… | |
… | |
2383 | Add support for XIM (X Input Method) protocol. This allows using |
2281 | Add support for XIM (X Input Method) protocol. This allows using |
2384 | alternative input methods (e.g. kinput2) and will also correctly |
2282 | alternative input methods (e.g. kinput2) and will also correctly |
2385 | set up the input for people using dead keys or compose keys. |
2283 | set up the input for people using dead keys or compose keys. |
2386 | |
2284 | |
2387 | =item --enable-unicode3 (default: off) |
2285 | =item --enable-unicode3 (default: off) |
|
|
2286 | |
|
|
2287 | Recommended to stay off unless you really need non-BMP characters. |
2388 | |
2288 | |
2389 | Enable direct support for displaying unicode codepoints above |
2289 | Enable direct support for displaying unicode codepoints above |
2390 | 65535 (the basic multilingual page). This increases storage |
2290 | 65535 (the basic multilingual page). This increases storage |
2391 | requirements per character from 2 to 4 bytes. X11 fonts do not yet |
2291 | requirements per character from 2 to 4 bytes. X11 fonts do not yet |
2392 | support these extra characters, but Xft does. |
2292 | support these extra characters, but Xft does. |
2393 | |
2293 | |
2394 | Please note that rxvt-unicode can store unicode code points >65535 |
2294 | Please note that rxvt-unicode can store unicode code points >65535 |
2395 | even without this flag, but the number of such characters is |
2295 | even without this flag, but the number of such characters is |
2396 | limited to a view thousand (shared with combining characters, |
2296 | limited to a few thousand (shared with combining characters, |
2397 | see next switch), and right now rxvt-unicode cannot display them |
2297 | see next switch), and right now rxvt-unicode cannot display them |
2398 | (input/output and cut&paste still work, though). |
2298 | (input/output and cut&paste still work, though). |
2399 | |
2299 | |
2400 | =item --enable-combining (default: on) |
2300 | =item --enable-combining (default: on) |
2401 | |
2301 | |
… | |
… | |
2403 | composite characters. This is required for proper viewing of text |
2303 | composite characters. This is required for proper viewing of text |
2404 | where accents are encoded as seperate unicode characters. This is |
2304 | where accents are encoded as seperate unicode characters. This is |
2405 | done by using precomposited characters when available or creating |
2305 | done by using precomposited characters when available or creating |
2406 | new pseudo-characters when no precomposed form exists. |
2306 | new pseudo-characters when no precomposed form exists. |
2407 | |
2307 | |
2408 | Without --enable-unicode3, the number of additional precomposed characters |
2308 | Without --enable-unicode3, the number of additional precomposed |
2409 | is rather limited (2048, if this is full, rxvt-unicode will use the |
2309 | 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. |
2310 | (ab-)used). With --enable-unicode3, no practical limit exists. |
2412 | |
2311 | |
2413 | This option will also enable storage (but not display) of characters |
2312 | This option will also enable storage (but not display) of characters |
2414 | beyond plane 0 (>65535) when --enable-unicode3 was not specified. |
2313 | beyond plane 0 (>65535) when --enable-unicode3 was not specified. |
2415 | |
2314 | |
2416 | The combining table also contains entries for arabic presentation forms, |
2315 | 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 |
2316 | 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...). |
2317 | tell me how these are to be used...). |
2419 | |
2318 | |
2420 | =item --enable-fallback(=CLASS) (default: Rxvt) |
2319 | =item --enable-fallback(=CLASS) (default: Rxvt) |
2421 | |
2320 | |
2422 | When reading resource settings, also read settings for class CLASS. To disable resource fallback use --disable-fallback. |
2321 | When reading resource settings, also read settings for class CLASS. To |
|
|
2322 | disable resource fallback use --disable-fallback. |
2423 | |
2323 | |
2424 | =item --with-res-name=NAME (default: urxvt) |
2324 | =item --with-res-name=NAME (default: urxvt) |
2425 | |
2325 | |
2426 | Use the given name as default application name when |
2326 | Use the given name as default application name when |
2427 | reading resources. Specify --with-res-name=rxvt to replace rxvt. |
2327 | reading resources. Specify --with-res-name=rxvt to replace rxvt. |
2428 | |
2328 | |
2429 | =item --with-res-class=CLASS /default: URxvt) |
2329 | =item --with-res-class=CLASS (default: URxvt) |
2430 | |
2330 | |
2431 | Use the given class as default application class |
2331 | Use the given class as default application class |
2432 | when reading resources. Specify --with-res-class=Rxvt to replace |
2332 | when reading resources. Specify --with-res-class=Rxvt to replace |
2433 | rxvt. |
2333 | rxvt. |
2434 | |
2334 | |
… | |
… | |
2447 | |
2347 | |
2448 | Write user and tty to lastlog file (used by programs like |
2348 | Write user and tty to lastlog file (used by programs like |
2449 | F<lastlogin>) at start of rxvt execution. This option requires |
2349 | F<lastlogin>) at start of rxvt execution. This option requires |
2450 | --enable-utmp to also be specified. |
2350 | --enable-utmp to also be specified. |
2451 | |
2351 | |
2452 | =item --enable-xpm-background (default: on) |
2352 | =item --enable-afterimage (default: on) |
2453 | |
2353 | |
2454 | Add support for XPM background pixmaps. |
2354 | Add support for libAfterImage to be used for transparency and background |
|
|
2355 | images. It adds support for many file formats including JPG, PNG, |
|
|
2356 | SVG, TIFF, GIF, XPM, BMP, ICO, XCF, TGA and AfterStep image XML |
|
|
2357 | (L<http://www.afterstep.org/visualdoc.php?show=asimagexml>). |
|
|
2358 | |
|
|
2359 | This option also adds such eye candy as blending an image over the root |
|
|
2360 | background, as well as dynamic scaling and bluring of background images. |
|
|
2361 | |
|
|
2362 | Note that with this option enabled, @@RXVT_NAME@@'s memory footprint might |
|
|
2363 | increase by a few megabytes even if no extra features are used (mostly due |
|
|
2364 | to third-party libraries used by libAI). Memory footprint may somewhat be |
|
|
2365 | lowered if libAfterImage is configured without support for SVG. |
2455 | |
2366 | |
2456 | =item --enable-transparency (default: on) |
2367 | =item --enable-transparency (default: on) |
2457 | |
2368 | |
2458 | Add support for inheriting parent backgrounds thus giving a fake |
2369 | Add support for backgrounds, creating illusion of transparency in the term. |
2459 | transparency to the term. |
|
|
2460 | |
2370 | |
2461 | =item --enable-fading (default: on) |
2371 | =item --enable-fading (default: on) |
2462 | |
2372 | |
2463 | Add support for fading the text when focus is lost (requires C<--enable-transparency>). |
2373 | Add support for fading the text when focus is lost. |
2464 | |
|
|
2465 | =item --enable-tinting (default: on) |
|
|
2466 | |
|
|
2467 | Add support for tinting of transparent backgrounds (requires C<--enable-transparency>). |
|
|
2468 | |
|
|
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 | |
2374 | |
2475 | =item --enable-rxvt-scroll (default: on) |
2375 | =item --enable-rxvt-scroll (default: on) |
2476 | |
2376 | |
2477 | Add support for the original rxvt scrollbar. |
2377 | Add support for the original rxvt scrollbar. |
2478 | |
2378 | |
… | |
… | |
2488 | |
2388 | |
2489 | Add support for a very unobtrusive, plain-looking scrollbar that |
2389 | Add support for a very unobtrusive, plain-looking scrollbar that |
2490 | is the favourite of the rxvt-unicode author, having used it for |
2390 | is the favourite of the rxvt-unicode author, having used it for |
2491 | many years. |
2391 | many years. |
2492 | |
2392 | |
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) |
|
|
2499 | |
|
|
2500 | Change tty device setting to group "tty" - only use this if |
|
|
2501 | your system uses this type of security. |
|
|
2502 | |
|
|
2503 | =item --disable-backspace-key |
2393 | =item --disable-backspace-key |
2504 | |
2394 | |
2505 | Removes any handling of the backspace key by us - let the X server do it. |
2395 | Removes any handling of the backspace key by us - let the X server do it. |
2506 | |
2396 | |
2507 | =item --disable-delete-key |
2397 | =item --disable-delete-key |
… | |
… | |
2510 | do it. |
2400 | do it. |
2511 | |
2401 | |
2512 | =item --disable-resources |
2402 | =item --disable-resources |
2513 | |
2403 | |
2514 | Removes any support for resource checking. |
2404 | 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 | |
2405 | |
2534 | =item --disable-swapscreen |
2406 | =item --disable-swapscreen |
2535 | |
2407 | |
2536 | Remove support for secondary/swap screen. |
2408 | Remove support for secondary/swap screen. |
2537 | |
2409 | |
… | |
… | |
2544 | A non-exhaustive list of features enabled by C<--enable-frills> (possibly |
2416 | A non-exhaustive list of features enabled by C<--enable-frills> (possibly |
2545 | in combination with other switches) is: |
2417 | in combination with other switches) is: |
2546 | |
2418 | |
2547 | MWM-hints |
2419 | MWM-hints |
2548 | EWMH-hints (pid, utf8 names) and protocols (ping) |
2420 | EWMH-hints (pid, utf8 names) and protocols (ping) |
|
|
2421 | urgency hint |
2549 | seperate underline colour (-underlineColor) |
2422 | seperate underline colour (-underlineColor) |
2550 | settable border widths and borderless switch (-w, -b, -bl) |
2423 | settable border widths and borderless switch (-w, -b, -bl) |
|
|
2424 | visual depth selection (-depth) |
2551 | settable extra linespacing /-lsp) |
2425 | settable extra linespacing /-lsp) |
2552 | iso-14755-2 and -3, and visual feedback |
2426 | iso-14755 5.1 (basic) support |
2553 | backindex and forwardindex escape sequence |
|
|
2554 | window op and some xterm/OSC escape sequences |
|
|
2555 | tripleclickwords (-tcw) |
2427 | tripleclickwords (-tcw) |
2556 | settable insecure mode (-insecure) |
2428 | settable insecure mode (-insecure) |
2557 | keysym remapping support |
2429 | keysym remapping support |
2558 | cursor blinking and underline cursor (-cb, -uc) |
2430 | cursor blinking and underline cursor (-cb, -uc) |
2559 | XEmbed support (-embed) |
2431 | XEmbed support (-embed) |
2560 | user-pty (-pty-fd) |
2432 | user-pty (-pty-fd) |
2561 | hold on exit (-hold) |
2433 | hold on exit (-hold) |
|
|
2434 | compile in built-in block graphics |
2562 | skip builtin block graphics (-sbg) |
2435 | skip builtin block graphics (-sbg) |
|
|
2436 | separate highlightcolor support (-hc) |
|
|
2437 | |
|
|
2438 | It also enables some non-essential features otherwise disabled, such as: |
|
|
2439 | |
|
|
2440 | some round-trip time optimisations |
|
|
2441 | nearest color allocation on pseudocolor screens |
|
|
2442 | UTF8_STRING support for selection |
2563 | sgr modes 90..97 and 100..107 |
2443 | sgr modes 90..97 and 100..107 |
|
|
2444 | backindex and forwardindex escape sequences |
|
|
2445 | view change/zero scrollback escape sequences |
|
|
2446 | locale switching escape sequence |
|
|
2447 | window op and some xterm/OSC escape sequences |
|
|
2448 | rectangular selections |
|
|
2449 | trailing space removal for selections |
|
|
2450 | verbose X error handling |
2564 | |
2451 | |
2565 | =item --enable-iso14755 (default: on) |
2452 | =item --enable-iso14755 (default: on) |
2566 | |
2453 | |
2567 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2454 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2568 | F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by |
2455 | F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by |
… | |
… | |
2572 | =item --enable-keepscrolling (default: on) |
2459 | =item --enable-keepscrolling (default: on) |
2573 | |
2460 | |
2574 | Add support for continual scrolling of the display when you hold |
2461 | Add support for continual scrolling of the display when you hold |
2575 | the mouse button down on a scrollbar arrow. |
2462 | the mouse button down on a scrollbar arrow. |
2576 | |
2463 | |
|
|
2464 | =item --enable-selectionscrolling (default: on) |
|
|
2465 | |
|
|
2466 | Add support for scrolling when the selection moves to the top or |
|
|
2467 | bottom of the screen. |
|
|
2468 | |
2577 | =item --enable-mousewheel (default: on) |
2469 | =item --enable-mousewheel (default: on) |
2578 | |
2470 | |
2579 | Add support for scrolling via mouse wheel or buttons 4 & 5. |
2471 | Add support for scrolling via mouse wheel or buttons 4 & 5. |
2580 | |
2472 | |
2581 | =item --enable-slipwheeling (default: on) |
2473 | =item --enable-slipwheeling (default: on) |
2582 | |
2474 | |
2583 | Add support for continual scrolling (using the mouse wheel as an |
2475 | Add support for continual scrolling (using the mouse wheel as an |
2584 | accelerator) while the control key is held down. This option |
2476 | accelerator) while the control key is held down. This option |
2585 | requires --enable-mousewheel to also be specified. |
2477 | requires --enable-mousewheel to also be specified. |
2586 | |
2478 | |
2587 | =item --disable-new-selection |
|
|
2588 | |
|
|
2589 | Remove support for mouse selection style like that of xterm. |
|
|
2590 | |
|
|
2591 | =item --enable-dmalloc (default: off) |
|
|
2592 | |
|
|
2593 | Use Gray Watson's malloc - which is good for debugging See |
|
|
2594 | http://www.letters.com/dmalloc/ for details If you use either this or the |
|
|
2595 | next option, you may need to edit src/Makefile after compiling to point |
|
|
2596 | DINCLUDE and DLIB to the right places. |
|
|
2597 | |
|
|
2598 | You can only use either this option and the following (should |
|
|
2599 | you use either) . |
|
|
2600 | |
|
|
2601 | =item --enable-dlmalloc (default: off) |
|
|
2602 | |
|
|
2603 | Use Doug Lea's malloc - which is good for a production version |
|
|
2604 | See L<http://g.oswego.edu/dl/html/malloc.html> for details. |
|
|
2605 | |
|
|
2606 | =item --enable-smart-resize (default: on) |
2479 | =item --enable-smart-resize (default: off) |
2607 | |
2480 | |
2608 | Add smart growth/shrink behaviour when changing font size via hot |
2481 | Add smart growth/shrink behaviour when resizing. |
2609 | keys. This should keep the window corner which is closest to a corner of |
2482 | This should keep the window corner which is closest to a corner of |
2610 | the screen in a fixed position. |
2483 | the screen in a fixed position. |
2611 | |
2484 | |
|
|
2485 | =item --enable-text-blink (default: on) |
|
|
2486 | |
|
|
2487 | Add support for blinking text. |
|
|
2488 | |
2612 | =item --enable-pointer-blank (default: on) |
2489 | =item --enable-pointer-blank (default: on) |
2613 | |
2490 | |
2614 | Add support to have the pointer disappear when typing or inactive. |
2491 | Add support to have the pointer disappear when typing or inactive. |
2615 | |
2492 | |
2616 | =item --enable-perl (default: off) |
2493 | =item --enable-perl (default: on) |
2617 | |
2494 | |
2618 | Enable an embedded perl interpreter. See the B<@@RXVT_NAME@@perl(3)> |
2495 | 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 |
2496 | manpage (F<doc/rxvtperl.txt>) for more info on this feature, or the |
2620 | in F<src/perl-ext/> for the extensions that are installed by default. The |
2497 | files in F<src/perl-ext/> for the extensions that are installed by |
2621 | perl interpreter that is used can be specified via the C<PERL> environment |
2498 | default. The perl interpreter that is used can be specified via the |
2622 | variable when running configure. |
2499 | C<PERL> environment variable when running configure. Even when compiled |
|
|
2500 | in, perl will I<not> be initialised when all extensions have been disabled |
|
|
2501 | C<-pe "" --perl-ext-common "">, so it should be safe to enable from a |
|
|
2502 | resource standpoint. |
|
|
2503 | |
|
|
2504 | =item --with-afterimage-config=DIR |
|
|
2505 | |
|
|
2506 | Look for the libAfterImage config script in DIR. |
2623 | |
2507 | |
2624 | =item --with-name=NAME (default: urxvt) |
2508 | =item --with-name=NAME (default: urxvt) |
2625 | |
2509 | |
2626 | Set the basename for the installed binaries, resulting |
2510 | Set the basename for the installed binaries, resulting |
2627 | in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with |
2511 | in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with |
… | |
… | |
2637 | PATH. |
2521 | PATH. |
2638 | |
2522 | |
2639 | =item --with-x |
2523 | =item --with-x |
2640 | |
2524 | |
2641 | Use the X Window System (pretty much default, eh?). |
2525 | Use the X Window System (pretty much default, eh?). |
2642 | |
|
|
2643 | =item --with-xpm-includes=DIR |
|
|
2644 | |
|
|
2645 | Look for the XPM includes in DIR. |
|
|
2646 | |
|
|
2647 | =item --with-xpm-library=DIR |
|
|
2648 | |
|
|
2649 | Look for the XPM library in DIR. |
|
|
2650 | |
|
|
2651 | =item --with-xpm |
|
|
2652 | |
|
|
2653 | Not needed - define via --enable-xpm-background. |
|
|
2654 | |
2526 | |
2655 | =back |
2527 | =back |
2656 | |
2528 | |
2657 | =head1 AUTHORS |
2529 | =head1 AUTHORS |
2658 | |
2530 | |