2011/9/21 Graham Percival <[email protected]>: > On Wed, Sep 21, 2011 at 08:20:39AM +0200, Jan Nieuwenhuizen wrote: >> David Kastrup writes: >> >> > Personally, I'd prefer it if we focused on solving rather than creating >> > real problems. >> >> +1 > > Automatic indentation *does* solve real problems. Take a look at > this: > http://codereview.appspot.com/4490045/ > and then compare with the final commit: > 258dd9a854b627b533ab709a137b23c539857838 > > Drafts 3-9 were indentation. Note that discussion involved me, > Carl, Janek, Janek, and Benko -- that's a lot of lilypond > development experience. And yet the end result was still 5 weeks > to get a ~50 line patch from a new contributor contributor. > > Gee, I wonder why we haven't seen any more patches from that new > contributor? > </sarcasm> > > Now admittedly I haven't seen anything like that for scheme > indentation, but I never want to. If a simple script can lower > the chances of driving away new contributors, let's go for it.
Yes. There are two acceptable choices about indentation: don't care about it at all, or have an auto-indenting script and therefore don't have to worry about it at all. Issue 1630 was a nightmare. cheers, Janek _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
