Re: Adapt fixcc.py to use Astyle and/or emacs (issue4662074)

[Jan Nieuwenhuizen]

Graham Percival writes:

> I was interpreting "GNU code" to mean "code which strictly follows the
> GNU guidelines".

I do not see the difference: we try to do that, of course.

> LilyPond code has not done this for years

Then that's probably largely my fault.  Sorry.  So somehow we
unconsciously arrived at some status quo, but how can that be
taken for a guideline or policy?

When Han-Wen and I wrote most code [using Emacs] indentation was fine
implicitly.  All other code and patches went through our hands and so
they were fine too.

When I did not have the time to maintain that and to fix other
sloppiness that Emacs' cc-mode does not fix, I wrote fixcc and ran that
once in a while.

When I stopped doing that, I failed to communicate this procedure,
possibly I assumed this was known (I even seem to remember I had to
point to the existance of this script although it is in our source
tree), and I assumed that people knew we are a GNU project (it's on our
front page).

Jan

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl