From 73c81a00a10766900318d86640249d1b54c6b351 Mon Sep 17 00:00:00 2001
From: Craig Jennings <c@cjennings.net>
Date: Sat, 4 Apr 2026 16:32:16 -0500
Subject: feat: specific error messages for fetch failures
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Add HTTP status code checking (wttrin--extract-http-status) and pass
error descriptions through the callback chain so users see "Location
not found (HTTP 404)" or "Network error — check your connection"
instead of the generic "Perhaps the location was misspelled?" for
every failure.

Also fix pre-existing bug where the condition-case error handler in
extract-response-body killed an unrelated buffer after unwind-protect
already cleaned up.

330 tests (was 307), all passing.
---
 wttrin-debug.el | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'wttrin-debug.el')

diff --git a/wttrin-debug.el b/wttrin-debug.el
index d0473dd..53f7e29 100644
--- a/wttrin-debug.el
+++ b/wttrin-debug.el
@@ -45,7 +45,7 @@ Always fetches fresh data from the API, bypassing cache."
   (let ((wttrin--force-refresh t))
     (wttrin--get-cached-or-fetch
      location
-   (lambda (raw-string)
+   (lambda (raw-string &optional _error-msg)
      (with-current-buffer (get-buffer-create "*wttrin-debug*")
        (erase-buffer)
        (when raw-string
-- 
cgit v1.2.3