From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Randomcoder <randomcoder1@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [proposal] better documentation around syntax highlighting Org-Mode code blocks when exporting to LaTeX
Date: Tue, 17 Mar 2015 16:02:47 +0100 [thread overview]
Message-ID: <87y4mvzmy0.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20150317145008.GB14053@xw> (Randomcoder's message of "Tue, 17 Mar 2015 16:50:08 +0200")
Hello,
Randomcoder <randomcoder1@gmail.com> writes:
> 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
Did you read `org-latex-listings' docstring? If so, what do you think is
missing or not clear enough?
> 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.
What do you suggest, concretely?
> I think there's even reason to believe that this should be working out
> of the box.
I think the default value is right. Any other value requires the user
additional steps (requiring "listings" package or even adding pygments
as a dependency)
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2015-03-17 15:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 14:50 [proposal] better documentation around syntax highlighting Org-Mode code blocks when exporting to LaTeX Randomcoder
2015-03-17 15:02 ` Nicolas Goaziou [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
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=87y4mvzmy0.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=randomcoder1@gmail.com \
/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).