From: Kenichi Handa <handa@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Stromeko@nexgo.de, 12598@debbugs.gnu.org
Subject: bug#12598: 24.2; utf-8 codepoints in doc-strings and compression of .el and .elc files
Date: Sun, 03 Feb 2013 20:44:16 +0900 [thread overview]
Message-ID: <87vca94o6n.fsf@gnu.org> (raw)
In-Reply-To: <jwv4nhwrv0k.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 01 Feb 2013 09:06:45 -0500)
In article <jwv4nhwrv0k.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
> We could, but I suspect that the problem (and the fix) would be the same
> for all file-name-handlers. IOW, the problem is not in how to access
> the file's contents, but in how eval-buffer (used by
> load-with-code-conversion) doesn't handle byte-compiled file correctly.
Should eval-buffer handle byte-compiled code in a buffer?
---
Kenichi Handa
handa@gnu.org
next prev parent reply other threads:[~2013-02-03 11:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 17:44 bug#12598: 24.2; utf-8 codepoints in doc-strings and compression of .el and .elc files Achim Gratz
2012-10-07 19:40 ` Stefan Monnier
2012-10-07 20:05 ` Achim Gratz
2012-10-07 21:15 ` Andreas Schwab
2012-10-08 5:24 ` Achim Gratz
2012-10-08 5:36 ` Achim Gratz
2013-01-31 18:15 ` Stefan Monnier
2013-01-31 18:37 ` Achim Gratz
2013-02-01 9:23 ` Kenichi Handa
2013-02-01 14:06 ` Stefan Monnier
2013-02-03 11:44 ` Kenichi Handa [this message]
2013-02-03 16:04 ` Stefan Monnier
2013-02-05 13:40 ` Kenichi Handa
2013-02-05 17:43 ` Stefan Monnier
2013-02-06 0:46 ` Kenichi Handa
2013-02-03 16:06 ` Stefan Monnier
2013-02-06 15:02 ` Stefan Monnier
2013-02-09 5:05 ` Kenichi Handa
2013-02-09 9:16 ` Eli Zaretskii
2013-02-09 14:51 ` Kenichi Handa
2014-04-23 3:11 ` Stefan Monnier
2022-04-23 16:18 ` Lars Ingebrigtsen
2022-04-25 9:19 ` Michael Albinus
2022-04-25 9:45 ` Lars Ingebrigtsen
2022-06-02 9:51 ` Lars Ingebrigtsen
2013-02-08 17:43 ` Stefan Monnier
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=87vca94o6n.fsf@gnu.org \
--to=handa@gnu.org \
--cc=12598@debbugs.gnu.org \
--cc=Stromeko@nexgo.de \
--cc=monnier@iro.umontreal.ca \
/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).