Bash has some problems with wide chars. Readline functions of bash maybe cause this problem. If user wants to edit a lien with non-wide chars with wide-char's then, line turn into garbage and wide-chars written over them. In tr_TR.UTF-8 locale problem can demonstrate like this; $ echo "abc" abc < up arrow > $ echo "abc"| <left arrow twice> $ echo "ab|c" < enter UTF-8 char like [
Bash has some problems with wide chars. Readline functions of bash maybe cause this problem. If user wants to edit a lien with non-wide chars with wide-char's then, line turn into garbage and wide-chars written over them. In tr_TR.UTF-8 locale problem can demonstrate like this; $ echo "abc" abc < up arrow > $ echo "abc"| <left arrow twice> $ echo "ab|c" < enter UTF-8 char like [ ç,ö,?,?,ü in Turkish locale ] >
Created attachment 42907 [details, diff] bash-3.0-utf-8.patch I found another in bash history file. The bug in http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=83331 also exists in bash 3.x series. So i convert this patch for bash 3.x series
This problem description is same as in bash's offical patch "Bash30-011". The patch cannot solve problem for at least tr_TR.UTF-8 locale.
Created attachment 43427 [details, diff] bashrc.patch This patch solves the problem ( with utf-8 patch ). Problem is colors of prompt :). I'dont know why but if i apply this patch, wide-chars can be used without anyproblem. Otherwise there all overwritten each other.
Created attachment 43522 [details, diff] bash-3.0-prompt.patch This patch also solves the prompt problem
it's a utf-8 problem so i assigned it to utf-8 rather than coreutils team [ hope im not doing anything wrong ]. https://svn.uludag.org.tr/paketler/trunk/app-shells/bash/ has the working ebuild and patches [ some from debian ]
Fetching the patches from your subversion repo is not easy... wget just returns an empty file. Could you please attach the patches and updated ebuild here?
Created attachment 48318 [details, diff] bash-3.0-invisible.patch
Created attachment 48319 [details, diff] bash-3.0-update-multibyte-ifs.patch
Created attachment 48320 [details, diff] bash-3.0-random.patch
Created attachment 48321 [details, diff] bash-3.0-privmode.patch
Created attachment 48322 [details, diff] bash-3.0-command-not-found.patch
Created attachment 48323 [details, diff] bash-3.0-histtimeformat.patch
Created attachment 48324 [details, diff] bash-3.0-rl-del-backspace-policy.patch
Created attachment 48325 [details, diff] bash-3.0-rl-header.patch
Created attachment 48326 [details, diff] bash-3.0-rl-setenv.patch
Created attachment 48328 [details, diff] bash-3.0-r7.ebuild.diff Modifed ebuild with attached patches...
have you sent these patches upstream to the bash maintainer ?
No :), because some of them are from debian, some of them from Suse. So i think they send these to bash. The only part i wrote can be seen in bash-3.0-r7.ebuild.diff. Also, they are not tested well in ISO modes [ we only use UTF-8 ], so im not sure they are ok or not.
any progress on this? bash-3.0-r8 has still some wired behaviour with utf-8...
Nope, New offical patches broke our utf-8 support so we throw away the new offical patches until we solve the issue. Pardus Linux still use attached ebuild and patches for utf-8 compatibility. Without them console is useless. Also ı've got no response from Bash Developers. So still i dont know what are they think and what cause these problems? :(
so let's ask again ;) any progress? what can we currently do?
I'm very busy with other things sorry :), let me do this; in one week, i'll grap newest bash with offical patches and merge with these. And if i can solve the issue will report here. After that of course if u accept, you report to bash-developers so they may answer :))
Heh, i'll write a book titled as "Why i hate bash?" :) I found some time for bash today, and also want to update this for our distro. As a result i merged debian's, gentoo's and suse's patches with mine and seems there is no utf-8 problem at all. Also some other potential problem solved ( i hope ). You can grap it from ( i don't want to attach all patches to bugzilla, after your test if u agree i'll attach ); $ svn co https://svn.uludag.org.tr/paketler/trunk/app-shells/bash/
Created attachment 59114 [details, diff] bash-3.0-r11.ebuild.patch The latest ebuild without patches just show the differences between this and offical gentoo one...
*** Bug 96012 has been marked as a duplicate of this bug. ***
talked to upstream and they pretty much have all the relevant fixes here so the next version of bash should be OK ... the question is what to do with our current 3.0
(In reply to comment #26) > talked to upstream and they pretty much have all the relevant fixes here so the > next version of bash should be OK ... Good news :) > the question is what to do with our current 3.0 I sync latest bash in portage [r12] with these patches. The only differences is SUSE's utf-8 patch removed {because there is a problem with this patch} and mine added [ http://bugs.gentoo.org/attachment.cgi?id=42907&action=view ], attached tarball has all patches and synced ebuild. After you test this tarball, if u accept, i suggest use this in current situation.
Created attachment 63407 [details] bash.tar.gz tarball has all patches and modified ebuild...
*** Bug 108936 has been marked as a duplicate of this bug. ***
ok, i added the two patches mentioned in Bug 108936 only when USE=unicode since they are clearly not the correct fix, but they do fix the bug for unicode systems this is all in bash-3.0-r13
