From d0029622d8a7c2ce27ee925594d74e4216108576 Mon Sep 17 00:00:00 2001
From: James Cherti <60946298+jamescherti@users.noreply.github.com>
Date: Wed, 23 Jul 2025 19:16:21 -0400
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index acbd787..3f16908 100644
--- a/README.md
+++ b/README.md
@@ -1487,7 +1487,7 @@ fc-list : family | sed 's/,/\n/g' | sort -u
 
 ### Loading the custom.el file
 
-**NOTE:** The author advises against loading `custom.el`. To disable it, set `custom-file` to the null device using `(setq custom-file null-device)`. Users are instead encouraged to define their configuration programmatically in files such as `post-init.el`.
+**NOTE:** The author advises against loading `custom.el`. To disable it, set `custom-file` to the null device using `(setq custom-file null-device)`. Users are instead encouraged to define their configuration programmatically in files such as `post-init.el`. Maintaining configuration programmatically offers several advantages: it ensures transparency and reproducibility, facilitates version control. Unlike the automatically generated custom.el, which may introduce opaque or redundant settings, programmatic configuration is explicit and deterministic. This makes it easier to understand, audit, and evolve the configuration over time.
 
 In Emacs, customization variables modified via the UI (e.g., `M-x customize`) are typically stored in a separate file, commonly named `custom.el`. To ensure these settings are loaded during Emacs initialization, it is necessary to explicitly load this file if it exists. To accomplish this, add the following form to your `~/.emacs.d/post-init.el`: