From: Rainer M Krug <r.m.krug@gmail.com>
To: nicholas.dokos@hp.com
Cc: Bernt Hansen <bernt@norang.ca>, emacs-orgmode@gnu.org
Subject: Re: [Babel] Blank line preceeds tangled data
Date: Fri, 26 Aug 2011 11:17:41 +0200 [thread overview]
Message-ID: <CAGhLh6GjHOx9crChvLx=UbsaiU=TYhzL51uuDgLp0vQ8U9i1gg@mail.gmail.com> (raw)
In-Reply-To: <5525.1314333321@alphaville.dokosmarshall.org>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
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.
Cheers,
Rainer
>
> Nick
>
>
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax (F): +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
[-- Attachment #2: Type: text/html, Size: 2236 bytes --]
next prev parent reply other threads:[~2011-08-26 9:17 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 [this message]
2011-08-26 10:20 ` Bernt Hansen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGhLh6GjHOx9crChvLx=UbsaiU=TYhzL51uuDgLp0vQ8U9i1gg@mail.gmail.com' \
--to=r.m.krug@gmail.com \
--cc=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.