Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: carriage-returns and nnimap
Date: Fri, 17 Dec 2010 08:09:14 -0600	[thread overview]
Message-ID: <87r5dg4hkl.fsf@lifelogs.com> (raw)
In-Reply-To: <87hbech7yi.fsf@andy.bu.edu>

On Fri, 17 Dec 2010 07:58:29 -0500 Andrew Cohen <cohen@andy.bu.edu> wrote: 

AC> I had noticed that gnus-registry-split-fancy-with-parent had stopped
AC> working with "sender" splitting. I finally decided to track this down.

AC> Looking at the registry I noticed that the "sender" and "subject" fields
AC> (and some others) had a spurious space at the end of them (which is
AC> wrong), while an old copy of the registry (from months ago) has no such
AC> spaces (which is right). I can't pinpoint exactly when this changed so
AC> I'm not sure of the exact cause.

AC> Tracing this a bit I found that 'gnus-get-newsgroup-headers translates
AC> \r into spaces, so I suspect that this is where the extra spaces are
AC> coming from. I added a call to 'nnheader-remove-cr-followed-by-lf in
AC> 'gnus-get-newsgroup-headers just before the \r->space translation and it
AC> seems to fix the problem. 

AC> I didn't want to just push this in case I've missed something. The whole
AC> carriage-return thing in nnimap confuses me.

I hadn't noticed, thanks for catching that.

I think your fix is correct, but if necessary I can always adjust
gnus-registry.el alone to trim those extra CRs.

Ted




  reply	other threads:[~2010-12-17 14:09 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 [this message]
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
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=87r5dg4hkl.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).