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: Tue, 10 Oct 2017 00:31:55 -0400 Message-ID: <87mv4zbp38.fsf@gmail.com> References: <87r2ucb1qn.fsf@gmail.com> <87shesc7bt.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40217) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e1mD3-0001ND-5O for emacs-orgmode@gnu.org; Tue, 10 Oct 2017 00:32:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e1mD0-0001jt-3L for emacs-orgmode@gnu.org; Tue, 10 Oct 2017 00:32:01 -0400 Received: from mail-qt0-x232.google.com ([2607:f8b0:400d:c0d::232]:44546) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e1mCz-0001jo-V5 for emacs-orgmode@gnu.org; Tue, 10 Oct 2017 00:31:58 -0400 Received: by mail-qt0-x232.google.com with SMTP id 8so2015108qtv.1 for ; Mon, 09 Oct 2017 21:31:57 -0700 (PDT) In-Reply-To: <87shesc7bt.fsf@gmail.com> (Tim Cross's message of "Tue, 10 Oct 2017 08:57:58 +1100") 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: Tim Cross Cc: emacs-orgmode@gnu.org 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