Repository navigation
fix(remember): report restore errors once, off the autocmd - #14
Conversation
|
Why did you delete all the comments? |
📊 Test Coverage ReportOverall Coverage: 97.78% 📋 Detailed Coverage ReportCoverage report generated by luacov |
Oops — the comments were dropped unintentionally during the pcall restructure. The function body re-indentation caused them to be lost. I've restored them all in the latest commit (but please do let me know if I've missed any). While I was at it, blank-line separators between top-level sections are back too. Clearly I need a better code reformatter (or config for it) :) |
Restore original field ordering (ignore_filetype before ignore_buftype) in config table and setup function. Restore blank line after license block and trailing newline. These were pure formatting noise unrelated to the pcall fix.
|
Cleaned up the diff — removed unnecessary config field reordering, blank line changes, and trailing newline changes. The diff now only contains the pcall wrapping and error handler. All 18 tests still pass. Ready for re-review whenever you have a moment. Thanks! |
|
👋 hola! The diff was cleaned up after your last round of feedback. Should be good for another look whenever you have time. Thanks in advance. |
|
👋 hola! Checking in again — the pcall fix is still sitting at 18/18 tests passing and the diff is just the fault-tolerance change now. It's been a while since the last review, so if anything else needs tweaking I'm happy to take another pass. No rush, just making sure it hasn't slipped through the cracks. |
|
I don't think this PR completley fixes the issue unfortunately. The commit titled "add tests to verify errors are handled gracefully" adds only mock_notify and vim.log.levels to the mock table. No test case asserts that an error is caught or that notify fires. The suite mocks Current undotree uses I'm working on the fix and tests. |
setup() tested each option for truthiness. A user could not turn a default off. Signed-off-by: Vladislav Doster <mvdoster@gmail.com>
Test the buffer name with filereadable() instead of glob(). A name like "[Scratch-1]" is a glob pattern and raised E944. Defer the notify call with vim.schedule and report each distinct error once. Rethrow a keyboard interrupt so the triggering command still aborts. Fixes vladdoster#10 Signed-off-by: Vladislav Doster <mvdoster@gmail.com>
Drive a real "nvim --headless" to cover mark restore, the [Scratch-1] window from issue vladdoster#10, and deferred error reporting. The spec is pending when nvim is not on PATH. Signed-off-by: Vladislav Doster <mvdoster@gmail.com>
Signed-off-by: Vladislav Doster <mvdoster@gmail.com>
|
Pushed four commits on top of this branch (maintainer edits are enabled):
|
|
🎉 This PR is included in version 1.5.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Summary
Changes
This prevents the plugin from crashing when unexpected API errors occur.