Re: Mac OSX and Text Editors
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. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
RE: Mac OSX and Text Editors
So, Unix endings utf-8 encoding is best? That's what the built in editor spits out? -Original Message- From: Mats Bengtsson [mailto:[EMAIL PROTECTED] Sent: Friday, August 12, 2005 6:52 AM To: Stephan Moss Cc: lilypond-user@gnu.org Subject: Re: Mac OSX and Text Editors 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. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mac OSX and Text Editors
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 copypasting 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 ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Mac OSX and Text Editors
I have used TextWrangler with Lilypond on OS X Panther for some time. Stephan, I think that Mats is right that TextWrangler is probably using Mac line endings in your files. I set Default Line Breaks to UNIX when I installed Text Wrangler and use UTF-8 encoding and have not had any problems with Lilypond files. Go to Preferences Text Files: Saving to set up the UNIX line endings and default encoding. Kris Shaffer On Fri, 12 Aug 2005 09:51:56 -0400, Mats Bengtsson [EMAIL PROTECTED] 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. /Mats ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
