On Wed, Oct 21, 2009 at 08:49:33PM +0200, Martin Tarenskeen wrote: > > Be careful: This version overwrites the original file without making a > backup ( infile.ly~ )first. Maybe I should add that in the next version.
Yes, that would be good. What about a version that read from standard input and wrote to standard input? I'm thinking about the documentation -- we could automatically format all lilypond input syntax. The documentation _mostly_ follows our semi-defined style already, but I'm sure that there's a handful of places where it doesn't. It be nice if we could auto-format all 2143 portions of lilypond input in the docs. :) >> Yes, scheme code should be formatted in the scheme way. > I know very very little about scheme. Some example lilypond files with > much scheme code might help. The snippets->advanced scheme might help here, but I'm not certain if they're all formatted correctly. The definitive guide[1] would be "whatever emacs does" -- if you can install emacs and try its formatting on a few scheme files, you could satisfy all your questions about this. :) [1] I dislike installing 30 megs of programs just to have good indentation, which is why I consider this python indentation script such a great project. >> One more item to consider: whitespace at the ends of lines should >> be stripped. > > I thought I already did that ? I'll look in to it. Sorry, I still haven't looked at the program; I'm just commenting on the discussion. If you already do this, great! (BTW, this end-of-line whitespace-removal is a *huge* issue for the docs and our code. When the lilypond indenting script is done, it would be fantastic if you could write a similar program to help the documentation writers and programmers. :) Cheers, - Graham _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user