1 | =head1 NAME |
1 | =head1 NAME |
2 | |
2 | |
3 | RXVT REFERENCE - FAQ, command sequences and other background information |
3 | RXVT REFERENCE - FAQ, command sequences and other background information |
4 | |
4 | |
|
|
5 | =head1 SYNOPSIS |
|
|
6 | |
|
|
7 | # set a new font set |
|
|
8 | printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho" |
|
|
9 | |
|
|
10 | # change the locale and tell rxvt-unicode about it |
|
|
11 | export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007" |
|
|
12 | |
|
|
13 | # set window title |
|
|
14 | printf '\33]2;%s\007' "new window title" |
|
|
15 | |
|
|
16 | =head1 DESCRIPTION |
|
|
17 | |
|
|
18 | This document contains the FAQ, the RXVT TECHNICAL REFERENCE documenting |
|
|
19 | all escape sequences, and other background information. |
|
|
20 | |
|
|
21 | The newest version of this document is |
|
|
22 | also available on the World Wide Web at |
|
|
23 | L<http://cvs.schmorp.de/browse/*checkout*/rxvt-unicode/doc/rxvt.7.html>. |
|
|
24 | |
5 | =head1 FREQUENTLY ASKED QUESTIONS |
25 | =head1 FREQUENTLY ASKED QUESTIONS |
6 | |
26 | |
7 | =over 4 |
27 | =over 4 |
8 | |
28 | |
9 | =item How do I know which rxvt-unicode version I'm using? |
29 | =item How do I know which rxvt-unicode version I'm using? |
10 | |
30 | |
11 | The version number is displayed with the usage (-h). Also the escape |
31 | The version number is displayed with the usage (-h). Also the escape |
12 | sequence C<ESC[8n> sets the window title to the version number. |
32 | sequence C<ESC [ 8 n> sets the window title to the version number. |
|
|
33 | |
|
|
34 | =item I am using Debian GNU/Linux and have a problem... |
|
|
35 | |
|
|
36 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
|
|
37 | patches that considerably change the behaviour of rxvt-unicode. Before |
|
|
38 | reporting a bug to the original rxvt-unicode author please download and |
|
|
39 | install the genuine version (L<http://software.schmorp.de#rxvt-unicode>) |
|
|
40 | and try to reproduce the problem. If you cannot, chances are that the |
|
|
41 | problems are specific to Debian GNU/Linux, in which case it should be |
|
|
42 | reported via the Debian Bug Tracking System (use C<reportbug> to report |
|
|
43 | the bug). |
|
|
44 | |
|
|
45 | For other problems that also affect the Debian package, you can and |
|
|
46 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
47 | bug in the Debian version and it serves as a reminder for other users that |
|
|
48 | might encounter the same issue. |
13 | |
49 | |
14 | =item When I log-in to another system it tells me about missing terminfo data? |
50 | =item When I log-in to another system it tells me about missing terminfo data? |
15 | |
51 | |
16 | The terminal description used by rxvt-unicode is not as widely available |
52 | The terminal description used by rxvt-unicode is not as widely available |
17 | as that for xterm, or even rxvt (for which the same problem often arises). |
53 | as that for xterm, or even rxvt (for which the same problem often arises). |
… | |
… | |
28 | C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
64 | C<TERM=rxvt> or even C<TERM=xterm>, and live with the small number of |
29 | problems arising, which includes wrong keymapping, less and different |
65 | problems arising, which includes wrong keymapping, less and different |
30 | colours and some refresh errors in fullscreen applications. It's a nice |
66 | colours and some refresh errors in fullscreen applications. It's a nice |
31 | quick-and-dirty workaround for rare cases, though. |
67 | quick-and-dirty workaround for rare cases, though. |
32 | |
68 | |
33 | If you always want to do this you can either recompile rxvt-unicode with |
69 | If you always want to do this (and are fine with the consequences) you |
34 | the desired TERM value or use a resource to set it: |
70 | can either recompile rxvt-unicode with the desired TERM value or use a |
|
|
71 | resource to set it: |
35 | |
72 | |
36 | URxvt.termName: rxvt |
73 | URxvt.termName: rxvt |
37 | |
74 | |
38 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
75 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
39 | the rxvt terminfo file with the rxvt-unicode one. |
76 | the rxvt terminfo file with the rxvt-unicode one. |
40 | |
77 | |
|
|
78 | =item C<tic> outputs some error when compiling the terminfo entry. |
|
|
79 | |
|
|
80 | Most likely it's the empty definition for C<enacs=>. Just replace it by |
|
|
81 | C<enacs=\E[0@> and try again. |
|
|
82 | |
|
|
83 | =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
|
|
84 | |
41 | =item I need a termcap file entry. |
85 | =item I need a termcap file entry. |
|
|
86 | |
|
|
87 | One reason you might want this is that some distributions or operating |
|
|
88 | systems still compile some programs using the long-obsoleted termcap |
|
|
89 | library (Fedora Core's bash is one example) and rely on a termcap entry |
|
|
90 | for C<rxvt-unicode>. |
42 | |
91 | |
43 | You could use rxvt's termcap entry with resonable results in many cases. |
92 | You could use rxvt's termcap entry with resonable results in many cases. |
44 | You can also create a termcap entry by using terminfo's infocmp program |
93 | You can also create a termcap entry by using terminfo's infocmp program |
45 | like this: |
94 | like this: |
46 | |
95 | |
47 | infocmp -C rxvt-unicode |
96 | infocmp -C rxvt-unicode |
48 | |
97 | |
49 | OR you could this termcap entry: |
98 | Or you could use this termcap entry, generated by the command above: |
50 | |
99 | |
51 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
100 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
52 | :am:bw:eo:km:mi:ms:xn:xo:\ |
101 | :am:bw:eo:km:mi:ms:xn:xo:\ |
53 | :co#80:it#8:li#24:\ |
102 | :co#80:it#8:li#24:lm#0:\ |
54 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
103 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
55 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
104 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
56 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=^O:al=\E[L:\ |
105 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
57 | :as=^N:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:\ |
106 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
58 | :cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:\ |
107 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
59 | :ec=\E[%dX:ei=\E[4l:ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:\ |
108 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
|
|
109 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
60 | :im=\E[4h:is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
110 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
61 | :k0=\E[21~:k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:\ |
111 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
62 | :k5=\E[15~:k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:\ |
112 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
63 | :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:\ |
113 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
64 | :ke=\E[?1l\E>:kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:\ |
114 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
65 | :ku=\EOA:le=^H:mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:\ |
115 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
66 | :nd=\E[C:rc=\E8:sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:\ |
116 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
67 | :st=\EH:ta=^I:te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:\ |
117 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
68 | :up=\E[A:us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
118 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
69 | :vs=\E[?25h: |
119 | :vs=\E[?25h: |
70 | |
120 | |
71 | =item How can I configure rxvt-unicode so that it looks similar to the original rxvt? |
121 | =item Why does C<ls> no longer have coloured output? |
72 | |
122 | |
73 | Felix von Leitner says that these two lines, in your F<.Xdefaults>, will make rxvt-unicode |
123 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
74 | behave similar to the original rxvt: |
124 | decide wether a terminal has colour, but uses it's own configuration |
|
|
125 | file. Needless to say, C<rxvt-unicode> is not in it's default file (among |
|
|
126 | with most other terminals supporting colour). Either add: |
75 | |
127 | |
76 | URxvt.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1 |
128 | TERM rxvt-unicode |
77 | URxvt.boldFont: -misc-fixed-bold-r-semicondensed--13-120-75-75-c-60-iso8859-1 |
129 | |
|
|
130 | to C</etc/DIR_COLORS> or simply add: |
|
|
131 | |
|
|
132 | alias ls='ls --color=auto' |
|
|
133 | |
|
|
134 | to your C<.profile> or C<.bashrc>. |
|
|
135 | |
|
|
136 | =item Why doesn't vim/emacs etc. use the 88 colour mode? |
|
|
137 | |
|
|
138 | =item Why doesn't vim/emacs etc. make use of italic? |
|
|
139 | |
|
|
140 | =item Why are the secondary screen-related options not working properly? |
|
|
141 | |
|
|
142 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
|
|
143 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
|
|
144 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
|
|
145 | features. Unfortunately, some of these (most notably, again, Debian |
|
|
146 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
|
|
147 | file, so you will need to install it on your own (See the question B<When |
|
|
148 | I log-in to another system it tells me about missing terminfo data?> on |
|
|
149 | how to do this). |
|
|
150 | |
|
|
151 | =item My numerical keypad acts weird and generates differing output? |
|
|
152 | |
|
|
153 | Some Debian GNUL/Linux users seem to have this problem, although no |
|
|
154 | specific details were reported so far. It is possible that this is caused |
|
|
155 | by the wrong C<TERM> setting, although the details of wether and how |
|
|
156 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
|
|
157 | keymap. See the answer to the previous question, and please report if that |
|
|
158 | helped. |
78 | |
159 | |
79 | =item Rxvt-unicode does not seem to understand the selected encoding? |
160 | =item Rxvt-unicode does not seem to understand the selected encoding? |
80 | |
161 | |
81 | =item Unicode does not seem to work? |
162 | =item Unicode does not seem to work? |
82 | |
163 | |
… | |
… | |
85 | subtly garbled, then you should check your locale settings. |
166 | subtly garbled, then you should check your locale settings. |
86 | |
167 | |
87 | Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
168 | Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
88 | programs. Often rxvt-unicode is started in the C<C> locale, while the |
169 | programs. Often rxvt-unicode is started in the C<C> locale, while the |
89 | login script running within the rxvt-unicode window changes the locale to |
170 | login script running within the rxvt-unicode window changes the locale to |
90 | sth. else, e.h. C<en_GB.UTF-8>. Needless to say, this is not going to work. |
171 | something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work. |
91 | |
172 | |
92 | The best thing is to fix your startup environment, as you will likely run |
173 | The best thing is to fix your startup environment, as you will likely run |
93 | into other problems. If nothing works you can try this in your .profile. |
174 | into other problems. If nothing works you can try this in your .profile. |
94 | |
175 | |
95 | printf '\e]701;%s\007' "$LC_CTYPE" |
176 | printf '\e]701;%s\007' "$LC_CTYPE" |
96 | |
177 | |
97 | If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
178 | If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
98 | supported on your systems. Some systems have a C<locale> command which |
179 | supported on your systems. Some systems have a C<locale> command which |
99 | displays this. If it displays sth. like: |
180 | displays this (also, C<perl -e0> can be used to check locale settings, as |
|
|
181 | it will complain loudly if it cannot set the locale). If it displays something |
|
|
182 | like: |
100 | |
183 | |
101 | locale: Cannot set LC_CTYPE to default locale: ... |
184 | locale: Cannot set LC_CTYPE to default locale: ... |
102 | |
185 | |
103 | Then the locale you specified is not supported on your system. |
186 | Then the locale you specified is not supported on your system. |
104 | |
187 | |
… | |
… | |
115 | your system/os) have specified does not cover all the characters you want |
198 | your system/os) have specified does not cover all the characters you want |
116 | to display. |
199 | to display. |
117 | |
200 | |
118 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
201 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
119 | font. Often the result is fine, but sometimes the chosen font looks |
202 | font. Often the result is fine, but sometimes the chosen font looks |
120 | bad. Many fonts have totally strange characters that don't resemble the |
203 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
121 | correct glyph at all, and rxvt-unicode lacks the artificial intelligence |
204 | resemble the correct glyph at all, and rxvt-unicode lacks the artificial |
122 | to detect that a specific glyph is wrong: it has to believe the font that |
205 | intelligence to detect that a specific glyph is wrong: it has to believe |
123 | the characters it contains indeed look correct. |
206 | the font that the characters it claims to contain indeed look correct. |
124 | |
207 | |
125 | In that case, select a font of your taste and add it to the font list, |
208 | In that case, select a font of your taste and add it to the font list, |
126 | e.g.: |
209 | e.g.: |
127 | |
210 | |
128 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
211 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
… | |
… | |
130 | When rxvt-unicode sees a character, it will first look at the base |
213 | When rxvt-unicode sees a character, it will first look at the base |
131 | font. If the base font does not contain the character, it will go to the |
214 | font. If the base font does not contain the character, it will go to the |
132 | next font, and so on. Specifying your own fonts will also speed up this |
215 | next font, and so on. Specifying your own fonts will also speed up this |
133 | search and use less resources within rxvt-unicode and the X-server. |
216 | search and use less resources within rxvt-unicode and the X-server. |
134 | |
217 | |
135 | The only limitation is that all the fonts must not be larger than the base |
218 | The only limitation is that none of the fonts may be larger than the base |
136 | font, as the base font defines the principal cell size, which must be the |
219 | font, as the base font defines the terminal character cell size, which |
137 | same due to the way terminals work. |
220 | must be the same due to the way terminals work. |
138 | |
221 | |
139 | =item Why do some chinese characters look so different than others? |
222 | =item Why do some chinese characters look so different than others? |
140 | |
223 | |
141 | This is because there is a difference between script and language -- |
224 | This is because there is a difference between script and language -- |
142 | rxvt-unicode does not know which language the text that is output |
225 | rxvt-unicode does not know which language the text that is output is, |
143 | is, as it only knows the unicode character codes. If rxvt-unicode |
226 | as it only knows the unicode character codes. If rxvt-unicode first |
144 | first sees a japanese character, it might choose a japanese font for |
227 | sees a japanese/chinese character, it might choose a japanese font for |
145 | it. Subsequent japanese characters will take that font. Now, many chinese |
228 | display. Subsequent japanese characters will use that font. Now, many |
146 | characters aren't represented in japanese fonts, so when the first |
229 | chinese characters aren't represented in japanese fonts, so when the first |
147 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
230 | non-japanese character comes up, rxvt-unicode will look for a chinese font |
148 | -- unfortunately at this point, it will still use the japanese font for |
231 | -- unfortunately at this point, it will still use the japanese font for |
149 | japanese characters that are also chinese. |
232 | chinese characters that are also in the japanese font. |
150 | |
233 | |
151 | The workaround is easy: just tag a chinese font at the end of your font |
234 | The workaround is easy: just tag a chinese font at the end of your font |
152 | list (see the previous question). The key is to view the font list as |
235 | list (see the previous question). The key is to view the font list as |
153 | a preference list: If you expect more japanese, list a japanese font |
236 | a preference list: If you expect more japanese, list a japanese font |
154 | first. If you expect more chinese, put a chinese font first. |
237 | first. If you expect more chinese, put a chinese font first. |
155 | |
238 | |
156 | In the future it might be possible to switch preferences at runtime (the |
239 | In the future it might be possible to switch language preferences at |
157 | internal data structure has no problem with using different fonts for |
240 | runtime (the internal data structure has no problem with using different |
158 | the same character at the same time, but no interface for this has been |
241 | fonts for the same character at the same time, but no interface for this |
159 | designed yet). |
242 | has been designed yet). |
|
|
243 | |
|
|
244 | Until then, you might get away with switching fonts at runtime (see L<Can |
|
|
245 | I switch the fonts at runtime?> later in this document). |
160 | |
246 | |
161 | =item Why does rxvt-unicode sometimes leave pixel droppings? |
247 | =item Why does rxvt-unicode sometimes leave pixel droppings? |
162 | |
248 | |
163 | Most fonts were not designed for terminal use, which means that character |
249 | Most fonts were not designed for terminal use, which means that character |
164 | size varies a lot. A font that is otherwise fine for terminal use might |
250 | size varies a lot. A font that is otherwise fine for terminal use might |
… | |
… | |
170 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
256 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
171 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
257 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
172 | ask for the character bounding box, which unfortunately is wrong in these |
258 | ask for the character bounding box, which unfortunately is wrong in these |
173 | cases). |
259 | cases). |
174 | |
260 | |
175 | It's not clear (to me at least), wether this is a bug in Xft, freetype, or |
261 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
176 | the respective font. If you encounter this problem there is no way to work |
262 | or the respective font. If you encounter this problem you might try using |
177 | around this except by using a different font. |
263 | the C<-lsp> option to give the font more height. If that doesn't work, you |
|
|
264 | might be forced to use a different font. |
178 | |
265 | |
179 | All of this is not a problem when using X11 core fonts, as their bounding |
266 | All of this is not a problem when using X11 core fonts, as their bounding |
180 | box data is correct. |
267 | box data is correct. |
|
|
268 | |
|
|
269 | =item On Solaris 9, many line-drawing characters are too wide. |
|
|
270 | |
|
|
271 | Seems to be a known bug, read |
|
|
272 | L<http://nixdoc.net/files/forum/about34198.html>. Some people use the |
|
|
273 | following ugly workaround to get non-double-wide-characters working: |
|
|
274 | |
|
|
275 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
181 | |
276 | |
182 | =item My Compose (Multi_key) key is no longer working. |
277 | =item My Compose (Multi_key) key is no longer working. |
183 | |
278 | |
184 | The most common causes for this are that either your locale is not set |
279 | The most common causes for this are that either your locale is not set |
185 | correctly, or you specified a B<preeditStyle> that is not supported by |
280 | correctly, or you specified a B<preeditStyle> that is not supported by |
… | |
… | |
189 | rxvt-unicode will continue without an input method. |
284 | rxvt-unicode will continue without an input method. |
190 | |
285 | |
191 | In this case either do not specify a B<preeditStyle> or specify more than |
286 | In this case either do not specify a B<preeditStyle> or specify more than |
192 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
287 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
193 | |
288 | |
|
|
289 | =item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
|
|
290 | |
|
|
291 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
|
|
292 | international keyboards) or simply use ISO 14755 support to your |
|
|
293 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
|
|
294 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
|
|
295 | character and so on. |
|
|
296 | |
194 | =item How can I keep rxvt-unicode from using reverse video so much? |
297 | =item How can I keep rxvt-unicode from using reverse video so much? |
195 | |
298 | |
196 | First of all, make sure you are running with the right terminfo |
299 | First of all, make sure you are running with the right terminal settings |
197 | (C<urxvt>), which will get rid of most of these effects. Then make sure |
300 | (C<TERM=rxvt-unicode>), which will get rid of most of these effects. Then |
198 | you have specified colours for italic and bold, as otherwise rxvt-unicode |
301 | make sure you have specified colours for italic and bold, as otherwise |
199 | might use reverse video to simulate the effect: |
302 | rxvt-unicode might use reverse video to simulate the effect: |
200 | |
303 | |
201 | URxvt*colorBD: white |
304 | URxvt.colorBD: white |
202 | URxvt*colorIT: green |
305 | URxvt.colorIT: green |
203 | |
306 | |
204 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
307 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
205 | |
308 | |
206 | For some unexplainable reason, some programs (i.e. irssi) assume a very |
309 | For some unexplainable reason, some rare programs assume a very weird |
207 | weird colour palette when confronted with a terminal with more than the |
310 | colour palette when confronted with a terminal with more than the standard |
208 | standard 8 colours (rxvt-unicode supports 88). The right fix is, of |
311 | 8 colours (rxvt-unicode supports 88). The right fix is, of course, to fix |
209 | course, to fix these programs not to assume non-ISO colours without very |
312 | these programs not to assume non-ISO colours without very good reasons. |
210 | good reasons. |
|
|
211 | |
313 | |
212 | In the meantime, you can either edit your C<urxvt> terminfo definition to |
314 | In the meantime, you can either edit your C<rxvt-unicode> terminfo |
213 | only claim 8 colour support or use C<TERM=rxvt>, which will fix colours |
315 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
214 | but keep you from using other rxvt-unicode features. |
316 | fix colours but keep you from using other rxvt-unicode features. |
215 | |
317 | |
216 | =item I am on FreeBSD and rxvt-unicode does not seem to work at all. |
318 | =item I am on FreeBSD and rxvt-unicode does not seem to work at all. |
217 | |
319 | |
218 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
320 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
219 | in your compile environment, or an implementation that implements it, |
321 | in your compile environment, or an implementation that implements it, |
220 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
322 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
221 | B<wchar_t> is represented as unicode. |
323 | B<wchar_t> is represented as unicode. |
222 | |
324 | |
223 | As you might have guessed, FreeBSD does neither define this symobl nor |
325 | As you might have guessed, FreeBSD does neither define this symobl nor |
224 | does it support it. Instead, it uses it's own internal representation of |
326 | does it support it. Instead, it uses it's own internal representation of |
225 | B<wchar_t>. This is, of course, completely legal. |
327 | B<wchar_t>. This is, of course, completely fine with respect to standards. |
226 | |
328 | |
|
|
329 | However, that means rxvt-unicode only works in C<POSIX>, C<ISO-8859-1> and |
|
|
330 | C<UTF-8> locales under FreeBSD (which all use Unicode as B<wchar_t>. |
|
|
331 | |
227 | However, C<__STDC_ISO_10646__> is the only sane way to support |
332 | C<__STDC_ISO_10646__> is the only sane way to support multi-language |
228 | multi-language apps in an OS, as using a locale-dependent (and |
333 | apps in an OS, as using a locale-dependent (and non-standardized) |
229 | non-standardized) representation of B<wchar_t> makes it impossible to |
334 | representation of B<wchar_t> makes it impossible to convert between |
230 | convert between B<wchar_t> (as used by X11 and your applications) and any |
335 | B<wchar_t> (as used by X11 and your applications) and any other encoding |
231 | other encoding without implementing OS-specific-wrappers for each and |
336 | without implementing OS-specific-wrappers for each and every locale. There |
232 | every locale. There simply are no APIs to convert B<wchar_t> into anything |
337 | simply are no APIs to convert B<wchar_t> into anything except the current |
233 | except the current locale encoding. |
338 | locale encoding. |
234 | |
339 | |
235 | Some applications (such as the formidable B<mlterm>) work around this |
340 | Some applications (such as the formidable B<mlterm>) work around this |
236 | by carrying their own replacement functions for character set handling |
341 | by carrying their own replacement functions for character set handling |
237 | with them, and either implementing OS-dependent hacks or doing multiple |
342 | with them, and either implementing OS-dependent hacks or doing multiple |
238 | conversions (which is slow and unreliable in case the OS implements |
343 | conversions (which is slow and unreliable in case the OS implements |
239 | encodings slightly different than the terminal emulator). |
344 | encodings slightly different than the terminal emulator). |
240 | |
345 | |
241 | The rxvt-unicode author insists that the right way to fix this is in the |
346 | The rxvt-unicode author insists that the right way to fix this is in the |
242 | system libraries once and for all, instead of forcing every app to carry |
347 | system libraries once and for all, instead of forcing every app to carry |
243 | complete replacements. |
348 | complete replacements for them :) |
|
|
349 | |
|
|
350 | =item I use Solaris 9 and it doesn't compile/work/etc. |
|
|
351 | |
|
|
352 | Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst |
|
|
353 | problems with C<wcwidth> and a compile problem. |
|
|
354 | |
|
|
355 | =item How can I use rxvt-unicode under cygwin? |
|
|
356 | |
|
|
357 | rxvt-unicode should compile and run out of the box on cygwin, using |
|
|
358 | the X11 libraries that come with cygwin. libW11 emulation is no |
|
|
359 | longer supported (and makes no sense, either, as it only supported a |
|
|
360 | single font). I recommend starting the X-server in C<-multiwindow> or |
|
|
361 | C<-rootless> mode instead, which will result in similar look&feel as the |
|
|
362 | old libW11 emulation. |
|
|
363 | |
|
|
364 | At the time of this writing, cygwin didn't seem to support any multi-byte |
|
|
365 | encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited |
|
|
366 | to 8-bit encodings. |
244 | |
367 | |
245 | =item How does rxvt-unicode determine the encoding to use? |
368 | =item How does rxvt-unicode determine the encoding to use? |
246 | |
369 | |
247 | =item Is there an option to switch encodings? |
370 | =item Is there an option to switch encodings? |
248 | |
371 | |
… | |
… | |
250 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
373 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
251 | UTF-8 or any other encodings with respect to terminal I/O. |
374 | UTF-8 or any other encodings with respect to terminal I/O. |
252 | |
375 | |
253 | The reasons is that there exists a perfectly fine mechanism for selecting |
376 | The reasons is that there exists a perfectly fine mechanism for selecting |
254 | the encoding, doing I/O and (most important) communicating this to all |
377 | the encoding, doing I/O and (most important) communicating this to all |
255 | applications so everybody agrees on character properties such as width and |
378 | applications so everybody agrees on character properties such as width |
256 | code number. This mechanism is the I<locale>. |
379 | and code number. This mechanism is the I<locale>. Applications not using |
|
|
380 | that info will have problems (for example, C<xterm> gets the width of |
|
|
381 | characters wrong as it uses it's own, locale-independent table under all |
|
|
382 | locales). |
257 | |
383 | |
258 | Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
384 | Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
259 | programs doing the same (that is, most) will automatically agree in the |
385 | programs doing the same (that is, most) will automatically agree in the |
260 | interpretation of characters. |
386 | interpretation of characters. |
261 | |
387 | |
… | |
… | |
268 | C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
394 | C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
269 | (i.e. C<de> or C<german>) are also common. |
395 | (i.e. C<de> or C<german>) are also common. |
270 | |
396 | |
271 | Rxvt-unicode ignores all other locale categories, and except for |
397 | Rxvt-unicode ignores all other locale categories, and except for |
272 | the encoding, ignores country or language-specific settings, |
398 | the encoding, ignores country or language-specific settings, |
273 | i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the same for rxvt-unicode. |
399 | i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to |
|
|
400 | rxvt-unicode. |
274 | |
401 | |
275 | If you want to use a specific encoding you have to make sure you start |
402 | If you want to use a specific encoding you have to make sure you start |
276 | rxvt-unicode with the correct C<LC_CTYPE> category. |
403 | rxvt-unicode with the correct C<LC_CTYPE> category. |
277 | |
404 | |
278 | =item Can I switch locales at runtime? |
405 | =item Can I switch locales at runtime? |
279 | |
406 | |
280 | Yes, using an escape sequence. Try sth. like this, which sets |
407 | Yes, using an escape sequence. Try something like this, which sets |
281 | rxvt-unicode's idea of C<LC_CTYPE>. |
408 | rxvt-unicode's idea of C<LC_CTYPE>. |
282 | |
409 | |
283 | printf '\e]701;%s\007' ja_JP.SJIS |
410 | printf '\e]701;%s\007' ja_JP.SJIS |
284 | |
411 | |
285 | See also the previous question. |
412 | See also the previous answer. |
286 | |
413 | |
287 | Sometimes this capability is rather handy when you want to work in one |
414 | Sometimes this capability is rather handy when you want to work in |
288 | locale (e.g. C<de_DE.UTF-8>) but some programs don't support UTF-8. For |
415 | one locale (e.g. C<de_DE.UTF-8>) but some programs don't support it |
289 | example, I use this script to start C<xjdic>, which first switches to a |
416 | (e.g. UTF-8). For example, I use this script to start C<xjdic>, which |
290 | locale supported by xjdic and back later: |
417 | first switches to a locale supported by xjdic and back later: |
291 | |
418 | |
292 | printf '\e]701;%s\007' ja_JP.SJIS |
419 | printf '\e]701;%s\007' ja_JP.SJIS |
293 | xjdic -js |
420 | xjdic -js |
294 | printf '\e]701;%s\007' de_DE.UTF-8 |
421 | printf '\e]701;%s\007' de_DE.UTF-8 |
295 | |
422 | |
|
|
423 | You can also use xterm's C<luit> program, which usually works fine, except |
|
|
424 | for some locales where character width differs between program- and |
|
|
425 | rxvt-unicode-locales. |
|
|
426 | |
296 | =item Can I switch the fonts at runtime? |
427 | =item Can I switch the fonts at runtime? |
297 | |
428 | |
298 | Yes, using an escape sequence. Try sth. like this, which has the same |
429 | Yes, using an escape sequence. Try something like this, which has the same |
299 | effect as using the C<-fn> switch, and takes effect immediately: |
430 | effect as using the C<-fn> switch, and takes effect immediately: |
300 | |
431 | |
301 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
432 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
302 | |
433 | |
303 | This is useful if you e.g. work primarily with japanese (and prefer a |
434 | This is useful if you e.g. work primarily with japanese (and prefer a |
… | |
… | |
308 | |
439 | |
309 | =item Why do italic characters look as if clipped? |
440 | =item Why do italic characters look as if clipped? |
310 | |
441 | |
311 | Many fonts have difficulties with italic characters and hinting. For |
442 | Many fonts have difficulties with italic characters and hinting. For |
312 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
443 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
313 | Mono> completely fails in it's italic face. A workaround is to enable |
444 | Mono> completely fails in it's italic face. A workaround might be to |
314 | freetype autohinting, i.e. like this: |
445 | enable freetype autohinting, i.e. like this: |
315 | |
446 | |
316 | URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
447 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
317 | URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
448 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
318 | |
449 | |
319 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
450 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
320 | |
451 | |
321 | You can specify separate locales for the input method and the rest of the |
452 | You can specify separate locales for the input method and the rest of the |
322 | terminal, using the resource C<imlocale>: |
453 | terminal, using the resource C<imlocale>: |
… | |
… | |
326 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
457 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
327 | use your input method. Please note, however, that you will not be able to |
458 | use your input method. Please note, however, that you will not be able to |
328 | input characters outside C<EUC-JP> in a normal way then, as your input |
459 | input characters outside C<EUC-JP> in a normal way then, as your input |
329 | method limits you. |
460 | method limits you. |
330 | |
461 | |
|
|
462 | =item Rxvt-unicode crashes when the X Input Method changes or exits. |
|
|
463 | |
|
|
464 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
|
|
465 | design. Applications can avoid some crashes at the expense of memory |
|
|
466 | leaks, and Input Methods can avoid some crashes by careful ordering at |
|
|
467 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
|
|
468 | while B<SCIM> (or similar input methods) fails. In the end, however, |
|
|
469 | crashes cannot be completely avoided even if both sides cooperate. |
|
|
470 | |
|
|
471 | So the only workaround is not to kill your Input Method Servers. |
|
|
472 | |
331 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
473 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
332 | |
474 | |
333 | Rxvt-unicode tries to obey the rule of not charging you for sth. you |
475 | Rxvt-unicode tries to obey the rule of not charging you for something you |
334 | don't use. One thing you should try is to configure out all settings that |
476 | don't use. One thing you should try is to configure out all settings that |
335 | you don't need, for example, Xft support is a resource hog by design, |
477 | you don't need, for example, Xft support is a resource hog by design, |
336 | when used. Compiling it out ensures that no Xft font will be loaded |
478 | when used. Compiling it out ensures that no Xft font will be loaded |
337 | accidentally when rxvt-unicode tries to find a font for your characters. |
479 | accidentally when rxvt-unicode tries to find a font for your characters. |
338 | |
480 | |
… | |
… | |
391 | resources (or as long-options). |
533 | resources (or as long-options). |
392 | |
534 | |
393 | Here are values that are supposed to resemble a VGA screen, |
535 | Here are values that are supposed to resemble a VGA screen, |
394 | including the murky brown that passes for low-intensity yellow: |
536 | including the murky brown that passes for low-intensity yellow: |
395 | |
537 | |
396 | Rxvt*color0: #000000 |
538 | URxvt.color0: #000000 |
397 | Rxvt*color1: #A80000 |
539 | URxvt.color1: #A80000 |
398 | Rxvt*color2: #00A800 |
540 | URxvt.color2: #00A800 |
399 | Rxvt*color3: #A8A800 |
541 | URxvt.color3: #A8A800 |
400 | Rxvt*color4: #0000A8 |
542 | URxvt.color4: #0000A8 |
401 | Rxvt*color5: #A800A8 |
543 | URxvt.color5: #A800A8 |
402 | Rxvt*color6: #00A8A8 |
544 | URxvt.color6: #00A8A8 |
403 | Rxvt*color7: #A8A8A8 |
545 | URxvt.color7: #A8A8A8 |
404 | |
546 | |
405 | Rxvt*color8: #000054 |
547 | URxvt.color8: #000054 |
406 | Rxvt*color9: #FF0054 |
548 | URxvt.color9: #FF0054 |
407 | Rxvt*color10: #00FF54 |
549 | URxvt.color10: #00FF54 |
408 | Rxvt*color11: #FFFF54 |
550 | URxvt.color11: #FFFF54 |
409 | Rxvt*color12: #0000FF |
551 | URxvt.color12: #0000FF |
410 | Rxvt*color13: #FF00FF |
552 | URxvt.color13: #FF00FF |
411 | Rxvt*color14: #00FFFF |
553 | URxvt.color14: #00FFFF |
412 | Rxvt*color15: #FFFFFF |
554 | URxvt.color15: #FFFFFF |
|
|
555 | |
|
|
556 | And here is a more complete set of non-standard colors described (not by |
|
|
557 | me) as "pretty girly". |
|
|
558 | |
|
|
559 | URxvt.cursorColor: #dc74d1 |
|
|
560 | URxvt.pointerColor: #dc74d1 |
|
|
561 | URxvt.background: #0e0e0e |
|
|
562 | URxvt.foreground: #4ad5e1 |
|
|
563 | URxvt.color0: #000000 |
|
|
564 | URxvt.color8: #8b8f93 |
|
|
565 | URxvt.color1: #dc74d1 |
|
|
566 | URxvt.color9: #dc74d1 |
|
|
567 | URxvt.color2: #0eb8c7 |
|
|
568 | URxvt.color10: #0eb8c7 |
|
|
569 | URxvt.color3: #dfe37e |
|
|
570 | URxvt.color11: #dfe37e |
|
|
571 | URxvt.color5: #9e88f0 |
|
|
572 | URxvt.color13: #9e88f0 |
|
|
573 | URxvt.color6: #73f7ff |
|
|
574 | URxvt.color14: #73f7ff |
|
|
575 | URxvt.color7: #e1dddd |
|
|
576 | URxvt.color15: #e1dddd |
|
|
577 | |
|
|
578 | =item How can I start @@RXVT_NAME@@d in a race-free way? |
|
|
579 | |
|
|
580 | Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a |
|
|
581 | server that answers @@RXVT_NAME@@c's requests, so it doesn't background |
|
|
582 | itself. |
|
|
583 | |
|
|
584 | To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the |
|
|
585 | following method to wait for the startup message before continuing: |
|
|
586 | |
|
|
587 | { @@RXVT_NAME@@d & } | read |
413 | |
588 | |
414 | =item What's with the strange Backspace/Delete key behaviour? |
589 | =item What's with the strange Backspace/Delete key behaviour? |
415 | |
590 | |
416 | Assuming that the physical Backspace key corresponds to the |
591 | Assuming that the physical Backspace key corresponds to the |
417 | BackSpace keysym (not likely for Linux ... see the following |
592 | BackSpace keysym (not likely for Linux ... see the following |
… | |
… | |
436 | |
611 | |
437 | # use Backspace = ^? |
612 | # use Backspace = ^? |
438 | $ stty erase ^? |
613 | $ stty erase ^? |
439 | $ @@RXVT_NAME@@ |
614 | $ @@RXVT_NAME@@ |
440 | |
615 | |
441 | Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7). |
616 | Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7). |
442 | |
617 | |
443 | For an existing rxvt-unicode: |
618 | For an existing rxvt-unicode: |
444 | |
619 | |
445 | # use Backspace = ^H |
620 | # use Backspace = ^H |
446 | $ stty erase ^H |
621 | $ stty erase ^H |
… | |
… | |
455 | properly reflects that. |
630 | properly reflects that. |
456 | |
631 | |
457 | The Delete key is a another casualty of the ill-defined Backspace problem. |
632 | The Delete key is a another casualty of the ill-defined Backspace problem. |
458 | To avoid confusion between the Backspace and Delete keys, the Delete |
633 | To avoid confusion between the Backspace and Delete keys, the Delete |
459 | key has been assigned an escape sequence to match the vt100 for Execute |
634 | key has been assigned an escape sequence to match the vt100 for Execute |
460 | (ESC[3~) and is in the supplied termcap/terminfo. |
635 | (C<ESC [ 3 ~>) and is in the supplied termcap/terminfo. |
461 | |
636 | |
462 | Some other Backspace problems: |
637 | Some other Backspace problems: |
463 | |
638 | |
464 | some editors use termcap/terminfo, |
639 | some editors use termcap/terminfo, |
465 | some editors (vim I'm told) expect Backspace = ^H, |
640 | some editors (vim I'm told) expect Backspace = ^H, |
… | |
… | |
469 | |
644 | |
470 | =item I don't like the key-bindings. How do I change them? |
645 | =item I don't like the key-bindings. How do I change them? |
471 | |
646 | |
472 | There are some compile-time selections available via configure. Unless |
647 | There are some compile-time selections available via configure. Unless |
473 | you have run "configure" with the C<--disable-resources> option you can |
648 | you have run "configure" with the C<--disable-resources> option you can |
474 | use the `keysym' resource to alter the keystrings associated with keysym |
649 | use the `keysym' resource to alter the keystrings associated with keysyms. |
475 | 0xFF00 - 0xFFFF (function, cursor keys, etc). |
|
|
476 | |
650 | |
477 | Here's an example for a tn3270 session started using `@@RXVT_NAME@@ -name tn3270' |
651 | Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt> |
478 | |
652 | |
479 | !# ----- special uses ------: |
653 | URxvt.keysym.Home: \033[1~ |
480 | ! tn3270 login, remap function and arrow keys. |
654 | URxvt.keysym.End: \033[4~ |
481 | tn3270*font: *clean-bold-*-*--15-* |
655 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
656 | URxvt.keysym.C-slash: \033<C-/> |
|
|
657 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
658 | URxvt.keysym.C-grave: \033<C-`> |
|
|
659 | URxvt.keysym.C-comma: \033<C-,> |
|
|
660 | URxvt.keysym.C-period: \033<C-.> |
|
|
661 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
662 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
663 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
664 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
665 | URxvt.keysym.S-space: \033<S-Space> |
|
|
666 | URxvt.keysym.M-Up: \033<M-Up> |
|
|
667 | URxvt.keysym.M-Down: \033<M-Down> |
|
|
668 | URxvt.keysym.M-Left: \033<M-Left> |
|
|
669 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
670 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
671 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
672 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
482 | |
673 | |
483 | ! keysym - used by rxvt only |
674 | See some more examples in the documentation for the B<keysym> resource. |
484 | ! Delete - ^D |
|
|
485 | tn3270*keysym.0xFFFF: \004 |
|
|
486 | |
|
|
487 | ! Home - ^A |
|
|
488 | tn3270*keysym.0xFF50: \001 |
|
|
489 | ! Left - ^B |
|
|
490 | tn3270*keysym.0xFF51: \002 |
|
|
491 | ! Up - ^P |
|
|
492 | tn3270*keysym.0xFF52: \020 |
|
|
493 | ! Right - ^F |
|
|
494 | tn3270*keysym.0xFF53: \006 |
|
|
495 | ! Down - ^N |
|
|
496 | tn3270*keysym.0xFF54: \016 |
|
|
497 | ! End - ^E |
|
|
498 | tn3270*keysym.0xFF57: \005 |
|
|
499 | |
|
|
500 | ! F1 - F12 |
|
|
501 | tn3270*keysym.0xFFBE: \e1 |
|
|
502 | tn3270*keysym.0xFFBF: \e2 |
|
|
503 | tn3270*keysym.0xFFC0: \e3 |
|
|
504 | tn3270*keysym.0xFFC1: \e4 |
|
|
505 | tn3270*keysym.0xFFC2: \e5 |
|
|
506 | tn3270*keysym.0xFFC3: \e6 |
|
|
507 | tn3270*keysym.0xFFC4: \e7 |
|
|
508 | tn3270*keysym.0xFFC5: \e8 |
|
|
509 | tn3270*keysym.0xFFC6: \e9 |
|
|
510 | tn3270*keysym.0xFFC7: \e0 |
|
|
511 | tn3270*keysym.0xFFC8: \e- |
|
|
512 | tn3270*keysym.0xFFC9: \e= |
|
|
513 | |
|
|
514 | ! map Prior/Next to F7/F8 |
|
|
515 | tn3270*keysym.0xFF55: \e7 |
|
|
516 | tn3270*keysym.0xFF56: \e8 |
|
|
517 | |
675 | |
518 | =item I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
676 | =item I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
519 | How do I make use of them? For example, the Sun Keyboard type 4 |
677 | How do I make use of them? For example, the Sun Keyboard type 4 |
520 | has the following mappings that rxvt-unicode doesn't recognize. |
678 | has the following mappings that rxvt-unicode doesn't recognize. |
521 | |
679 | |
… | |
… | |
524 | F27 == Home |
682 | F27 == Home |
525 | F29 == Prior |
683 | F29 == Prior |
526 | F33 == End |
684 | F33 == End |
527 | F35 == Next |
685 | F35 == Next |
528 | |
686 | |
529 | Rather than have rxvt-unicode try to accommodate all the various possible keyboard |
687 | Rather than have rxvt-unicode try to accommodate all the various possible |
530 | mappings, it is better to use `xmodmap' to remap the keys as required for |
688 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
531 | your particular machine. |
689 | required for your particular machine. |
532 | |
690 | |
533 | =item How do I distinguish if I'm running rxvt-unicode or a regular xterm? |
691 | =item How do I distinguish wether I'm running rxvt-unicode or a regular xterm? |
534 | I need this to decide about setting colors etc. |
692 | I need this to decide about setting colors etc. |
535 | |
693 | |
536 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
694 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
537 | check and see if that is set. Note that several programs, JED, slrn, |
695 | check and see if that is set. Note that several programs, JED, slrn, |
538 | Midnight Commander automatically check this variable to decide whether or |
696 | Midnight Commander automatically check this variable to decide whether or |
… | |
… | |
575 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
733 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
576 | interested in learning about new and exciting problems (but not FAQs :). |
734 | interested in learning about new and exciting problems (but not FAQs :). |
577 | |
735 | |
578 | =back |
736 | =back |
579 | |
737 | |
580 | =head1 SYNOPSIS |
738 | =head1 RXVT TECHNICAL REFERENCE |
581 | |
|
|
582 | # set a new font set |
|
|
583 | printf '\33]50;%s\007' 9x15,xft:Kochi" Mincho" |
|
|
584 | |
|
|
585 | # change the locale and tell rxvt-unicode about it |
|
|
586 | export LC_CTYPE=ja_JP.EUC-JP; printf "\33]701;$LC_CTYPE\007" |
|
|
587 | |
|
|
588 | # set window title |
|
|
589 | printf '\33]2;%s\007' "new window title" |
|
|
590 | |
739 | |
591 | =head1 DESCRIPTION |
740 | =head1 DESCRIPTION |
592 | |
741 | |
593 | The rest of this document describes various technical aspects of |
742 | The rest of this document describes various technical aspects of |
594 | B<rxvt-unicode>. First the description of supported command sequences, |
743 | B<rxvt-unicode>. First the description of supported command sequences, |
595 | followed by menu and pixmap support and last by a description of all |
744 | followed by menu and pixmap support and last by a description of all |
596 | features selectable at C<configure> time. |
745 | features selectable at C<configure> time. |
597 | |
746 | |
598 | =head1 RXVT TECHNICAL REFERENCE |
|
|
599 | |
|
|
600 | =head1 Definitions |
747 | =head1 Definitions |
601 | |
748 | |
602 | =over 4 |
749 | =over 4 |
603 | |
750 | |
604 | =item B<< C<c> >> |
751 | =item B<< C<c> >> |
… | |
… | |
732 | Single Shift Select of G3 Character Set (SS3): affects next character |
879 | Single Shift Select of G3 Character Set (SS3): affects next character |
733 | only I<unimplemented> |
880 | only I<unimplemented> |
734 | |
881 | |
735 | =item B<< C<ESC Z> >> |
882 | =item B<< C<ESC Z> >> |
736 | |
883 | |
737 | Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt-unicode compile-time option> |
884 | Obsolete form of returns: B<< C<ESC [ ? 1 ; 2 C> >> I<rxvt-unicode compile-time option> |
738 | |
885 | |
739 | =item B<< C<ESC c> >> |
886 | =item B<< C<ESC c> >> |
740 | |
887 | |
741 | Full reset (RIS) |
888 | Full reset (RIS) |
742 | |
889 | |
… | |
… | |
746 | |
893 | |
747 | =item B<< C<ESC o> >> |
894 | =item B<< C<ESC o> >> |
748 | |
895 | |
749 | Invoke the G3 Character Set (LS3) |
896 | Invoke the G3 Character Set (LS3) |
750 | |
897 | |
751 | =item B<< C<ESC> ( C> >> |
898 | =item B<< C<ESC ( C> >> |
752 | |
899 | |
753 | Designate G0 Character Set (ISO 2022), see below for values of C<C>. |
900 | Designate G0 Character Set (ISO 2022), see below for values of C<C>. |
754 | |
901 | |
755 | =item B<< C<ESC> ) C> >> |
902 | =item B<< C<ESC ) C> >> |
756 | |
903 | |
757 | Designate G1 Character Set (ISO 2022), see below for values of C<C>. |
904 | Designate G1 Character Set (ISO 2022), see below for values of C<C>. |
758 | |
905 | |
759 | =item B<< C<ESC * C> >> |
906 | =item B<< C<ESC * C> >> |
760 | |
907 | |
… | |
… | |
901 | |
1048 | |
902 | =item B<< C<ESC [ Ps c> >> |
1049 | =item B<< C<ESC [ Ps c> >> |
903 | |
1050 | |
904 | Send Device Attributes (DA) |
1051 | Send Device Attributes (DA) |
905 | B<< C<Ps = 0> >> (or omitted): request attributes from terminal |
1052 | B<< C<Ps = 0> >> (or omitted): request attributes from terminal |
906 | returns: B<< C<ESC[?1;2c> >> (``I am a VT100 with Advanced Video |
1053 | returns: B<< C<ESC [ ? 1 ; 2 c> >> (``I am a VT100 with Advanced Video |
907 | Option'') |
1054 | Option'') |
908 | |
1055 | |
909 | =item B<< C<ESC [ Ps d> >> |
1056 | =item B<< C<ESC [ Ps d> >> |
910 | |
1057 | |
911 | Cursor to Line B<< C<Ps> >> (VPA) |
1058 | Cursor to Line B<< C<Ps> >> (VPA) |
… | |
… | |
1027 | |
1174 | |
1028 | =item B<< C<ESC [ s> >> |
1175 | =item B<< C<ESC [ s> >> |
1029 | |
1176 | |
1030 | Save Cursor (SC) |
1177 | Save Cursor (SC) |
1031 | |
1178 | |
|
|
1179 | =item B<< C<ESC [ Ps;Pt t> >> |
|
|
1180 | |
|
|
1181 | Window Operations |
|
|
1182 | |
|
|
1183 | =begin table |
|
|
1184 | |
|
|
1185 | B<< C<Ps = 1> >> Deiconify (map) window |
|
|
1186 | B<< C<Ps = 2> >> Iconify window |
|
|
1187 | B<< C<Ps = 3> >> B<< C<ESC [ 3 ; X ; Y t> >> Move window to (X|Y) |
|
|
1188 | B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels |
|
|
1189 | B<< C<Ps = 5> >> Raise window |
|
|
1190 | B<< C<Ps = 6> >> Lower window |
|
|
1191 | B<< C<Ps = 7> >> Refresh screen once |
|
|
1192 | B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns |
|
|
1193 | B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>) |
|
|
1194 | B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>) |
|
|
1195 | B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>) |
|
|
1196 | B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>) |
|
|
1197 | B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9> |
|
|
1198 | B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>) |
|
|
1199 | B<< C<Ps = 21> >> Reports window title (B<< C<ESC ] l NAME \234> >>) |
|
|
1200 | B<< C<Ps = 24..> >> Set window height to C<Ps> rows |
|
|
1201 | |
|
|
1202 | =end table |
|
|
1203 | |
|
|
1204 | =item B<< C<ESC [ u> >> |
|
|
1205 | |
|
|
1206 | Restore Cursor |
|
|
1207 | |
1032 | =item B<< C<ESC [ Ps x> >> |
1208 | =item B<< C<ESC [ Ps x> >> |
1033 | |
1209 | |
1034 | Request Terminal Parameters (DECREQTPARM) |
1210 | Request Terminal Parameters (DECREQTPARM) |
1035 | |
|
|
1036 | =item B<< C<ESC [ u> >> |
|
|
1037 | |
|
|
1038 | Restore Cursor |
|
|
1039 | |
1211 | |
1040 | =back |
1212 | =back |
1041 | |
1213 | |
1042 | X<PrivateModes> |
1214 | X<PrivateModes> |
1043 | |
1215 | |
… | |
… | |
1338 | B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >> |
1510 | B<< C<Ps = 13> >> Change colour of mouse foreground to B<< C<Pt> >> |
1339 | B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >> |
1511 | B<< C<Ps = 17> >> Change colour of highlight characters to B<< C<Pt> >> |
1340 | B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> |
1512 | B<< C<Ps = 18> >> Change colour of bold characters to B<< C<Pt> >> |
1341 | B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> |
1513 | B<< C<Ps = 19> >> Change colour of underlined characters to B<< C<Pt> >> |
1342 | B<< C<Ps = 20> >> Change default background to B<< C<Pt> >> |
1514 | B<< C<Ps = 20> >> Change default background to B<< C<Pt> >> |
1343 | B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >> I<rxvt compile-time option> |
1515 | B<< C<Ps = 39> >> Change default foreground colour to B<< C<Pt> >>. |
1344 | B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented> |
1516 | B<< C<Ps = 46> >> Change Log File to B<< C<Pt> >> I<unimplemented> |
1345 | B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >> I<rxvt compile-time option> |
1517 | B<< C<Ps = 49> >> Change default background colour to B<< C<Pt> >>. |
1346 | 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> >> |
1518 | 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> >> |
1347 | B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >> |
1519 | B<< C<Ps = 55> >> Log all scrollback buffer and all of screen to B<< C<Pt> >> |
1348 | B<< C<Ps = 701> >> Change current locale to B<< C<Pt> >>, or, if B<< C<Pt> >> is B<< C<?> >>, return the current locale (@@RXVT_NAME@@ extension) |
1520 | 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). |
1349 | B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> I<rxvt compile-time option> (rxvt-unicode extension) |
1521 | B<< C<Ps = 703> >> Menubar command B<< C<Pt> >> (Compile menubar). |
1350 | B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >> |
1522 | B<< C<Ps = 704> >> Change colour of italic characters to B<< C<Pt> >> |
1351 | B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> |
1523 | B<< C<Ps = 705> >> Change background pixmap tint colour to B<< C<Pt> >> (Compile transparency). |
1352 | B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>. |
1524 | B<< C<Ps = 710> >> Set normal fontset to B<< C<Pt> >>. Same as C<Ps = 50>. |
1353 | B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50>. |
1525 | B<< C<Ps = 711> >> Set bold fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles). |
1354 | B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>. |
1526 | B<< C<Ps = 712> >> Set italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles). |
1355 | B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50>. |
1527 | B<< C<Ps = 713> >> Set bold-italic fontset to B<< C<Pt> >>. Similar to C<Ps = 50> (Compile styles). |
|
|
1528 | B<< C<Ps = 720> >> Move viewing window up by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills). |
|
|
1529 | B<< C<Ps = 721> >> Move viewing window down by B<< C<Pt> >> lines, or clear scrollback buffer if C<Pt = 0> (Compile frills). |
1356 | |
1530 | |
1357 | =end table |
1531 | =end table |
1358 | |
1532 | |
1359 | =back |
1533 | =back |
1360 | |
1534 | |
… | |
… | |
1412 | |
1586 | |
1413 | =item B<< [title:+I<string>] >> |
1587 | =item B<< [title:+I<string>] >> |
1414 | |
1588 | |
1415 | set the current menuBar's title to I<string>, which may contain the |
1589 | set the current menuBar's title to I<string>, which may contain the |
1416 | following format specifiers: |
1590 | following format specifiers: |
1417 | B<%%> : literal B<%> character |
1591 | |
1418 | B<%n> : rxvt name (as per the B<-name> command-line option) |
1592 | B<%n> rxvt name (as per the B<-name> command-line option) |
1419 | B<%v> : rxvt version |
1593 | B<%v> rxvt version |
|
|
1594 | B<%%> literal B<%> character |
1420 | |
1595 | |
1421 | =item B<[done]> |
1596 | =item B<[done]> |
1422 | |
1597 | |
1423 | set menuBar access as B<readonly>. |
1598 | set menuBar access as B<readonly>. |
1424 | End-of-file tag for B<< [read:+I<file>] >> operations. |
1599 | End-of-file tag for B<< [read:+I<file>] >> operations. |
… | |
… | |
1570 | |
1745 | |
1571 | As a convenience for the many Emacs-type editors, I<action> may start |
1746 | As a convenience for the many Emacs-type editors, I<action> may start |
1572 | with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be |
1747 | with B<M-> (eg, B<M-$> is equivalent to B<\E$>) and a B<CR> will be |
1573 | appended if missed from B<M-x> commands. |
1748 | appended if missed from B<M-x> commands. |
1574 | |
1749 | |
1575 | As a convenience for issuing XTerm B<ESC]> sequences from a menubar (or |
1750 | As a convenience for issuing XTerm B<ESC ]> sequences from a menubar (or |
1576 | quick arrow), a B<BEL> (B<^G>) will be appended if needed. |
1751 | quick arrow), a B<BEL> (B<^G>) will be appended if needed. |
1577 | |
1752 | |
1578 | =over 4 |
1753 | =over 4 |
1579 | |
1754 | |
1580 | =item For example, |
1755 | =item For example, |
… | |
… | |
2044 | Add support for B<bold>, I<italic> and B<< I<bold italic> >> font |
2219 | Add support for B<bold>, I<italic> and B<< I<bold italic> >> font |
2045 | styles. The fonts can be set manually or automatically. |
2220 | styles. The fonts can be set manually or automatically. |
2046 | |
2221 | |
2047 | =item --with-codesets=NAME,... |
2222 | =item --with-codesets=NAME,... |
2048 | |
2223 | |
2049 | Compile in support for additional codeset (encoding) groups (eu, vn are |
2224 | Compile in support for additional codeset (encoding) groups (C<eu>, C<vn> |
2050 | always compiled in, which includes most 8-bit character sets). These |
2225 | are always compiled in, which includes most 8-bit character sets). These |
2051 | codeset tables are currently only used for driving X11 core fonts, they |
2226 | codeset tables are used for driving X11 core fonts, they are not required |
2052 | are not required for Xft fonts. Compiling them in will make your binary |
2227 | for Xft fonts, although having them compiled in lets rxvt-unicode choose |
2053 | bigger (together about 700kB), but it doesn't increase memory usage unless |
2228 | replacement fonts more intelligently. Compiling them in will make your |
|
|
2229 | binary bigger (all of together cost about 700kB), but it doesn't increase |
2054 | you use an X11 font requiring one of these encodings. |
2230 | memory usage unless you use a font requiring one of these encodings. |
2055 | |
2231 | |
2056 | =begin table |
2232 | =begin table |
2057 | |
2233 | |
2058 | all all available codeset groups |
2234 | all all available codeset groups |
2059 | zh common chinese encodings |
2235 | zh common chinese encodings |
… | |
… | |
2089 | composite characters. This is required for proper viewing of text |
2265 | composite characters. This is required for proper viewing of text |
2090 | where accents are encoded as seperate unicode characters. This is |
2266 | where accents are encoded as seperate unicode characters. This is |
2091 | done by using precomposited characters when available or creating |
2267 | done by using precomposited characters when available or creating |
2092 | new pseudo-characters when no precomposed form exists. |
2268 | new pseudo-characters when no precomposed form exists. |
2093 | |
2269 | |
2094 | Without --enable-unicode3, the number of additional precomposed |
2270 | Without --enable-unicode3, the number of additional precomposed characters |
2095 | characters is rather limited (2048, if this is full, rxvt will use the |
2271 | is rather limited (2048, if this is full, rxvt-unicode will use the |
2096 | private use area, extending the number of combinations to 8448). With |
2272 | private use area, extending the number of combinations to 8448). With |
2097 | --enable-unicode3, no practical limit exists. This will also enable |
2273 | --enable-unicode3, no practical limit exists. |
2098 | storage of characters >65535. |
2274 | |
|
|
2275 | This option will also enable storage (but not display) of characters |
|
|
2276 | beyond plane 0 (>65535) when --enable-unicode3 was not specified. |
2099 | |
2277 | |
2100 | The combining table also contains entries for arabic presentation forms, |
2278 | The combining table also contains entries for arabic presentation forms, |
2101 | but these are not currently used. Bug me if you want these to be used. |
2279 | but these are not currently used. Bug me if you want these to be used (and |
|
|
2280 | tell me how these are to be used...). |
2102 | |
2281 | |
2103 | =item --enable-fallback(=CLASS) |
2282 | =item --enable-fallback(=CLASS) |
2104 | |
2283 | |
2105 | When reading resource settings, also read settings for class CLASS |
2284 | When reading resource settings, also read settings for class CLASS |
2106 | (default: Rxvt). To disable resource fallback use --disable-fallback. |
2285 | (default: Rxvt). To disable resource fallback use --disable-fallback. |
… | |
… | |
2198 | Remove all resources checking. |
2377 | Remove all resources checking. |
2199 | |
2378 | |
2200 | =item --enable-xgetdefault |
2379 | =item --enable-xgetdefault |
2201 | |
2380 | |
2202 | Make resources checking via XGetDefault() instead of our small |
2381 | Make resources checking via XGetDefault() instead of our small |
2203 | version which only checks ~/.Xdefaults, or if that doesn't exist |
2382 | version which only checks ~/.Xdefaults, or if that doesn't exist then |
2204 | then ~/.Xresources. |
2383 | ~/.Xresources. |
|
|
2384 | |
|
|
2385 | Please note that nowadays, things like XIM will automatically pull in and |
|
|
2386 | use the full X resource manager, so the overhead of using it might be very |
|
|
2387 | small, if nonexistant. |
2205 | |
2388 | |
2206 | =item --enable-strings |
2389 | =item --enable-strings |
2207 | |
2390 | |
2208 | Add support for our possibly faster memset() function and other |
2391 | Add support for our possibly faster memset() function and other |
2209 | various routines, overriding your system's versions which may |
2392 | various routines, overriding your system's versions which may |
… | |
… | |
2219 | |
2402 | |
2220 | Add support for many small features that are not essential but nice to |
2403 | Add support for many small features that are not essential but nice to |
2221 | have. Normally you want this, but for very small binaries you may want to |
2404 | have. Normally you want this, but for very small binaries you may want to |
2222 | disable this. |
2405 | disable this. |
2223 | |
2406 | |
|
|
2407 | A non-exhaustive list of features enabled by C<--enable-frills> (possibly |
|
|
2408 | in combination with other switches) is: |
|
|
2409 | |
|
|
2410 | MWM-hints |
|
|
2411 | EWMH-hints (pid, utf8 names) and protocols (ping) |
|
|
2412 | seperate underline colour |
|
|
2413 | settable border widths and borderless switch |
|
|
2414 | settable extra linespacing |
|
|
2415 | iso-14755-2 and -3, and visual feedback |
|
|
2416 | backindex and forwardindex escape sequence |
|
|
2417 | window op and some xterm/OSC escape sequences |
|
|
2418 | tripleclickwords |
|
|
2419 | settable insecure mode |
|
|
2420 | keysym remapping support |
|
|
2421 | cursor blinking and underline cursor |
|
|
2422 | -embed and -pty-fd options |
|
|
2423 | |
2224 | =item --enable-iso14755 |
2424 | =item --enable-iso14755 |
2225 | |
2425 | |
2226 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2426 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2227 | F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by |
2427 | F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by |
2228 | C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with |
2428 | C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with |
2229 | this switch. |
2429 | this switch. |
2230 | |
2430 | |
2231 | =item --enable-linespace |
|
|
2232 | |
|
|
2233 | Add support to provide user specified line spacing between text rows. |
|
|
2234 | |
|
|
2235 | =item --enable-keepscrolling |
2431 | =item --enable-keepscrolling |
2236 | |
2432 | |
2237 | Add support for continual scrolling of the display when you hold |
2433 | Add support for continual scrolling of the display when you hold |
2238 | the mouse button down on a scrollbar arrow. |
2434 | the mouse button down on a scrollbar arrow. |
2239 | |
2435 | |
… | |
… | |
2270 | |
2466 | |
2271 | Add smart growth/shrink behaviour when changing font size via from hot |
2467 | Add smart growth/shrink behaviour when changing font size via from hot |
2272 | keys. This should keep in a fixed position the rxvt corner which is |
2468 | keys. This should keep in a fixed position the rxvt corner which is |
2273 | closest to a corner of the screen. |
2469 | closest to a corner of the screen. |
2274 | |
2470 | |
2275 | =item --enable-cursor-blink |
|
|
2276 | |
|
|
2277 | Add support for a blinking cursor. |
|
|
2278 | |
|
|
2279 | =item --enable-pointer-blank |
2471 | =item --enable-pointer-blank |
2280 | |
2472 | |
2281 | Add support to have the pointer disappear when typing or inactive. |
2473 | Add support to have the pointer disappear when typing or inactive. |
2282 | |
2474 | |
2283 | =item --with-name=NAME |
2475 | =item --with-name=NAME |
2284 | |
2476 | |
2285 | Set the basename for the installed binaries (default: urxvt, resulting in |
2477 | Set the basename for the installed binaries (default: C<urxvt>, resulting |
2286 | urxvt, urxvtd etc.). Specify --with-name=rxvt to replace rxvt. |
2478 | in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with |
|
|
2479 | C<rxvt>. |
2287 | |
2480 | |
2288 | =item --with-term=NAME |
2481 | =item --with-term=NAME |
2289 | |
2482 | |
2290 | Change the environmental variable for the terminal to NAME (default |
2483 | Change the environmental variable for the terminal to NAME (default |
2291 | "rxvt") |
2484 | C<rxvt-unicode>) |
2292 | |
2485 | |
2293 | =item --with-terminfo=PATH |
2486 | =item --with-terminfo=PATH |
2294 | |
2487 | |
2295 | Change the environmental variable for the path to the terminfo tree to |
2488 | Change the environmental variable for the path to the terminfo tree to |
2296 | PATH. |
2489 | PATH. |