From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: carriage-returns and nnimap
Date: Fri, 17 Dec 2010 17:16:08 +0100 [thread overview]
Message-ID: <m38vzofk8m.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87hbech7yi.fsf@andy.bu.edu>
Andrew Cohen <cohen@andy.bu.edu> writes:
> Tracing this a bit I found that 'gnus-get-newsgroup-headers translates
> \r into spaces, so I suspect that this is where the extra spaces are
> coming from. I added a call to 'nnheader-remove-cr-followed-by-lf in
> 'gnus-get-newsgroup-headers just before the \r->space translation and it
> seems to fix the problem.
There should be no \r\n in the buffers when Gnus gets them. The backend
should do \r\n decoding if the transport it uses uses \r\n...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2010-12-17 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 12:58 Andrew Cohen
2010-12-17 14:09 ` Ted Zlatanov
2010-12-17 14:18 ` Andrew Cohen
2010-12-17 15:36 ` Ted Zlatanov
2010-12-17 16:17 ` Lars Magne Ingebrigtsen
2010-12-17 16:16 ` Lars Magne Ingebrigtsen [this message]
2010-12-17 16:25 ` Andrew Cohen
2010-12-17 16:33 ` 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=m38vzofk8m.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).