dotemacs/tests/test-custom-line-paragraph-join-paragraph.el, branch load-graph-classify-start

fix(line-paragraph): join-line-or-region strands space on next line

2026-05-03T11:56:10+00:00

The region branch's `(while (< (point) end) (join-line 1))` ran one iteration too many. After the final in-region join, point sat just before the end marker, so the loop fired once more. That extra `join-line 1` consumed the next line's preceding newline and replaced it with a space. Then `(goto-char end)` + `(newline)` reinserted a newline at the original end position, before the inserted space, so the space ended up stranded at BOL of the next line. I replaced the position-based loop with `count-lines` + `dotimes` to do exactly the right number of joins. I also swapped the trailing `(newline)` for `(forward-line 1)`. The bullet-list use case now lands directly on the next existing line with no blank gap. The trailing-newline change ripples to `cj/join-paragraph` (which delegates here), so paragraphs now also stop adding a trailing newline when the input lacks one. `require-final-newline` handles file-end discipline on save anyway. I added 3 new tests that fail against the old loop and pass against the fix. I also updated 11 existing tests whose assertions baked in the old trailing-newline behavior. While in there I wrapped the `cj/custom-keymap` defvar stub in `eval-and-compile` in both test files. The bare defvar wasn't evaluated at byte-compile time, so the `require` of `custom-line-paragraph` would hit a void symbol when the validate-el hook ran.

Revert "checking in modified/removed tests and other misc changes"

2025-11-14T08:35:00+00:00

This reverts commit 1218bae708a6755e3628f15fef58e6806ac81039.

checking in modified/removed tests and other misc changes

2025-11-14T08:31:16+00:00

test: Add unit tests for `join-line-or-region` and `join-paragraph`

2025-10-23T04:55:10+00:00

Add comprehensive test cases for the `cj/join-line-or-region` and `cj/join-paragraph` functions within the custom-line-paragraph module. These tests cover normal, boundary, and error cases to ensure the proper functionality of line and paragraph joining features. They address various scenarios including line breaks, whitespace, Unicode content, and cursor positioning, enhancing the robustness of existing functionality.