emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: [Babel] Blank line preceeds tangled data
Date: Fri, 26 Aug 2011 06:20:44 -0400	[thread overview]
Message-ID: <87aaaw324j.fsf@norang.ca> (raw)
In-Reply-To: <CAGhLh6GjHOx9crChvLx=UbsaiU=TYhzL51uuDgLp0vQ8U9i1gg@mail.gmail.com> (Rainer M. Krug's message of "Fri, 26 Aug 2011 11:17:41 +0200")

Rainer M Krug <r.m.krug@gmail.com> writes:

> On Fri, Aug 26, 2011 at 6:35 AM, Nick Dokos <nicholas.dokos@hp.com>
> wrote:
>
>     Bernt Hansen <bernt@norang.ca> wrote:
>    
>     > Hi,
>     >
>     > When I tangle some file such as
>     >
>     > #+begin_src sh :tangle x.sh
>     >   #!/bin/sh
>     >   echo done
>     > #+end_src
>     >
>     > I get the following output which includes a blank line up
>     front.
>     >
>     > ,----[ x.sh ]
>     > |
>     > | #!/bin/sh
>     > | echo done
>     > `----
>     >
>     > Doesn't this break the shebang line on unix?  I don't think the
>     leading
>     > blank line should be in the tangled output.
>     >
>    
>     Not sure why it's there (I'm sure Eric S. will enlighten us)
>     but you can get rid of it with :padline no.
>
>
> and there is also the :shebang parameter to specify the shebang, so
>
>
> #+begin_src sh :tangle x.sh :shebang #!bin/sh :padline no
>  echo done
> #+end_src
>
> will give you the expected file x.sh. No idea why it is not enabled
> in your config.

Thanks Rainer and Nick!

I didn't know about either of these babel options.

The :shebang line works for me.

Regards,
Bernt

      reply	other threads:[~2011-08-26 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26  1:15 [Babel] Blank line preceeds tangled data Bernt Hansen
2011-08-26  4:35 ` Nick Dokos
2011-08-26  9:17   ` Rainer M Krug
2011-08-26 10:20     ` Bernt Hansen [this message]

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=87aaaw324j.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    --cc=r.m.krug@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).