From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#28806: syntax highlighting in ox-odt and emacs26+ broken Date: Fri, 13 Oct 2017 10:49:13 +0300 Message-ID: <837evzlc7a.fsf@gnu.org> References: <87wp3za7cs.fsf@gmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1507881030 20572 195.159.176.226 (13 Oct 2017 07:50:30 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 13 Oct 2017 07:50:30 +0000 (UTC) Cc: 28806@debbugs.gnu.org To: Jay Kamat Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Oct 13 09:50:24 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e2ujQ-0002bG-JV for geb-bug-gnu-emacs@m.gmane.org; Fri, 13 Oct 2017 09:50:08 +0200 Original-Received: from localhost ([::1]:48822 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e2ujW-0003op-Dt for geb-bug-gnu-emacs@m.gmane.org; Fri, 13 Oct 2017 03:50:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48299) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e2ujQ-0003mn-Ka for bug-gnu-emacs@gnu.org; Fri, 13 Oct 2017 03:50:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e2ujM-0004GG-Aw for bug-gnu-emacs@gnu.org; Fri, 13 Oct 2017 03:50:08 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:56326) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e2ujM-0004Fo-6k for bug-gnu-emacs@gnu.org; Fri, 13 Oct 2017 03:50:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e2ujK-0005PD-9s for bug-gnu-emacs@gnu.org; Fri, 13 Oct 2017 03:50:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 13 Oct 2017 07:50:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 28806 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 28806-submit@debbugs.gnu.org id=B28806.150788097620736 (code B ref 28806); Fri, 13 Oct 2017 07:50:02 +0000 Original-Received: (at 28806) by debbugs.gnu.org; 13 Oct 2017 07:49:36 +0000 Original-Received: from localhost ([127.0.0.1]:36774 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e2uit-0005ON-LG for submit@debbugs.gnu.org; Fri, 13 Oct 2017 03:49:35 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:57186) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1e2uiq-0005O8-7d for 28806@debbugs.gnu.org; Fri, 13 Oct 2017 03:49:34 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e2uig-0003Ov-Lb for 28806@debbugs.gnu.org; Fri, 13 Oct 2017 03:49:27 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:32913) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e2uig-0003On-HY; Fri, 13 Oct 2017 03:49:22 -0400 Original-Received: from [176.228.60.248] (port=1155 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1e2uif-0002on-LS; Fri, 13 Oct 2017 03:49:22 -0400 In-reply-to: <87wp3za7cs.fsf@gmail.com> (message from Jay Kamat on Fri, 13 Oct 2017 02:29:23 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:138325 Archived-At: > From: Jay Kamat > Date: Fri, 13 Oct 2017 02:29:23 -0400 > > 1. Compile Emacs *26* from source (emacs-26 branch) > 2. Load an org file with the following (built-in org): > > #+BEGIN_SRC c > int main() { > return 0; > } > #+END_SRC > > 3. Export to odt via C-c C-e o o > 4. Open file in libreoffice > > Expected Results > > Syntax highlighting for the code block as in emacs25 > > Actual Results > > Code seems to be colored in a single color, interestingly, this is *not* > black. > > (I can provide screenshots if that would be helpful) > > After poking around, I found a bit more information on how to reproduce > it: > > Environments with working syntax export: > 1. Emacs25, always (unless unrelated errors are present) > 2. Emacs26, when running org compiled with emacs 25 (from elpa/repo) > 3. Emacs26, when running org 'interpreted' (not compiled to bytecode) > > Environments with broken syntax export: > 1. Emacs26 when compiled from source, using builtin org > 2. Emacs26 when org is compiled with Emacs 26 (from elpa/repo) > > I tested all emacs versions on org 0b83168465, changing which version > org was compiled with by modifying the EMACS variable in local.mk in > org. I ran everything in ~emacs -Q~. > > I attempted to bisect emacs to find which change in emacs is causing > this, bug I wasn't able to compile some older versions of emacs due to > internal bytecode errors preventing a clean compilation. I was able to > find that it was '14 revisions away from 5f3379b338' but I don't know if > that's helpful. > > >From what I can tell (which is probably incorrect), this seems like > either: > > 1. A bug in the new bytecode > 2. Some backwards-incompatible change to macros in emacs 26 that org > didn't pick up on. > > In the latter case, the change should be added to the NEWS file as a > backwards incompatible change. > > A stackexchange question about this is here: > https://emacs.stackexchange.com/questions/36023/how-to-export-babel-source-blocks-with-syntax-highlighting-to-odt-in-org-mode-in > > I posted in the org mode mailing list about this to try to get some > initial feedback from orgmode before posting here: > http://lists.gnu.org/archive/html/emacs-orgmode/2017-10/msg00161.html Thanks. Having read all of the references and discussions you've provided, I see no evidence that this is an Emacs issue, as opposed to an Org issue. I think the Org developers should take a look at this first, and only if they provide clear evidence that the problem is due to Emacs, should the problem come here.