Benno Schulenberg wrote:
> On what terminal are you doing this? To what encoding is the
> terminal set?
Mainly xterm (version 225, at least in one case). And I have the utf8
option on. Does this set the encoding to the proper value, or do I need
more?
But also, I have tried this in the simple
Giraud wrote:
> Benno Schulenberg wrote:
> > 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
Giraud wrote:
> Hmm, interesting.
Please don't top-post.
> Yes, I do have PROMPT_COMMAND set, it appears. However, if I
> unset it (and even also 'export PS1="foo "' to set PS1 to a
> simple string), the problem remains.
Then look at a new typescript, and see if that strange 1034h is
still th
Bob Proulx wrote:
>
>
>>Internally bash will use the libc isatty(3) routine to determine if
>>the input/output files are tty devices. In the shell these are
>>available in the 'test' operator as the '-t' file operator.
>
>> $ test -t 0 && echo input is a tty
>> $ test -t 1 && echo output is
