Check diff before "pretty-print on save"

[marceltaeumel]

I suggest that the "pretty-print on save" scopes itself to the changed portion of code to avoid re-formatting a (legacy) method with a different style. That it, a fix in a single line of code can be reviewed faster if the code around does not change.

(Hmm... maybe the poppy print could also scan for a specific style and reconfigure itself on-the-fly :)

[tom95]

Currently, poppy-print is "opinionated by design", that is to mean: format it one way and no other. Personally, I think introducing preferences might be something that is an option further down the road but I would prefer getting to a very good and stable formatting following a single style first.

Integrating with a diff on regions of text is an interesting idea. I can think of a number of scenarios where it might catastrophically break, depending on the implementation, but also a number of scenarios where it would be quite convenient and also likely straightforward to implement.

[marceltaeumel]

Currently, poppy-print is "opinionated by design"

I know. :-) It would be nice if this project would add "expressing your thoughts through text" to one of its basic values. Implicit knowledge remains one of the biggest challenges in program comprehension.