From: Adonay Felipe Nogueira <adfeno@hyperbola.info>
To: 30961@debbugs.gnu.org
Subject: bug#30961: Byte compilation problem with emacs-org
Date: Tue, 27 Mar 2018 11:43:55 -0300 [thread overview]
Message-ID: <87muytefys.fsf@hyperbola.info> (raw)
In-Reply-To: <m1y3idwqfr.fsf@fastmail.net> (Konrad Hinsen's message of "Tue, 27 Mar 2018 16:20:24 +0200")
> happens when the newer org-mode is byte-compiled, and leads to wrong
> .elc files.
Doesn't the official Emacs docs recommend against byte compiling? Why we
have such nasty thing here?
I also noticed some odd behavior with emacs-org coming from GNU Guix,
mainly causing the impossibility of exporting a simple document as this
to LaTeX or to PDF:
--8<---------------cut here---------------start------------->8---
#+TITLE: Test
* A test
Yes, a test.
--8<---------------cut here---------------end--------------->8---
I'll make another detailed bug report about this specific issue once I
have time to take more information.
--
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
(apenas sem DRM), PNG, TXT, WEBM.
next prev parent reply other threads:[~2018-03-27 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 14:20 bug#30961: Byte compilation problem with emacs-org Konrad Hinsen
2018-03-27 14:43 ` Adonay Felipe Nogueira [this message]
2018-03-31 8:23 ` Konrad Hinsen
2019-12-08 21:38 ` Maxim Cournoyer
2019-12-09 8:52 ` Konrad Hinsen
2019-12-13 2:06 ` T460s laptop
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87muytefys.fsf@hyperbola.info \
--to=adfeno@hyperbola.info \
--cc=30961@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.