From: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
To: Dario Hamidi <dario.hamidi@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: src blocks in texinfo export
Date: Tue, 12 Feb 2013 11:32:28 -0500 [thread overview]
Message-ID: <CAEWDx5cowXcFdmK0iMss-DMVGRtGvLbSxurR8Dp8KXMi9AqKyg@mail.gmail.com> (raw)
In-Reply-To: <87liat35ny.fsf@sofia.zeitform.net>
[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]
Hello Dario,
On 12 February 2013 10:36, Dario Hamidi <dario.hamidi@gmail.com> wrote:
> Hello,
>
> I discovered a problem when exporting source blocks containing braces to
> texinfo using `ox-texinfo'. The texinfo exporter wraps source blocks
> into a `example' environment, which takes care of source block
> indentation but doesn't allow any braces to occur in the contained text,
> since braces have a special meaning in TeX.
>
> After reading the `texinfo' manual, it became clear that literal examples
> should be exported also in a `verbatim' environment. A patch making
> this change to the exporter is attached.
>
Using your patch as is would wrap the source blocks in both example and
verbatim blocks. If going with verbatim it would be better to remove all
references to @example/@end example.
I had chosen to go with @example rather than @verbatim because it does state
that lisp blocks should be wrapped in @lisp which is synonymous to @example.
It should be possible to escape any braces or @ before inserting them into
the
example block to ensure there is no expansion.
The only differences in using @verbatim over escaping any characters in
@example are the following:
- Tabs are treated as tabs and not as single spaces
- The code block is not indented.
Regards,
Jon
> Dario
>
[-- Attachment #2: Type: text/html, Size: 2035 bytes --]
next prev parent reply other threads:[~2013-02-12 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 15:36 src blocks in texinfo export Dario Hamidi
2013-02-12 16:32 ` Jonathan Leech-Pepin [this message]
2013-02-12 22:09 ` Dario Hamidi
2013-03-10 19:49 ` Jonathan Leech-Pepin
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=CAEWDx5cowXcFdmK0iMss-DMVGRtGvLbSxurR8Dp8KXMi9AqKyg@mail.gmail.com \
--to=jonathan.leechpepin@gmail.com \
--cc=dario.hamidi@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
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).