Am 13.12.2012 um 18:19 schrieb Dave Love: > Ian Kaufman <[email protected]> writes: > >> Hi Jan, >> >> Have you made any modifications to the script recently? It looks like >> something is inserting Windows carriage returns which show up as "\n\r" in >> UNIX/Linux, which subsequently newlines the "\n", leaving a "\r" on the >> following empty line. > > Yes, but from the posted example, it looks as if the lines are getting > broken. The script needs checking for non-printing characters anyhow. > > [I detect CRLF endings with a JSV, but those usually manifest as failing > to exec the shell from the #! line.]
Hehe - it would be good to see the original line, as $'\r' is a special bash syntax to include a CR at this location: "Words of the form $'string' are treated specially. ..." I assume soemthing before this actual string doesn't expand properly and hence this one is treated as command. -- Reuti > -- > Community Grid Engine: http://arc.liv.ac.uk/SGE/ > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
