Jean-Marc Lasgouttes wrote:
> Let's say we can go the sh route anyway, but keep in mind that the
> code should be only added in a few known place, so that we can rewrite
> it easily later.
Ok.
> But of course we do not really know what script languages we are going
> to choose...
Or we can let
Alfredo Braunstein wrote:
> Jean-Marc Lasgouttes wrote:
>
>> Let's say we can go the sh route anyway, but keep in mind that the
>> code should be only added in a few known place, so that we can
>> rewrite it easily later.
>
> Ok.
>
>> But of course we do not really know what script languages w
Angus wrote:
> On Tuesday 05 August 2003 8:38 am, Alfredo Braunstein wrote:
> > > 2. Rewrite the logic as a shell script and just use the forked call
> > > stuff.
> >
> > This is an option. But the LyX LaTeX code seems to be full of tricks and
> > hacks I don't understand, so it's completely out o
> "Alfredo" == Alfredo Braunstein <[EMAIL PROTECTED]> writes:
Alfredo> Jean-Marc Lasgouttes wrote:
>> Note that this means that all this file manipulation will reside in
>> sh scripts, which will really be unix-specific, and this is not a
>> good design IMO. Of course, we could use lua :)
Alf
Alfredo Braunstein wrote:
>
> Jean-Marc Lasgouttes wrote:
> > But of course we do not really know what script languages we are going
> > to choose...
TeXmacs and Siag use Guile/Scheme.
Garst
Jean-Marc Lasgouttes wrote:
> Alfredo Braunstein wrote:
>> Angus wrote:
>>>In order to achieve that we need a new member function to perform
>>>any necessary manipulation of the external material. To my mind, it
>>>makes sense here to write these instructions to an ostream also. We
>>>end up with
Jean-Marc Lasgouttes wrote:
> Note that this means that all this file manipulation will reside in sh
> scripts, which will really be unix-specific, and this is not a good
> design IMO. Of course, we could use lua :)
But what do we do now? I see, we could fill a list of "arguments to
forkedcall" i
Alfredo Braunstein wrote:
Angus wrote:
In order to achieve that we need a new member function to perform any
necessary manipulation of the external material. To my mind, it makes sense
here to write these instructions to an ostream also. We end up with two
separate ostreams, one containing instr
