On 02-22-2012 10:06, Barry Margolin wrote:
> Richard Kettlewell<
r...@greenend.org.uk> wrote:
>> Wes Groleau<Grolea...@FreeShell.org> writes:
>>> iMac:~ wgroleau$ time UniGen-update
>>> -bash: /Users/wgroleau/bin/UniGen-update: /bin/sh: bad interpreter:
>>> Operation not permitted
>>>
>>> Just a brief revisiting of this. It is indeed SORT OF what someone
>>> suggested, a non-standard (from the Unix point-of-view) line break.
>>> It happens every time I edit the script, and it is always fixed by
>>> perl -p -i -e 's:\r:\n:g;' bin/UniGen-update
>>>
>>> But the weird thing is that if I examine the file (before fixing) with
>>> either vim or 'od -xc' I _cannot_ find a single instance or \r or its
>>> hex value!
>>
>> Try
>> perl -p -i -e '' bin/UniGen-update
>> instead next time. I suspect that the change is not in the contents of
>> the file (if there aren't any CRs then your perl one-liner won't remove
>> them) but is down to the fact of rewriting it.
>>
>> What are you using to edit the file?