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

Comparing rxvt-unicode/doc/rxvt.7.man.in (file contents):
Revision 1.20 by root, Sun Apr 17 22:36:13 2005 UTC vs.
Revision 1.24 by root, Wed Aug 10 01:44:35 2005 UTC

1.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.14 1.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.3
2.\" 2.\"
3.\" Standard preamble: 3.\" Standard preamble:
4.\" ======================================================================== 4.\" ========================================================================
5.de Sh \" Subsection heading 5.de Sh \" Subsection heading
6.br 6.br
… …
127.\} 127.\}
128.rm #[ #] #H #V #F C 128.rm #[ #] #H #V #F C
129.\" ======================================================================== 129.\" ========================================================================
130.\" 130.\"
131.IX Title "rxvt 7" 131.IX Title "rxvt 7"
132.TH rxvt 7 "2005-04-17" "5.3" "RXVT-UNICODE" 132.TH rxvt 7 "2005-08-05" "5.7" "RXVT-UNICODE"
133.SH "NAME" 133.SH "NAME"
134RXVT REFERENCE \- FAQ, command sequences and other background information 134RXVT REFERENCE \- FAQ, command sequences and other background information
135.SH "SYNOPSIS" 135.SH "SYNOPSIS"
136.IX Header "SYNOPSIS" 136.IX Header "SYNOPSIS"
137.Vb 2 137.Vb 2
… …
162.IX Item "How do I know which rxvt-unicode version I'm using?" 162.IX Item "How do I know which rxvt-unicode version I'm using?"
163The version number is displayed with the usage (\-h). Also the escape 163The version number is displayed with the usage (\-h). Also the escape
164sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. 164sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number.
165.IP "I am using Debian GNU/Linux and have a problem..." 4 165.IP "I am using Debian GNU/Linux and have a problem..." 4
166.IX Item "I am using Debian GNU/Linux and have a problem..." 166.IX Item "I am using Debian GNU/Linux and have a problem..."
167The Debian GNU/Linux package of rxvt-unicode contains large patches that 167The Debian GNU/Linux package of rxvt-unicode in sarge contains large
168considerably change the behaviour of rxvt\-unicode. Before reporting a 168patches that considerably change the behaviour of rxvt\-unicode. Before
169bug to the original rxvt-unicode author please download and install the 169reporting a bug to the original rxvt-unicode author please download and
170genuine version (<http://software.schmorp.de#rxvt\-unicode>) and try to 170install the genuine version (<http://software.schmorp.de#rxvt\-unicode>)
171reproduce the problem. If you cannot, chances are that the problems are 171and try to reproduce the problem. If you cannot, chances are that the
172specific to Debian GNU/Linux, in which case it should be reported via the 172problems are specific to Debian GNU/Linux, in which case it should be
173Debian Bug Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug). 173reported via the Debian Bug Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report
174the bug).
174.Sp 175.Sp
175For other problems that also affect the Debian package, you can and 176For other problems that also affect the Debian package, you can and
176probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a 177probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a
177bug in the Debian version and it serves as a reminder for other users that 178bug in the Debian version and it serves as a reminder for other users that
178might encounter the same issue. 179might encounter the same issue.
… …
205\& URxvt.termName: rxvt 206\& URxvt.termName: rxvt
206.Ve 207.Ve
207.Sp 208.Sp
208If you don't plan to use \fBrxvt\fR (quite common...) you could also replace 209If you don't plan to use \fBrxvt\fR (quite common...) you could also replace
209the rxvt terminfo file with the rxvt-unicode one. 210the rxvt terminfo file with the rxvt-unicode one.
211.ie n .IP """tic"" outputs some error when compiling the terminfo entry." 4
212.el .IP "\f(CWtic\fR outputs some error when compiling the terminfo entry." 4
213.IX Item "tic outputs some error when compiling the terminfo entry."
214Most likely it's the empty definition for \f(CW\*(C`enacs=\*(C'\fR. Just replace it by
215\&\f(CW\*(C`enacs=\eE[0@\*(C'\fR and try again.
210.ie n .IP """bash""'s readline does not work correctly under @@RXVT_NAME@@." 4 216.ie n .IP """bash""'s readline does not work correctly under @@RXVT_NAME@@." 4
211.el .IP "\f(CWbash\fR's readline does not work correctly under @@RXVT_NAME@@." 4 217.el .IP "\f(CWbash\fR's readline does not work correctly under @@RXVT_NAME@@." 4
212.IX Item "bash's readline does not work correctly under @@RXVT_NAME@@." 218.IX Item "bash's readline does not work correctly under @@RXVT_NAME@@."
213.PD 0 219.PD 0
214.IP "I need a termcap file entry." 4 220.IP "I need a termcap file entry." 4
… …
406the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you 412the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you
407might be forced to use a different font. 413might be forced to use a different font.
408.Sp 414.Sp
409All of this is not a problem when using X11 core fonts, as their bounding 415All of this is not a problem when using X11 core fonts, as their bounding
410box data is correct. 416box data is correct.
417.IP "On Solaris 9, many line-drawing characters are too wide." 4
418.IX Item "On Solaris 9, many line-drawing characters are too wide."
419Seems to be a known bug, read
420<http://nixdoc.net/files/forum/about34198.html>. Some people use the
421following ugly workaround to get non-double-wide-characters working:
422.Sp
423.Vb 1
424\& #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x)
425.Ve
411.IP "My Compose (Multi_key) key is no longer working." 4 426.IP "My Compose (Multi_key) key is no longer working." 4
412.IX Item "My Compose (Multi_key) key is no longer working." 427.IX Item "My Compose (Multi_key) key is no longer working."
413The most common causes for this are that either your locale is not set 428The most common causes for this are that either your locale is not set
414correctly, or you specified a \fBpreeditStyle\fR that is not supported by 429correctly, or you specified a \fBpreeditStyle\fR that is not supported by
415your input method. For example, if you specified \fBOverTheSpot\fR and 430your input method. For example, if you specified \fBOverTheSpot\fR and
… …
477encodings slightly different than the terminal emulator). 492encodings slightly different than the terminal emulator).
478.Sp 493.Sp
479The rxvt-unicode author insists that the right way to fix this is in the 494The rxvt-unicode author insists that the right way to fix this is in the
480system libraries once and for all, instead of forcing every app to carry 495system libraries once and for all, instead of forcing every app to carry
481complete replacements for them :) 496complete replacements for them :)
497.IP "I use Solaris 9 and it doesn't compile/work/etc." 4
498.IX Item "I use Solaris 9 and it doesn't compile/work/etc."
499Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst
500problems with \f(CW\*(C`wcwidth\*(C'\fR and a compile problem.
501.IP "How can I use rxvt-unicode under cygwin?" 4
502.IX Item "How can I use rxvt-unicode under cygwin?"
503rxvt-unicode should compile and run out of the box on cygwin, using
504the X11 libraries that come with cygwin. libW11 emulation is no
505longer supported (and makes no sense, either, as it only supported a
506single font). I recommend starting the X\-server in \f(CW\*(C`\-multiwindow\*(C'\fR or
507\&\f(CW\*(C`\-rootless\*(C'\fR mode instead, which will result in similar look&feel as the
508old libW11 emulation.
509.Sp
510At the time of this writing, cygwin didn't seem to support any multi-byte
511encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited
512to 8\-bit encodings.
482.IP "How does rxvt-unicode determine the encoding to use?" 4 513.IP "How does rxvt-unicode determine the encoding to use?" 4
483.IX Item "How does rxvt-unicode determine the encoding to use?" 514.IX Item "How does rxvt-unicode determine the encoding to use?"
484.PD 0 515.PD 0
485.IP "Is there an option to switch encodings?" 4 516.IP "Is there an option to switch encodings?" 4
486.IX Item "Is there an option to switch encodings?" 517.IX Item "Is there an option to switch encodings?"
… …
606rxvt-unicode then uses 8 bytes per screen cell. 637rxvt-unicode then uses 8 bytes per screen cell.
607.IP "Can I speed up Xft rendering somehow?" 4 638.IP "Can I speed up Xft rendering somehow?" 4
608.IX Item "Can I speed up Xft rendering somehow?" 639.IX Item "Can I speed up Xft rendering somehow?"
609Yes, the most obvious way to speed it up is to avoid Xft entirely, as 640Yes, the most obvious way to speed it up is to avoid Xft entirely, as
610it is simply slow. If you still want Xft fonts you might try to disable 641it is simply slow. If you still want Xft fonts you might try to disable
611antialiasing (by appending \f(CW\*(C`:antialiasing=false\*(C'\fR), which saves lots of 642antialiasing (by appending \f(CW\*(C`:antialias=false\*(C'\fR), which saves lots of
612memory and also speeds up rendering considerably. 643memory and also speeds up rendering considerably.
613.IP "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 4 644.IP "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 4
614.IX Item "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?" 645.IX Item "Rxvt-unicode doesn't seem to anti-alias its fonts, what is wrong?"
615Rxvt-unicode will use whatever you specify as a font. If it needs to 646Rxvt-unicode will use whatever you specify as a font. If it needs to
616fall back to it's default font search list it will prefer X11 core 647fall back to it's default font search list it will prefer X11 core
… …
695\& URxvt.color7: #e1dddd 726\& URxvt.color7: #e1dddd
696\& URxvt.color15: #e1dddd 727\& URxvt.color15: #e1dddd
697.Ve 728.Ve
698.IP "How can I start @@RXVT_NAME@@d in a race-free way?" 4 729.IP "How can I start @@RXVT_NAME@@d in a race-free way?" 4
699.IX Item "How can I start @@RXVT_NAME@@d in a race-free way?" 730.IX Item "How can I start @@RXVT_NAME@@d in a race-free way?"
700Despite it's name, @@RXVT_NAME@@d is not a real daemon, but more like a 731Try \f(CW\*(C`@@RXVT_NAME@@d \-f \-o\*(C'\fR, which tells @@RXVT_NAME@@d to open the
701server that answers @@RXVT_NAME@@c's requests, so it doesn't background 732display, create the listening socket and then fork.
702itself.
703.Sp
704To ensure @@RXVT_NAME@@d is listening on it's socket, you can use the
705following method to wait for the startup message before continuing:
706.Sp
707.Vb 1
708\& { @@RXVT_NAME@@d & } | read
709.Ve
710.IP "What's with the strange Backspace/Delete key behaviour?" 4 733.IP "What's with the strange Backspace/Delete key behaviour?" 4
711.IX Item "What's with the strange Backspace/Delete key behaviour?" 734.IX Item "What's with the strange Backspace/Delete key behaviour?"
712Assuming that the physical Backspace key corresponds to the 735Assuming that the physical Backspace key corresponds to the
713BackSpace keysym (not likely for Linux ... see the following 736BackSpace keysym (not likely for Linux ... see the following
714question) there are two standard values that can be used for 737question) there are two standard values that can be used for

Diff Legend

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