Sébastien Miquel writes:
> The uses are maybe too niche to warrant the breaking change. A syntax
> extension like
> : var=block-id[]
> seems possible, even though brackets are already overloaded.
This sounds better. Using brackets will actually make a lot of sense.
Currently, we have roughly
Hi,
Ihor Radchenko writes:
> Hmm. You are right. I missed "optionally".
>
> Still, I find this idea as the best solution for people who want to
> process the source block text during noweb expansion.
>
> Alternative ideas are welcome though. I'd prefer to avoid breaking
> change if we can find
Ihor,
> Alternative ideas are welcome though. I'd prefer to avoid breaking
> change if we can find an equally simple syntax alternative to assign
> source block code to a variable.
my two cents would be to avoid the breaking change. (i notice, for
example, that i use this construct in some of my
Greg Minshall writes:
>> The current behaviour of :var foo=name-of-src-block is assigning result
>> of evaluation. However, this behaviour is actually not documented.
>> 16.4 Environment of a Code Block section of the manual only documents
>> uses like
>
> in fact, the text of the info page (on m
Ihor,
> The current behaviour of :var foo=name-of-src-block is assigning result
> of evaluation. However, this behaviour is actually not documented.
> 16.4 Environment of a Code Block section of the manual only documents
> uses like
in fact, the text of the info page (on my system?) says
> code b
Sébastien Miquel writes:
> Ihor Radchenko writes:
>> Can you provide more concrete examples?
>>
>>> Some drawbacks:
>>> + doesn't work for all languages (does work for LaTeX)
>> Which languages do not work?
> Most languages do not work. Using your proposed solution, what I'm
> trying to do is
