[Insight-developers] Why does the KWStyle hook not let me commit, and why can't I turn the **&@#$ing thing off?

[kent williams]

Yeah that was the problem.

Learning to use git reminds me of when, at a former job, a womand from
Dassault System said that we were "joining the society" of Dassault
Systemes.  What she was unable to properly formulate in English was
something like  "becoming users of," but her phrase always struck me as
unintentionally accurate.

So we're all trying to join the Git Society. Where familiar commands from
other version control systems mean something just different enough to keep
you scratching your head for hours. Where there are dozens of secret
handshakes and arcane rituals to learn.


On 10/13/10 3:14 PM, "Matthew McCormick (thewtex)" <matt at mmmccormick.com>
wrote:

> Hi Kent,
> 
>> 
>> This is killing me -- even if I fix the files it objects to, I still get the
>> same pre-commit hook failure! Furthermore, in Emacs I can see the trailing
>> white spaces it's finding and they no longer exist in the files I'm trying
>> to commit!
>> 
> 
> Are you possibly forgetting to add the new changes to the files after
> they have been changed?  This is done with
> 
>   git add <file name>
> 
> or
> 
>   git commit -a
> 
> to automatically add all changes to files already tracked by Git.
> 
>> And it's complaining about trailing white space even though I've set the
>> KWStyle hook to false!
>> 
> 
> KWStyle will catch trailing whitespaces on all C++ files, but an
> additional pre-commit check occurs that checks for trailing whitespace
> on all text files.  It is not disabled by turning of the KWStyle hook.
> 
> Matt