emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: reza <reza@housseini.me>
To: "Org Mode List" <emacs-orgmode@gnu.org>
Subject: Re: Syntax highlighting for julia source blocks
Date: Mon, 26 Sep 2022 15:18:33 +0000	[thread overview]
Message-ID: <010201837a60e332-a5c36637-9ebc-4bf0-acc1-ddd8d21ac7f9-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <87illab20i.fsf@ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 528 bytes --]

On 9/26/22 17:15, Fraga, Eric wrote:
> On Monday, 26 Sep 2022 at 14:09, reza wrote:
>> When exporting to html, syntax highlighting is automatically applied to
>> exported python source blocks (syntax elements get a span element
>> applied). But this does not work for julia source code blocks. Is this
>> just not implemented or do I miss something?
> 
> What are you using to convert src blocks to HTML?  Specifically, what is
> the setting of org-html-htmlize-output-type?

it is set to `css', this is the correct choice, no?

[-- Attachment #2: OpenPGP_0xC375C6AF05125C52.asc --]
[-- Type: application/pgp-keys, Size: 15557 bytes --]

[-- Attachment #3: OpenPGP_signature --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

  parent reply	other threads:[~2022-09-26 15:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dc63ff58-575d-1a3c-8072-b6199bd0daa4@housseini.me>
2022-09-26 14:09 ` Syntax highlighting for julia source blocks reza
2022-09-26 15:15   ` Fraga, Eric
     [not found]     ` <f0ee94af-c8b8-ff6d-e6c3-5a94527c9568@housseini.me>
2022-09-26 15:18       ` reza [this message]
2022-09-27  6:57         ` Fraga, Eric
     [not found]     ` <8982e37e-88cb-5f5d-6163-b52520307690@housseini.me>
2022-09-26 15:29       ` reza
2022-09-27  1:41         ` Ihor Radchenko
     [not found]           ` <2db697de-82c3-3b81-ecaa-7b90781c0e28@housseini.me>
2022-09-27  6:46             ` reza

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=010201837a60e332-a5c36637-9ebc-4bf0-acc1-ddd8d21ac7f9-000000@eu-west-1.amazonses.com \
    --to=reza@housseini.me \
    --cc=emacs-orgmode@gnu.org \
    /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 public 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).