aboutsummaryrefslogtreecommitdiff
path: root/tests/test-prog-python--format-wiring.el
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-30 15:42:56 -0400
committerCraig Jennings <c@cjennings.net>2026-06-30 15:42:56 -0400
commit72b149227dcb44cc44a232138289bd6d7f7e3309 (patch)
treea1a1e32ec3c0087df0c22024c99a5fe97e02a3a6 /tests/test-prog-python--format-wiring.el
parentd5e9451022e9254655cc67e015f9d331414d2d76 (diff)
downloaddotemacs-72b149227dcb44cc44a232138289bd6d7f7e3309.tar.gz
dotemacs-72b149227dcb44cc44a232138289bd6d7f7e3309.zip
fix(undead-buffers): drop cj/save-some-buffers name collision
Emacs crashed at launch with wrong-number-of-arguments on cj/save-some-buffers, down the startup path (dashboard-only to kill-all-other-buffers to save). Two modules defined a function by that name: custom-buffer-file.el's legible save prompt (arg + pred), installed as an override on save-some-buffers, and undead-buffers.el's older one-arg wrapper that called save-some-buffers internally. custom-buffer-file loads first, undead-buffers second. The one-arg version won the shared symbol, so the override re-entered it with two args. I removed undead-buffers.el's wrapper. cj/kill-all-other-buffers-and-windows now calls the standard save-some-buffers with the undead predicate, which routes through the override when loaded and the built-in otherwise, so undead-buffers no longer depends on custom-buffer-file. The legible override keeps the cj/save-some-buffers name. A regression test loads both modules in launch order and guards the call and the arity so a one-arg shadow can't return.
Diffstat (limited to 'tests/test-prog-python--format-wiring.el')
0 files changed, 0 insertions, 0 deletions