From d341beea020cfad52942b854a8f42d0be2e34ae9 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 3 May 2026 19:40:28 -0500 Subject: fix: clarify reset-auth-cache failure message `cj/reset-auth-cache`'s error path read "Failed to clear gpg-agent cache". A user seeing that warning could reasonably think nothing happened. But at that point the Emacs-side caches (auth-source + EPA file handler) have already been cleared. Only the gpg-agent cache failed. I rewrote the message as "Emacs caches cleared, but failed to clear gpg-agent cache" so the user sees both the partial success and the remaining problem. The error-path test from the previous commit asserts a substring match on "Failed to clear gpg-agent cache", so it still passes after the rewording. --- modules/auth-config.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'modules/auth-config.el') diff --git a/modules/auth-config.el b/modules/auth-config.el index f2df1746..02fc7858 100644 --- a/modules/auth-config.el +++ b/modules/auth-config.el @@ -158,7 +158,7 @@ Use this when you see errors like: (let ((result (shell-command "echo RELOADAGENT | gpg-connect-agent"))) (if (zerop result) (message "✓ Emacs and gpg-agent caches cleared. Next access will prompt for password.") - (message "⚠ Warning: Failed to clear gpg-agent cache"))) + (message "⚠ Emacs caches cleared, but failed to clear gpg-agent cache"))) (message "✓ Emacs caches cleared. GPG/SSH passphrases preserved for session."))) (defun cj/kill-gpg-agent () -- cgit v1.2.3