Re: Bugfix for issue 1630 (issue4490045)

[Carl Sorensen]

On 6/14/11 4:19 PM, "Janek Warchoł" <address@hidden>
wrote:

> 2011/6/14 <address@hidden>
>> and Janek: you are probably quite
>> confused (and maybe disheartened) by this indentation problem, because
>> the current indentation policy used in lilypond is completely braindead
>> and ridiculous for any editor other than GNU/emacs.
> 
> I'm disheartened by the idea of reverting tab->space conversion,
> because CG 10.3.2 says "All indentation should be done with spaces".

Strictly speaking, CG 10.3.2 applies to changes in .scm and .ly files (see
section 10.3). 

The .ly file proposal is fully supported, AFAIK.  The .scm proposal is
moderately supported.

But the current policy is "do what's in the current file."

I hope we can get to "don't use tabs", but we haven't got there fully.

> 
>> I have just postponed the "lessons from 2.14" GOP policy question for
>> another week so that we can start dealing with "C++ indentation" on Wed
>> 22 June.  Unfortunately the discussion would not be over until 06 July,
>> but that's the best I can do (unless I postpone the "mentors"
>> discussion, but I think that one's even more pressing than indentation).
> 
> No, don't postpone mentors!
> 
>> If you want the patch pushed sooner, then unfortunately you need to use
>> the exact (braindead) indentation we currently have for C++ code.
>> Alternately, wait until we have a sensible policy
> 
> I think we are inconsistent: sometimes we stick to the rules very
> strictly, and sometimes not at all.

I think that the C++ rules are quite strictly enforced, although I won't
promise that all existing files follow them.  C++ standards are in CG 10.5;
indentation standards are 10.5.3.

Previous discussions on tabs v. spaces include the following:

http://thread.gmane.org/gmane.comp.gnu.lilypond.devel/22691
http://lists.gnu.org/archive/html/lilypond-devel/2009-04/msg00076.html

It's part of GLISS, I think.

Carl