… | |
… | |
31 | 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 |
32 | sequence C<ESC [ 8 n> sets the window title to the version number. |
32 | sequence C<ESC [ 8 n> sets the window title to the version number. |
33 | |
33 | |
34 | =item I am using Debian GNU/Linux and have a problem... |
34 | =item I am using Debian GNU/Linux and have a problem... |
35 | |
35 | |
36 | The Debian GNU/Linux package of rxvt-unicode contains large patches that |
36 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
37 | considerably change the behaviour of rxvt-unicode. Before reporting a |
37 | patches that considerably change the behaviour of rxvt-unicode. Before |
38 | bug to the original rxvt-unicode author please download and install the |
38 | reporting a bug to the original rxvt-unicode author please download and |
39 | genuine version (L<http://software.schmorp.de#rxvt-unicode>) and try to |
39 | install the genuine version (L<http://software.schmorp.de#rxvt-unicode>) |
40 | reproduce the problem. If you cannot, chances are that the problems are |
40 | and try to reproduce the problem. If you cannot, chances are that the |
41 | specific to Debian GNU/Linux, in which case it should be reported via the |
41 | problems are specific to Debian GNU/Linux, in which case it should be |
42 | Debian Bug Tracking System (use C<reportbug> to report the bug). |
42 | reported via the Debian Bug Tracking System (use C<reportbug> to report |
|
|
43 | the bug). |
43 | |
44 | |
44 | For other problems that also affect the Debian package, you can and |
45 | 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 | 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 | bug in the Debian version and it serves as a reminder for other users that |
47 | might encounter the same issue. |
48 | might encounter the same issue. |
… | |
… | |
71 | |
72 | |
72 | URxvt.termName: rxvt |
73 | URxvt.termName: rxvt |
73 | |
74 | |
74 | 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 |
75 | the rxvt terminfo file with the rxvt-unicode one. |
76 | the rxvt terminfo file with the rxvt-unicode one. |
|
|
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. |
76 | |
82 | |
77 | =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
83 | =item C<bash>'s readline does not work correctly under @@RXVT_NAME@@. |
78 | |
84 | |
79 | =item I need a termcap file entry. |
85 | =item I need a termcap file entry. |
80 | |
86 | |
… | |
… | |
258 | might be forced to use a different font. |
264 | might be forced to use a different font. |
259 | |
265 | |
260 | 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 |
261 | box data is correct. |
267 | box data is correct. |
262 | |
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) |
|
|
276 | |
263 | =item My Compose (Multi_key) key is no longer working. |
277 | =item My Compose (Multi_key) key is no longer working. |
264 | |
278 | |
265 | 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 |
266 | 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 |
267 | your input method. For example, if you specified B<OverTheSpot> and |
281 | your input method. For example, if you specified B<OverTheSpot> and |
… | |
… | |
330 | encodings slightly different than the terminal emulator). |
344 | encodings slightly different than the terminal emulator). |
331 | |
345 | |
332 | 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 |
333 | 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 |
334 | complete replacements for them :) |
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. |
335 | |
367 | |
336 | =item How does rxvt-unicode determine the encoding to use? |
368 | =item How does rxvt-unicode determine the encoding to use? |
337 | |
369 | |
338 | =item Is there an option to switch encodings? |
370 | =item Is there an option to switch encodings? |
339 | |
371 | |
… | |
… | |
2187 | 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 |
2188 | styles. The fonts can be set manually or automatically. |
2220 | styles. The fonts can be set manually or automatically. |
2189 | |
2221 | |
2190 | =item --with-codesets=NAME,... |
2222 | =item --with-codesets=NAME,... |
2191 | |
2223 | |
2192 | Compile in support for additional codeset (encoding) groups (eu, vn are |
2224 | Compile in support for additional codeset (encoding) groups (C<eu>, C<vn> |
2193 | always compiled in, which includes most 8-bit character sets). These |
2225 | are always compiled in, which includes most 8-bit character sets). These |
2194 | 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 |
2195 | 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 |
2196 | 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 |
2197 | you use an X11 font requiring one of these encodings. |
2230 | memory usage unless you use a font requiring one of these encodings. |
2198 | |
2231 | |
2199 | =begin table |
2232 | =begin table |
2200 | |
2233 | |
2201 | all all available codeset groups |
2234 | all all available codeset groups |
2202 | zh common chinese encodings |
2235 | zh common chinese encodings |
… | |
… | |
2383 | backindex and forwardindex escape sequence |
2416 | backindex and forwardindex escape sequence |
2384 | window op and some xterm/OSC escape sequences |
2417 | window op and some xterm/OSC escape sequences |
2385 | tripleclickwords |
2418 | tripleclickwords |
2386 | settable insecure mode |
2419 | settable insecure mode |
2387 | keysym remapping support |
2420 | keysym remapping support |
|
|
2421 | cursor blinking and underline cursor |
2388 | -embed and -pty-fd options |
2422 | -embed and -pty-fd options |
2389 | |
2423 | |
2390 | =item --enable-iso14755 |
2424 | =item --enable-iso14755 |
2391 | |
2425 | |
2392 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
2426 | Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or |
… | |
… | |
2432 | |
2466 | |
2433 | 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 |
2434 | 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 |
2435 | closest to a corner of the screen. |
2469 | closest to a corner of the screen. |
2436 | |
2470 | |
2437 | =item --enable-cursor-blink |
|
|
2438 | |
|
|
2439 | Add support for a blinking cursor. |
|
|
2440 | |
|
|
2441 | =item --enable-pointer-blank |
2471 | =item --enable-pointer-blank |
2442 | |
2472 | |
2443 | Add support to have the pointer disappear when typing or inactive. |
2473 | Add support to have the pointer disappear when typing or inactive. |
2444 | |
2474 | |
2445 | =item --with-name=NAME |
2475 | =item --with-name=NAME |