When one compiles a file on it's own, no indents are present, which is the intent (not indent, hehe), as the book has several small paragraph, making indents look a bad, which are for some reason present when the entire book gets compiled.

Make the project compilable with CMake build scripts.

• cmake use latex helper

There is no good reason to compile cpp_book.tex by first having a program generating it from the other lectures. This should be made with includes, or some other similar technique.

Although, there are some issues with this as well.

1. There is a good chance, that going this way would make compiling the lectures separately harder. But even then, it should be possible. This point also raises the question whether there is a real need for a PDF for each lecture. If there really isn't, maybe another structure of separate files should work better (e.g. not 01gy_cpp.tex and so on, but rather templates.tex etc)
2. lstlistings, the package used to display codes obviously cant know all existing type names (this is important for syntax highlighting). For this reason, collecting all custom types declared in the book is easier with a program. However, since the majority, if not all the type names are already collected and added to the first lecture's preamble, it would be simpler that when someone makes a new code snippet with a new type name, to just add it to the preamble manually.

Fixing this may require serious work, and should be delayed when most other things are said to be good to go.

Why don't we format assembly code in Intel style?

To generate only assembly in Intel style:

>g++     -S -masm=intel mycpp.cpp
>clang++ -S -masm=intel mycpp.cpp

Results: mycpp.s

int pi = 3, 14;

This code snippet, and some of the text around it is incorrect, as it doesn't compile.

This has to be done in a portable way, as I'm mainly using windows for writing.

Create a travis build for this repo.
And embedd the badge into the README.md file.

YouTube short example with Node JS
Example latex travis build
How to embed the badge in markdown

Now that the old style c++ lectures and exercises are becoming the days of old, we'd be better of having a file for each section, and restructure the book, or, even better, make a new one, which is kinda difficult with the current, arbitrary division points.

Practice is the way to mastery, so we should encourage that with a proper exercise book.

Worth using different style tags for different code snippets in tex file.
Especially for C++ code, to be able to automatically reformat all C++ snippets.

This problem occurs regulary in the codebase.

• ELTE-IK-CPP/book/01gy_cpp/01gy_cpp.tex

  Line 155 in c9a1f69

  >cd C:\test

• ELTE-IK-CPP/book/01gy_cpp/01gy_cpp.tex

  Line 172 in c9a1f69

  >g++ main.cpp && a.exe

• ELTE-IK-CPP/book/01gy_cpp/01gy_cpp.tex

  Line 176 in c9a1f69

  ~$ g++ main.cpp && ./a.out

• ELTE-IK-CPP/book/01gy_cpp/01gy_cpp.tex

  Line 459 in c9a1f69

  movl $5, (%esp)

and many more...

I can see that you are using [style = customasm] attribute for assembly snippets, are there any for bash too?