[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Mac OSX and Text Editors
From: |
Erik Sandberg |
Subject: |
Re: Mac OSX and Text Editors |
Date: |
Fri, 12 Aug 2005 18:32:20 +0200 |
User-agent: |
KMail/1.8.1 |
On Friday 12 August 2005 15.51, Mats Bengtsson wrote:
> Stephan Moss wrote:
> > When Lilypond reads the .ly file, what is it looking for in terms of
> > format (line endings, etc)?
>
> Line endings are treated like any other white space (spaces and tabs),
> so you can write your input on a single line if you like.
>
> > I took a file that worked from the built in editor to Text Wrangler and
> > then back again and it generated lots of errors (Unexpected #end, if I
> > remember right). I wound up re-entering it in the built in editor. I'm
> > assuming that Text Wrangler (from the people who make Bbedit) mangled
> > the file in such a way that the parser didn't like it anymore.
>
> My guess is that it didn't output a plain text file but added some
> extra control characters somewhere. An alternative is that it didn't
> use UNIX style line endings but the old-style Mac line endings or
> used the wrong character encoding. I don't know anything about this
> particular editor, but usually it's possible to specify what format
> the file is saved in.
I have experienced the same error message after copy&pasting from messages in
kmail. Due to a kmail bug, some illegal characters were sometimes inserted in
the beginning of lines. In my case, I could spot which the invalid characters
were, by viewing it in less.
Erik