bug#2416: marked as done (23.0.60; decode-coding-region)

[owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)]

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]


Your message dated Sun, 22 Feb 2009 13:15:35 -0500
with message-id <87eixqz6bc.fsf@cyd.mit.edu>
and subject line Re: bug#1809: decode-coding-inserted-region corrupts files
has caused the Emacs bug report #1809,
regarding 23.0.60; decode-coding-region
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
1809: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1809
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 5749 bytes --]

From: mj <mj54590@gmail.com>
To: emacs-pretest-bug@gnu.org
Subject: 23.0.60; decode-coding-region
Date: Fri, 20 Feb 2009 13:13:01 -0800 (PST)
Message-ID: <499f1cdd.050cc00a.4267.ffffc0ce@mx.google.com>

I have been having this problem since I switched to Emacs 23 several
weeks ago. I'm using VM to read my mails. There seems to be a problem
in decode-coding-region when VM tries to decode a string. When VM
tries to decode a region or a string, it uses a temporary buffer and
basically runs the following lisp code:

(apply 'decode-coding-region (point-min) (point-max)  'us-ascii nil)

The original buffer  content would be something like this:

B7040400-12
some text here

after decode-coding-region is executed, the buffer content became:

^@7040450-12
some text here

Where ^@ is actually binary code \0 (not ascii ^ and @). There is another instance
that a string was decoded and the result is  ^@ prefixed. 

I could not reproduce this with "Emacs -Q". But it always happens when
thsoe particular messages were processed by VM. 

Strangely enough, if I inserted a few spaces at the beginning of
buffer: (one space in the following buffer)

 B7040400-12
some text here

And, the decoding was done correctly. In another instance mentioned
above, one space is not enough. I had to put several spaces to get the
decoding working. 

I saw another bug report just yesterday regarding decode-coding-region
crashing. I applied the patch, but it did not help in the
decoding. 

Please let me know if you need other information to help understand
the problem. Thanks. 

-----
Emacs version: "GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2009-01-29 on T42"

Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --cflags -I../../GnuWin32/include'

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ENU
  value of $XMODIFIERS: nil
  locale-coding-system: chinese-big5
  default-enable-multibyte-characters: t

Major mode: Shell

Minor modes in effect:
  auto-image-file-mode: t
  shell-dirtrack-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t




[-- Attachment #3: Type: message/rfc822, Size: 1399 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: Andreas Schwab  <schwab@linux-m68k.org>
Cc: Juri Linkov <juri@jurta.org>, mj <mj54590@gmail.com>, Juanma Barranquero <lekktu@gmail.com>, 1809-done@emacsbugs.donarmstrong.com
Subject: Re: bug#1809: decode-coding-inserted-region corrupts files
Date: Sun, 22 Feb 2009 13:15:35 -0500
Message-ID: <87eixqz6bc.fsf@cyd.mit.edu>

> 2009-02-22  Andreas Schwab  <schwab@linux-m68k.org>
>
>    * insdel.c (del_range_2): Don't modify gap contents when
>      called from decode_coding_object.  (Bug#1809)

Thanks for fixing this bug.