René Kijewski

Yeah, makes sense. * `{% else %} bloop {%=` → ` bloop ` and * `{% else -%} bloop {%=` → `bloop ` ?

Ah, thank you for finding the issued and adding an example to reproduce it! The [generator for for-loops](https://github.com/djc/askama/blob/874e0350335de3049c6cddc10bc371b11958e79c/askama_derive/src/generator.rs#L827) only calls `self.locals.push()` if it is used with `for … in …...

Actually, using a single character as delimiter (even such a character as newline) (w|sh)ould work, but then it would be difficult to extend the language in the future if we...

Well, 1st and foremost I wanted to remove the restriction that you have to use exactly two ASCII characters as delimiters. With this PR you can use any and all...

In the end I want to use askama to format a single latex file. Using braces as delimiters does not work very well in this context. Adding a config file...

> Sorry for the slow feedback. No problem at all! What do you think about adding a new syntax config struct `{whitespace, block_start, ..}` that I would pass around? Instead...

PR needs to be redone entirely, because the codebase changed entirely.

I don't think it's possible to override the default ToString implementation until [`feature(specialization)`](https://github.com/rust-lang/rfcs/blob/master/text/1210-impl-specialization.md) is stable. ```text Error[E0119]: conflicting implementations of trait `ToString` for type `test_match_ws::MatchWs` --> testing/tests/ws.rs:469:18 | 469 |...

@djc, the need for two character delimiters was lifted in [#541](https://github.com/djc/askama/pull/541/files#diff-48297b9b3a3f70c8521bedbaa0601f9e2b405eaa7a99fbffe0d9131e3207e478L202-L234). Yeah, I think its reasonable to remove the check in [config.rs:167](https://github.com/djc/askama/blob/6f52d0eef5a3178e1ebf7d4c7e2cf397756f57eb/askama_derive/src/config.rs#L167).

@Gigate, is think this is an [X/Y problem](https://en.wikipedia.org/wiki/XY_problem). Did you see #664 which introduced `{{+ ... +}` to fold many white spaces into one?