Shell Script : isolate CR/LF from a variable

[DGRFL]

Hello,
I am using Microsoft Services for UNIX to port Korn shell scripts towards a NT environment.
In order to evaluate an environment variable passed on the command line, I wrote:
hlp=$(echo "$"$1)
result=`eval echo $hlp`
On OSF and HP/UX, the result variable now contains the value of the environment var. whose name is in $1.
On NT, this result variable has a carriage return appended to it.
I can remove this by typing
result2=${result:0:22}
if I know the significant length, but normally I do not know the length.
So how can I check whether there is a CR or LF present in an environment variable, and how can I remove it in a simple way ?

Regards,

Luc

 

[MikeLacey]

There is, I remember, some pattern matching stuff in ksh that uses the same type of construct, ${result:0:22}, as you're already using. Have a look in the ksh docu for pattern matching as I can't remember how to do it.
Mike
michael.j.lacey@ntlworld.com

 

[DGRFL]

Mike,

There is a construct ${parameter%%pattern} that deletes the longest possible suffix that matches the pattern, but how can I indicate CR or LF inside this pattern ?

It seems that ${parameter%%[\015\012]} does not work, and ${parameter%%['\r''\n']} neither.

Has anybody a suggestion ?

Luc
luc.degraef@cosmosworldwide.com

 

[MikeLacey]

Luc,

This is probably a stupid comment, but shouldn't that be:
[tt]\10\13[/tt]
Or am I just getting my bases mixed up?
Mike
michael.j.lacey@ntlworld.com

 

[DGRFL]

Hello,

In the meanwhile I did the following investigation :
the above problem arose in a shell script; however when I execute these commands from the command line the carriage return or line feed is NOT appended.

So it had to be a problem with the Shell script interpreter.

I downloaded the MKS toolkit demo software (an older version of which is being used by the Microsoft Services for UNIX), and in this MKS toolkit the problem does not occur.
So it is a bug in the Microsoft attempt to support UNIX commands. (Did I hear someone laughing ?)

Concerning your advice, I tested it but it is not working.


Thanks for the suggestions, but it all ended up in a weird way.
Luc

 

[MikeLacey]

<g>
Mike
michael.j.lacey@ntlworld.com