# Enforcing Nix formatting in Nixpkgs

**URL:** https://discourse.nixos.org/t/enforcing-nix-formatting-in-nixpkgs/49506
**Category:** Development
**Created:** [July 23, 2024, 7:03pm UTC](https://discourse.nixos.org/t/enforcing-nix-formatting-in-nixpkgs/49506 "2024-07-23T19:03:19Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![ppenguin](https://discourse.nixos.org/user_avatar/discourse.nixos.org/ppenguin/32/3583_2.png) [@ppenguin](https://discourse.nixos.org/u/ppenguin)
#### Post date: [July 23, 2024, 9:09pm UTC](https://discourse.nixos.org/t/enforcing-nix-formatting-in-nixpkgs/49506/2 "2024-07-23T21:09:30Z")

</div>

Thanks for your efforts on standardisation!

As a coincidence, I had just stumbled on [this (ancient) topic](https://discourse.nixos.org/t/the-uncompromising-nix-code-formatter/17385), which was suddenly on my radar since a trivial PR to `nixpkgs` of mine “blew up” on auto-formatting `all-packages.nix` (with `alejandra`, the discovery of which was a coincidence due to it being a default in `nvf` (nix-wrapper-config-module for `nvim`.)

What I was a bit surprised about was that the mentioned formatter seemed to have huge interest/momentum at the time (in 2022), I believe mostly in tandem with RFC101, but that I couldn’t easily find historical info on the decision making process after that, that apparently eventually lead to RFC166 “overruling” the former, getting us where we are now.

Don’t get me wrong, I think the fact that there is an official consensus now trumps any other considerations, I’m just interested in the decision making process that lead us here.

---

_[View the full topic](https://discourse.nixos.org/t/enforcing-nix-formatting-in-nixpkgs/49506)._