all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Pierre Téchoueyres" <pierre.techoueyres@free.fr>
Cc: jaygkamat@gmail.com, 28806@debbugs.gnu.org
Subject: bug#28806: syntax highlighting in ox-odt and emacs26+ broken
Date: Fri, 09 Feb 2018 10:57:05 +0200	[thread overview]
Message-ID: <83mv0i4k2m.fsf@gnu.org> (raw)
In-Reply-To: <871shvulrw.fsf@killashandra.ballybran.fr> (pierre.techoueyres@free.fr)

> From: pierre.techoueyres@free.fr (Pierre Téchoueyres)
> Cc: Jay Kamat <jaygkamat@gmail.com>,  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.

      parent reply	other threads:[~2018-02-09  8:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13  6:29 bug#28806: syntax highlighting in ox-odt and emacs26+ broken Jay Kamat
2017-10-13  7:49 ` Eli Zaretskii
     [not found]   ` <871shvulrw.fsf@killashandra.ballybran.fr>
2018-02-09  8:57     ` Eli Zaretskii [this message]

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=83mv0i4k2m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28806@debbugs.gnu.org \
    --cc=jaygkamat@gmail.com \
    --cc=pierre.techoueyres@free.fr \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.