emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: emacs-orgmode@gnu.org, schulte.eric@gmail.com
Subject: Bug: Babel blocks with continuation line at end of block fails to export [7.8.03 (release_7.8.03.542.gdfeac)]
Date: Tue, 06 Mar 2012 12:20:54 -0500	[thread overview]
Message-ID: <87ty21lk7d.fsf@norang.ca> (raw)


Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

     http://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org-mode mailing list.
------------------------------------------------------------------------

Hi Eric,

I ran into a Babel related export problem at work where I took 
a single C source line in a block which has a trailing \ for a
continuation character like the following example.

,----[ test.org ]
| * Text export
| #+begin_src c
|   #define FOO bar \
| #+end_src
`----

If I try to export this file I get a "Beginning of buffer" error and
the export fails.  I can fix it by removing the trailing \ or adding
another line to the end of the block.

This took a while to find in my huge work org file by manually selecting
headings to export until I found the problem block.  I think babel
should probably handle this more gracefully (if possible) and just 
ignore the error and continue.

Thanks for all your great work!!

Regards,
Bernt


Emacs  : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
 of 2010-12-11 on raven, modified by Debian
Package: Org-mode version 7.8.03 (release_7.8.03.542.gdfeac)

             reply	other threads:[~2012-03-06 17:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 17:20 Bernt Hansen [this message]
2012-03-07 17:48 ` Bug: Babel blocks with continuation line at end of block fails to export [7.8.03 (release_7.8.03.542.gdfeac)] Eric Schulte
2012-03-07 18:28   ` Bernt Hansen
2012-03-07 21:19     ` 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=87ty21lk7d.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@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).