emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Randomcoder <randomcoder1@gmail.com>
To: emacs-orgmode@gnu.org
Subject: [proposal] better documentation around syntax highlighting Org-Mode code blocks when exporting to LaTeX
Date: Tue, 17 Mar 2015 16:50:08 +0200	[thread overview]
Message-ID: <20150317145008.GB14053@xw> (raw)

Hi,

While writing technical documents, as a programmer and an Org-Mode user,
for me it's important to have ways to syntax highlight code blocks when
exporting them to LaTeX.

While I am aware of the customizations that need to be done
to Org-Mode's configuration in order to get that to work, in
particular customizing these variables(see [1] for details):

* org-latex-listings
* org-latex-custom-lang-environments
* org-latex-minted-options

and having tried them, I got this working for one document, but it
really felt like a lot of trial-and-error and a lot of room for error
on my side as a user.

Although this is Org-Mode and it is supposed to be very customizable
(like Emacs is), I still believe the documentation and the implementation
can be improved on this.

I think there's even reason to believe that this should be working out
of the box. The only reason I see for this not being the default setting
is to not add pygments [2] as a dependency. Still, I think it should be
much easier for me as a user to spend less time getting it to work.

I welcome any feedback on this.

Thank you for taking the time to read my proposal.


[1] http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-2
[2] http://pygments.org/

next             reply	other threads:[~2015-03-17 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 14:50 Randomcoder [this message]
2015-03-17 15:02 ` [proposal] better documentation around syntax highlighting Org-Mode code blocks when exporting to LaTeX Nicolas Goaziou

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=20150317145008.GB14053@xw \
    --to=randomcoder1@gmail.com \
    --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

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