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 contains large patches that |
|
|
37 | considerably change the behaviour of rxvt-unicode. Before reporting a |
|
|
38 | bug to the original rxvt-unicode author please download and install the |
|
|
39 | genuine version (L<http://software.schmorp.de#rxvt-unicode>) and try to |
|
|
40 | reproduce the problem. If you cannot, chances are that the problems are |
|
|
41 | specific to Debian GNU/Linux, in which case it should be reported via the |
|
|
42 | Debian Bug Tracking System (use C<reportbug> to report the bug). |
|
|
43 | |
|
|
44 | For other problems that also affect the Debian package, you can and |
|
|
45 | probably should use the Debian BTS, too, because, after all, it's also a |
|
|
46 | bug in the Debian version and it serves as a reminder for other users that |
|
|
47 | might encounter the same issue. |
13 | |
48 | |
14 | =item When I log-in to another system it tells me about missing terminfo data? |
49 | =item When I log-in to another system it tells me about missing terminfo data? |
15 | |
50 | |
16 | The terminal description used by rxvt-unicode is not as widely available |
51 | 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). |
52 | 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 |
63 | 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 |
64 | problems arising, which includes wrong keymapping, less and different |
30 | colours and some refresh errors in fullscreen applications. It's a nice |
65 | colours and some refresh errors in fullscreen applications. It's a nice |
31 | quick-and-dirty workaround for rare cases, though. |
66 | quick-and-dirty workaround for rare cases, though. |
32 | |
67 | |
33 | If you always want to do this you can either recompile rxvt-unicode with |
68 | 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: |
69 | can either recompile rxvt-unicode with the desired TERM value or use a |
|
|
70 | resource to set it: |
35 | |
71 | |
36 | URxvt.termName: rxvt |
72 | URxvt.termName: rxvt |
37 | |
73 | |
38 | If you don't plan to use B<rxvt> (quite common...) you could also replace |
74 | 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. |
75 | the rxvt terminfo file with the rxvt-unicode one. |
40 | |
76 | |
|
|
77 | =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
|
|
78 | |
41 | =item I need a termcap file entry. |
79 | =item I need a termcap file entry. |
|
|
80 | |
|
|
81 | One reason you might want this is that some distributions or operating |
|
|
82 | systems still compile some programs using the long-obsoleted termcap |
|
|
83 | library (Fedora Core's bash is one example) and rely on a termcap entry |
|
|
84 | for C<rxvt-unicode>. |
42 | |
85 | |
43 | You could use rxvt's termcap entry with resonable results in many cases. |
86 | 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 |
87 | You can also create a termcap entry by using terminfo's infocmp program |
45 | like this: |
88 | like this: |
46 | |
89 | |
47 | infocmp -C rxvt-unicode |
90 | infocmp -C rxvt-unicode |
48 | |
91 | |
49 | OR you could this termcap entry: |
92 | Or you could use this termcap entry, generated by the command above: |
50 | |
93 | |
51 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
94 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
52 | :am:bw:eo:km:mi:ms:xn:xo:\ |
95 | :am:bw:eo:km:mi:ms:xn:xo:\ |
53 | :co#80:it#8:li#24:\ |
96 | :co#80:it#8:li#24:lm#0:\ |
54 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
97 | :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:\ |
98 | :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:\ |
99 | :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:\ |
100 | :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:\ |
101 | :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[@:\ |
102 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
|
|
103 | :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:\ |
104 | :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~:\ |
105 | :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~:\ |
106 | :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:\ |
107 | :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=:\ |
108 | :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:\ |
109 | :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:\ |
110 | :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:\ |
111 | :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:\ |
112 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
69 | :vs=\E[?25h: |
113 | :vs=\E[?25h: |
70 | |
114 | |
71 | =item How can I configure rxvt-unicode so that it looks similar to the original rxvt? |
115 | =item Why does C<ls> no longer have coloured output? |
72 | |
116 | |
73 | Felix von Leitner says that these two lines, in your F<.Xdefaults>, will make rxvt-unicode |
117 | The C<ls> in the GNU coreutils unfortunately doesn't use terminfo to |
74 | behave similar to the original rxvt: |
118 | decide wether a terminal has colour, but uses it's own configuration |
|
|
119 | file. Needless to say, C<rxvt-unicode> is not in it's default file (among |
|
|
120 | with most other terminals supporting colour). Either add: |
75 | |
121 | |
76 | URxvt.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1 |
122 | TERM rxvt-unicode |
77 | URxvt.boldFont: -misc-fixed-bold-r-semicondensed--13-120-75-75-c-60-iso8859-1 |
123 | |
|
|
124 | to C</etc/DIR_COLORS> or simply add: |
|
|
125 | |
|
|
126 | alias ls='ls --color=auto' |
|
|
127 | |
|
|
128 | to your C<.profile> or C<.bashrc>. |
|
|
129 | |
|
|
130 | =item Why doesn't vim/emacs etc. use the 88 colour mode? |
|
|
131 | |
|
|
132 | =item Why doesn't vim/emacs etc. make use of italic? |
|
|
133 | |
|
|
134 | =item Why are the secondary screen-related options not working properly? |
|
|
135 | |
|
|
136 | Make sure you are using C<TERM=rxvt-unicode>. Some pre-packaged |
|
|
137 | distributions (most notably Debian GNU/Linux) break rxvt-unicode |
|
|
138 | by setting C<TERM> to C<rxvt>, which doesn't have these extra |
|
|
139 | features. Unfortunately, some of these (most notably, again, Debian |
|
|
140 | GNU/Linux) furthermore fail to even install the C<rxvt-unicode> terminfo |
|
|
141 | file, so you will need to install it on your own (See the question B<When |
|
|
142 | I log-in to another system it tells me about missing terminfo data?> on |
|
|
143 | how to do this). |
|
|
144 | |
|
|
145 | =item My numerical keypad acts weird and generates differing output? |
|
|
146 | |
|
|
147 | Some Debian GNUL/Linux users seem to have this problem, although no |
|
|
148 | specific details were reported so far. It is possible that this is caused |
|
|
149 | by the wrong C<TERM> setting, although the details of wether and how |
|
|
150 | this can happen are unknown, as C<TERM=rxvt> should offer a compatible |
|
|
151 | keymap. See the answer to the previous question, and please report if that |
|
|
152 | helped. |
78 | |
153 | |
79 | =item Rxvt-unicode does not seem to understand the selected encoding? |
154 | =item Rxvt-unicode does not seem to understand the selected encoding? |
80 | |
155 | |
81 | =item Unicode does not seem to work? |
156 | =item Unicode does not seem to work? |
82 | |
157 | |
… | |
… | |
85 | subtly garbled, then you should check your locale settings. |
160 | subtly garbled, then you should check your locale settings. |
86 | |
161 | |
87 | Rxvt-unicode must be started with the same C<LC_CTYPE> setting as the |
162 | 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 |
163 | 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 |
164 | 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. |
165 | something else, e.g. C<en_GB.UTF-8>. Needless to say, this is not going to work. |
91 | |
166 | |
92 | The best thing is to fix your startup environment, as you will likely run |
167 | 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. |
168 | into other problems. If nothing works you can try this in your .profile. |
94 | |
169 | |
95 | printf '\e]701;%s\007' "$LC_CTYPE" |
170 | printf '\e]701;%s\007' "$LC_CTYPE" |
96 | |
171 | |
97 | If this doesn't work, then maybe you use a C<LC_CTYPE> specification not |
172 | 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 |
173 | supported on your systems. Some systems have a C<locale> command which |
99 | displays this. If it displays sth. like: |
174 | displays this (also, C<perl -e0> can be used to check locale settings, as |
|
|
175 | it will complain loudly if it cannot set the locale). If it displays something |
|
|
176 | like: |
100 | |
177 | |
101 | locale: Cannot set LC_CTYPE to default locale: ... |
178 | locale: Cannot set LC_CTYPE to default locale: ... |
102 | |
179 | |
103 | Then the locale you specified is not supported on your system. |
180 | Then the locale you specified is not supported on your system. |
104 | |
181 | |
… | |
… | |
115 | your system/os) have specified does not cover all the characters you want |
192 | your system/os) have specified does not cover all the characters you want |
116 | to display. |
193 | to display. |
117 | |
194 | |
118 | B<rxvt-unicode> makes a best-effort try at finding a replacement |
195 | 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 |
196 | 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 |
197 | bad/ugly/wrong. Some fonts have totally strange characters that don't |
121 | correct glyph at all, and rxvt-unicode lacks the artificial intelligence |
198 | 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 |
199 | intelligence to detect that a specific glyph is wrong: it has to believe |
123 | the characters it contains indeed look correct. |
200 | the font that the characters it claims to contain indeed look correct. |
124 | |
201 | |
125 | In that case, select a font of your taste and add it to the font list, |
202 | In that case, select a font of your taste and add it to the font list, |
126 | e.g.: |
203 | e.g.: |
127 | |
204 | |
128 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
205 | @@RXVT_NAME@@ -fn basefont,font2,font3... |
… | |
… | |
130 | When rxvt-unicode sees a character, it will first look at the base |
207 | 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 |
208 | 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 |
209 | 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. |
210 | search and use less resources within rxvt-unicode and the X-server. |
134 | |
211 | |
135 | The only limitation is that all the fonts must not be larger than the base |
212 | 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 |
213 | font, as the base font defines the terminal character cell size, which |
137 | same due to the way terminals work. |
214 | must be the same due to the way terminals work. |
138 | |
215 | |
139 | =item Why do some chinese characters look so different than others? |
216 | =item Why do some chinese characters look so different than others? |
140 | |
217 | |
141 | This is because there is a difference between script and language -- |
218 | This is because there is a difference between script and language -- |
142 | rxvt-unicode does not know which language the text that is output |
219 | 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 |
220 | 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 |
221 | sees a japanese/chinese character, it might choose a japanese font for |
145 | it. Subsequent japanese characters will take that font. Now, many chinese |
222 | display. Subsequent japanese characters will use that font. Now, many |
146 | characters aren't represented in japanese fonts, so when the first |
223 | 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 |
224 | 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 |
225 | -- unfortunately at this point, it will still use the japanese font for |
149 | japanese characters that are also chinese. |
226 | chinese characters that are also in the japanese font. |
150 | |
227 | |
151 | The workaround is easy: just tag a chinese font at the end of your font |
228 | 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 |
229 | 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 |
230 | a preference list: If you expect more japanese, list a japanese font |
154 | first. If you expect more chinese, put a chinese font first. |
231 | first. If you expect more chinese, put a chinese font first. |
155 | |
232 | |
156 | In the future it might be possible to switch preferences at runtime (the |
233 | In the future it might be possible to switch language preferences at |
157 | internal data structure has no problem with using different fonts for |
234 | 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 |
235 | fonts for the same character at the same time, but no interface for this |
159 | designed yet). |
236 | has been designed yet). |
|
|
237 | |
|
|
238 | Until then, you might get away with switching fonts at runtime (see L<Can |
|
|
239 | I switch the fonts at runtime?> later in this document). |
160 | |
240 | |
161 | =item Why does rxvt-unicode sometimes leave pixel droppings? |
241 | =item Why does rxvt-unicode sometimes leave pixel droppings? |
162 | |
242 | |
163 | Most fonts were not designed for terminal use, which means that character |
243 | 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 |
244 | 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 |
250 | 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 |
251 | 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 |
252 | ask for the character bounding box, which unfortunately is wrong in these |
173 | cases). |
253 | cases). |
174 | |
254 | |
175 | It's not clear (to me at least), wether this is a bug in Xft, freetype, or |
255 | 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 |
256 | or the respective font. If you encounter this problem you might try using |
177 | around this except by using a different font. |
257 | the C<-lsp> option to give the font more height. If that doesn't work, you |
|
|
258 | might be forced to use a different font. |
178 | |
259 | |
179 | All of this is not a problem when using X11 core fonts, as their bounding |
260 | All of this is not a problem when using X11 core fonts, as their bounding |
180 | box data is correct. |
261 | box data is correct. |
181 | |
262 | |
182 | =item My Compose (Multi_key) key is no longer working. |
263 | =item My Compose (Multi_key) key is no longer working. |
… | |
… | |
189 | rxvt-unicode will continue without an input method. |
270 | rxvt-unicode will continue without an input method. |
190 | |
271 | |
191 | In this case either do not specify a B<preeditStyle> or specify more than |
272 | 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>. |
273 | one pre-edit style, such as B<OverTheSpot,Root,None>. |
193 | |
274 | |
|
|
275 | =item I cannot type C<Ctrl-Shift-2> to get an ASCII NUL character due to ISO 14755 |
|
|
276 | |
|
|
277 | Either try C<Ctrl-2> alone (it often is mapped to ASCII NUL even on |
|
|
278 | international keyboards) or simply use ISO 14755 support to your |
|
|
279 | advantage, typing <Ctrl-Shift-0> to get a ASCII NUL. This works for other |
|
|
280 | codes, too, such as C<Ctrl-Shift-1-d> to type the default telnet escape |
|
|
281 | character and so on. |
|
|
282 | |
194 | =item How can I keep rxvt-unicode from using reverse video so much? |
283 | =item How can I keep rxvt-unicode from using reverse video so much? |
195 | |
284 | |
196 | First of all, make sure you are running with the right terminfo |
285 | 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 |
286 | (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 |
287 | make sure you have specified colours for italic and bold, as otherwise |
199 | might use reverse video to simulate the effect: |
288 | rxvt-unicode might use reverse video to simulate the effect: |
200 | |
289 | |
201 | URxvt*colorBD: white |
290 | URxvt.colorBD: white |
202 | URxvt*colorIT: green |
291 | URxvt.colorIT: green |
203 | |
292 | |
204 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
293 | =item Some programs assume totally weird colours (red instead of blue), how can I fix that? |
205 | |
294 | |
206 | For some unexplainable reason, some programs (i.e. irssi) assume a very |
295 | For some unexplainable reason, some rare programs assume a very weird |
207 | weird colour palette when confronted with a terminal with more than the |
296 | 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 |
297 | 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 |
298 | these programs not to assume non-ISO colours without very good reasons. |
210 | good reasons. |
|
|
211 | |
299 | |
212 | In the meantime, you can either edit your C<urxvt> terminfo definition to |
300 | 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 |
301 | definition to only claim 8 colour support or use C<TERM=rxvt>, which will |
214 | but keep you from using other rxvt-unicode features. |
302 | fix colours but keep you from using other rxvt-unicode features. |
215 | |
303 | |
216 | =item I am on FreeBSD and rxvt-unicode does not seem to work at all. |
304 | =item I am on FreeBSD and rxvt-unicode does not seem to work at all. |
217 | |
305 | |
218 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
306 | Rxvt-unicode requires the symbol C<__STDC_ISO_10646__> to be defined |
219 | in your compile environment, or an implementation that implements it, |
307 | in your compile environment, or an implementation that implements it, |
220 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
308 | wether it defines the symbol or not. C<__STDC_ISO_10646__> requires that |
221 | B<wchar_t> is represented as unicode. |
309 | B<wchar_t> is represented as unicode. |
222 | |
310 | |
223 | As you might have guessed, FreeBSD does neither define this symobl nor |
311 | 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 |
312 | does it support it. Instead, it uses it's own internal representation of |
225 | B<wchar_t>. This is, of course, completely legal. |
313 | B<wchar_t>. This is, of course, completely fine with respect to standards. |
226 | |
314 | |
227 | However, C<__STDC_ISO_10646__> is the only sane way to support |
315 | However, C<__STDC_ISO_10646__> is the only sane way to support |
228 | multi-language apps in an OS, as using a locale-dependent (and |
316 | multi-language apps in an OS, as using a locale-dependent (and |
229 | non-standardized) representation of B<wchar_t> makes it impossible to |
317 | non-standardized) representation of B<wchar_t> makes it impossible to |
230 | convert between B<wchar_t> (as used by X11 and your applications) and any |
318 | convert between B<wchar_t> (as used by X11 and your applications) and any |
… | |
… | |
238 | conversions (which is slow and unreliable in case the OS implements |
326 | conversions (which is slow and unreliable in case the OS implements |
239 | encodings slightly different than the terminal emulator). |
327 | encodings slightly different than the terminal emulator). |
240 | |
328 | |
241 | The rxvt-unicode author insists that the right way to fix this is in the |
329 | 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 |
330 | system libraries once and for all, instead of forcing every app to carry |
243 | complete replacements. |
331 | complete replacements for them :) |
244 | |
332 | |
245 | =item How does rxvt-unicode determine the encoding to use? |
333 | =item How does rxvt-unicode determine the encoding to use? |
246 | |
334 | |
247 | =item Is there an option to switch encodings? |
335 | =item Is there an option to switch encodings? |
248 | |
336 | |
… | |
… | |
250 | specific "utf-8" mode, such as xterm. In fact, it doesn't even know about |
338 | 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. |
339 | UTF-8 or any other encodings with respect to terminal I/O. |
252 | |
340 | |
253 | The reasons is that there exists a perfectly fine mechanism for selecting |
341 | 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 |
342 | the encoding, doing I/O and (most important) communicating this to all |
255 | applications so everybody agrees on character properties such as width and |
343 | applications so everybody agrees on character properties such as width |
256 | code number. This mechanism is the I<locale>. |
344 | and code number. This mechanism is the I<locale>. Applications not using |
|
|
345 | that info will have problems (for example, C<xterm> gets the width of |
|
|
346 | characters wrong as it uses it's own, locale-independent table under all |
|
|
347 | locales). |
257 | |
348 | |
258 | Rxvt-unicode uses the C<LC_CTYPE> locale category to select encoding. All |
349 | 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 |
350 | programs doing the same (that is, most) will automatically agree in the |
260 | interpretation of characters. |
351 | interpretation of characters. |
261 | |
352 | |
… | |
… | |
268 | C<ja_JP.EUC-JP>, i.e. C<language_country.encoding>, but other forms |
359 | 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. |
360 | (i.e. C<de> or C<german>) are also common. |
270 | |
361 | |
271 | Rxvt-unicode ignores all other locale categories, and except for |
362 | Rxvt-unicode ignores all other locale categories, and except for |
272 | the encoding, ignores country or language-specific settings, |
363 | 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. |
364 | i.e. C<de_DE.UTF-8> and C<ja_JP.UTF-8> are the normally same to |
|
|
365 | rxvt-unicode. |
274 | |
366 | |
275 | If you want to use a specific encoding you have to make sure you start |
367 | 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. |
368 | rxvt-unicode with the correct C<LC_CTYPE> category. |
277 | |
369 | |
278 | =item Can I switch locales at runtime? |
370 | =item Can I switch locales at runtime? |
279 | |
371 | |
280 | Yes, using an escape sequence. Try sth. like this, which sets |
372 | Yes, using an escape sequence. Try something like this, which sets |
281 | rxvt-unicode's idea of C<LC_CTYPE>. |
373 | rxvt-unicode's idea of C<LC_CTYPE>. |
282 | |
374 | |
283 | printf '\e]701;%s\007' ja_JP.SJIS |
375 | printf '\e]701;%s\007' ja_JP.SJIS |
284 | |
376 | |
285 | See also the previous question. |
377 | See also the previous answer. |
286 | |
378 | |
287 | Sometimes this capability is rather handy when you want to work in one |
379 | 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 |
380 | 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 |
381 | (e.g. UTF-8). For example, I use this script to start C<xjdic>, which |
290 | locale supported by xjdic and back later: |
382 | first switches to a locale supported by xjdic and back later: |
291 | |
383 | |
292 | printf '\e]701;%s\007' ja_JP.SJIS |
384 | printf '\e]701;%s\007' ja_JP.SJIS |
293 | xjdic -js |
385 | xjdic -js |
294 | printf '\e]701;%s\007' de_DE.UTF-8 |
386 | printf '\e]701;%s\007' de_DE.UTF-8 |
295 | |
387 | |
|
|
388 | You can also use xterm's C<luit> program, which usually works fine, except |
|
|
389 | for some locales where character width differs between program- and |
|
|
390 | rxvt-unicode-locales. |
|
|
391 | |
296 | =item Can I switch the fonts at runtime? |
392 | =item Can I switch the fonts at runtime? |
297 | |
393 | |
298 | Yes, using an escape sequence. Try sth. like this, which has the same |
394 | 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: |
395 | effect as using the C<-fn> switch, and takes effect immediately: |
300 | |
396 | |
301 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
397 | printf '\e]50;%s\007' "9x15bold,xft:Kochi Gothic" |
302 | |
398 | |
303 | This is useful if you e.g. work primarily with japanese (and prefer a |
399 | This is useful if you e.g. work primarily with japanese (and prefer a |
… | |
… | |
308 | |
404 | |
309 | =item Why do italic characters look as if clipped? |
405 | =item Why do italic characters look as if clipped? |
310 | |
406 | |
311 | Many fonts have difficulties with italic characters and hinting. For |
407 | Many fonts have difficulties with italic characters and hinting. For |
312 | example, the otherwise very nicely hinted font C<xft:Bitstream Vera Sans |
408 | 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 |
409 | Mono> completely fails in it's italic face. A workaround might be to |
314 | freetype autohinting, i.e. like this: |
410 | enable freetype autohinting, i.e. like this: |
315 | |
411 | |
316 | URxvt*italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
412 | URxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
317 | URxvt*boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
413 | URxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
318 | |
414 | |
319 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
415 | =item My input method wants <some encoding> but I want UTF-8, what can I do? |
320 | |
416 | |
321 | You can specify separate locales for the input method and the rest of the |
417 | You can specify separate locales for the input method and the rest of the |
322 | terminal, using the resource C<imlocale>: |
418 | terminal, using the resource C<imlocale>: |
… | |
… | |
326 | Now you can start your terminal with C<LC_CTYPE=ja_JP.UTF-8> and still |
422 | 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 |
423 | 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 |
424 | input characters outside C<EUC-JP> in a normal way then, as your input |
329 | method limits you. |
425 | method limits you. |
330 | |
426 | |
|
|
427 | =item Rxvt-unicode crashes when the X Input Method changes or exits. |
|
|
428 | |
|
|
429 | Unfortunately, this is unavoidable, as the XIM protocol is racy by |
|
|
430 | design. Applications can avoid some crashes at the expense of memory |
|
|
431 | leaks, and Input Methods can avoid some crashes by careful ordering at |
|
|
432 | exit time. B<kinput2> (and derived input methods) generally succeeds, |
|
|
433 | while B<SCIM> (or similar input methods) fails. In the end, however, |
|
|
434 | crashes cannot be completely avoided even if both sides cooperate. |
|
|
435 | |
|
|
436 | So the only workaround is not to kill your Input Method Servers. |
|
|
437 | |
331 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
438 | =item Rxvt-unicode uses gobs of memory, how can I reduce that? |
332 | |
439 | |
333 | Rxvt-unicode tries to obey the rule of not charging you for sth. you |
440 | 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 |
441 | 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, |
442 | 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 |
443 | 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. |
444 | accidentally when rxvt-unicode tries to find a font for your characters. |
338 | |
445 | |
… | |
… | |
391 | resources (or as long-options). |
498 | resources (or as long-options). |
392 | |
499 | |
393 | Here are values that are supposed to resemble a VGA screen, |
500 | Here are values that are supposed to resemble a VGA screen, |
394 | including the murky brown that passes for low-intensity yellow: |
501 | including the murky brown that passes for low-intensity yellow: |
395 | |
502 | |
396 | Rxvt*color0: #000000 |
503 | URxvt.color0: #000000 |
397 | Rxvt*color1: #A80000 |
504 | URxvt.color1: #A80000 |
398 | Rxvt*color2: #00A800 |
505 | URxvt.color2: #00A800 |
399 | Rxvt*color3: #A8A800 |
506 | URxvt.color3: #A8A800 |
400 | Rxvt*color4: #0000A8 |
507 | URxvt.color4: #0000A8 |
401 | Rxvt*color5: #A800A8 |
508 | URxvt.color5: #A800A8 |
402 | Rxvt*color6: #00A8A8 |
509 | URxvt.color6: #00A8A8 |
403 | Rxvt*color7: #A8A8A8 |
510 | URxvt.color7: #A8A8A8 |
404 | |
511 | |
405 | Rxvt*color8: #000054 |
512 | URxvt.color8: #000054 |
406 | Rxvt*color9: #FF0054 |
513 | URxvt.color9: #FF0054 |
407 | Rxvt*color10: #00FF54 |
514 | URxvt.color10: #00FF54 |
408 | Rxvt*color11: #FFFF54 |
515 | URxvt.color11: #FFFF54 |
409 | Rxvt*color12: #0000FF |
516 | URxvt.color12: #0000FF |
410 | Rxvt*color13: #FF00FF |
517 | URxvt.color13: #FF00FF |
411 | Rxvt*color14: #00FFFF |
518 | URxvt.color14: #00FFFF |
412 | Rxvt*color15: #FFFFFF |
519 | URxvt.color15: #FFFFFF |
|
|
520 | |
|
|
521 | And here is a more complete set of non-standard colors described (not by |
|
|
522 | me) as "pretty girly". |
|
|
523 | |
|
|
524 | URxvt.cursorColor: #dc74d1 |
|
|
525 | URxvt.pointerColor: #dc74d1 |
|
|
526 | URxvt.background: #0e0e0e |
|
|
527 | URxvt.foreground: #4ad5e1 |
|
|
528 | URxvt.color0: #000000 |
|
|
529 | URxvt.color8: #8b8f93 |
|
|
530 | URxvt.color1: #dc74d1 |
|
|
531 | URxvt.color9: #dc74d1 |
|
|
532 | URxvt.color2: #0eb8c7 |
|
|
533 | URxvt.color10: #0eb8c7 |
|
|
534 | URxvt.color3: #dfe37e |
|
|
535 | URxvt.color11: #dfe37e |
|
|
536 | URxvt.color5: #9e88f0 |
|
|
537 | URxvt.color13: #9e88f0 |
|
|
538 | URxvt.color6: #73f7ff |
|
|
539 | URxvt.color14: #73f7ff |
|
|
540 | URxvt.color7: #e1dddd |
|
|
541 | URxvt.color15: #e1dddd |
|
|
542 | |
|
|
543 | =item How can I start @@RXVT_NAME@@d in a race-free way? |
|
|
544 | |
|
|
545 | Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a |
|
|
546 | server that answers @@RXVT_NAME@@c's requests, so it doesn't background |
|
|
547 | itself. |
|
|
548 | |
|
|
549 | To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the |
|
|
550 | following method to wait for the startup message before continuing: |
|
|
551 | |
|
|
552 | { @@RXVT_NAME@@d & } | read |
413 | |
553 | |
414 | =item What's with the strange Backspace/Delete key behaviour? |
554 | =item What's with the strange Backspace/Delete key behaviour? |
415 | |
555 | |
416 | Assuming that the physical Backspace key corresponds to the |
556 | Assuming that the physical Backspace key corresponds to the |
417 | BackSpace keysym (not likely for Linux ... see the following |
557 | BackSpace keysym (not likely for Linux ... see the following |
… | |
… | |
436 | |
576 | |
437 | # use Backspace = ^? |
577 | # use Backspace = ^? |
438 | $ stty erase ^? |
578 | $ stty erase ^? |
439 | $ @@RXVT_NAME@@ |
579 | $ @@RXVT_NAME@@ |
440 | |
580 | |
441 | Toggle with "ESC[36h" / "ESC[36l" as documented in @@RXVT_NAME@@(7). |
581 | Toggle with C<ESC [ 36 h> / C<ESC [ 36 l> as documented in @@RXVT_NAME@@(7). |
442 | |
582 | |
443 | For an existing rxvt-unicode: |
583 | For an existing rxvt-unicode: |
444 | |
584 | |
445 | # use Backspace = ^H |
585 | # use Backspace = ^H |
446 | $ stty erase ^H |
586 | $ stty erase ^H |
… | |
… | |
455 | properly reflects that. |
595 | properly reflects that. |
456 | |
596 | |
457 | The Delete key is a another casualty of the ill-defined Backspace problem. |
597 | 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 |
598 | 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 |
599 | key has been assigned an escape sequence to match the vt100 for Execute |
460 | (ESC[3~) and is in the supplied termcap/terminfo. |
600 | (C<ESC [ 3 ~>) and is in the supplied termcap/terminfo. |
461 | |
601 | |
462 | Some other Backspace problems: |
602 | Some other Backspace problems: |
463 | |
603 | |
464 | some editors use termcap/terminfo, |
604 | some editors use termcap/terminfo, |
465 | some editors (vim I'm told) expect Backspace = ^H, |
605 | some editors (vim I'm told) expect Backspace = ^H, |
… | |
… | |
469 | |
609 | |
470 | =item I don't like the key-bindings. How do I change them? |
610 | =item I don't like the key-bindings. How do I change them? |
471 | |
611 | |
472 | There are some compile-time selections available via configure. Unless |
612 | There are some compile-time selections available via configure. Unless |
473 | you have run "configure" with the C<--disable-resources> option you can |
613 | you have run "configure" with the C<--disable-resources> option you can |
474 | use the `keysym' resource to alter the keystrings associated with keysym |
614 | use the `keysym' resource to alter the keystrings associated with keysyms. |
475 | 0xFF00 - 0xFFFF (function, cursor keys, etc). |
|
|
476 | |
615 | |
477 | Here's an example for a tn3270 session started using `@@RXVT_NAME@@ -name tn3270' |
616 | Here's an example for a URxvt session started using C<@@RXVT_NAME@@ -name URxvt> |
478 | |
617 | |
479 | !# ----- special uses ------: |
618 | URxvt.keysym.Home: \033[1~ |
480 | ! tn3270 login, remap function and arrow keys. |
619 | URxvt.keysym.End: \033[4~ |
481 | tn3270*font: *clean-bold-*-*--15-* |
620 | URxvt.keysym.C-apostrophe: \033<C-'> |
|
|
621 | URxvt.keysym.C-slash: \033<C-/> |
|
|
622 | URxvt.keysym.C-semicolon: \033<C-;> |
|
|
623 | URxvt.keysym.C-grave: \033<C-`> |
|
|
624 | URxvt.keysym.C-comma: \033<C-,> |
|
|
625 | URxvt.keysym.C-period: \033<C-.> |
|
|
626 | URxvt.keysym.C-0x60: \033<C-`> |
|
|
627 | URxvt.keysym.C-Tab: \033<C-Tab> |
|
|
628 | URxvt.keysym.C-Return: \033<C-Return> |
|
|
629 | URxvt.keysym.S-Return: \033<S-Return> |
|
|
630 | URxvt.keysym.S-space: \033<S-Space> |
|
|
631 | URxvt.keysym.M-Up: \033<M-Up> |
|
|
632 | URxvt.keysym.M-Down: \033<M-Down> |
|
|
633 | URxvt.keysym.M-Left: \033<M-Left> |
|
|
634 | URxvt.keysym.M-Right: \033<M-Right> |
|
|
635 | URxvt.keysym.M-C-0: list \033<M-C- 0123456789 > |
|
|
636 | URxvt.keysym.M-C-a: list \033<M-C- abcdefghijklmnopqrstuvwxyz > |
|
|
637 | URxvt.keysym.F12: command:\033]701;zh_CN.GBK\007 |
482 | |
638 | |
483 | ! keysym - used by rxvt only |
639 | 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 | |
640 | |
518 | =item I'm using keyboard model XXX that has extra Prior/Next/Insert keys. |
641 | =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 |
642 | 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. |
643 | has the following mappings that rxvt-unicode doesn't recognize. |
521 | |
644 | |
… | |
… | |
524 | F27 == Home |
647 | F27 == Home |
525 | F29 == Prior |
648 | F29 == Prior |
526 | F33 == End |
649 | F33 == End |
527 | F35 == Next |
650 | F35 == Next |
528 | |
651 | |
529 | Rather than have rxvt-unicode try to accommodate all the various possible keyboard |
652 | 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 |
653 | keyboard mappings, it is better to use `xmodmap' to remap the keys as |
531 | your particular machine. |
654 | required for your particular machine. |
532 | |
655 | |
533 | =item How do I distinguish if I'm running rxvt-unicode or a regular xterm? |
656 | =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. |
657 | I need this to decide about setting colors etc. |
535 | |
658 | |
536 | rxvt and rxvt-unicode always export the variable "COLORTERM", so you can |
659 | 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, |
660 | check and see if that is set. Note that several programs, JED, slrn, |
538 | Midnight Commander automatically check this variable to decide whether or |
661 | Midnight Commander automatically check this variable to decide whether or |
… | |
… | |
575 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
698 | channel C<#rxvt-unicode> has some rxvt-unicode enthusiasts that might be |
576 | interested in learning about new and exciting problems (but not FAQs :). |
699 | interested in learning about new and exciting problems (but not FAQs :). |
577 | |
700 | |
578 | =back |
701 | =back |
579 | |
702 | |
580 | =head1 SYNOPSIS |
703 | =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 | |
704 | |
591 | =head1 DESCRIPTION |
705 | =head1 DESCRIPTION |
592 | |
706 | |
593 | The rest of this document describes various technical aspects of |
707 | The rest of this document describes various technical aspects of |
594 | B<rxvt-unicode>. First the description of supported command sequences, |
708 | B<rxvt-unicode>. First the description of supported command sequences, |
595 | followed by menu and pixmap support and last by a description of all |
709 | followed by menu and pixmap support and last by a description of all |
596 | features selectable at C<configure> time. |
710 | features selectable at C<configure> time. |
597 | |
711 | |
598 | =head1 RXVT TECHNICAL REFERENCE |
|
|
599 | |
|
|
600 | =head1 Definitions |
712 | =head1 Definitions |
601 | |
713 | |
602 | =over 4 |
714 | =over 4 |
603 | |
715 | |
604 | =item B<< C<c> >> |
716 | =item B<< C<c> >> |
… | |
… | |
732 | Single Shift Select of G3 Character Set (SS3): affects next character |
844 | Single Shift Select of G3 Character Set (SS3): affects next character |
733 | only I<unimplemented> |
845 | only I<unimplemented> |
734 | |
846 | |
735 | =item B<< C<ESC Z> >> |
847 | =item B<< C<ESC Z> >> |
736 | |
848 | |
737 | Obsolete form of returns: B<< C<ESC[?1;2C> >> I<rxvt-unicode compile-time option> |
849 | Obsolete form of returns: B<< C<ESC [ ? 1 ; 2 C> >> I<rxvt-unicode compile-time option> |
738 | |
850 | |
739 | =item B<< C<ESC c> >> |
851 | =item B<< C<ESC c> >> |
740 | |
852 | |
741 | Full reset (RIS) |
853 | Full reset (RIS) |
742 | |
854 | |
… | |
… | |
746 | |
858 | |
747 | =item B<< C<ESC o> >> |
859 | =item B<< C<ESC o> >> |
748 | |
860 | |
749 | Invoke the G3 Character Set (LS3) |
861 | Invoke the G3 Character Set (LS3) |
750 | |
862 | |
751 | =item B<< C<ESC> ( C> >> |
863 | =item B<< C<ESC ( C> >> |
752 | |
864 | |
753 | Designate G0 Character Set (ISO 2022), see below for values of C<C>. |
865 | Designate G0 Character Set (ISO 2022), see below for values of C<C>. |
754 | |
866 | |
755 | =item B<< C<ESC> ) C> >> |
867 | =item B<< C<ESC ) C> >> |
756 | |
868 | |
757 | Designate G1 Character Set (ISO 2022), see below for values of C<C>. |
869 | Designate G1 Character Set (ISO 2022), see below for values of C<C>. |
758 | |
870 | |
759 | =item B<< C<ESC * C> >> |
871 | =item B<< C<ESC * C> >> |
760 | |
872 | |
… | |
… | |
901 | |
1013 | |
902 | =item B<< C<ESC [ Ps c> >> |
1014 | =item B<< C<ESC [ Ps c> >> |
903 | |
1015 | |
904 | Send Device Attributes (DA) |
1016 | Send Device Attributes (DA) |
905 | B<< C<Ps = 0> >> (or omitted): request attributes from terminal |
1017 | B<< C<Ps = 0> >> (or omitted): request attributes from terminal |
906 | returns: B<< C<ESC[?1;2c> >> (``I am a VT100 with Advanced Video |
1018 | returns: B<< C<ESC [ ? 1 ; 2 c> >> (``I am a VT100 with Advanced Video |
907 | Option'') |
1019 | Option'') |
908 | |
1020 | |
909 | =item B<< C<ESC [ Ps d> >> |
1021 | =item B<< C<ESC [ Ps d> >> |
910 | |
1022 | |
911 | Cursor to Line B<< C<Ps> >> (VPA) |
1023 | Cursor to Line B<< C<Ps> >> (VPA) |
… | |
… | |
1027 | |
1139 | |
1028 | =item B<< C<ESC [ s> >> |
1140 | =item B<< C<ESC [ s> >> |
1029 | |
1141 | |
1030 | Save Cursor (SC) |
1142 | Save Cursor (SC) |
1031 | |
1143 | |
|
|
1144 | =item B<< C<ESC [ Ps;Pt t> >> |
|
|
1145 | |
|
|
1146 | Window Operations |
|
|
1147 | |
|
|
1148 | =begin table |
|
|
1149 | |
|
|
1150 | B<< C<Ps = 1> >> Deiconify (map) window |
|
|
1151 | B<< C<Ps = 2> >> Iconify window |
|
|
1152 | B<< C<Ps = 3> >> B<< C<ESC [ 3 ; X ; Y t> >> Move window to (X|Y) |
|
|
1153 | B<< C<Ps = 4> >> B<< C<ESC [ 4 ; H ; W t> >> Resize to WxH pixels |
|
|
1154 | B<< C<Ps = 5> >> Raise window |
|
|
1155 | B<< C<Ps = 6> >> Lower window |
|
|
1156 | B<< C<Ps = 7> >> Refresh screen once |
|
|
1157 | B<< C<Ps = 8> >> B<< C<ESC [ 8 ; R ; C t> >> Resize to R rows and C columns |
|
|
1158 | B<< C<Ps = 11> >> Report window state (responds with C<Ps = 1> or C<Ps = 2>) |
|
|
1159 | B<< C<Ps = 13> >> Report window position (responds with C<Ps = 3>) |
|
|
1160 | B<< C<Ps = 14> >> Report window pixel size (responds with C<Ps = 4>) |
|
|
1161 | B<< C<Ps = 18> >> Report window text size (responds with C<Ps = 7>) |
|
|
1162 | B<< C<Ps = 19> >> Currently the same as C<Ps = 18>, but responds with C<Ps = 9> |
|
|
1163 | B<< C<Ps = 20> >> Reports icon label (B<< C<ESC ] L NAME \234> >>) |
|
|
1164 | B<< C<Ps = 21> >> Reports window title (B<< C<ESC ] l NAME \234> >>) |
|
|
1165 | B<< C<Ps = 24..> >> Set window height to C<Ps> rows |
|
|
1166 | |
|
|
1167 | =end table |
|
|
1168 | |
|
|
1169 | =item B<< C<ESC [ u> >> |
|
|
1170 | |
|
|
1171 | Restore Cursor |
|
|
1172 | |
1032 | =item B<< C<ESC [ Ps x> >> |
1173 | =item B<< C<ESC [ Ps x> >> |
1033 | |
1174 | |
1034 | Request Terminal Parameters (DECREQTPARM) |
1175 | Request Terminal Parameters (DECREQTPARM) |
1035 | |
|
|
1036 | =item B<< C<ESC [ u> >> |
|
|
1037 | |
|
|
1038 | Restore Cursor |
|
|
1039 | |
1176 | |
1040 | =back |
1177 | =back |
1041 | |
1178 | |
1042 | X<PrivateModes> |
1179 | X<PrivateModes> |
1043 | |
1180 | |
… | |
… | |
1412 | |
1549 | |
1413 | =item B<< [title:+I<string>] >> |
1550 | =item B<< [title:+I<string>] >> |
1414 | |
1551 | |
1415 | set the current menuBar's title to I<string>, which may contain the |
1552 | set the current menuBar's title to I<string>, which may contain the |
1416 | following format specifiers: |
1553 | following format specifiers: |
1417 | B<%%> : literal B<%> character |
1554 | |
1418 | B<%n> : rxvt name (as per the B<-name> command-line option) |
1555 | B<%n> rxvt name (as per the B<-name> command-line option) |
1419 | B<%v> : rxvt version |
1556 | B<%v> rxvt version |
|
|
1557 | B<%%> literal B<%> character |
1420 | |
1558 | |
1421 | =item B<[done]> |
1559 | =item B<[done]> |
1422 | |
1560 | |
1423 | set menuBar access as B<readonly>. |
1561 | set menuBar access as B<readonly>. |
1424 | End-of-file tag for B<< [read:+I<file>] >> operations. |
1562 | End-of-file tag for B<< [read:+I<file>] >> operations. |
… | |
… | |
1570 | |
1708 | |
1571 | As a convenience for the many Emacs-type editors, I<action> may start |
1709 | 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 |
1710 | 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. |
1711 | appended if missed from B<M-x> commands. |
1574 | |
1712 | |
1575 | As a convenience for issuing XTerm B<ESC]> sequences from a menubar (or |
1713 | 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. |
1714 | quick arrow), a B<BEL> (B<^G>) will be appended if needed. |
1577 | |
1715 | |
1578 | =over 4 |
1716 | =over 4 |
1579 | |
1717 | |
1580 | =item For example, |
1718 | =item For example, |
… | |
… | |
2089 | composite characters. This is required for proper viewing of text |
2227 | composite characters. This is required for proper viewing of text |
2090 | where accents are encoded as seperate unicode characters. This is |
2228 | where accents are encoded as seperate unicode characters. This is |
2091 | done by using precomposited characters when available or creating |
2229 | done by using precomposited characters when available or creating |
2092 | new pseudo-characters when no precomposed form exists. |
2230 | new pseudo-characters when no precomposed form exists. |
2093 | |
2231 | |
2094 | Without --enable-unicode3, the number of additional precomposed |
2232 | Without --enable-unicode3, the number of additional precomposed characters |
2095 | characters is rather limited (2048, if this is full, rxvt will use the |
2233 | 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 |
2234 | private use area, extending the number of combinations to 8448). With |
2097 | --enable-unicode3, no practical limit exists. This will also enable |
2235 | --enable-unicode3, no practical limit exists. |
2098 | storage of characters >65535. |
2236 | |
|
|
2237 | This option will also enable storage (but not display) of characters |
|
|
2238 | beyond plane 0 (>65535) when --enable-unicode3 was not specified. |
2099 | |
2239 | |
2100 | The combining table also contains entries for arabic presentation forms, |
2240 | 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. |
2241 | but these are not currently used. Bug me if you want these to be used (and |
|
|
2242 | tell me how these are to be used...). |
2102 | |
2243 | |
2103 | =item --enable-fallback(=CLASS) |
2244 | =item --enable-fallback(=CLASS) |
2104 | |
2245 | |
2105 | When reading resource settings, also read settings for class CLASS |
2246 | When reading resource settings, also read settings for class CLASS |
2106 | (default: Rxvt). To disable resource fallback use --disable-fallback. |
2247 | (default: Rxvt). To disable resource fallback use --disable-fallback. |
… | |
… | |
2198 | Remove all resources checking. |
2339 | Remove all resources checking. |
2199 | |
2340 | |
2200 | =item --enable-xgetdefault |
2341 | =item --enable-xgetdefault |
2201 | |
2342 | |
2202 | Make resources checking via XGetDefault() instead of our small |
2343 | Make resources checking via XGetDefault() instead of our small |
2203 | version which only checks ~/.Xdefaults, or if that doesn't exist |
2344 | version which only checks ~/.Xdefaults, or if that doesn't exist then |
2204 | then ~/.Xresources. |
2345 | ~/.Xresources. |
|
|
2346 | |
|
|
2347 | Please note that nowadays, things like XIM will automatically pull in and |
|
|
2348 | use the full X resource manager, so the overhead of using it might be very |
|
|
2349 | small, if nonexistant. |
2205 | |
2350 | |
2206 | =item --enable-strings |
2351 | =item --enable-strings |
2207 | |
2352 | |
2208 | Add support for our possibly faster memset() function and other |
2353 | Add support for our possibly faster memset() function and other |
2209 | various routines, overriding your system's versions which may |
2354 | various routines, overriding your system's versions which may |
… | |
… | |
2219 | |
2364 | |
2220 | Add support for many small features that are not essential but nice to |
2365 | 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 |
2366 | have. Normally you want this, but for very small binaries you may want to |
2222 | disable this. |
2367 | disable this. |
2223 | |
2368 | |
|
|
2369 | A non-exhaustive list of features enabled by C<--enable-frills> (possibly |
|
|
2370 | in combination with other switches) is: |
|
|
2371 | |
|
|
2372 | MWM-hints |
|
|
2373 | seperate underline colour |
|
|
2374 | settable border widths and borderless switch |
|
|
2375 | settable extra linespacing |
|
|
2376 | extra window properties (e.g. UTF-8 window names and PID) |
|
|
2377 | iso-14755-2 and -3, and visual feedback |
|
|
2378 | backindex and forwardindex escape sequence |
|
|
2379 | window op and locale change escape sequences |
|
|
2380 | tripleclickwords |
|
|
2381 | settable insecure mode |
|
|
2382 | keysym remapping support |
|
|
2383 | |
2224 | =item --enable-iso14755 |
2384 | =item --enable-iso14755 |
2225 | |
2385 | |
2226 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2386 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2227 | F<doc/rxvt.1.txt>). Basic support (section 5.1) is enabled by |
2387 | 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 |
2388 | C<--enable-frills>, while support for 5.2, 5.3 and 5.4 is enabled with |
2229 | this switch. |
2389 | this switch. |
2230 | |
2390 | |
2231 | =item --enable-linespace |
|
|
2232 | |
|
|
2233 | Add support to provide user specified line spacing between text rows. |
|
|
2234 | |
|
|
2235 | =item --enable-keepscrolling |
2391 | =item --enable-keepscrolling |
2236 | |
2392 | |
2237 | Add support for continual scrolling of the display when you hold |
2393 | Add support for continual scrolling of the display when you hold |
2238 | the mouse button down on a scrollbar arrow. |
2394 | the mouse button down on a scrollbar arrow. |
2239 | |
2395 | |
… | |
… | |
2280 | |
2436 | |
2281 | Add support to have the pointer disappear when typing or inactive. |
2437 | Add support to have the pointer disappear when typing or inactive. |
2282 | |
2438 | |
2283 | =item --with-name=NAME |
2439 | =item --with-name=NAME |
2284 | |
2440 | |
2285 | Set the basename for the installed binaries (default: urxvt, resulting in |
2441 | Set the basename for the installed binaries (default: C<urxvt>, resulting |
2286 | urxvt, urxvtd etc.). Specify --with-name=rxvt to replace rxvt. |
2442 | in C<urxvt>, C<urxvtd> etc.). Specify C<--with-name=rxvt> to replace with |
|
|
2443 | C<rxvt>. |
2287 | |
2444 | |
2288 | =item --with-term=NAME |
2445 | =item --with-term=NAME |
2289 | |
2446 | |
2290 | Change the environmental variable for the terminal to NAME (default |
2447 | Change the environmental variable for the terminal to NAME (default |
2291 | "rxvt") |
2448 | C<rxvt-unicode>) |
2292 | |
2449 | |
2293 | =item --with-terminfo=PATH |
2450 | =item --with-terminfo=PATH |
2294 | |
2451 | |
2295 | Change the environmental variable for the path to the terminfo tree to |
2452 | Change the environmental variable for the path to the terminfo tree to |
2296 | PATH. |
2453 | PATH. |