| … | |
… | |
| 127 | .\} |
127 | .\} |
| 128 | .rm #[ #] #H #V #F C |
128 | .rm #[ #] #H #V #F C |
| 129 | .\" ======================================================================== |
129 | .\" ======================================================================== |
| 130 | .\" |
130 | .\" |
| 131 | .IX Title "@@RXVT_NAME@@ 7" |
131 | .IX Title "@@RXVT_NAME@@ 7" |
| 132 | .TH @@RXVT_NAME@@ 7 "2006-07-17" "7.8" "RXVT-UNICODE" |
132 | .TH @@RXVT_NAME@@ 7 "2006-08-07" "7.9" "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 |
| … | |
… | |
| 229 | This tries to create a new terminal, and if fails with exit status 2, |
229 | This tries to create a new terminal, and if fails with exit status 2, |
| 230 | meaning it couldn't connect to the daemon, it will start the daemon and |
230 | meaning it couldn't connect to the daemon, it will start the daemon and |
| 231 | re-run the command. Subsequent invocations of the script will re-use the |
231 | re-run the command. Subsequent invocations of the script will re-use the |
| 232 | existing daemon. |
232 | existing daemon. |
| 233 | .PP |
233 | .PP |
| 234 | \fIHow do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR |
234 | \fIHow do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc.\fR |
| 235 | .IX Subsection "How do I distinguish wether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
235 | .IX Subsection "How do I distinguish whether I'm running rxvt-unicode or a regular xterm? I need this to decide about setting colors etc." |
| 236 | .PP |
236 | .PP |
| 237 | The original rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", |
237 | The original rxvt and rxvt-unicode always export the variable \*(L"\s-1COLORTERM\s0\*(R", |
| 238 | so you can check and see if that is set. Note that several programs, \s-1JED\s0, |
238 | so you can check and see if that is set. Note that several programs, \s-1JED\s0, |
| 239 | slrn, Midnight Commander automatically check this variable to decide |
239 | slrn, Midnight Commander automatically check this variable to decide |
| 240 | whether or not to use color. |
240 | whether or not to use color. |
| … | |
… | |
| 291 | \& 188985 9048 66616 18222 1788 urxvt \-\-disable\-everything |
291 | \& 188985 9048 66616 18222 1788 urxvt \-\-disable\-everything |
| 292 | .Ve |
292 | .Ve |
| 293 | .PP |
293 | .PP |
| 294 | When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which \fIis\fR unfair, as this involves xft |
294 | When you \f(CW\*(C`\-\-enable\-everything\*(C'\fR (which \fIis\fR unfair, as this involves xft |
| 295 | and full locale/XIM support which are quite bloaty inside libX11 and my |
295 | and full locale/XIM support which are quite bloaty inside libX11 and my |
| 296 | libc), the two diverge, but not unreasnobaly so. |
296 | libc), the two diverge, but not unreasonably so. |
| 297 | .PP |
297 | .PP |
| 298 | .Vb 3 |
298 | .Vb 3 |
| 299 | \& text data bss drs rss filename |
299 | \& text data bss drs rss filename |
| 300 | \& 163431 2152 24 20123 2060 rxvt \-\-enable\-everything |
300 | \& 163431 2152 24 20123 2060 rxvt \-\-enable\-everything |
| 301 | \& 1035683 49680 66648 29096 3680 urxvt \-\-enable\-everything |
301 | \& 1035683 49680 66648 29096 3680 urxvt \-\-enable\-everything |
| … | |
… | |
| 400 | \& @@URXVT_NAME@@ \-depth 32 \-fg grey90 \-bg rgba:0000/0000/4444/cccc |
400 | \& @@URXVT_NAME@@ \-depth 32 \-fg grey90 \-bg rgba:0000/0000/4444/cccc |
| 401 | .Ve |
401 | .Ve |
| 402 | .PP |
402 | .PP |
| 403 | This requires \s-1XFT\s0 support, and the support of your X\-server. If that |
403 | This requires \s-1XFT\s0 support, and the support of your X\-server. If that |
| 404 | doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't |
404 | doesn't work for you, blame Xorg and Keith Packard. \s-1ARGB\s0 visuals aren't |
| 405 | there yet, no matter what they claim. Rxvt-Unicode contains the neccessary |
405 | there yet, no matter what they claim. Rxvt-Unicode contains the necessary |
| 406 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
406 | bugfixes and workarounds for Xft and Xlib to make it work, but that |
| 407 | doesn't mean that your \s-1WM\s0 has the required kludges in place. |
407 | doesn't mean that your \s-1WM\s0 has the required kludges in place. |
| 408 | .PP |
408 | .PP |
| 409 | 4. Use xcompmgr and let it do the job: |
409 | 4. Use xcompmgr and let it do the job: |
| 410 | .PP |
410 | .PP |
| … | |
… | |
| 430 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
430 | however: Xft fonts often draw glyphs larger than their acclaimed bounding |
| 431 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
431 | box, and rxvt-unicode has no way of detecting this (the correct way is to |
| 432 | ask for the character bounding box, which unfortunately is wrong in these |
432 | ask for the character bounding box, which unfortunately is wrong in these |
| 433 | cases). |
433 | cases). |
| 434 | .PP |
434 | .PP |
| 435 | It's not clear (to me at least), wether this is a bug in Xft, freetype, |
435 | It's not clear (to me at least), whether this is a bug in Xft, freetype, |
| 436 | or the respective font. If you encounter this problem you might try using |
436 | or the respective font. If you encounter this problem you might try using |
| 437 | the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you |
437 | the \f(CW\*(C`\-lsp\*(C'\fR option to give the font more height. If that doesn't work, you |
| 438 | might be forced to use a different font. |
438 | might be forced to use a different font. |
| 439 | .PP |
439 | .PP |
| 440 | All of this is not a problem when using X11 core fonts, as their bounding |
440 | All of this is not a problem when using X11 core fonts, as their bounding |
| … | |
… | |
| 708 | circumstances, it will move your cursor around when you click into the |
708 | circumstances, it will move your cursor around when you click into the |
| 709 | line that contains it. It tries hard not to do this at the wrong moment, |
709 | line that contains it. It tries hard not to do this at the wrong moment, |
| 710 | but when running a program that doesn't parse cursor movements or in some |
710 | but when running a program that doesn't parse cursor movements or in some |
| 711 | cases during rlogin sessions, it fails to detect this properly. |
711 | cases during rlogin sessions, it fails to detect this properly. |
| 712 | .PP |
712 | .PP |
| 713 | You can permamently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR |
713 | You can permanently switch this feature off by disabling the \f(CW\*(C`readline\*(C'\fR |
| 714 | extension: |
714 | extension: |
| 715 | .PP |
715 | .PP |
| 716 | .Vb 1 |
716 | .Vb 1 |
| 717 | \& URxvt.perl\-ext\-common: default,\-readline |
717 | \& URxvt.perl\-ext\-common: default,\-readline |
| 718 | .Ve |
718 | .Ve |
| … | |
… | |
| 720 | \fIMy numerical keypad acts weird and generates differing output?\fR |
720 | \fIMy numerical keypad acts weird and generates differing output?\fR |
| 721 | .IX Subsection "My numerical keypad acts weird and generates differing output?" |
721 | .IX Subsection "My numerical keypad acts weird and generates differing output?" |
| 722 | .PP |
722 | .PP |
| 723 | Some Debian GNUL/Linux users seem to have this problem, although no |
723 | Some Debian GNUL/Linux users seem to have this problem, although no |
| 724 | specific details were reported so far. It is possible that this is caused |
724 | specific details were reported so far. It is possible that this is caused |
| 725 | by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of wether and how |
725 | by the wrong \f(CW\*(C`TERM\*(C'\fR setting, although the details of whether and how |
| 726 | this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible |
726 | this can happen are unknown, as \f(CW\*(C`TERM=rxvt\*(C'\fR should offer a compatible |
| 727 | keymap. See the answer to the previous question, and please report if that |
727 | keymap. See the answer to the previous question, and please report if that |
| 728 | helped. |
728 | helped. |
| 729 | .PP |
729 | .PP |
| 730 | \fIMy Compose (Multi_key) key is no longer working.\fR |
730 | \fIMy Compose (Multi_key) key is no longer working.\fR |
| … | |
… | |
| 760 | .PP |
760 | .PP |
| 761 | \fIWhat's with the strange Backspace/Delete key behaviour?\fR |
761 | \fIWhat's with the strange Backspace/Delete key behaviour?\fR |
| 762 | .IX Subsection "What's with the strange Backspace/Delete key behaviour?" |
762 | .IX Subsection "What's with the strange Backspace/Delete key behaviour?" |
| 763 | .PP |
763 | .PP |
| 764 | Assuming that the physical Backspace key corresponds to the |
764 | Assuming that the physical Backspace key corresponds to the |
| 765 | BackSpace keysym (not likely for Linux ... see the following |
765 | Backspace keysym (not likely for Linux ... see the following |
| 766 | question) there are two standard values that can be used for |
766 | question) there are two standard values that can be used for |
| 767 | Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR. |
767 | Backspace: \f(CW\*(C`^H\*(C'\fR and \f(CW\*(C`^?\*(C'\fR. |
| 768 | .PP |
768 | .PP |
| 769 | Historically, either value is correct, but rxvt-unicode adopts the debian |
769 | Historically, either value is correct, but rxvt-unicode adopts the debian |
| 770 | policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct |
770 | policy of using \f(CW\*(C`^?\*(C'\fR when unsure, because it's the one only only correct |
| … | |
… | |
| 911 | directory and also tells urxvt to use a large number of extensions. I |
911 | directory and also tells urxvt to use a large number of extensions. I |
| 912 | develop for myself mostly, so I actually use most of the extensions I |
912 | develop for myself mostly, so I actually use most of the extensions I |
| 913 | write. |
913 | write. |
| 914 | .PP |
914 | .PP |
| 915 | The selection stuff mainly makes the selection perl-error-message aware |
915 | The selection stuff mainly makes the selection perl-error-message aware |
| 916 | and tells it to convert pelr error mssages into vi-commands to load the |
916 | and tells it to convert perl error messages into vi-commands to load the |
| 917 | relevant file and go tot he error line number. |
917 | relevant file and go tot he error line number. |
| 918 | .PP |
918 | .PP |
| 919 | .Vb 2 |
919 | .Vb 2 |
| 920 | \& URxvt.scrollstyle: plain |
920 | \& URxvt.scrollstyle: plain |
| 921 | \& URxvt.secondaryScroll: true |
921 | \& URxvt.secondaryScroll: true |
| 922 | .Ve |
922 | .Ve |
| 923 | .PP |
923 | .PP |
| 924 | As the documentation says: plain is the preferred scrollbar for the |
924 | As the documentation says: plain is the preferred scrollbar for the |
| 925 | author. The \f(CW\*(C`secondaryScroll\*(C'\fR confgiures urxvt to scroll in full-screen |
925 | author. The \f(CW\*(C`secondaryScroll\*(C'\fR configures urxvt to scroll in full-screen |
| 926 | apps, like screen, so lines scorlled out of screen end up in urxvt's |
926 | apps, like screen, so lines scrolled out of screen end up in urxvt's |
| 927 | scrollback buffer. |
927 | scrollback buffer. |
| 928 | .PP |
928 | .PP |
| 929 | .Vb 7 |
929 | .Vb 7 |
| 930 | \& URxvt.background: #000000 |
930 | \& URxvt.background: #000000 |
| 931 | \& URxvt.foreground: gray90 |
931 | \& URxvt.foreground: gray90 |
| … | |
… | |
| 1000 | \& urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
1000 | \& urxvt.italicFont: xft:Bitstream Vera Sans Mono:italic:autohint=true |
| 1001 | \& urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
1001 | \& urxvt.boldItalicFont: xft:Bitstream Vera Sans Mono:bold:italic:autohint=true |
| 1002 | .Ve |
1002 | .Ve |
| 1003 | .PP |
1003 | .PP |
| 1004 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
1004 | I wrote rxvt-unicode to be able to specify fonts exactly. So don't be |
| 1005 | overwhelmed. A special note: the \f(CW\*(C`9x15bold\*(C'\fR mentioend above is actually |
1005 | overwhelmed. A special note: the \f(CW\*(C`9x15bold\*(C'\fR mentioned above is actually |
| 1006 | the version from XFree\-3.3, as XFree\-4 replaced it by a totally different |
1006 | the version from XFree\-3.3, as XFree\-4 replaced it by a totally different |
| 1007 | font (different glyphs for \f(CW\*(C`;\*(C'\fR and many other harmless characters), |
1007 | font (different glyphs for \f(CW\*(C`;\*(C'\fR and many other harmless characters), |
| 1008 | while the second font is actually the \f(CW\*(C`9x15bold\*(C'\fR from XFree4/XOrg. The |
1008 | while the second font is actually the \f(CW\*(C`9x15bold\*(C'\fR from XFree4/XOrg. The |
| 1009 | bold version has less chars than the medium version, so I use it for rare |
1009 | bold version has less chars than the medium version, so I use it for rare |
| 1010 | characters, too. Whene ditign sources with vim, I use italic for comments |
1010 | characters, too. When editing sources with vim, I use italic for comments |
| 1011 | and other stuff, which looks quite good with Bitstream Vera anti\-aliased. |
1011 | and other stuff, which looks quite good with Bitstream Vera anti\-aliased. |
| 1012 | .PP |
1012 | .PP |
| 1013 | Terminus is a quite bad font (many very wrong glyphs), but for most of my |
1013 | Terminus is a quite bad font (many very wrong glyphs), but for most of my |
| 1014 | purposes, it works, and gives a different look, as my normal (Non\-bold) |
1014 | purposes, it works, and gives a different look, as my normal (Non\-bold) |
| 1015 | font is already bold, and I want to see a difference between bold and |
1015 | font is already bold, and I want to see a difference between bold and |
| … | |
… | |
| 1073 | .Vb 1 |
1073 | .Vb 1 |
| 1074 | \& URxvt.resource: value |
1074 | \& URxvt.resource: value |
| 1075 | .Ve |
1075 | .Ve |
| 1076 | .PP |
1076 | .PP |
| 1077 | If you want to use another form (there are lots of different ways of |
1077 | If you want to use another form (there are lots of different ways of |
| 1078 | specifying resources), make sure you understand wether and why it |
1078 | specifying resources), make sure you understand whether and why it |
| 1079 | works. If unsure, use the form above. |
1079 | works. If unsure, use the form above. |
| 1080 | .PP |
1080 | .PP |
| 1081 | \fIWhen I log-in to another system it tells me about missing terminfo data?\fR |
1081 | \fIWhen I log-in to another system it tells me about missing terminfo data?\fR |
| 1082 | .IX Subsection "When I log-in to another system it tells me about missing terminfo data?" |
1082 | .IX Subsection "When I log-in to another system it tells me about missing terminfo data?" |
| 1083 | .PP |
1083 | .PP |
| … | |
… | |
| 1128 | One reason you might want this is that some distributions or operating |
1128 | One reason you might want this is that some distributions or operating |
| 1129 | systems still compile some programs using the long-obsoleted termcap |
1129 | systems still compile some programs using the long-obsoleted termcap |
| 1130 | library (Fedora Core's bash is one example) and rely on a termcap entry |
1130 | library (Fedora Core's bash is one example) and rely on a termcap entry |
| 1131 | for \f(CW\*(C`rxvt\-unicode\*(C'\fR. |
1131 | for \f(CW\*(C`rxvt\-unicode\*(C'\fR. |
| 1132 | .PP |
1132 | .PP |
| 1133 | You could use rxvt's termcap entry with resonable results in many cases. |
1133 | You could use rxvt's termcap entry with reasonable results in many cases. |
| 1134 | You can also create a termcap entry by using terminfo's infocmp program |
1134 | You can also create a termcap entry by using terminfo's infocmp program |
| 1135 | like this: |
1135 | like this: |
| 1136 | .PP |
1136 | .PP |
| 1137 | .Vb 1 |
1137 | .Vb 1 |
| 1138 | \& infocmp \-C rxvt\-unicode |
1138 | \& infocmp \-C rxvt\-unicode |
| … | |
… | |
| 1165 | .PP |
1165 | .PP |
| 1166 | \fIWhy does \f(CI\*(C`ls\*(C'\fI no longer have coloured output?\fR |
1166 | \fIWhy does \f(CI\*(C`ls\*(C'\fI no longer have coloured output?\fR |
| 1167 | .IX Subsection "Why does ls no longer have coloured output?" |
1167 | .IX Subsection "Why does ls no longer have coloured output?" |
| 1168 | .PP |
1168 | .PP |
| 1169 | The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to |
1169 | The \f(CW\*(C`ls\*(C'\fR in the \s-1GNU\s0 coreutils unfortunately doesn't use terminfo to |
| 1170 | decide wether a terminal has colour, but uses its own configuration |
1170 | decide whether a terminal has colour, but uses its own configuration |
| 1171 | file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in its default file (among |
1171 | file. Needless to say, \f(CW\*(C`rxvt\-unicode\*(C'\fR is not in its default file (among |
| 1172 | with most other terminals supporting colour). Either add: |
1172 | with most other terminals supporting colour). Either add: |
| 1173 | .PP |
1173 | .PP |
| 1174 | .Vb 1 |
1174 | .Vb 1 |
| 1175 | \& TERM rxvt\-unicode |
1175 | \& TERM rxvt\-unicode |
| … | |
… | |
| 1333 | .ie n .IP "\- Make sure the ""XMODIFIERS""\fR environment variable is set correctly when \fIstarting rxvt\-unicode." 4 |
1333 | .ie n .IP "\- Make sure the ""XMODIFIERS""\fR environment variable is set correctly when \fIstarting rxvt\-unicode." 4 |
| 1334 | .el .IP "\- Make sure the \f(CWXMODIFIERS\fR environment variable is set correctly when \fIstarting\fR rxvt\-unicode." 4 |
1334 | .el .IP "\- Make sure the \f(CWXMODIFIERS\fR environment variable is set correctly when \fIstarting\fR rxvt\-unicode." 4 |
| 1335 | .IX Item "- Make sure the XMODIFIERS environment variable is set correctly when starting rxvt-unicode." |
1335 | .IX Item "- Make sure the XMODIFIERS environment variable is set correctly when starting rxvt-unicode." |
| 1336 | .PD |
1336 | .PD |
| 1337 | When you want to use e.g. \fBkinput2\fR, it must be set to |
1337 | When you want to use e.g. \fBkinput2\fR, it must be set to |
| 1338 | \&\f(CW\*(C`@im=kinput2\*(C'\fR. For \fBscim\fR, use \f(CW\*(C`@im=SCIM\*(C'\fR. Youc an see what input |
1338 | \&\f(CW\*(C`@im=kinput2\*(C'\fR. For \fBscim\fR, use \f(CW\*(C`@im=SCIM\*(C'\fR. You can see what input |
| 1339 | method servers are running with this command: |
1339 | method servers are running with this command: |
| 1340 | .Sp |
1340 | .Sp |
| 1341 | .Vb 1 |
1341 | .Vb 1 |
| 1342 | \& xprop \-root XIM_SERVERS |
1342 | \& xprop \-root XIM_SERVERS |
| 1343 | .Ve |
1343 | .Ve |
| … | |
… | |
| 1391 | \fII am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?\fR |
1391 | \fII am maintaining rxvt-unicode for distribution/OS \s-1XXX\s0, any recommendation?\fR |
| 1392 | .IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?" |
1392 | .IX Subsection "I am maintaining rxvt-unicode for distribution/OS XXX, any recommendation?" |
| 1393 | .PP |
1393 | .PP |
| 1394 | You should build one binary with the default options. \fIconfigure\fR |
1394 | You should build one binary with the default options. \fIconfigure\fR |
| 1395 | now enables most useful options, and the trend goes to making them |
1395 | now enables most useful options, and the trend goes to making them |
| 1396 | runtime\-switchable, too, so there is usually no drawback to enbaling them, |
1396 | runtime\-switchable, too, so there is usually no drawback to enabling them, |
| 1397 | except higher disk and possibly memory usage. The perl interpreter should |
1397 | except higher disk and possibly memory usage. The perl interpreter should |
| 1398 | be enabled, as important functionality (menus, selection, likely more in |
1398 | be enabled, as important functionality (menus, selection, likely more in |
| 1399 | the future) depends on it. |
1399 | the future) depends on it. |
| 1400 | .PP |
1400 | .PP |
| 1401 | You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources |
1401 | You should not overwrite the \f(CW\*(C`perl\-ext\-common\*(C'\fR snd \f(CW\*(C`perl\-ext\*(C'\fR resources |
| … | |
… | |
| 1441 | \fII am on FreeBSD and rxvt-unicode does not seem to work at all.\fR |
1441 | \fII am on FreeBSD and rxvt-unicode does not seem to work at all.\fR |
| 1442 | .IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all." |
1442 | .IX Subsection "I am on FreeBSD and rxvt-unicode does not seem to work at all." |
| 1443 | .PP |
1443 | .PP |
| 1444 | Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined |
1444 | Rxvt-unicode requires the symbol \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR to be defined |
| 1445 | in your compile environment, or an implementation that implements it, |
1445 | in your compile environment, or an implementation that implements it, |
| 1446 | wether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that |
1446 | whether it defines the symbol or not. \f(CW\*(C`_\|_STDC_ISO_10646_\|_\*(C'\fR requires that |
| 1447 | \&\fBwchar_t\fR is represented as unicode. |
1447 | \&\fBwchar_t\fR is represented as unicode. |
| 1448 | .PP |
1448 | .PP |
| 1449 | As you might have guessed, FreeBSD does neither define this symobl nor |
1449 | As you might have guessed, FreeBSD does neither define this symbol nor |
| 1450 | does it support it. Instead, it uses its own internal representation of |
1450 | does it support it. Instead, it uses its own internal representation of |
| 1451 | \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. |
1451 | \&\fBwchar_t\fR. This is, of course, completely fine with respect to standards. |
| 1452 | .PP |
1452 | .PP |
| 1453 | However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and |
1453 | However, that means rxvt-unicode only works in \f(CW\*(C`POSIX\*(C'\fR, \f(CW\*(C`ISO\-8859\-1\*(C'\fR and |
| 1454 | \&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. |
1454 | \&\f(CW\*(C`UTF\-8\*(C'\fR locales under FreeBSD (which all use Unicode as \fBwchar_t\fR. |
