Eric Schulte writes:
> Rainer M Krug writes:
>
>> Hi
>>
>> I assume this is related to this discussion and the patches: after
>> updating this morning, get an error message after tangling:
>> variable padline void. This goes away after reverting to 8.2 2 release.
>>
>> Default settings for padli
Vladimir Lomov writes:
> Hello,
> ** Eric Schulte [2013-09-28 06:17:51 -0600]:
>
>
>>> The blank line which was inserted between blocks isn't anymore for me.
>
>>> ECM:
>
>>> --8<---cut here---start->8---
>>> * Tangle these blocks
>>> :PROPERTIES:
>>> :tang
Rainer M Krug writes:
> Hi
>
> I assume this is related to this discussion and the patches: after
> updating this morning, get an error message after tangling:
> variable padline void. This goes away after reverting to 8.2 2 release.
>
> Default settings for padline used.
>
> Cheers,
>
> Rainer
Hi
I assume this is related to this discussion and the patches: after
updating this morning, get an error message after tangling:
variable padline void. This goes away after reverting to 8.2 2 release.
Default settings for padline used.
Cheers,
Rainer
"Sebastien Vauban"
writes:
> Hi Eric,
Hello,
** Eric Schulte [2013-09-28 06:17:51 -0600]:
>> 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
Hi Eric,
Eric Schulte wrote:
>> The blank line which was inserted between blocks isn't anymore for me.
>>
>> [...] results in:
>>
>> --8<---cut here---start->8---
>> "data"
>> "datb"
>> --8<---cut here---end--->8---
>>
>>
>
> 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"
> #
Hi Eric,
Eric Schulte wrote:
> "Sebastien Vauban" writes:
>> Eric Schulte wrote:
>>> aditya siram 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
Hi Eric,
Eric Schulte wrote:
> "Sebastien Vauban" writes:
>> Eric Schulte wrote:
>>> aditya siram 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
"Sebastien Vauban" writes:
> Hi Eric,
>
> Eric Schulte wrote:
>> aditya siram 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
Hi Eric,
Eric Schulte wrote:
> aditya siram 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
aditya siram writes:
> Hi all,
> 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.
> Thanks!
aditya siram wrote:
> What's the rationale for having padlines by default in tangled source?
It generates more readable source-code, as blocks are not "glued" next to each
other.
> It generates wrong programs for languages where whitespace is significant
> (Haskell) and, for me, doesn't noticeabl
Hi all,
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.
Thanks!
-deech
14 matches
Mail list logo
