From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juri Linkov <juri@jurta.org>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: Crashes with non-default language environments
Date: Sun, 10 Feb 2008 20:39:45 -0500 [thread overview]
Message-ID: <jwvmyq8e0i4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87prv4l96f.fsf@jurta.org> (Juri Linkov's message of "Mon, 11 Feb 2008 00:48:40 +0200")
>>> This crash is caused by the corrupt byte-code produced by
>>> `byte-compile-lapcode'. `string-make-unibyte' at the end of this
>>> function produces different bytecode strings in different
>>> language environments. This problem can be narrowed down to:
>>
>> Shouldn't it be string-to-unibyte instead?
> I've just checked that `string-as-unibyte' produces even worse results
> than `string-make-unibyte'. It replaces every byte in the original
> string with 2-byte sequences.
Of course, string-AS-unibyte is the worst of all three. But nobody
suggested to use that one. I just suggested to replace
string-MAKE-uniybte by string-TO-unibyte.
string-TO-unibyte ~= (encode-coding-string STR 'binary)
string-AS-unibyte ~= (encode-coding-string STR 'emacs-internal)
(unicode or emacs-mule, depending on the Emacs version)
string-MAKE-unibyte ~= (encode-coding-string STR locale-coding-system)
Stefan
next prev parent reply other threads:[~2008-02-11 1:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 19:54 Crashes with non-default language environments Juri Linkov
2008-02-09 22:17 ` Juri Linkov
2008-02-10 2:09 ` Stefan Monnier
2008-02-10 22:48 ` Juri Linkov
2008-02-11 1:39 ` Stefan Monnier [this message]
2008-02-11 1:56 ` Miles Bader
2008-02-11 3:02 ` Stefan Monnier
2008-02-11 4:11 ` Miles Bader
2008-02-11 14:06 ` Stefan Monnier
2008-02-11 15:16 ` Miles Bader
2008-02-11 16:51 ` Stefan Monnier
2008-02-11 21:27 ` Juri Linkov
2008-02-12 11:41 ` Kenichi Handa
2008-02-12 16:29 ` Stefan Monnier
2008-02-12 11:23 ` Kenichi Handa
2008-02-12 19:29 ` Juri Linkov
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=jwvmyq8e0i4.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-pretest-bug@gnu.org \
--cc=juri@jurta.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.
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).