Consistent code presentation

[cdlm]

Have we decided on the amount of indentation in listings? I can update chapter while I read/edit them, but that's going to be a huge patch. The thing that I find most disturbing is that some listings do not align with the previous paragraph, because the code is indented inside the pillar markup. Now that there is a line at the left margin, it makes it even more obvious.

Same for result arrows, some chapters use -->, some use ->

[Ducasse]

On 31 Jan 2016, at 04:01, Damien Pollet notifications@github.com wrote:

Have we decided on the amount of indentation in listings? I can update chapter while I read/edit them, but that's going to be a huge patch. The thing that I find most disturbing is that some listings do not align with the previous paragraph, because the code is indented inside the pillar markup. Now that there is a line at the left margin, it makes it even more obvious.

Same for result arrows, some chapters use -->, some use ->

for —> and ->
I would always use

on the following line
I found the —> substitution annoying because when we change lib we may not have if.

Damien I would like to have >> as >> and not > >

—
Reply to this email directly or view it on GitHub.

[DamienCassou]

Code should start at column 0. I propose we indent with 3 spaces, that what we did for the mooc.

[cdlm]

Ok then my commit above is incorrect, it uses 2 spaces.

[DamienCassou]

I'm ok with 2 spaces too. Can you please fix your PR?

[DamienCassou]

Ok, I did it for the whole book.