Dear Ingao, Thank you!
I am very interested in implementing UTF-8 input into csh(1). Would you agree that a good startig point would be to look at how your implemented UTF-8 support in ksh(1)? I tried to find your commit on GitHub, which implement UTF-8 support in ksh(1). I could not find it. Was the change commited to a file in src/bin/ksh/? Which file was it? Do you remember the approximate time of the implementation? Such information will be helpful for me to find the implementation and to study it. Sincerely, Xianwen On Sun, Feb 11, 2018 at 3:54 AM, Ingo Schwarze <[email protected]<mailto:[email protected]>> wrote: Hi Xianwen Chen, Xianwen Chen wrote on Sat, Feb 10, 2018 at 10:41:19PM +0000: > I use C shell, csh. When I change the shell to Bourne shell, sh, On OpenBSD, sh(1) is not a Bourne shell, but the same binary as ksh(1), a Korn shell, which is reasonably POSIX-compatible with various extensions. You can see that with ls -i. > I am able to type [non-ASCII characters]. > > Could you check whether you can reproduce my problem by > entering csh and typing [non-ASCII characters]. Some time ago, i hacked into ksh(1) and added minimal UTF-8 support to both emacs and vi input mode, with very little disruption to the existing code base. I didn't bother to do anything similar for csh(1); whatever Theo may say, it is not a very modern shell IMHO... ;) I did not test, but i would be very surprised if csh(1) were able to work sensibly with UTF-8 input. Of course, i wouldn't object to similar work being done in csh(1). > I think I would like to file a bug report. Please don't, it is already well-known that no UTF-8 support was added to OpenBSD csh(1). Yours, Ingo
