From: Juanma Barranquero <lekktu@gmail.com>
To: MJ <mj54590@gmail.com>
Cc: Chong Yidong <cyd@stupidchicken.com>, 2416@emacsbugs.donarmstrong.com
Subject: bug#2416: 23.0.60; decode-coding-region
Date: Sun, 22 Feb 2009 07:07:41 +0100 [thread overview]
Message-ID: <f7ccd24b0902212207t769b5786k39521bd7da9722f2@mail.gmail.com> (raw)
In-Reply-To: <f7ccd24b0902212113s41439eb2ve192a87fe7bca8f0@mail.gmail.com>
On Sun, Feb 22, 2009 at 06:13, Juanma Barranquero <lekktu@gmail.com> wrote:
> If you look at #1809, you'll see that the problem seems to be
> sensitive to string length. Assuming you're using ASCII, do you see it
> with strings of length != 20?
A clue: the bug is sensitive to the value of the BUF_GAP_SIZE set in
`get-buffer-create', at buffer.c:364.
If you change
BUF_GAP_SIZE (b) = 20;
to another size, so does the bug's triggering length.
Juanma
next prev parent reply other threads:[~2009-02-22 6:07 UTC|newest]
Thread overview: 20+ 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
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 [this message]
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
2009-02-21 17:21 bug#2416: 23.0.60; decode-coding-region Chong Yidong
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b0902212207t769b5786k39521bd7da9722f2@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=2416@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=mj54590@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).