From: Achim Gratz <Stromeko@nexgo.de>
To: 12598@debbugs.gnu.org
Subject: bug#12598: 24.2; utf-8 codepoints in doc-strings and compression of .el and .elc files
Date: Sun, 07 Oct 2012 22:05:23 +0200 [thread overview]
Message-ID: <87391qavzw.fsf@Rainer.invalid> (raw)
In-Reply-To: <877gr2b2in.fsf@Rainer.invalid>
Stefan Monnier writes:
>> I've just removed some utf-8 codepoints from docstrings in org-mode
>> because when I compress either the source (.el.gz) or the resulting
>> byte-compiled file (.elc.gz), the loader fails after the first function
>> definition that has such a docstring.
>
> Sounds like a bug. Can you send a precise recipe?
The org.el currently in trunk should demonstrate it: compress the
bytecompiled file with gzip, then try to (load "org") with the load-path
set so that it finds those compressed files. With the byte-compiled
file you'll then get this error:
Debugger entered--Lisp error: (void-variable defalias)
eval-buffer(#<buffer *load*> nil "/home/emacs/lisp/org/org.elc.gz" nil t) ; Reading at buffer position 317443
load-with-code-conversion("/home/emacs/lisp/org/org.elc.gz" "/home/emacs/lisp/org/org.elc.gz" nil nil)
load("org.elc")
eval((load "org.elc"))
eval-expression((load "org.elc") nil)
call-interactively(eval-expression nil nil)
The corresponding line in the source is L9026 (the defun for the second
function that has unicode in the docstring).
The exact same error happens in Emacs 23.3, btw.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2012-10-07 20:05 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 [this message]
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
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=87391qavzw.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=12598@debbugs.gnu.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).