From: Andreas Schwab <schwab@linux-m68k.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: 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 23:15:43 +0200 [thread overview]
Message-ID: <m2r4pagf0g.fsf@igel.home> (raw)
In-Reply-To: <87391qavzw.fsf@Rainer.invalid> (Achim Gratz's message of "Sun, 07 Oct 2012 22:05:23 +0200")
Achim Gratz <Stromeko@nexgo.de> writes:
> 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)
That's because #@N counts in bytes, not characters.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-10-07 21:15 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 [this message]
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=m2r4pagf0g.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=12598@debbugs.gnu.org \
--cc=Stromeko@nexgo.de \
/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).