From: Juri Linkov <juri@jurta.org>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: 1809@emacsbugs.donarmstrong.com
Subject: bug#1809: decode-coding-inserted-region corrupts files
Date: Fri, 16 Jan 2009 01:02:38 +0200 [thread overview]
Message-ID: <87ab9sdvg1.fsf@jurta.org> (raw)
In-Reply-To: <f7ccd24b0901141840p158e2f10kfd713c0e99e4c189@mail.gmail.com> (Juanma Barranquero's message of "Thu, 15 Jan 2009 03:40:22 +0100")
>> (progn
>> (switch-to-buffer "test")
>> (insert "Test.\nTest2.\nTest3.\n")
>> (decode-coding-inserted-region
>> (point-min) (point-max) "/tmp/test" t nil nil nil))
>
> (with-temp-buffer
> (insert (make-string 20 ?.))
> (decode-coding-region 1 (point-max) 'raw-text)
> (buffer-string))
>
> => "^@..................."
>
> It only happens for a string of length 20 bytes.
Does this mean I was lucky discovering the exact length where the bug
manifests itself?
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-01-15 23:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87eixqz6bc.fsf@cyd.mit.edu>
2009-01-06 17:32 ` bug#1809: 23.0.60; epa-encrypt-file corrupts files Juri Linkov
2009-01-15 1:12 ` bug#1809: decode-coding-inserted-region " Juri Linkov
2009-01-15 2:40 ` Juanma Barranquero
2009-01-15 23:02 ` Juri Linkov [this message]
2009-01-15 23:35 ` Juanma Barranquero
2009-02-22 18:20 ` bug#1809: marked as done (decode-coding-inserted-region corrupts files) Emacs bug Tracking System
2009-02-20 21:13 ` bug#2416: 23.0.60; decode-coding-region mj
2009-02-21 9:16 ` Eli Zaretskii
2009-02-21 13:20 ` MJ
2009-02-22 2:47 ` Juanma Barranquero
2009-02-22 5:07 ` MJ
2009-02-22 5:13 ` Juanma Barranquero
2009-02-22 5:23 ` MJ
2009-02-22 5:44 ` Juanma Barranquero
2009-02-22 5:50 ` Processed: " Emacs bug Tracking System
2009-02-22 6:07 ` Juanma Barranquero
2009-02-22 14:31 ` Andreas Schwab
2009-02-23 2:23 ` MJ
2009-02-22 18:20 ` bug#2416: marked as done (23.0.60; decode-coding-region) Emacs bug Tracking System
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=87ab9sdvg1.fsf@jurta.org \
--to=juri@jurta.org \
--cc=1809@emacsbugs.donarmstrong.com \
--cc=lekktu@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.