On Wed, 2009-09-23 at 08:02 -0400, Robert Moskowitz wrote:
> Mogens Kjaer wrote:
> > On 09/23/2009 01:35 PM, Robert Moskowitz wrote:
> >> '/test1: line 1: syntax error near unexpected token `{
> >
> > Starting the script with
> >
> > #!/bin/bash
> >
> > might be a good idea.
>
> I used vi to insert this line and I get:
>
> ./test1
> -bash: ./test1: /bin/bash^M: bad interpreter: No such file or directory
>
> I don't see that control M in vi or gedit...
----
control characters are invisible unless the software has a provision to
make invisible characters visible (something like OOo can do).
adding a (^M) Control-M to each line ending is something a Macintosh
would normally do. When in doubt, you can always use 'od' command to
tell you exactly what is in a file, byte by byte.
You can 'fix' the line endings in any file using 'dos2unix' command.
Type 'dos2unix --help' to get the syntax.
Craig
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
