Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: nnrss broken on Emacs master?
Date: Tue, 21 Feb 2017 09:39:10 +0900	[thread overview]
Message-ID: <b4mino4e5sh.fsf@jpl.org> (raw)
In-Reply-To: <23567.1487395783@alto>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

On Fri, 17 Feb 2017 21:29:43 -0800, Mike Kupfer wrote:
> I have a few nnrss groups.  When I read them with Emacs 21.5.91, the
> postings appear as multipart/alternative with buttons, e.g.,
[...]
> When I read them with Emacs master (a83b6692), I get stuff that looks
> like

> -----8<-----8<-----
> Newsgroups: ACM Queue Blogroll
> Subject: The Road to Debugging Success
> From: blog dds
> Date: Thu, 16 Feb 2017 13:55:44 GMT
> MIME-Version: 1.0
> Content-Type: text/plain
> Message-ID: <1738@ACM_Queue_Blogroll.nnrss>

> <#multipart type=alternative>
> <#part type="text/plain">
> A colleague recently asked me how to debug a Linux embedded system
----->8----->8-----

> Sometimes the text/plain version has HTML markup, which makes it hard to
> read.

Fixed in master:
<http://lists.gnu.org/archive/html/emacs-diffs/2017-02/msg00271.html>

> Are nnrss groups working for anyone else?

I needed to tweak `url-insert-file-contents' temporarily as
follows to make nnrss work.  It will probably cause some trouble
if the server is not working properly, though. :(


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 1468 bytes --]

--- lisp/url/url-hanrlers.el~	2017-01-04 22:17:18 +0000
+++ lisp/url/url-hanrlers.el	2017-02-21 00:36:20 +0000
@@ -339,23 +339,6 @@
 (defun url-insert-file-contents (url &optional visit beg end replace)
   (let ((buffer (url-retrieve-synchronously url)))
     (unless buffer (signal 'file-error (list url "No Data")))
-    (with-current-buffer buffer
-      ;; XXX: This is HTTP/S specific and should be moved to url-http
-      ;; instead.  See http://debbugs.gnu.org/17549.
-      (when (bound-and-true-p url-http-response-status)
-        ;; Don't signal an error if VISIT is non-nil, because
-        ;; 'insert-file-contents' doesn't.  This is required to
-        ;; support, e.g., 'browse-url-emacs', which is a fancy way of
-        ;; visiting the HTML source of a URL: in that case, we want to
-        ;; display a file buffer even if the URL does not exist and
-        ;; 'url-retrieve-synchronously' returns 404 or whatever.
-        (unless (or visit
-                    (and (>= url-http-response-status 200)
-                         (< url-http-response-status 300)))
-          (let ((desc (nth 2 (assq url-http-response-status url-http-codes))))
-            (kill-buffer buffer)
-            ;; Signal file-error per http://debbugs.gnu.org/16733.
-            (signal 'file-error (list url desc))))))
     (url-insert-buffer-contents buffer url visit beg end replace)))
 
 (put 'insert-file-contents 'url-file-handlers 'url-insert-file-contents)

  reply	other threads:[~2017-02-21  0:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18  5:29 Mike Kupfer
2017-02-21  0:39 ` Katsumi Yamaoka [this message]
2017-02-21  3:31   ` Mike Kupfer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b4mino4e5sh.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).