emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Richard Stanton <stanton@haas.berkeley.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Error when running org-babel-tangle
Date: Thu, 5 Mar 2015 18:31:51 -0800	[thread overview]
Message-ID: <alpine.OSX.2.00.1503051829310.1906@charles-berrys-macbook.local> (raw)
In-Reply-To: <alpine.OSX.2.00.1503051702250.1846@charles-berrys-macbook.local>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1219 bytes --]

On Thu, 5 Mar 2015, Charles C. Berry wrote:

> On Thu, 5 Mar 2015, Richard Stanton wrote:
>
>> I’m experimenting with tangling files in org-mode, and have found
>> that certain files cause org-babel-tangle to ie with an error
>> (Org-mode version 8.3beta (release_8.3beta-884-g9ed426). Here’s a
>> small example:
>
>> 
>> ————————————
>> 
>> * Sample code
>> 
>> #+BEGIN_SRC makefile :tangle makefile-main
>> circle:
>> 	@gfortran -c circle.f90
>> 
>> main: circle
>> 	@gfortran -c main.f90
>> 	@gfortran circle.o main.o -o main
>> 
>> clean:
>> 	@rm -f *.o main
>> #+END_SRC
>> 
>> Run this block to tangle out the new files.
>> 
>> #+BEGIN_SRC emacs-lisp
>> (org-babel-tangle)
>> #+END_SRC
>> 
>> #+RESULTS:
>> | makefile-main |
>> 
>> In this block I use this header:
>> #+BEGIN_EXAMPLE
>> #+BEGIN_SRC sh :results raw
>> #+END_EXAMPLE
>> 
>
> [rest deleted]
>
> ===
>
> #+BEGIN_EXAMPLE
>  ,#+BEGIN_SRC sh :results raw #+END_EXAMPLE
>
> will work. The comma is stripped on export.
>
> If you use org-edit-src (C-c C-c) on your original example block, it
> will format it in that way automagically.

Whoops!

Make that =C-c ' C-c '= or (org-edit-src) followed by (org-edit-src-exit).

Chuck

  reply	other threads:[~2015-03-06  2:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 22:50 Error when running org-babel-tangle Richard Stanton
2015-03-06  1:08 ` Charles C. Berry
2015-03-06  2:31   ` Charles C. Berry [this message]
2015-03-06  4:13   ` Richard Stanton

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=alpine.OSX.2.00.1503051829310.1906@charles-berrys-macbook.local \
    --to=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=stanton@haas.berkeley.edu \
    /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).