From: Suvayu Ali <email@example.com> To: Tom <firstname.lastname@example.org> Cc: email@example.com Subject: Re: XML src block syntax highlighting Date: Fri, 26 Apr 2013 08:50:36 +0200 [thread overview] Message-ID: <20130426065036.GB2769@kuru.dyndns-at-home.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Thu, Apr 25, 2013 at 05:03:37PM +0200, Tom wrote: > Suvayu Ali <email@example.com> schrieb: > > >On Thu, Apr 25, 2013 at 11:57:49AM +0200, Tom wrote: > >> > >> #+BEGIN_SRC xml :exports code > >> <?xml version="1.0" encoding="utf-8"?> > >> <validxml> > >> ... > >> </validxml> > >> #+END_SRC > >> > >> I have org-src-fontify-natively = and it works for other code, but > >xml > >> is fontified as a fundamental buffer, not like nxml-mode shows the > >> block contents. nxml-mode /is/ used when I use C-c ' to edit the > >> contents. > > > >Can you try the following: > > > > #+BEGIN_SRC nxml :exports code > > .. > > #+END_SRC > > > >As far as I know, the language is supposed to be the leading part of > ><some>-mode. My information is a bit outdated, so I could be wrong. > > I should have written that in my OP: I tried that to no avail. > > I also tried > > (add-to-list 'org-src-lang-modes '("xml" . nxml)) Sorry, I cannot reproduce this. I tried (setq org-src-fontify-natively t) and both of the following work for me. #+BEGIN_SRC xml :exports code .. #+END_SRC #+BEGIN_SRC nxml :exports code .. #+END_SRC Maybe it is your configuration? Did you try a binary search on it? Comment out half of it at a time and you should be able to find the problem lines in no time! GL, -- Suvayu Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-04-26 6:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-25 9:57 Tom 2013-04-25 14:24 ` Suvayu Ali 2013-04-25 15:03 ` Tom 2013-04-26 6:50 ` Suvayu Ali [this message] 2013-04-26 7:07 ` Tom
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 List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20130426065036.GB2769@kuru.dyndns-at-home.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: XML src block syntax highlighting' \ /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
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).