From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Eric Schulte <schulte.eric-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [Babel] Padlines
Date: Fri, 27 Sep 2013 16:53:55 +0200 [thread overview]
Message-ID: <8638oqtiws.fsf@somewhere.org> (raw)
In-Reply-To: <87siwz5gml.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> (Eric Schulte's message of "Fri, 20 Sep 2013 15:26:42 -0600")
Hi Eric,
Eric Schulte wrote:
> "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org> writes:
>> Eric Schulte wrote:
>>> aditya siram <aditya.siram-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>>> What's the rationale for having padlines by default in tangled source? It
>>>> generates wrong programs for languages where whitespace is significant
>>>> (Haskell) and, for me, doesn't noticeably improve the look of the tangled
>>>> file in cases where it isn't.
>>>
>>> It is possible to change the value of default header arguments on a
>>> per-language basis because e.g., while (:padlines "yes") may make sense for
>>> sh, it probably doesn't for Haskell.
>>
>> Could it be possible that ":padline yes" does not insert a blank line in
>> front of the very first block, only *between* all blocks?
>
> I just pushed up a commit which implements this behavior. See the
> attached file for an example.
>
> #+Title: Examples with the new padline behavior
The blank line which was inserted between blocks isn't anymore for me.
ECM:
--8<---------------cut here---------------start------------->8---
* Tangle these blocks
:PROPERTIES:
:tangle: yes
:padline: yes
:END:
#+begin_src emacs-lisp :file test.csv
"data"
#+end_src
#+begin_src emacs-lisp :file test.csv
"datb"
#+end_src
--8<---------------cut here---------------end--------------->8---
results in:
--8<---------------cut here---------------start------------->8---
"data"
"datb"
--8<---------------cut here---------------end--------------->8---
Note that I tried adding ":padline" to yes, but I normally should not, as it is
the default.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-09-27 14:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 22:36 [Babel] Padlines aditya siram
2013-09-18 7:32 ` Sebastien Vauban
2013-09-18 21:23 ` Eric Schulte
2013-09-18 22:02 ` Sebastien Vauban
2013-09-20 21:26 ` Eric Schulte
2013-09-23 7:31 ` Sebastien Vauban
[not found] ` <87siwz5gml.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-09-27 14:53 ` Sebastien Vauban [this message]
2013-09-28 12:17 ` Eric Schulte
2013-09-30 8:54 ` Sebastien Vauban
2013-10-01 10:28 ` Rainer M Krug
2013-10-01 11:59 ` Eric Schulte
2013-10-01 12:53 ` Rainer M Krug
2013-10-01 5:57 ` Vladimir Lomov
2013-10-01 11:59 ` Eric Schulte
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=8638oqtiws.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
--cc=schulte.eric-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).