From: Mark Plaksin <happy@usg.edu>
Subject: Re: PATCH: Make nnrss include RSS dc:subject
Date: Tue, 20 Dec 2005 10:46:17 -0500 [thread overview]
Message-ID: <87y82fkbzq.fsf@stone.tss.usg.edu> (raw)
In-Reply-To: <b4mwti08efy.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>>> In <b4mirtka4vn.fsf@jpl.org> Katsumi Yamaoka wrote:
>
>> Sorry, it's not good. I see `<br /><br />' in the article
>> buffer when I choose the text/plain part[1]. Any idea? It
>> seems to me enough to use "\n\n\n" instead of "<br /><br />\n".
>
> It's also bad to use "\n\n\n". I've fixed it by replacing
> `<br />'s with newlines when generating text/plain parts. It
> will not have a bad influence because only `nnrss-check-group'
> inserts `<br />'s.
Thanks for fixing it! I forgot that I put "<br /><br />" in there. And I
never tested text/plain.
>> ;; I don't usually use nnrss.
You say this a lot. Do you read a lot of feeds? Do you read all of them
with nnshimbun?
I read all of my feeds in Gnus and nnrss generally does a good enough job
for me (I'm pretty easy to please :) Sometimes nnshimbun is better
though--like for the emacswiki.org feed. When I want to make small
changes, like the nnrss change we're discussing, I'm not sure whether it's
better to make the change in nnrss or nnshimbun.
next prev parent reply other threads:[~2005-12-20 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-17 4:09 Mark Plaksin
2005-12-19 5:19 ` Katsumi Yamaoka
2005-12-20 2:17 ` Katsumi Yamaoka
2005-12-20 6:34 ` Katsumi Yamaoka
2005-12-20 15:46 ` Mark Plaksin [this message]
2005-12-21 0:45 ` Katsumi Yamaoka
2006-04-13 6:07 ` Lars Magne Ingebrigtsen
2006-04-13 8:59 ` yamaoka
2006-04-13 9:11 ` Lars Magne Ingebrigtsen
2006-04-13 9:42 ` Katsumi Yamaoka
2006-04-13 10:52 ` Lars Magne Ingebrigtsen
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=87y82fkbzq.fsf@stone.tss.usg.edu \
--to=happy@usg.edu \
/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).