Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@ifa.au.dk>
Cc: bugs@gnus.org, "Vladimir Volovich" <vvv@vsu.ru>
Subject: Re: bug in latest gnus when previewing certain message
Date: Fri, 30 May 2003 04:52:58 +0200	[thread overview]
Message-ID: <m3n0h5jgc5.fsf@defun.localdomain> (raw)
In-Reply-To: <rzqel2iiub6.fsf@albion.dl.ac.uk>

Dave Love <d.love@dl.ac.uk> writes:

> Jesper Harder <harder@myrealbox.com> writes:
>
>>> "Vladimir Volovich" <vvv@vsu.ru> writes:
>>>
>>>> using the latest gnus from cvs, i get the following error when trying to
>>>> view the attached (spam) message:
>>>>
>>>> Debugger entered--Lisp error: (args-out-of-range 650 650)
>>>>   mm-decode-coding-region(650 650 koi8-r)
>>>>   mail-decode-encoded-word-region(1 883)
>>
>> I think this change is the culprit:
>>
>> ,----
>> | 2003-05-02  Dave Love  <fx@gnu.org>
>> | 
>> | 	* rfc2047.el (rfc2047-q-encode-region, rfc2047-decode): Use
>> | 	mm-with-unibyte-current-buffer.
>> `----
>
> I don't see how that change could cause the error above.

It's some kind of bad interaction between narrowing and
`mm-with-unibyte-current-buffer'.  This example illustrates the
effect:

(with-temp-buffer
  (insert "From: ニシキノネット FC事業部
Content-Type: text/plain; charset=ISO-2022-JP\n\n")
  (article-narrow-to-head)
  (mm-with-unibyte-current-buffer)
  (buffer-string))

=>
"From: ニシキノネット FC事業部
Content-Type: text/plain"

Note how the last part of the text has been chopped off.  

If you edebug `rfc2047-decode' and step through Vladimirs example,
you'll see that this is also what's happening there.



      parent reply	other threads:[~2003-05-30  2:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-25 15:55 Vladimir Volovich
2003-05-26  8:19 ` Simon Josefsson
     [not found] ` <basjcm$28e$1@quimby.gnus.org>
2003-05-26 17:26   ` Jesper Harder
     [not found]     ` <rzqel2iiub6.fsf@albion.dl.ac.uk>
2003-05-30  2:52       ` Jesper Harder [this message]

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=m3n0h5jgc5.fsf@defun.localdomain \
    --to=harder@ifa.au.dk \
    --cc=bugs@gnus.org \
    --cc=vvv@vsu.ru \
    /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).