diff options
| author | Craig Jennings <c@cjennings.net> | 2025-11-08 12:12:52 -0600 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2025-11-08 12:12:52 -0600 |
| commit | 04b11059b831c94b4e5ba901b735fcc888cbbe1a (patch) | |
| tree | 06051abaed3c4e1b79f2a0e10447c7c80649d268 /tests/README-DEBUG-TESTS.md | |
| parent | 29b559bd1a956a4efdec625f1b5d878503d46a33 (diff) | |
refactor: make debug functions public (single hyphen naming)
Renamed private debug functions to public API:
- wttrin--debug-show-log → wttrin-debug-show-log
- wttrin--debug-clear-log → wttrin-debug-clear-log
Added ;;;###autoload to both functions for proper autoloading.
Updated all references:
- README.org (2 occurrences)
- tests/README-DEBUG-TESTS.md (4 occurrences)
- tests/test-wttrin-integration-with-debug.el (8 occurrences)
These are user-facing commands that should be discoverable via M-x,
so they follow the public API naming convention (single hyphen).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Diffstat (limited to 'tests/README-DEBUG-TESTS.md')
| -rw-r--r-- | tests/README-DEBUG-TESTS.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/tests/README-DEBUG-TESTS.md b/tests/README-DEBUG-TESTS.md index 7310123..c1abd52 100644 --- a/tests/README-DEBUG-TESTS.md +++ b/tests/README-DEBUG-TESTS.md @@ -55,7 +55,7 @@ M-x debug-wttrin-enable ### View Debug Log ```emacs-lisp -M-x wttrin--debug-show-log +M-x wttrin-debug-show-log ``` This opens a buffer showing all debug events with timestamps. @@ -63,7 +63,7 @@ This opens a buffer showing all debug events with timestamps. ### Clear Debug Log ```emacs-lisp -M-x wttrin--debug-clear-log +M-x wttrin-debug-clear-log ``` ## Test Fixtures @@ -76,7 +76,7 @@ If wttrin isn't loading in your configuration: 1. **Enable debug mode** (set `wttrin-debug` to `t` before loading) 2. **Check dependencies**: Run `M-x package-list-packages` and ensure `xterm-color` is installed -3. **View debug log**: Run `M-x wttrin--debug-show-log` after trying to use wttrin +3. **View debug log**: Run `M-x wttrin-debug-show-log` after trying to use wttrin 4. **Check for errors**: Look in `*Messages*` buffer for any error messages The debug log will show you exactly where the process stops or fails. |