From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jay Kamat Subject: Re: Bug: syntax highlighting in ox-odt and emacs26+ broken [9.1.2 (9.1.2-elpa @ /home/jay/Code/tmp/emacs/lisp/org/)] Date: Wed, 18 Oct 2017 00:47:52 -0400 Message-ID: <874lqxuknb.fsf@gmail.com> References: <87r2ucb1qn.fsf@gmail.com> <87shesc7bt.fsf@gmail.com> <87mv4zbp38.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52769) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e4gGt-0008Gl-OQ for emacs-orgmode@gnu.org; Wed, 18 Oct 2017 00:48:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e4gGq-0004ro-NW for emacs-orgmode@gnu.org; Wed, 18 Oct 2017 00:47:59 -0400 Received: from mail-qt0-x22e.google.com ([2607:f8b0:400d:c0d::22e]:55099) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e4gGq-0004qP-I2 for emacs-orgmode@gnu.org; Wed, 18 Oct 2017 00:47:56 -0400 Received: by mail-qt0-x22e.google.com with SMTP id z19so8267029qtg.11 for ; Tue, 17 Oct 2017 21:47:55 -0700 (PDT) Received: from laythe (res404s-128-61-104-57.res.gatech.edu. [128.61.104.57]) by smtp.gmail.com with ESMTPSA id y11sm6740951ywc.70.2017.10.17.21.47.53 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 17 Oct 2017 21:47:53 -0700 (PDT) In-Reply-To: <87mv4zbp38.fsf@gmail.com> (Jay Kamat's message of "Tue, 10 Oct 2017 00:31:55 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org I submitted a bug report to emacs core, and Eli says: > 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. http://lists.gnu.org/archive/html/emacs-orgmode/2017-10/msg00163.html I tried to take a look at this, but this problem seems more subtle than I originally thought. The `org-odt-src-block' function seems to be returning the exact same thing in both scenarios, so the problem (unfortunately) must be related to the highest level (where the odt is stitched together). I'll try to keep looking at this, but I would appreciate if someone else could take a look. I would also be happy to accept any pointers relating to the ox-odt build process. -Jay Jay Kamat writes: > Hi Tim, > >> My recommendation would be to confirm if the problem exists in the org >> bundled with Emacs 26 (9.1.1) and if it is, report this on the emacs >> devel list, making it clear the issue does not exist with emacs >> 25.3. This will at least allow Emacs devel to note that something which >> it is changing is either buggy and needs more work or is an incompatible >> change for org (and possibly other modes) which will need to be >> added to the changes/News file and addressed by mode authors prior to 26 >> being released. > > This bug does indeed exist in the org bundled with emacs. Reporting this > to emacs-devel sounds like a good plan, and I'll do so in a couple days > to let anyone on the org mailing list have a chance to correct me if I'm > doing anything wrong on the org side. But I do agree this looks like a > bug in emacs core (even though I wansn't able to find the cause). > > -Jay