From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii Subject: bug#28806: syntax highlighting in ox-odt and emacs26+ broken Date: Fri, 09 Feb 2018 10:57:05 +0200 Message-ID: <83mv0i4k2m.fsf@gnu.org> References: <87wp3za7cs.fsf@gmail.com> <837evzlc7a.fsf@gnu.org> <871shvulrw.fsf@killashandra.ballybran.fr> Reply-To: Eli Zaretskii Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33144) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ek4VR-0001Ko-T1 for emacs-orgmode@gnu.org; Fri, 09 Feb 2018 03:58:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ek4VO-0006BH-0j for emacs-orgmode@gnu.org; Fri, 09 Feb 2018 03:58:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:54958) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ek4VN-0006B7-Rx for emacs-orgmode@gnu.org; Fri, 09 Feb 2018 03:58:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ek4VN-0006pM-Kl for emacs-orgmode@gnu.org; Fri, 09 Feb 2018 03:58:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <871shvulrw.fsf@killashandra.ballybran.fr> (pierre.techoueyres@free.fr) 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: Pierre =?UTF-8?Q?T=C3=A9choueyres?= Cc: jaygkamat@gmail.com, 28806@debbugs.gnu.org > From: pierre.techoueyres@free.fr (Pierre Téchoueyres) > Cc: Jay Kamat , 28806@debbugs.gnu.org > Date: Fri, 09 Feb 2018 00:03:31 +0100 > > > 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. > > > > Hi Eli, > I don't know if you noticed it but the fact that the uncompiled version > is working as expected or that an compiled one with an older emacs > (version 25 for example) tend to indicate a problem on the emacs side. > > I can also add that forcing reevaluation of > `org-odt-do-format-code' solve the problem. > > Can this be considered as an evidence that the problem is on the emacs > side ? No, I don't think so. All of the above can be the result of some Org specific problem. That's why I suggested that the Org developers look into this issue first.