[gnus git] branch no-gnus updated: m0-1-16-g151b0e6 =2= Make error reporting when doing `M-g' work again ; Make nntp report connection errors better

Lars Ingebrigtsen <[email protected]>
Newsgroups gmane.emacs.gnus.cvs
Message-ID <[email protected]>
       via  151b0e629d001d9e1cb9c0a6779c6136b0731424 (commit)
       via  c0bd60e0c007d95c540e3cf05218dfe7f096be85 (commit)
      from  674439465f70ff04dc483df45a4581a113ca44cf (commit)


- Log -----------------------------------------------------------------
commit 151b0e629d001d9e1cb9c0a6779c6136b0731424
Author: Lars Ingebrigtsen <[email protected]>
Date:   Wed Feb 1 23:18:49 2012 +0100

    Make error reporting when doing `M-g' work again
    
    * gnus-group.el (gnus-group-get-new-news-this-group): Don't overwrite
    the real error message with the useless "previously known to be down".
    Which isn't even correct.

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index a323a37..b1bc099 100644
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,5 +1,9 @@
 2012-02-01  Lars Ingebrigtsen  <[email protected]>
 
+	* gnus-group.el (gnus-group-get-new-news-this-group): Don't overwrite
+	the real error message with the useless "previously known to be down".
+	Which isn't even correct.
+
 	* nntp.el (nntp-open-connection): Report the error message if the nntp
 	server can't be reached.
 
diff --git a/lisp/gnus-group.el b/lisp/gnus-group.el
index 85bd156..de97d9a 100644
--- a/lisp/gnus-group.el
+++ b/lisp/gnus-group.el
@@ -4072,10 +4072,7 @@ If DONT-SCAN is non-nil, scan non-activated groups as well."
 	      (gnus-agent-save-group-info
 	       method (gnus-group-real-name group) active))
 	    (gnus-group-update-group group nil t))
-	(if (eq (gnus-server-status (gnus-find-method-for-group group))
-		'denied)
-	    (gnus-error 3 "Server previously determined to be down; not retrying")
-	  (gnus-error 3 "%s error: %s" group (gnus-status-message group)))))
+	(gnus-error 3 "%s error: %s" group (gnus-status-message group))))
     (when beg
       (goto-char beg))
     (when gnus-goto-next-group-when-activating

commit c0bd60e0c007d95c540e3cf05218dfe7f096be85
Author: Lars Ingebrigtsen <[email protected]>
Date:   Wed Feb 1 23:14:05 2012 +0100

    Make nntp report connection errors better
    
    * nntp.el (nntp-open-connection): Report the error message if the nntp
    server can't be reached.

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index f541ee1..a323a37 100644
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,5 +1,8 @@
 2012-02-01  Lars Ingebrigtsen  <[email protected]>
 
+	* nntp.el (nntp-open-connection): Report the error message if the nntp
+	server can't be reached.
+
 	* nnimap.el (nnimap-retrieve-group-data-early): Keep track of how many
 	groups we do a total scan for.
 	(nnimap-wait-for-response): Say that we're doing a total scan, if we're
diff --git a/lisp/nntp.el b/lisp/nntp.el
index 7148fdb..98393a6 100644
--- a/lisp/nntp.el
+++ b/lisp/nntp.el
@@ -1385,6 +1385,10 @@ password contained in '~/.nntp-authinfo'."
       (nnheader-cancel-timer timer))
     (when (and process
 	       (not (memq (process-status process) '(open run))))
+      (with-current-buffer pbuffer
+	(goto-char (point-min))
+	(nnheader-report 'nntp "Error when connecting: %s"
+			 (buffer-substring (point) (line-end-position))))
       (setq process nil))
     (unless process
       (nntp-kill-buffer pbuffer))

-----------------------------------------------------------------------
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we listed those
revisions in full, above.

Summary of changes:
 lisp/ChangeLog     |    7 +++++++
 lisp/gnus-group.el |    5 +----
 lisp/nntp.el       |    4 ++++
 3 files changed, 12 insertions(+), 4 deletions(-)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Gnus Project".

The branch, no-gnus has been updated


hooks/post-receive
-- 
Gnus Project
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.