Benno Schulenberg wrote:
> Then look at a new typescript, and see if that strange 1034h is
> still there. If yes, a simple 'set | grep 1034' might find the
> variable that contains it.
Nothing found doing this grep... As for doing a script, the "1034h" is
indeed missing in the plain shell you suggest below, but the problem
remains (see below).
>> How best to debug this? tcsh and sh do not exhibit the problem,
>
> Aha. Then try 'env -i bash --noprofile --norc'. If that instance
> of the shell doesn't exhibit the problem, then you know for sure
> it's something in the environment.
Initially, after entering this plain shell, the problem does not exist.
However, a simple "export LANG='en_US.UTF-8'" resumes the problem
faithfully.
> If the problem remains even with an empty environment, try using an
> empty ~/.inputrc or /etc/inputrc.
These files do not exist on my system, so I tried without one and with
an empty one. No change (problem still happens).
Is there somewhere in the bash code I can put some debugging statements
(or some way of logging) that you can suggest? Since I'm running
Gentoo, altering the source to test is fairly simple.
-Joe
_______________________________________________
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
