From: Nicolas Goaziou <n.goaziou@gmail.com>
To: S S <super.quazimodo@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Literal Examples are malformed in exports (to html/tex) [8.0.3 (release_8.0.3-165-g60ca9e @ /home/quazimodo/.emacs.d/vendor/org-mode/lisp/)]
Date: Wed, 29 May 2013 23:36:36 +0200 [thread overview]
Message-ID: <87wqqhfoyj.fsf@gmail.com> (raw)
In-Reply-To: <CAKnJoB6Fhi-XDLOcXnZjERD8EdJD1TZA1xosbc=JyDgx2p_BnQ@mail.gmail.com> (S. S.'s message of "Thu, 30 May 2013 05:45:18 +1000")
S S <super.quazimodo@gmail.com> writes:
> I've added test.org and test_no_init.org along with their html exports plus
> my init.el
> to a gist.
>
> https://gist.github.com/quazimodo/9055aca6167df1398c94
>
> The init.el is long but you'll see from a fast skim there's nothing unusual
> there.
Indeed. But I suspect something wrong in your config: your example
exports correctly here.
> 7.8.11 is used with emacs -q and that seems to export the example blocks
> properly,
> doesn't seem to know what to do with code blocks though.
Constructs like #+begin_code are called "special blocks". They are not
meant to be used for source code. Use #+begin_src instead.
> Do you need more?
What happens if you eval (org-element-at-point) with point on the faulty
#+begin_example line?
Also, what's the value for `org-element-block-name-alist'?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-05-29 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 18:59 Bug: Literal Examples are malformed in exports (to html/tex) [8.0.3 (release_8.0.3-165-g60ca9e @ /home/quazimodo/.emacs.d/vendor/org-mode/lisp/)] S.S
2013-05-29 19:10 ` Nicolas Goaziou
[not found] ` <CAKnJoB5cg-7m0qyh2nun5ANMxg=d9tukTrXEg2d8Oo-fXZDWuw@mail.gmail.com>
[not found] ` <871u8ph9r5.fsf@gmail.com>
2013-05-29 19:45 ` S S
2013-05-29 21:36 ` Nicolas Goaziou [this message]
2013-05-30 1:16 ` S S
2013-05-30 2:20 ` S S
2013-05-30 6:34 ` S S
2013-05-30 7:38 ` Nicolas Goaziou
-- strict thread matches above, loose matches on Subject: below --
2013-05-29 18:15 S.S
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=87wqqhfoyj.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=super.quazimodo@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).