Gnus development mailing list
 help / color / mirror / Atom feed
From: Mike Kupfer <m.kupfer@acm.org>
To: ding@gnus.org
Subject: nnrss broken on Emacs master?
Date: Fri, 17 Feb 2017 21:29:43 -0800	[thread overview]
Message-ID: <23567.1487395783@alto> (raw)

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.,

-----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: multipart/alternative; boundary="=-=-="
Message-ID: <1738@ACM_Queue_Blogroll.nnrss>

1.  (*) text/plain          ( ) text/html           

A colleague recently asked me how to debug a Linux embedded system
----->8----->8-----

(This is after invoking gnus-summary-toggle-header.)

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.  With 25.1.91, I can click on the text/html button to make it
readable.  With the current code in master, I seem to be out of luck.

Are nnrss groups working for anyone else?

mike



             reply	other threads:[~2017-02-18  5:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18  5:29 Mike Kupfer [this message]
2017-02-21  0:39 ` Katsumi Yamaoka
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=23567.1487395783@alto \
    --to=m.kupfer@acm.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).