aboutsummaryrefslogtreecommitdiff
path: root/tests/test-undead-buffers-kill-other-window.el
Commit message (Collapse)AuthorAgeFilesLines
* fix(undead-buffers): guard kill-other-window against a lone windowCraig Jennings6 days1-4/+5
| | | | | | | | In a single-window frame cj/kill-other-window killed the buffer being viewed: other-window no-ops, delete-window was guarded, but the kill still ran on the current buffer. Signal a user-error instead, matching the sibling cj/kill-other-window-buffer. Past the guard there's always another window, so delete-window drops its own check. The single-window test asserted the broken behavior, so I rewrote it to expect the user-error and an untouched buffer. Also documented the prefix-argument undead-mark in cj/kill-buffer-or-bury-alive.
* Revert "checking in modified/removed tests and other misc changes"Craig Jennings2025-11-141-0/+123
| | | | This reverts commit d36afc3f277b9a4228eb7b2464ec4e503695b8d4.
* checking in modified/removed tests and other misc changesCraig Jennings2025-11-141-123/+0
|
* feat: undead-buffers: Add `cj/make-buffer-undead` function and testsCraig Jennings2025-10-221-0/+123
Introduce a new function `cj/make-buffer-undead` that appends a buffer name to the `cj/undead-buffer-list`, preventing it from being killed. This comes along with a suite of tests to check various scenarios and edge cases for handling undead buffers. Additionally, add tests for related functions: `cj/kill-buffer-or-bury-alive`, `cj/kill-buffer-and-window`, and others to ensure they correctly manage buffers, particularly with undead-status considerations. Refactor `undead-buffer-list` naming for consistency and clarity in the module.