Re: (hypothetical) Availability of LilyPond engravers

[Urs Liska]

Am 17.04.2015 um 21:05 schrieb Noeck:
> > note->articulation->dynamic->slur->beam->tie
>
> note->articulation->beam->slur->dynamic->tie please
>
> ;) just kidding – but coding style has to come with coding-style discussions

Yes, of course.
And we decided not to be too strict about it for the project. But by now 
I think I'd prefer a really uniform style - it's really significantly 
easier to quickly understand others' code.

The best and least "intrusive" way would be a script that formats the 
code according to such agreed-upon guidelines (just as I suggest to 
reindent a file automatically before committing to Git). I assume that 
having such a script would gently push people in the right direction - 
most people would work towards the state where the script wouldn't 
change the code anymore ;-)

I think when python-ly is able to fully generate code it should be more 
or less trivial to write such a linter tool (simply read the file and 
write it back again), and that should then be configurable regarding the 
coding style.

Urs

> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user


--
Urs Liska
www.openlilylib.org