emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Giuseppe Lipari <giulipari@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Cannot export bash src
Date: Tue, 23 Feb 2016 10:23:20 +0000	[thread overview]
Message-ID: <CABHo5SDiK3ABNx1-XJxHZVAqqLSYMSmwYA76D7K1Nsma3vOu0A@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

Hello,

I have a strange behaviour when trying to produce a beamer presentation .

I have a rather complicated set of slides, one of the slide contains this
snippet:

%--------- snippet ----------%
** CGI - producing output
- Example in shell script:
#+BEGIN_SRC bash
  echo "content-type: text/html"
  echo
  echo "<!doctype html publi\"-//w3c/dtd html 3.2 final/en\">"
  echo "<html>"
  echo "<body>"
  echo "it is <b>"`date`"</b>"
  echo "</body>"
  echo "</html>"
#+END_SRC
%--------- snippet ----------%

I use minted for formatting the visual output.
When I try to export to beamer, it stops well before the export with the
following error:

[...]
org-babel-exp process emacs-lisp at line 16...
org-babel-exp process html at line 114...
org-babel-exp process html at line 164...
org-babel-exp process bash at line 270...
byte-code: Invalid search bound (wrong side of point)


If I comment the above snippet, everything is all right, so I think it
should be the culprit.
However, if I isolate the above snippet in separate org file, the pdf file
is produced all right.

Anybody has any idea of what is going on? I am available to give you more
information (my init.org, and the whole org file, if necessary).


Giuseppe Lipari

[-- Attachment #2: Type: text/html, Size: 1816 bytes --]

             reply	other threads:[~2016-02-23 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 10:23 Giuseppe Lipari [this message]
2016-02-26  3:05 ` Cannot export bash src Grant Rettke

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=CABHo5SDiK3ABNx1-XJxHZVAqqLSYMSmwYA76D7K1Nsma3vOu0A@mail.gmail.com \
    --to=giulipari@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).