| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
Previously, 'indent run-equals-prev-output' was allowed even when there
was no 'indent run' section above. This created an ambiguity, since
'previous output' could mean either the 'indent run' section or the
'indent run-equals-input' section.
|
|
|
|
|
|
|
|
The "refactoring" back then tried to be too clever.
|
|
|
|
|
|
|
|
The C code in the whole tree does not contain a single literal
backspace.
|
|
|
|
|
|
This generates fewer error markers in syntax-aware editors.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Since 2023-06-10 06:52, which fixed the indentation of C11 _Generic
expressions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Due to buffering, there was no guarantee that the output would be
exactly in the same order as written in the tests.
|
|
|
|
|
|
|
|
|
|
One less moving part in the parser state.
No functional change.
|
|
No functional change.
|
|
They were handled in exactly the same way.
|
|
|
|
|
|
For several parser symbols, 2 symbols are pushed in a row, which led to
an out-of-bounds write.
|
|
|
|
|
|
|
|
As a side effect, indent handles _Generic from C11 properly now, at
least in -nlp mode.
|
|
No functional change.
|
|
|
|
|
|
|