Isn't developer-specific preference -- such as two vs four space tabbing -- a developer-specific problem? I imagine `nph`, much like python's `black` to be used like a pre-git-commit automatic step to standardize code. Doesn't much matter what it's standardized to. This frees you up to display and edit the code however you want, without regard to the preferences of your colleagues, while the codebase remains standardized, making other automations easier.
- `nph` opinionated formatter v0.3 Araq
- `nph` opinionated formatter v0.3 freeflow
- `nph` opinionated formatter v0.3 arnetheduck
- `nph` opinionated formatter v0.3 freeflow
- `nph` opinionated formatter v0.3 arnetheduck
- `nph` opinionated formatter v0.3 auxym
- `nph` opinionated formatter v0.3 morturo
- `nph` opinionated formatter v0.3 freeflow
- `nph` opinionated formatter v0.3 ggibson
- `nph` opinionated formatter v0.3 xigoi
