On Wed, Jun 22, 2011 at 12:54:15AM +0000, Keith OHara wrote:
> Graham Percival <graham <at> percival-music.ca> writes:
>
> > My preference is just to say
> > "let’s just use fixcc.py strictly".
>
> Even those of us who fear emacs could probably run that script on changed .cc
> .hh files before each commit.
Note that even people who use emacs will need to run that script
before each commit -- it contains tons of rules like:
('([\w\(\)\]])([ \t]*)(\.|->)([ \t]*)([\w\(\)])',
'\\1\\3\\5'),
('(\w+::\w+|[A-Z]\w*) < ((\w+::\w+|[A-Z]\w*)<[A-Z]\w*>) >',
'\\1<\\2 >'),
which must be applied after emacs has done its formatting.
We may even want to add a git hook to call this script for commits
or pushes.
> In any case, we will need to start using git blame -w (ignore whitespace)
> to research the history of the code.
Excellent, I didn't know about that git option! I've added it to
the proposal page.
Cheers,
- Graham
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
