Eric S Fraga writes:
> Eric Schulte writes:
>
> [...]
>
|> I've just pushed up a minor code change which makes customization of the
|> format of exported code blocks possible. I've added a new
|> customization
>
> I'm coming late to this but just wanted to say thanks! This is very
> nice indee
Eric Schulte writes:
[...]
> I've just pushed up a minor code change which makes customization of the
> format of exported code blocks possible. I've added a new
> customization
I'm coming late to this but just wanted to say thanks! This is very
nice indeed.
--
: Eric S Fraga (GnuPG: 0xC891
t...@tsdye.com (Thomas S. Dye) writes:
> Eric Schulte writes:
>
> As I recall this was originally implemented and then later removed because
> it was causing more confusion and problems than it was worth. I hope it
> hasn't crossed the line of existence more than once. At some point i
Eric Schulte writes:
As I recall this was originally implemented and then later removed because
it was causing more confusion and problems than it was worth. I hope it
hasn't crossed the line of existence more than once. At some point it
should be placed behind a user-customiz
>>> As I recall this was originally implemented and then later removed because
>>> it was causing more confusion and problems than it was worth. I hope it
>>> hasn't crossed the line of existence more than once. At some point it
>>> should be placed behind a user-customizable variable, preferably s
> | tangle | -| + | - |
> |+--++|
> | need | +| + | - |
>
>>
>> What should the name for such an option be?
>>
>
> Andreas' suggestion, :noweb no-export, seems right to me.
>
Me too,
I've just pushed up a patch adding a "no
"Sebastien Vauban" writes:
> Hi Thomas, Eric(s) and all,
Hi Sebastien,
[...]
> I use HTML export more and more, and would be sad if the solution wasn't
> targeted at all to HTML as well.
I agree although this doesn't preclude target specific customisation
variables; it just means that each ta
Hi Thomas, Eric(s) and all,
Thomas S. Dye wrote:
> Eric Schulte writes:
>> t...@tsdye.com (Thomas S. Dye) writes:
>>> "Sebastien Vauban" writes:
Thomas S. Dye wrote:
>
> | tangle | -| + | - |
> |+--++|
> | need | +| + | -
Eric Schulte writes:
> t...@tsdye.com (Thomas S. Dye) writes:
[...]
>> Alternatively for LaTeX, some way to wrap exported code blocks in a
>> \begin{listing} ... \end{listing} environment, complete with caption and
>> label. This way the code block name could appear in the caption, and
>> with
Hi Eric,
Eric Schulte writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Hi Seb,
>>
>> "Sebastien Vauban" writes:
>>
>>> Hi Thomas,
>>>
>>> Thomas S. Dye wrote:
Is there a difference between :noweb tangle and :noweb no?
>>>
>>> Yes: ":noweb no" is the default, and must *not expand* anyt
t...@tsdye.com (Thomas S. Dye) writes:
> Hi Seb,
>
> "Sebastien Vauban" writes:
>
>> Hi Thomas,
>>
>> Thomas S. Dye wrote:
>>> Is there a difference between :noweb tangle and :noweb no?
>>
>> Yes: ":noweb no" is the default, and must *not expand* anything.
>>
>>> Based on the documentation and so
Hi Seb,
"Sebastien Vauban" writes:
> Hi Thomas,
>
> Thomas S. Dye wrote:
>> Is there a difference between :noweb tangle and :noweb no?
>
> Yes: ":noweb no" is the default, and must *not expand* anything.
>
>> Based on the documentation and some limited testing, I made the following
>> table.
>>
"Sebastien Vauban" writes:
[...]
> Some time after that, we had block names in the HTML/PDF output, but not
> anymore.
I've been wondering about this for some time. The appearance of source
code block names in exported latex output comes and goes in what appears
to me as a random process! Per
"Sebastien Vauban"
writes:
[...]
>> I think it might be good to have a parameter that expands noweb
>> references on evaluation and tangling, but leaves them alone during
>> export. This way the code block would be fully functional, but wouldn't
>> duplicate code during export (when the noweb r
Hi Eric,
Is there a difference between :noweb tangle and :noweb no? Based on the
documentation and some limited testing, I made the following table.
*** :noweb parameters
| param | eval | tangle | export |
|+--++|
| yes| +| + | + |
| no | -
15 matches
Mail list logo
