kdelibs coding style

[Adam Treat]

On Thursday 20 July 2006 3:53 pm, Allen Winter wrote:
> On Thursday 20 July 2006 15:46, Ingo Klöcker wrote:
> > On Thursday 20 July 2006 21:23, Charles Samuels wrote:
> > > Aaron J. Seigo wrote, on Thursday 2006 July 20 12:20 pm:
> > > > please no adjustments. otherwise we'll discuss this till the cows
> > > > come home as people try and adjust this or that citing past changes
> > > > as precedent. =)
> > >
> > > I'm demanding that adjustment. And many others will agree with me.
> > > Sorry.
> >
> > Just for the record, I disagree with you, Charles. And if you look at
> > the KDE PIM coding style you'll see that most of the KDE PIM developers
> > (with the notable exception of David obviously) disagree with you as
> > well.
> >
> > FWIW, I'd love to have a space after an opening and before a closing
> > parenthesis but I'm okay with having no spaces in kdelibs code. It
> > won't kill me.
>
> Which brings up an interesting point.  The indent is 4 spaces in kdelibs.
> The indent is 2 spaces in kdepimlibs.  I'm sure there are other differences
> between the two coding styles.
>
> How does someone keep their sanity when switching between the two styles.
> Not that I'm a big kdelibs guy, but some folks contribute to both modules
> on a regular basis.
>
> Is there a way for me to tell the kde-emacs lisp to automagically switch
> between the two styles depending on which module I'm editing at the time?

Interestingly enough, I just implemented a feature in kdevelop to allow 
defining astyle settings per project.... 

Cheers,
Adam