| … | |
… | |
| 42 | |
42 | |
| 43 | How can I start urxvtd in a race-free way? |
43 | How can I start urxvtd in a race-free way? |
| 44 | Try "urxvtd -f -o", which tells urxvtd to open the display, create the |
44 | Try "urxvtd -f -o", which tells urxvtd to open the display, create the |
| 45 | listening socket and then fork. |
45 | listening socket and then fork. |
| 46 | |
46 | |
| 47 | How can I start urxvtd automatically when I run URXVT_NAME@@c? |
47 | How can I start urxvtd automatically when I run urxvtc? |
| 48 | If you want to start urxvtd automatically whenever you run urxvtc and |
48 | If you want to start urxvtd automatically whenever you run urxvtc and |
| 49 | the daemon isn't running yet, use this script: |
49 | the daemon isn't running yet, use this script: |
| 50 | |
50 | |
| 51 | #!/bin/sh |
51 | #!/bin/sh |
| 52 | urxvtc "$@" |
52 | urxvtc "$@" |
| … | |
… | |
| 90 | fi |
90 | fi |
| 91 | fi |
91 | fi |
| 92 | |
92 | |
| 93 | How do I compile the manual pages on my own? |
93 | How do I compile the manual pages on my own? |
| 94 | You need to have a recent version of perl installed as /usr/bin/perl, |
94 | You need to have a recent version of perl installed as /usr/bin/perl, |
| 95 | one that comes with pod2man, pod2text and pod2html. Then go to the doc |
95 | one that comes with pod2man, pod2text and pod2xhtml (from Pod::Xhtml). |
| 96 | subdirectory and enter "make alldoc". |
96 | Then go to the doc subdirectory and enter "make alldoc". |
| 97 | |
97 | |
| 98 | Isn't rxvt-unicode supposed to be small? Don't all those features bloat? |
98 | Isn't rxvt-unicode supposed to be small? Don't all those features bloat? |
| 99 | I often get asked about this, and I think, no, they didn't cause extra |
99 | I often get asked about this, and I think, no, they didn't cause extra |
| 100 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
100 | bloat. If you compare a minimal rxvt and a minimal urxvt, you can see |
| 101 | that the urxvt binary is larger (due to some encoding tables always |
101 | that the urxvt binary is larger (due to some encoding tables always |
| … | |
… | |
| 160 | |
160 | |
| 161 | And here is rxvt-unicode: |
161 | And here is rxvt-unicode: |
| 162 | |
162 | |
| 163 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
163 | libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x00002aaaaabc3000) |
| 164 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
164 | libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00002aaaaada2000) |
| 165 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
165 | libc.so.6 => /lib/libc.so.6 (0x00002aaaaaeb0000) |
| 166 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
166 | libdl.so.2 => /lib/libdl.so.2 (0x00002aaaab0ee000) |
| 167 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
167 | /lib64/ld-linux-x86-64.so.2 (0x00002aaaaaaab000) |
| 168 | |
168 | |
| 169 | No large bloated libraries (of course, none were linked in statically), |
169 | No large bloated libraries (of course, none were linked in statically), |
| 170 | except maybe libX11 :) |
170 | except maybe libX11 :) |
| 171 | |
171 | |
| 172 | Rendering, Font & Look and Feel Issues |
172 | Rendering, Font & Look and Feel Issues |
| 173 | I can't get transparency working, what am I doing wrong? |
173 | I can't get transparency working, what am I doing wrong? |
| 174 | First of all, transparency isn't officially supported in rxvt-unicode, |
174 | First of all, please address all transparency related issues to Sasha |
| 175 | so you are mostly on your own. Do not bug the author about it (but you |
175 | Vasko at sasha@aftercode.net and do not bug the author about it. Also, |
| 176 | may bug everybody else). Also, if you can't get it working consider it a |
176 | if you can't get it working consider it a rite of passage: ... and you |
| 177 | rite of passage: ... and you failed. |
177 | failed. |
| 178 | |
178 | |
| 179 | Here are four ways to get transparency. Do read the manpage and option |
179 | Here are four ways to get transparency. Do read the manpage and option |
| 180 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
180 | descriptions for the programs mentioned and rxvt-unicode. Really, do it! |
| 181 | |
181 | |
| 182 | 1. Use inheritPixmap: |
182 | 1. Use transparent mode: |
| 183 | |
183 | |
| 184 | Esetroot wallpaper.jpg |
184 | Esetroot wallpaper.jpg |
| 185 | urxvt -ip -tint red -sh 40 |
185 | urxvt -tr -tint red -sh 40 |
| 186 | |
186 | |
| 187 | That works. If you think it doesn't, you lack transparency and tinting |
187 | That works. If you think it doesn't, you lack transparency and tinting |
| 188 | support, or you are unable to read. |
188 | support, or you are unable to read. |
| 189 | |
189 | |
| 190 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
190 | 2. Use a simple pixmap and emulate pseudo-transparency. This enables you |
| 191 | to use effects other than tinting and shading: Just shade/tint/whatever |
191 | to use effects other than tinting and shading: Just shade/tint/whatever |
| 192 | your picture with gimp or any other tool: |
192 | your picture with gimp or any other tool: |
| 193 | |
193 | |
| 194 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.xpm |
194 | convert wallpaper.jpg -blur 20x20 -modulate 30 background.jpg |
| 195 | urxvt -pixmap background.xpm -pe automove-background |
195 | urxvt -pixmap "background.jpg;:root" |
| 196 | |
196 | |
| 197 | That works. If you think it doesn't, you lack XPM and Perl support, or |
197 | That works. If you think it doesn't, you lack AfterImage support, or you |
| 198 | you are unable to read. |
198 | are unable to read. |
| 199 | |
199 | |
| 200 | 3. Use an ARGB visual: |
200 | 3. Use an ARGB visual: |
| 201 | |
201 | |
| 202 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
202 | urxvt -depth 32 -fg grey90 -bg rgba:0000/0000/4444/cccc |
| 203 | |
203 | |
| … | |
… | |
| 297 | What's with this bold/blink stuff? |
297 | What's with this bold/blink stuff? |
| 298 | If no bold colour is set via "colorBD:", bold will invert text using the |
298 | If no bold colour is set via "colorBD:", bold will invert text using the |
| 299 | standard foreground colour. |
299 | standard foreground colour. |
| 300 | |
300 | |
| 301 | For the standard background colour, blinking will actually make the text |
301 | For the standard background colour, blinking will actually make the text |
| 302 | blink when compiled with "--enable-blinking". with standard colours. |
302 | blink when compiled with "--enable-text-blink". Without |
| 303 | Without "--enable-blinking", the blink attribute will be ignored. |
303 | "--enable-text-blink", the blink attribute will be ignored. |
| 304 | |
304 | |
| 305 | On ANSI colours, bold/blink attributes are used to set high-intensity |
305 | On ANSI colours, bold/blink attributes are used to set high-intensity |
| 306 | foreground/background colors. |
306 | foreground/background colors. |
| 307 | |
307 | |
| 308 | color0-7 are the low-intensity colors. |
308 | color0-7 are the low-intensity colors. |
| … | |
… | |
| 409 | has been designed yet). |
409 | has been designed yet). |
| 410 | |
410 | |
| 411 | Until then, you might get away with switching fonts at runtime (see "Can |
411 | Until then, you might get away with switching fonts at runtime (see "Can |
| 412 | I switch the fonts at runtime?" later in this document). |
412 | I switch the fonts at runtime?" later in this document). |
| 413 | |
413 | |
|
|
414 | How can I make mplayer display video correctly? |
|
|
415 | We are working on it, in the meantime, as a workaround, use something |
|
|
416 | like: |
|
|
417 | |
|
|
418 | urxvt -b 600 -geometry 20x1 -e sh -c 'mplayer -wid $WINDOWID file...' |
|
|
419 | |
| 414 | Keyboard, Mouse & User Interaction |
420 | Keyboard, Mouse & User Interaction |
| 415 | The new selection selects pieces that are too big, how can I select single words? |
421 | The new selection selects pieces that are too big, how can I select single words? |
| 416 | If you want to select e.g. alphanumeric words, you can use the following |
422 | If you want to select e.g. alphanumeric words, you can use the following |
| 417 | setting: |
423 | setting: |
| 418 | |
424 | |
| … | |
… | |
| 424 | To get a selection that is very similar to the old code, try this |
430 | To get a selection that is very similar to the old code, try this |
| 425 | pattern: |
431 | pattern: |
| 426 | |
432 | |
| 427 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
433 | URxvt.selection.pattern-0: ([^"&'()*,;<=>?@[\\\\]^`{|})]+) |
| 428 | |
434 | |
| 429 | Please also note that the *LeftClick Shift-LeftClik* combination also |
435 | Please also note that the *LeftClick Shift-LeftClick* combination also |
| 430 | selects words like the old code. |
436 | selects words like the old code. |
| 431 | |
437 | |
| 432 | I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
438 | I don't like the new selection/popups/hotkeys/perl, how do I change/disable it? |
| 433 | You can disable the perl extension completely by setting the |
439 | You can disable the perl extension completely by setting the |
| 434 | perl-ext-common resource to the empty string, which also keeps |
440 | perl-ext-common resource to the empty string, which also keeps |
| … | |
… | |
| 501 | Assuming that the physical Backspace key corresponds to the Backspace |
507 | Assuming that the physical Backspace key corresponds to the Backspace |
| 502 | keysym (not likely for Linux ... see the following question) there are |
508 | keysym (not likely for Linux ... see the following question) there are |
| 503 | two standard values that can be used for Backspace: "^H" and "^?". |
509 | two standard values that can be used for Backspace: "^H" and "^?". |
| 504 | |
510 | |
| 505 | Historically, either value is correct, but rxvt-unicode adopts the |
511 | Historically, either value is correct, but rxvt-unicode adopts the |
| 506 | debian policy of using "^?" when unsure, because it's the one only only |
512 | debian policy of using "^?" when unsure, because it's the one and only |
| 507 | correct choice :). |
513 | correct choice :). |
| 508 | |
514 | |
| 509 | Rxvt-unicode tries to inherit the current stty settings and uses the |
515 | Rxvt-unicode tries to inherit the current stty settings and uses the |
| 510 | value of `erase' to guess the value for backspace. If rxvt-unicode |
516 | value of `erase' to guess the value for backspace. If rxvt-unicode |
| 511 | wasn't started from a terminal (say, from a menu or by remote shell), |
517 | wasn't started from a terminal (say, from a menu or by remote shell), |
| … | |
… | |
| 772 | The terminal description used by rxvt-unicode is not as widely available |
778 | The terminal description used by rxvt-unicode is not as widely available |
| 773 | as that for xterm, or even rxvt (for which the same problem often |
779 | as that for xterm, or even rxvt (for which the same problem often |
| 774 | arises). |
780 | arises). |
| 775 | |
781 | |
| 776 | The correct solution for this problem is to install the terminfo, this |
782 | The correct solution for this problem is to install the terminfo, this |
| 777 | can be done like this (with ncurses' infocmp): |
783 | can be done like this (with ncurses' infocmp and works as user and |
|
|
784 | admin): |
| 778 | |
785 | |
| 779 | REMOTE=remotesystem.domain |
786 | REMOTE=remotesystem.domain |
| 780 | infocmp rxvt-unicode | ssh $REMOTE "cat >/tmp/ti && tic /tmp/ti" |
787 | infocmp rxvt-unicode | ssh $REMOTE "mkdir -p .terminfo && cat >/tmp/ti && tic /tmp/ti" |
| 781 | |
788 | |
| 782 | ... or by installing rxvt-unicode normally on the remote system, |
789 | ... or by installing rxvt-unicode normally on the remote system, |
|
|
790 | |
|
|
791 | One some systems you might need to set $TERMINFO to the full path of |
|
|
792 | $HOME/.terminfo for this to work. |
| 783 | |
793 | |
| 784 | If you cannot or do not want to do this, then you can simply set |
794 | If you cannot or do not want to do this, then you can simply set |
| 785 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
795 | "TERM=rxvt" or even "TERM=xterm", and live with the small number of |
| 786 | problems arising, which includes wrong keymapping, less and different |
796 | problems arising, which includes wrong keymapping, less and different |
| 787 | colours and some refresh errors in fullscreen applications. It's a nice |
797 | colours and some refresh errors in fullscreen applications. It's a nice |
| … | |
… | |
| 813 | cases. You can also create a termcap entry by using terminfo's infocmp |
823 | cases. You can also create a termcap entry by using terminfo's infocmp |
| 814 | program like this: |
824 | program like this: |
| 815 | |
825 | |
| 816 | infocmp -C rxvt-unicode |
826 | infocmp -C rxvt-unicode |
| 817 | |
827 | |
| 818 | Or you could use this termcap entry, generated by the command above: |
828 | Or you could use the termcap entry in doc/etc/rxvt-unicode.termcap, |
| 819 | |
829 | generated by the command above. |
| 820 | rxvt-unicode|rxvt-unicode terminal (X Window System):\ |
|
|
| 821 | :am:bw:eo:km:mi:ms:xn:xo:\ |
|
|
| 822 | :co#80:it#8:li#24:lm#0:\ |
|
|
| 823 | :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\ |
|
|
| 824 | :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\ |
|
|
| 825 | :RI=\E[%dC:SF=\E[%dS:SR=\E[%dT:UP=\E[%dA:ae=\E(B:al=\E[L:\ |
|
|
| 826 | :as=\E(0:bl=^G:cd=\E[J:ce=\E[K:cl=\E[H\E[2J:\ |
|
|
| 827 | :cm=\E[%i%d;%dH:cr=^M:cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:\ |
|
|
| 828 | :dl=\E[M:do=^J:ec=\E[%dX:ei=\E[4l:ho=\E[H:\ |
|
|
| 829 | :i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\ |
|
|
| 830 | :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\ |
|
|
| 831 | :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\ |
|
|
| 832 | :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:kD=\E[3~:\ |
|
|
| 833 | :kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=\177:kd=\EOB:ke=\E[?1l\E>:\ |
|
|
| 834 | :kh=\E[7~:kl=\EOD:kr=\EOC:ks=\E[?1h\E=:ku=\EOA:le=^H:\ |
|
|
| 835 | :mb=\E[5m:md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:\ |
|
|
| 836 | :sc=\E7:se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\ |
|
|
| 837 | :te=\E[r\E[?1049l:ti=\E[?1049h:ue=\E[24m:up=\E[A:\ |
|
|
| 838 | :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\ |
|
|
| 839 | :vs=\E[?25h: |
|
|
| 840 | |
830 | |
| 841 | Why does "ls" no longer have coloured output? |
831 | Why does "ls" no longer have coloured output? |
| 842 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
832 | The "ls" in the GNU coreutils unfortunately doesn't use terminfo to |
| 843 | decide whether a terminal has colour, but uses its own configuration |
833 | decide whether a terminal has colour, but uses its own configuration |
| 844 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
834 | file. Needless to say, "rxvt-unicode" is not in its default file (among |
| … | |
… | |
| 876 | If you encounter strange problems like typing an accented character but |
866 | If you encounter strange problems like typing an accented character but |
| 877 | getting two unrelated other characters or similar, or if program output |
867 | getting two unrelated other characters or similar, or if program output |
| 878 | is subtly garbled, then you should check your locale settings. |
868 | is subtly garbled, then you should check your locale settings. |
| 879 | |
869 | |
| 880 | Rxvt-unicode must be started with the same "LC_CTYPE" setting as the |
870 | Rxvt-unicode must be started with the same "LC_CTYPE" setting as the |
| 881 | programs. Often rxvt-unicode is started in the "C" locale, while the |
871 | programs running in it. Often rxvt-unicode is started in the "C" locale, |
| 882 | login script running within the rxvt-unicode window changes the locale |
872 | while the login script running within the rxvt-unicode window changes |
| 883 | to something else, e.g. "en_GB.UTF-8". Needless to say, this is not |
873 | the locale to something else, e.g. "en_GB.UTF-8". Needless to say, this |
| 884 | going to work. |
874 | is not going to work, and is the most common cause for problems. |
| 885 | |
875 | |
| 886 | The best thing is to fix your startup environment, as you will likely |
876 | The best thing is to fix your startup environment, as you will likely |
| 887 | run into other problems. If nothing works you can try this in your |
877 | run into other problems. If nothing works you can try this in your |
| 888 | .profile. |
878 | .profile. |
| 889 | |
879 | |
| 890 | printf '\33]701;%s\007' "$LC_CTYPE" |
880 | printf '\33]701;%s\007' "$LC_CTYPE" # $LANG or $LC_ALL are worth a try, too |
| 891 | |
881 | |
| 892 | If this doesn't work, then maybe you use a "LC_CTYPE" specification not |
882 | If this doesn't work, then maybe you use a "LC_CTYPE" specification not |
| 893 | supported on your systems. Some systems have a "locale" command which |
883 | supported on your systems. Some systems have a "locale" command which |
| 894 | displays this (also, "perl -e0" can be used to check locale settings, as |
884 | displays this (also, "perl -e0" can be used to check locale settings, as |
| 895 | it will complain loudly if it cannot set the locale). If it displays |
885 | it will complain loudly if it cannot set the locale). If it displays |
| … | |
… | |
| 1055 | This forking is done as the very first within main(), which is very |
1045 | This forking is done as the very first within main(), which is very |
| 1056 | early and reduces possible bugs to initialisation code run before |
1046 | early and reduces possible bugs to initialisation code run before |
| 1057 | main(), or things like the dynamic loader of your system, which should |
1047 | main(), or things like the dynamic loader of your system, which should |
| 1058 | result in very little risk. |
1048 | result in very little risk. |
| 1059 | |
1049 | |
| 1060 | On Solaris 9, many line-drawing characters are too wide. |
|
|
| 1061 | Seems to be a known bug, read |
|
|
| 1062 | <http://nixdoc.net/files/forum/about34198.html>. Some people use the |
|
|
| 1063 | following ugly workaround to get non-double-wide-characters working: |
|
|
| 1064 | |
|
|
| 1065 | #define wcwidth(x) wcwidth(x) > 1 ? 1 : wcwidth(x) |
|
|
| 1066 | |
|
|
| 1067 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
1050 | I am on FreeBSD and rxvt-unicode does not seem to work at all. |
| 1068 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
1051 | Rxvt-unicode requires the symbol "__STDC_ISO_10646__" to be defined in |
| 1069 | your compile environment, or an implementation that implements it, |
1052 | your compile environment, or an implementation that implements it, |
| 1070 | whether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
1053 | whether it defines the symbol or not. "__STDC_ISO_10646__" requires that |
| 1071 | wchar_t is represented as unicode. |
1054 | wchar_t is represented as unicode. |
| … | |
… | |
| 1073 | As you might have guessed, FreeBSD does neither define this symbol nor |
1056 | As you might have guessed, FreeBSD does neither define this symbol nor |
| 1074 | does it support it. Instead, it uses its own internal representation of |
1057 | does it support it. Instead, it uses its own internal representation of |
| 1075 | wchar_t. This is, of course, completely fine with respect to standards. |
1058 | wchar_t. This is, of course, completely fine with respect to standards. |
| 1076 | |
1059 | |
| 1077 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
1060 | However, that means rxvt-unicode only works in "POSIX", "ISO-8859-1" and |
| 1078 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t. |
1061 | "UTF-8" locales under FreeBSD (which all use Unicode as wchar_t). |
| 1079 | |
1062 | |
| 1080 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
1063 | "__STDC_ISO_10646__" is the only sane way to support multi-language apps |
| 1081 | in an OS, as using a locale-dependent (and non-standardized) |
1064 | in an OS, as using a locale-dependent (and non-standardized) |
| 1082 | representation of wchar_t makes it impossible to convert between wchar_t |
1065 | representation of wchar_t makes it impossible to convert between wchar_t |
| 1083 | (as used by X11 and your applications) and any other encoding without |
1066 | (as used by X11 and your applications) and any other encoding without |
| … | |
… | |
| 1093 | |
1076 | |
| 1094 | The rxvt-unicode author insists that the right way to fix this is in the |
1077 | The rxvt-unicode author insists that the right way to fix this is in the |
| 1095 | system libraries once and for all, instead of forcing every app to carry |
1078 | system libraries once and for all, instead of forcing every app to carry |
| 1096 | complete replacements for them :) |
1079 | complete replacements for them :) |
| 1097 | |
1080 | |
| 1098 | I use Solaris 9 and it doesn't compile/work/etc. |
|
|
| 1099 | Try the diff in doc/solaris9.patch as a base. It fixes the worst |
|
|
| 1100 | problems with "wcwidth" and a compile problem. |
|
|
| 1101 | |
|
|
| 1102 | How can I use rxvt-unicode under cygwin? |
1081 | How can I use rxvt-unicode under cygwin? |
| 1103 | rxvt-unicode should compile and run out of the box on cygwin, using the |
1082 | rxvt-unicode should compile and run out of the box on cygwin, using the |
| 1104 | X11 libraries that come with cygwin. libW11 emulation is no longer |
1083 | X11 libraries that come with cygwin. libW11 emulation is no longer |
| 1105 | supported (and makes no sense, either, as it only supported a single |
1084 | supported (and makes no sense, either, as it only supported a single |
| 1106 | font). I recommend starting the X-server in "-multiwindow" or |
1085 | font). I recommend starting the X-server in "-multiwindow" or |
| … | |
… | |
| 1109 | |
1088 | |
| 1110 | At the time of this writing, cygwin didn't seem to support any |
1089 | At the time of this writing, cygwin didn't seem to support any |
| 1111 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
1090 | multi-byte encodings (you might try "LC_CTYPE=C-UTF-8"), so you are |
| 1112 | likely limited to 8-bit encodings. |
1091 | likely limited to 8-bit encodings. |
| 1113 | |
1092 | |
|
|
1093 | Character widths are not correct. |
|
|
1094 | urxvt uses the system wcwidth function to know the information about the |
|
|
1095 | width of characters, so on systems with incorrect locale data you will |
|
|
1096 | likely get bad results. Two notorious examples are Solaris 9, where |
|
|
1097 | single-width characters like U+2514 are reported as double-width, and |
|
|
1098 | Darwin 8, where combining chars are reported having width 1. |
|
|
1099 | |
|
|
1100 | The solution is to upgrade your system or switch to a better one. A |
|
|
1101 | possibly working workaround is to use a wcwidth implementation like |
|
|
1102 | |
|
|
1103 | http://www.cl.cam.ac.uk/~mgk25/ucs/wcwidth.c |
|
|
1104 | |
