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-02-14" "" "RXVT-UNICODE" |
132 | .TH rxvt 7 "2005-07-13" "5.7" "RXVT-UNICODE" |
133 | .SH "NAME" |
133 | .SH "NAME" |
134 | RXVT REFERENCE \- FAQ, command sequences and other background information |
134 | RXVT 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?" |
163 | The version number is displayed with the usage (\-h). Also the escape |
163 | The version number is displayed with the usage (\-h). Also the escape |
164 | sequence \f(CW\*(C`ESC [ 8 n\*(C'\fR sets the window title to the version number. |
164 | sequence \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..." |
167 | The Debian GNU/Linux package of rxvt-unicode contains large patches that |
167 | The Debian GNU/Linux package of rxvt-unicode in sarge contains large |
168 | considerably change the behaviour of rxvt\-unicode. Before reporting a |
168 | patches that considerably change the behaviour of rxvt\-unicode. Before |
169 | bug to the original rxvt-unicode author please download and install the |
169 | reporting a bug to the original rxvt-unicode author please download and |
170 | genuine version (<http://software.schmorp.de#rxvt\-unicode>) and try to |
170 | install the genuine version (<http://software.schmorp.de#rxvt\-unicode>) |
171 | reproduce the problem. If you cannot, chances are that the problems are |
171 | and try to reproduce the problem. If you cannot, chances are that the |
172 | specific to Debian GNU/Linux, in which case it should be reported via the |
172 | problems are specific to Debian GNU/Linux, in which case it should be |
173 | Debian Bug Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report the bug). |
173 | reported via the Debian Bug Tracking System (use \f(CW\*(C`reportbug\*(C'\fR to report |
|
|
174 | the bug). |
174 | .Sp |
175 | .Sp |
175 | For other problems that also affect the Debian package, you can and |
176 | For other problems that also affect the Debian package, you can and |
176 | probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a |
177 | probably should use the Debian \s-1BTS\s0, too, because, after all, it's also a |
177 | bug in the Debian version and it serves as a reminder for other users that |
178 | bug in the Debian version and it serves as a reminder for other users that |
178 | might encounter the same issue. |
179 | might encounter the same issue. |
… | |
… | |
205 | \& URxvt.termName: rxvt |
206 | \& URxvt.termName: rxvt |
206 | .Ve |
207 | .Ve |
207 | .Sp |
208 | .Sp |
208 | If you don't plan to use \fBrxvt\fR (quite common...) you could also replace |
209 | If you don't plan to use \fBrxvt\fR (quite common...) you could also replace |
209 | the rxvt terminfo file with the rxvt-unicode one. |
210 | the 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." |
|
|
214 | Most 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 |
215 | .IX Item "I need a termcap file entry." |
221 | .IX Item "I need a termcap file entry." |
216 | .PD |
222 | .PD |
217 | One reason you might want this is that some distributions or operating |
223 | One reason you might want this is that some distributions or operating |
218 | systems still compile some programs using the long-obsoleted termcap |
224 | systems still compile some programs using the long-obsoleted termcap |
219 | (Fedora Core's bash is one example) and rely on a termcap entry for |
225 | library (Fedora Core's bash is one example) and rely on a termcap entry |
220 | \&\f(CW\*(C`rxvt\-unicode\*(C'\fR. |
226 | for \f(CW\*(C`rxvt\-unicode\*(C'\fR. |
221 | .Sp |
227 | .Sp |
222 | You could use rxvt's termcap entry with resonable results in many cases. |
228 | You could use rxvt's termcap entry with resonable results in many cases. |
223 | You can also create a termcap entry by using terminfo's infocmp program |
229 | You can also create a termcap entry by using terminfo's infocmp program |
224 | like this: |
230 | like this: |
225 | .Sp |
231 | .Sp |
… | |
… | |
227 | \& infocmp -C rxvt-unicode |
233 | \& infocmp -C rxvt-unicode |
228 | .Ve |
234 | .Ve |
229 | .Sp |
235 | .Sp |
230 | Or you could use this termcap entry, generated by the command above: |
236 | Or you could use this termcap entry, generated by the command above: |
231 | .Sp |
237 | .Sp |
232 | .Vb 19 |
238 | .Vb 20 |
233 | \& rxvt-unicode|rxvt-unicode terminal (X Window System):\e |
239 | \& rxvt-unicode|rxvt-unicode terminal (X Window System):\e |
234 | \& :am:bw:eo:km:mi:ms:xn:xo:\e |
240 | \& :am:bw:eo:km:mi:ms:xn:xo:\e |
235 | \& :co#80:it#8:li#24:\e |
241 | \& :co#80:it#8:li#24:lm#0:\e |
236 | \& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e |
242 | \& :AL=\eE[%dL:DC=\eE[%dP:DL=\eE[%dM:DO=\eE[%dB:IC=\eE[%d@:\e |
237 | \& :K1=\eEOw:K2=\eEOu:K3=\eEOy:K4=\eEOq:K5=\eEOs:LE=\eE[%dD:\e |
243 | \& :K1=\eEOw:K2=\eEOu:K3=\eEOy:K4=\eEOq:K5=\eEOs:LE=\eE[%dD:\e |
238 | \& :RI=\eE[%dC:SF=\eE[%dS:SR=\eE[%dT:UP=\eE[%dA:ae=^O:al=\eE[L:\e |
244 | \& :RI=\eE[%dC:SF=\eE[%dS:SR=\eE[%dT:UP=\eE[%dA:ae=\eE(B:al=\eE[L:\e |
239 | \& :as=^N:bl=^G:cd=\eE[J:ce=\eE[K:cl=\eE[H\eE[2J:cm=\eE[%i%d;%dH:\e |
245 | \& :as=\eE(0:bl=^G:cd=\eE[J:ce=\eE[K:cl=\eE[H\eE[2J:\e |
240 | \& :cr=^M:cs=\eE[%i%d;%dr:ct=\eE[3g:dc=\eE[P:dl=\eE[M:do=^J:\e |
246 | \& :cm=\eE[%i%d;%dH:cr=^M:cs=\eE[%i%d;%dr:ct=\eE[3g:dc=\eE[P:\e |
241 | \& :ec=\eE[%dX:ei=\eE[4l:ho=\eE[H:i1=\eE[?47l\eE=\eE[?1l:ic=\eE[@:\e |
247 | \& :dl=\eE[M:do=^J:ec=\eE[%dX:ei=\eE[4l:ho=\eE[H:\e |
|
|
248 | \& :i1=\eE[?47l\eE=\eE[?1l:ic=\eE[@:im=\eE[4h:\e |
242 | \& :im=\eE[4h:is=\eE[r\eE[m\eE[2J\eE[H\eE[?7h\eE[?1;3;4;6l\eE[4l:\e |
249 | \& :is=\eE[r\eE[m\eE[2J\eE[H\eE[?7h\eE[?1;3;4;6l\eE[4l:\e |
243 | \& :k0=\eE[21~:k1=\eE[11~:k2=\eE[12~:k3=\eE[13~:k4=\eE[14~:\e |
250 | \& :k1=\eE[11~:k2=\eE[12~:k3=\eE[13~:k4=\eE[14~:k5=\eE[15~:\e |
244 | \& :k5=\eE[15~:k6=\eE[17~:k7=\eE[18~:k8=\eE[19~:k9=\eE[20~:\e |
251 | \& :k6=\eE[17~:k7=\eE[18~:k8=\eE[19~:k9=\eE[20~:kD=\eE[3~:\e |
245 | \& :kD=\eE[3~:kI=\eE[2~:kN=\eE[6~:kP=\eE[5~:kb=\e177:kd=\eEOB:\e |
252 | \& :kI=\eE[2~:kN=\eE[6~:kP=\eE[5~:kb=\e177:kd=\eEOB:ke=\eE[?1l\eE>:\e |
246 | \& :ke=\eE[?1l\eE>:kh=\eE[7~:kl=\eEOD:kr=\eEOC:ks=\eE[?1h\eE=:\e |
253 | \& :kh=\eE[7~:kl=\eEOD:kr=\eEOC:ks=\eE[?1h\eE=:ku=\eEOA:le=^H:\e |
247 | \& :ku=\eEOA:le=^H:mb=\eE[5m:md=\eE[1m:me=\eE[m\e017:mr=\eE[7m:\e |
254 | \& :mb=\eE[5m:md=\eE[1m:me=\eE[m\e017:mr=\eE[7m:nd=\eE[C:rc=\eE8:\e |
248 | \& :nd=\eE[C:rc=\eE8:sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:\e |
255 | \& :sc=\eE7:se=\eE[27m:sf=^J:so=\eE[7m:sr=\eEM:st=\eEH:ta=^I:\e |
249 | \& :st=\eEH:ta=^I:te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:\e |
256 | \& :te=\eE[r\eE[?1049l:ti=\eE[?1049h:ue=\eE[24m:up=\eE[A:\e |
250 | \& :up=\eE[A:us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e |
257 | \& :us=\eE[4m:vb=\eE[?5h\eE[?5l:ve=\eE[?25h:vi=\eE[?25l:\e |
251 | \& :vs=\eE[?25h: |
258 | \& :vs=\eE[?25h: |
252 | .Ve |
259 | .Ve |
253 | .ie n .IP "Why does ""ls"" no longer have coloured output?" 4 |
260 | .ie n .IP "Why does ""ls"" no longer have coloured output?" 4 |
254 | .el .IP "Why does \f(CWls\fR no longer have coloured output?" 4 |
261 | .el .IP "Why does \f(CWls\fR no longer have coloured output?" 4 |
255 | .IX Item "Why does ls no longer have coloured output?" |
262 | .IX Item "Why does ls no longer have coloured output?" |
… | |
… | |
405 | the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you |
412 | the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you |
406 | might be forced to use a different font. |
413 | might be forced to use a different font. |
407 | .Sp |
414 | .Sp |
408 | All of this is not a problem when using X11 core fonts, as their bounding |
415 | All of this is not a problem when using X11 core fonts, as their bounding |
409 | box data is correct. |
416 | box 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." |
|
|
419 | Seems to be a known bug, read |
|
|
420 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
|
|
421 | following 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 |
410 | .IP "My Compose (Multi_key) key is no longer working." 4 |
426 | .IP "My Compose (Multi_key) key is no longer working." 4 |
411 | .IX Item "My Compose (Multi_key) key is no longer working." |
427 | .IX Item "My Compose (Multi_key) key is no longer working." |
412 | The most common causes for this are that either your locale is not set |
428 | The most common causes for this are that either your locale is not set |
413 | correctly, or you specified a \fBpreeditStyle\fR that is not supported by |
429 | correctly, or you specified a \fBpreeditStyle\fR that is not supported by |
414 | your input method. For example, if you specified \fBOverTheSpot\fR and |
430 | your input method. For example, if you specified \fBOverTheSpot\fR and |
… | |
… | |
456 | .Sp |
472 | .Sp |
457 | As you might have guessed, FreeBSD does neither define this symobl nor |
473 | As you might have guessed, FreeBSD does neither define this symobl nor |
458 | does it support it. Instead, it uses it's own internal representation of |
474 | does it support it. Instead, it uses it's own internal representation of |
459 | \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. |
475 | \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. |
460 | .Sp |
476 | .Sp |
|
|
477 | However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and |
|
|
478 | \&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. |
|
|
479 | .Sp |
461 | However, \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support |
480 | \&\f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR is the only sane way to support multi-language |
462 | multi-language apps in an \s-1OS\s0, as using a locale-dependent (and |
481 | apps in an \s-1OS\s0, as using a locale-dependent (and non\-standardized) |
463 | non\-standardized) representation of \fBwchar_t\fR makes it impossible to |
482 | representation of \fBwchar_t\fR makes it impossible to convert between |
464 | convert between \fBwchar_t\fR (as used by X11 and your applications) and any |
483 | \&\fBwchar_t\fR (as used by X11 and your applications) and any other encoding |
465 | other encoding without implementing OS-specific-wrappers for each and |
484 | without implementing OS-specific-wrappers for each and every locale. There |
466 | every locale. There simply are no APIs to convert \fBwchar_t\fR into anything |
485 | simply are no APIs to convert \fBwchar_t\fR into anything except the current |
467 | except the current locale encoding. |
486 | locale encoding. |
468 | .Sp |
487 | .Sp |
469 | Some applications (such as the formidable \fBmlterm\fR) work around this |
488 | Some applications (such as the formidable \fBmlterm\fR) work around this |
470 | by carrying their own replacement functions for character set handling |
489 | by carrying their own replacement functions for character set handling |
471 | with them, and either implementing OS-dependent hacks or doing multiple |
490 | with them, and either implementing OS-dependent hacks or doing multiple |
472 | conversions (which is slow and unreliable in case the \s-1OS\s0 implements |
491 | conversions (which is slow and unreliable in case the \s-1OS\s0 implements |
473 | encodings slightly different than the terminal emulator). |
492 | encodings slightly different than the terminal emulator). |
474 | .Sp |
493 | .Sp |
475 | The rxvt-unicode author insists that the right way to fix this is in the |
494 | The rxvt-unicode author insists that the right way to fix this is in the |
476 | system libraries once and for all, instead of forcing every app to carry |
495 | system libraries once and for all, instead of forcing every app to carry |
477 | complete replacements for them :) |
496 | complete 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." |
|
|
499 | Try the diff in \fIdoc/solaris9.patch\fR as a base. It fixes the worst |
|
|
500 | problems 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?" |
|
|
503 | rxvt-unicode should compile and run out of the box on cygwin, using |
|
|
504 | the X11 libraries that come with cygwin. libW11 emulation is no |
|
|
505 | longer supported (and makes no sense, either, as it only supported a |
|
|
506 | single 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 |
|
|
508 | old libW11 emulation. |
|
|
509 | .Sp |
|
|
510 | At the time of this writing, cygwin didn't seem to support any multi-byte |
|
|
511 | encodings (you might try \f(CW\*(C`LC_CTYPE=C\-UTF\-8\*(C'\fR), so you are likely limited |
|
|
512 | to 8\-bit encodings. |
478 | .IP "How does rxvt-unicode determine the encoding to use?" 4 |
513 | .IP "How does rxvt-unicode determine the encoding to use?" 4 |
479 | .IX Item "How does rxvt-unicode determine the encoding to use?" |
514 | .IX Item "How does rxvt-unicode determine the encoding to use?" |
480 | .PD 0 |
515 | .PD 0 |
481 | .IP "Is there an option to switch encodings?" 4 |
516 | .IP "Is there an option to switch encodings?" 4 |
482 | .IX Item "Is there an option to switch encodings?" |
517 | .IX Item "Is there an option to switch encodings?" |
… | |
… | |
1612 | Ps = 13 Change colour of mouse foreground to Pt |
1647 | Ps = 13 Change colour of mouse foreground to Pt |
1613 | Ps = 17 Change colour of highlight characters to Pt |
1648 | Ps = 17 Change colour of highlight characters to Pt |
1614 | Ps = 18 Change colour of bold characters to Pt |
1649 | Ps = 18 Change colour of bold characters to Pt |
1615 | Ps = 19 Change colour of underlined characters to Pt |
1650 | Ps = 19 Change colour of underlined characters to Pt |
1616 | Ps = 20 Change default background to Pt |
1651 | Ps = 20 Change default background to Pt |
1617 | Ps = 39 Change default foreground colour to Pt rxvt compile-time option |
1652 | Ps = 39 Change default foreground colour to Pt. |
1618 | Ps = 46 Change Log File to Pt unimplemented |
1653 | Ps = 46 Change Log File to Pt unimplemented |
1619 | Ps = 49 Change default background colour to Pt rxvt compile-time option |
1654 | Ps = 49 Change default background colour to Pt. |
1620 | Ps = 50 Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n |
1655 | Ps = 50 Set fontset to Pt, with the following special values of Pt (rxvt) #+n change up n #-n change down n if n is missing of 0, a value of 1 is used empty change to font0 n change to font n |
1621 | Ps = 55 Log all scrollback buffer and all of screen to Pt |
1656 | Ps = 55 Log all scrollback buffer and all of screen to Pt |
1622 | Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (@@RXVT_NAME@@ extension) |
1657 | Ps = 701 Change current locale to Pt, or, if Pt is ?, return the current locale (Compile frills). |
1623 | Ps = 703 Menubar command Pt rxvt compile-time option (rxvt-unicode extension) |
1658 | Ps = 703 Menubar command Pt (Compile menubar). |
1624 | Ps = 704 Change colour of italic characters to Pt |
1659 | Ps = 704 Change colour of italic characters to Pt |
1625 | Ps = 705 Change background pixmap tint colour to Pt |
1660 | Ps = 705 Change background pixmap tint colour to Pt (Compile transparency). |
1626 | Ps = 710 Set normal fontset to Pt. Same as Ps = 50. |
1661 | Ps = 710 Set normal fontset to Pt. Same as Ps = 50. |
1627 | Ps = 711 Set bold fontset to Pt. Similar to Ps = 50. |
1662 | Ps = 711 Set bold fontset to Pt. Similar to Ps = 50 (Compile styles). |
1628 | Ps = 712 Set italic fontset to Pt. Similar to Ps = 50. |
1663 | Ps = 712 Set italic fontset to Pt. Similar to Ps = 50 (Compile styles). |
1629 | Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50. |
1664 | Ps = 713 Set bold-italic fontset to Pt. Similar to Ps = 50 (Compile styles). |
|
|
1665 | Ps = 720 Move viewing window up by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
|
|
1666 | Ps = 721 Move viewing window down by Pt lines, or clear scrollback buffer if Pt = 0 (Compile frills). |
1630 | .TE |
1667 | .TE |
1631 | |
1668 | |
1632 | .PP |
1669 | .PP |
1633 | |
1670 | |
1634 | .IX Xref "menuBar" |
1671 | .IX Xref "menuBar" |
… | |
… | |
2184 | .IX Item "--enable-font-styles" |
2221 | .IX Item "--enable-font-styles" |
2185 | Add support for \fBbold\fR, \fIitalic\fR and \fB\f(BIbold italic\fB\fR font |
2222 | Add support for \fBbold\fR, \fIitalic\fR and \fB\f(BIbold italic\fB\fR font |
2186 | styles. The fonts can be set manually or automatically. |
2223 | styles. The fonts can be set manually or automatically. |
2187 | .IP "\-\-with\-codesets=NAME,..." 4 |
2224 | .IP "\-\-with\-codesets=NAME,..." 4 |
2188 | .IX Item "--with-codesets=NAME,..." |
2225 | .IX Item "--with-codesets=NAME,..." |
2189 | Compile in support for additional codeset (encoding) groups (eu, vn are |
2226 | Compile in support for additional codeset (encoding) groups (\f(CW\*(C`eu\*(C'\fR, \f(CW\*(C`vn\*(C'\fR |
2190 | always compiled in, which includes most 8\-bit character sets). These |
2227 | are always compiled in, which includes most 8\-bit character sets). These |
2191 | codeset tables are currently only used for driving X11 core fonts, they |
2228 | codeset tables are used for driving X11 core fonts, they are not required |
2192 | are not required for Xft fonts. Compiling them in will make your binary |
2229 | for Xft fonts, although having them compiled in lets rxvt-unicode choose |
2193 | bigger (together about 700kB), but it doesn't increase memory usage unless |
2230 | replacement fonts more intelligently. Compiling them in will make your |
|
|
2231 | binary bigger (all of together cost about 700kB), but it doesn't increase |
2194 | you use an X11 font requiring one of these encodings. |
2232 | memory usage unless you use a font requiring one of these encodings. |
2195 | .TS |
2233 | .TS |
2196 | l l . |
2234 | l l . |
2197 | all all available codeset groups |
2235 | all all available codeset groups |
2198 | zh common chinese encodings |
2236 | zh common chinese encodings |
2199 | zh_ext rarely used but very big chinese encodigs |
2237 | zh_ext rarely used but very big chinese encodigs |
… | |
… | |
2341 | disable this. |
2379 | disable this. |
2342 | .Sp |
2380 | .Sp |
2343 | A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly |
2381 | A non-exhaustive list of features enabled by \f(CW\*(C`\-\-enable\-frills\*(C'\fR (possibly |
2344 | in combination with other switches) is: |
2382 | in combination with other switches) is: |
2345 | .Sp |
2383 | .Sp |
2346 | .Vb 11 |
2384 | .Vb 13 |
2347 | \& MWM-hints |
2385 | \& MWM-hints |
|
|
2386 | \& EWMH-hints (pid, utf8 names) and protocols (ping) |
2348 | \& seperate underline colour |
2387 | \& seperate underline colour |
2349 | \& settable border widths and borderless switch |
2388 | \& settable border widths and borderless switch |
2350 | \& settable extra linespacing |
2389 | \& settable extra linespacing |
2351 | \& extra window properties (e.g. UTF-8 window names and PID) |
|
|
2352 | \& iso-14755-2 and -3, and visual feedback |
2390 | \& iso-14755-2 and -3, and visual feedback |
2353 | \& backindex and forwardindex escape sequence |
2391 | \& backindex and forwardindex escape sequence |
2354 | \& window op and locale change escape sequences |
2392 | \& window op and some xterm/OSC escape sequences |
2355 | \& tripleclickwords |
2393 | \& tripleclickwords |
2356 | \& settable insecure mode |
2394 | \& settable insecure mode |
2357 | \& keysym remapping support |
2395 | \& keysym remapping support |
|
|
2396 | \& cursor blinking and underline cursor |
|
|
2397 | \& -embed and -pty-fd options |
2358 | .Ve |
2398 | .Ve |
2359 | .IP "\-\-enable\-iso14755" 4 |
2399 | .IP "\-\-enable\-iso14755" 4 |
2360 | .IX Item "--enable-iso14755" |
2400 | .IX Item "--enable-iso14755" |
2361 | Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or |
2401 | Enable extended \s-1ISO\s0 14755 support (see @@RXVT_NAME@@(1), or |
2362 | \&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by |
2402 | \&\fIdoc/rxvt.1.txt\fR). Basic support (section 5.1) is enabled by |
… | |
… | |
2393 | .IP "\-\-enable\-smart\-resize" 4 |
2433 | .IP "\-\-enable\-smart\-resize" 4 |
2394 | .IX Item "--enable-smart-resize" |
2434 | .IX Item "--enable-smart-resize" |
2395 | Add smart growth/shrink behaviour when changing font size via from hot |
2435 | Add smart growth/shrink behaviour when changing font size via from hot |
2396 | keys. This should keep in a fixed position the rxvt corner which is |
2436 | keys. This should keep in a fixed position the rxvt corner which is |
2397 | closest to a corner of the screen. |
2437 | closest to a corner of the screen. |
2398 | .IP "\-\-enable\-cursor\-blink" 4 |
|
|
2399 | .IX Item "--enable-cursor-blink" |
|
|
2400 | Add support for a blinking cursor. |
|
|
2401 | .IP "\-\-enable\-pointer\-blank" 4 |
2438 | .IP "\-\-enable\-pointer\-blank" 4 |
2402 | .IX Item "--enable-pointer-blank" |
2439 | .IX Item "--enable-pointer-blank" |
2403 | Add support to have the pointer disappear when typing or inactive. |
2440 | Add support to have the pointer disappear when typing or inactive. |
2404 | .IP "\-\-with\-name=NAME" 4 |
2441 | .IP "\-\-with\-name=NAME" 4 |
2405 | .IX Item "--with-name=NAME" |
2442 | .IX Item "--with-name=NAME" |