Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: agent articles get \201 inserted
Date: Mon, 25 Apr 2011 09:04:43 +0200	[thread overview]
Message-ID: <87zkne3j78.fsf@dod.no> (raw)
In-Reply-To: <87aafe51uu.fsf@dod.no>

>>>>> Steinar Bang <sb@dod.no>:

>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
>> Steinar Bang <sb@dod.no> writes:
>>> Actually... this seems to be an emacs22 issue.  Happens with emacs22 on
>>> Ubuntu 10.10 and on CentOS5, but not in emacs23 on debian testing.
> [snip!]
>> This bug sounds familiar to me, but I don't remember what the underlying
>> issue was in Emacs 22 any more.  Anybody remember?

I decided to bisect the issue.  Between each good or bad, I did
 (cd ~/git/gnus; make clean; make; cd lisp; make tags)
and started a fresh emacs on the results.

It turns out that the issue has been there for a while (and also that
the bisect result isn't very useful... see below...:-) ).

The reason I haven't noticed it, is that I get it on some articles.  And
one of the offending articles have:
 Content-transfer-encoding: 8BIT
 Content-type: text/plain; charset=UTF-8

Could it be CTE 8BIT that is the culprit?  There was something about
that in the most recent thread (the 2008 thread from this group).

Articles that display correctly, are
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable

and (curiously):
 Content-transfer-encoding: 8BIT
 Content-type: text/html; charset=utf-8

(I'm not sure what I use to render HTML.  But should it matter, if the
problem is getting 8BIT stuff from nnimap?)


Anyway... the "offending" commit is this one:

sb@aa1steinar:~/git/gnus$ git bisect good
df6ac45b952171e7e709c1b0bf23cc7346429f81 is the first bad commit
commit df6ac45b952171e7e709c1b0bf23cc7346429f81
Author: Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org>
Date:   Fri Sep 17 18:18:39 2010 +0200

    Reimplement nnimap, and do tweaks to the rest of the code to support that.
    
    * gnus-int.el (gnus-finish-retrieve-group-infos)
    (gnus-retrieve-group-data-early): New functions.
    
    * gnus-range.el (gnus-range-nconcat): New function.
    
    * gnus-start.el (gnus-get-unread-articles): Support early retrieval of
    data.
    (gnus-read-active-for-groups): Support finishing the early retrieval of
    data.
    
    * gnus-sum.el (gnus-summary-move-article): Pass the move-to group name
    if the move is internal, so that nnimap can do fast internal moves.
    
    * gnus.el (gnus-article-special-mark-lists): Add uid/active tuples, for
    nnimap usage.
    
    * nnimap.el: Rewritten.
    
    * nnmail.el (nnmail-inhibit-default-split-group): New internal variable
    to allow the mail splitting to not return a default group.  This is
    useful for nnimap, which will leave unmatched mail in the inbox.
    
    * utf7.el (utf7-encode): Autoload.

:040000 040000 09a1ec556b1e7bd509b0d7ccaa718be697b6c6cd b9ca8dee8837ae5b13e9c23fece66471ebb0b5c3 M	lisp




  reply	other threads:[~2011-04-25  7:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08  9:23 Steinar Bang
2011-03-08 18:58 ` Steinar Bang
2011-03-08 21:34   ` Steinar Bang
2011-03-15 16:37     ` Lars Magne Ingebrigtsen
2011-04-25  5:36       ` Steinar Bang
2011-04-25  7:04         ` Steinar Bang [this message]
2011-05-01 15:07           ` Lars Magne Ingebrigtsen
2011-05-01 15:29             ` Steinar Bang
2011-05-01 15:43               ` Lars Magne Ingebrigtsen
2011-05-01 16:25                 ` Steinar Bang
2011-05-01 16:46                   ` Lars Magne Ingebrigtsen
2011-05-01 17:20                     ` Lars Magne Ingebrigtsen
2011-05-01 18:09                       ` Steinar Bang
2011-05-01 17:29                     ` 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=87zkne3j78.fsf@dod.no \
    --to=sb@dod.no \
    --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).