emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Gauland <mikelygee@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: "Org" source blocks and minted
Date: Thu, 1 Apr 2021 21:07:00 +1300	[thread overview]
Message-ID: <82ce0f04-bf55-94b6-73a2-52010bbaa2b0@gmail.com> (raw)
In-Reply-To: <878s6adt9i.fsf@posteo.net>

Yes, this looks very promising. I'm looking forward to playing with it
when I have more time.

On 27/03/21 12:55 am, Juan Manuel Macías wrote:
> Hi  Timothy,
> I really like your approach. And it is org/emacscentric! Minted has
> never quite convinced me, and gives me some trouble with certain
> packages in LuaLaTeX that I have not been able to solve. Thank you for
> this promising alternative.
> Best regards,
> Juan Manuel 
> Timothy <tecosaur@gmail.com> writes:
>> Juan mentioned an Org lexer exists, but another approach that may be of
>> interest is using Emacs' own font-lock. I wrote a package that's like
>> HTMLize but works with LaTeX and currently have it sitting in my config.
>> I plan on submitting a patch to Org at some point on this, but for now:
>> - https://github.com/tecosaur/engrave-faces
>> - https://tecosaur.github.io/emacs-config/config.html#pretty-code-blocks
>> Sample output: all the code blocks in
>> https://tecosaur.github.io/emacs-config/config.pdf
>> Since this uses Emacs' font-lock, this means that you can use any
>> language that you have a syntax-highlighting-mode for :)

      reply	other threads:[~2021-04-01  8:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24  1:33 "Org" source blocks and minted Michael Gauland
2021-03-24  4:18 ` Juan Manuel Macías
2021-03-24  4:24 ` Timothy
2021-03-26 11:55   ` Juan Manuel Macías
2021-04-01  8:07     ` Michael Gauland [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:

  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=82ce0f04-bf55-94b6-73a2-52010bbaa2b0@gmail.com \
    --to=mikelygee@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).