aboutsummaryrefslogtreecommitdiff
path: root/modules/prog-shell.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
commit3cb2790a391e708e9db63dbcd469cfa10afce98e (patch)
tree674f0a57494b482be6c754b60981985835267b75 /modules/prog-shell.el
parent582ed54ed9a3c600e7e1e68beeea8b16ce1ed613 (diff)
downloaddotemacs-3cb2790a391e708e9db63dbcd469cfa10afce98e.tar.gz
dotemacs-3cb2790a391e708e9db63dbcd469cfa10afce98e.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 'modules/prog-shell.el')
0 files changed, 0 insertions, 0 deletions