# RE: t0025 weird behaviour on NonStop ksh/bash

1 messages from 2015-05-09 to 2015-05-09. Participants: Randall S. Becker.
Thread: https://gitlist.dev/t/39282

## Randall S. Becker, 2015-05-09 02:46

Subject: RE: t0025 weird behaviour on NonStop ksh/bash
Message-ID: <004d01d08a02$627bc2b0$27734810$@nexbridge.com>
URL: https://gitlist.dev/e/004d01d08a02%24627bc2b0%2427734810%24%40nexbridge.com

```
On May 8, 2015 7:17 PM , I wrote in my haste:
> Ok, I'm sure that this is not a git problem, but there is an assumption
about
> echo behaviour in t0025 that may not be correct. When executed from a
shell
> function on the HP NonStop platform under ksh and bash, the LFonly file
> annoyingly contains cr-lf not just lf. This causes sub-test 4 to fail.
Weirdly, this
> does not happen from an interactive shell. My proposed solution, in
t0025-crlf-
> auto.sh, to this is to make it explicit that bad behaviour on the part of
echo
> should be dealt with severely, as in:
> 
>         for w in Hello world how are you; do echo $w; done | tr -d '\r'
>LFonly
> 
> instead of
> 
>         for w in Hello world how are you; do echo $w; done >LFonly
> 
> which is a no-op on platforms that behave themselves in this situation. Is
this
> the proper approach?

Digging deeper, this appears to be is Yet Another Platform Problem. There
are more '\r' characters sneaking about beyond just echo. I am taking it up
with other developers to see whether we can track down where the offending
'\r' characters are coming from. They do not appear to be from git or its
tests at this stage

Cheers,
Randall

-- Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)/NonStop(211288444200000000)
-- In my real life, I talk too much.

.

```