ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/rxvt-unicode/doc/rxvt.7.pod
(Generate patch)

Comparing rxvt-unicode/doc/rxvt.7.pod (file contents):
Revision 1.52 by root, Sat Mar 19 02:27:26 2005 UTC vs.
Revision 1.60 by root, Fri Jul 29 03:12:10 2005 UTC

… …
31The version number is displayed with the usage (-h). Also the escape 31The version number is displayed with the usage (-h). Also the escape
32sequence C<ESC [ 8 n> sets the window title to the version number. 32sequence 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
36The Debian GNU/Linux package of rxvt-unicode contains large patches that 36The Debian GNU/Linux package of rxvt-unicode in sarge contains large
37considerably change the behaviour of rxvt-unicode. Before reporting a 37patches that considerably change the behaviour of rxvt-unicode. Before
38bug to the original rxvt-unicode author please download and install the 38reporting a bug to the original rxvt-unicode author please download and
39genuine version (L<http://software.schmorp.de#rxvt-unicode>) and try to 39install the genuine version (L<http://software.schmorp.de#rxvt-unicode>)
40reproduce the problem. If you cannot, chances are that the problems are 40and try to reproduce the problem. If you cannot, chances are that the
41specific to Debian GNU/Linux, in which case it should be reported via the 41problems are specific to Debian GNU/Linux, in which case it should be
42Debian Bug Tracking System (use C<reportbug> to report the bug). 42reported via the Debian Bug Tracking System (use C<reportbug> to report
43the bug).
43 44
44For other problems that also affect the Debian package, you can and 45For other problems that also affect the Debian package, you can and
45probably should use the Debian BTS, too, because, after all, it's also a 46probably should use the Debian BTS, too, because, after all, it's also a
46bug in the Debian version and it serves as a reminder for other users that 47bug in the Debian version and it serves as a reminder for other users that
47might encounter the same issue. 48might encounter the same issue.
… …
71 72
72 URxvt.termName: rxvt 73 URxvt.termName: rxvt
73 74
74If you don't plan to use B<rxvt> (quite common...) you could also replace 75If you don't plan to use B<rxvt> (quite common...) you could also replace
75the rxvt terminfo file with the rxvt-unicode one. 76the rxvt terminfo file with the rxvt-unicode one.
77
78=item C<tic> outputs some error when compiling the terminfo entry.
79
80Most likely it's the empty definition for C<enacs=>. Just replace it by
81C<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
… …
258might be forced to use a different font. 264might be forced to use a different font.
259 265
260All of this is not a problem when using X11 core fonts, as their bounding 266All of this is not a problem when using X11 core fonts, as their bounding
261box data is correct. 267box data is correct.
262 268
269=item On Solaris 9, many line-drawing characters are too wide.
270
271Seems to be a known bug, read
272L<http://nixdoc.net/files/forum/about34198.html>. Some people use the
273following 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
265The most common causes for this are that either your locale is not set 279The most common causes for this are that either your locale is not set
266correctly, or you specified a B<preeditStyle> that is not supported by 280correctly, or you specified a B<preeditStyle> that is not supported by
267your input method. For example, if you specified B<OverTheSpot> and 281your input method. For example, if you specified B<OverTheSpot> and
… …
331 345
332The rxvt-unicode author insists that the right way to fix this is in the 346The rxvt-unicode author insists that the right way to fix this is in the
333system libraries once and for all, instead of forcing every app to carry 347system libraries once and for all, instead of forcing every app to carry
334complete replacements for them :) 348complete replacements for them :)
335 349
350=item I use Solaris 9 and it doesn't compile/work/etc.
351
352Try the diff in F<doc/solaris9.patch> as a base. It fixes the worst
353problems with C<wcwidth> and a compile problem.
354
355=item How can I use rxvt-unicode under cygwin?
356
357rxvt-unicode should compile and run out of the box on cygwin, using
358the X11 libraries that come with cygwin. libW11 emulation is no
359longer supported (and makes no sense, either, as it only supported a
360single font). I recommend starting the X-server in C<-multiwindow> or
361C<-rootless> mode instead, which will result in similar look&feel as the
362old libW11 emulation.
363
364At the time of this writing, cygwin didn't seem to support any multi-byte
365encodings (you might try C<LC_CTYPE=C-UTF-8>), so you are likely limited
366to 8-bit encodings.
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
340Unlike some other terminals, rxvt-unicode has no encoding switch, and no 372Unlike some other terminals, rxvt-unicode has no encoding switch, and no
… …
455 487
456=item Can I speed up Xft rendering somehow? 488=item Can I speed up Xft rendering somehow?
457 489
458Yes, the most obvious way to speed it up is to avoid Xft entirely, as 490Yes, the most obvious way to speed it up is to avoid Xft entirely, as
459it is simply slow. If you still want Xft fonts you might try to disable 491it is simply slow. If you still want Xft fonts you might try to disable
460antialiasing (by appending C<:antialiasing=false>), which saves lots of 492antialiasing (by appending C<:antialias=false>), which saves lots of
461memory and also speeds up rendering considerably. 493memory and also speeds up rendering considerably.
462 494
463=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong? 495=item Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?
464 496
465Rxvt-unicode will use whatever you specify as a font. If it needs to 497Rxvt-unicode will use whatever you specify as a font. If it needs to
… …
543 URxvt.color7: #e1dddd 575 URxvt.color7: #e1dddd
544 URxvt.color15: #e1dddd 576 URxvt.color15: #e1dddd
545 577
546=item How can I start @@RXVT_NAME@@d in a race-free way? 578=item How can I start @@RXVT_NAME@@d in a race-free way?
547 579
548Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a 580Try C<@@RXVT_NAME@@d -f -o>, which tells @@RXVT_NAME@@d to open the
549server that answers @@RXVT_NAME@@c's requests, so it doesn't background 581display, create the listening socket and then fork.
550itself.
551
552To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the
553following method to wait for the startup message before continuing:
554
555 { @@RXVT_NAME@@d & } | read
556 582
557=item What's with the strange Backspace/Delete key behaviour? 583=item What's with the strange Backspace/Delete key behaviour?
558 584
559Assuming that the physical Backspace key corresponds to the 585Assuming that the physical Backspace key corresponds to the
560BackSpace keysym (not likely for Linux ... see the following 586BackSpace keysym (not likely for Linux ... see the following
… …
2187Add support for B<bold>, I<italic> and B<< I<bold italic> >> font 2213Add support for B<bold>, I<italic> and B<< I<bold italic> >> font
2188styles. The fonts can be set manually or automatically. 2214styles. The fonts can be set manually or automatically.
2189 2215
2190=item --with-codesets=NAME,... 2216=item --with-codesets=NAME,...
2191 2217
2192Compile in support for additional codeset (encoding) groups (eu, vn are 2218Compile in support for additional codeset (encoding) groups (C<eu>, C<vn>
2193always compiled in, which includes most 8-bit character sets). These 2219are always compiled in, which includes most 8-bit character sets). These
2194codeset tables are currently only used for driving X11 core fonts, they 2220codeset tables are used for driving X11 core fonts, they are not required
2195are not required for Xft fonts. Compiling them in will make your binary 2221for Xft fonts, although having them compiled in lets rxvt-unicode choose
2196bigger (together about 700kB), but it doesn't increase memory usage unless 2222replacement fonts more intelligently. Compiling them in will make your
2223binary bigger (all of together cost about 700kB), but it doesn't increase
2197you use an X11 font requiring one of these encodings. 2224memory usage unless you use a font requiring one of these encodings.
2198 2225
2199=begin table 2226=begin table
2200 2227
2201 all all available codeset groups 2228 all all available codeset groups
2202 zh common chinese encodings 2229 zh common chinese encodings
… …
2383 backindex and forwardindex escape sequence 2410 backindex and forwardindex escape sequence
2384 window op and some xterm/OSC escape sequences 2411 window op and some xterm/OSC escape sequences
2385 tripleclickwords 2412 tripleclickwords
2386 settable insecure mode 2413 settable insecure mode
2387 keysym remapping support 2414 keysym remapping support
2415 cursor blinking and underline cursor
2388 -embed and -pty-fd options 2416 -embed and -pty-fd options
2389 2417
2390=item --enable-iso14755 2418=item --enable-iso14755
2391 2419
2392Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or 2420Enable extended ISO 14755 support (see @@RXVT_NAME@@(1), or
… …
2432 2460
2433Add smart growth/shrink behaviour when changing font size via from hot 2461Add smart growth/shrink behaviour when changing font size via from hot
2434keys. This should keep in a fixed position the rxvt corner which is 2462keys. This should keep in a fixed position the rxvt corner which is
2435closest to a corner of the screen. 2463closest to a corner of the screen.
2436 2464
2437=item --enable-cursor-blink
2438
2439Add support for a blinking cursor.
2440
2441=item --enable-pointer-blank 2465=item --enable-pointer-blank
2442 2466
2443Add support to have the pointer disappear when typing or inactive. 2467Add support to have the pointer disappear when typing or inactive.
2444 2468
2445=item --with-name=NAME 2469=item --with-name=NAME

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines