lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mac OSX and Text Editors


From: Kris Shaffer
Subject: Re: Mac OSX and Text Editors
Date: Fri, 12 Aug 2005 15:56:18 -0400
User-agent: Opera M2/8.01 (MacPPC, build 2092)

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 <address@hidden> 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
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-user






reply via email to

[Prev in Thread] Current Thread [Next in Thread]